[GRASSLIST:868] Re: [GRASS5] New GRASS intro
Michael Barton
michael.barton at asu.edu
Tue Apr 25 16:36:30 EDT 2006
I could probably make them update automatically every time anything is
changed in the layer tree. I thought about doing so and discussed this a bit
with some of the folks contributing to the GUI discussions. The general
feeling was that it would be better to let the user decide when to update
the monitor. This allows you to change multiple aspects of a set of
overlaying maps and not have to wait through a screen redraw for each
change...the way it is in some commercial packages.
Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics and Complexity
Arizona State University
phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton
> From: Jachym Cepicky <jachym.cepicky at centrum.cz>
> Date: Tue, 25 Apr 2006 22:29:27 +0200
> To: Michael Barton <michael.barton at asu.edu>
> Cc: grass developers list <grass5 at grass.itc.it>, Multiple recipients of list
> <GRASSLIST at baylor.edu>
> Subject: Re: [GRASS5] New GRASS intro
>
> Hallo developers,
>
> personaly I do not use the new gui, because I can not use d.* commands
> (d.rast and d.vect). I thing, that the new monitors do have the right
> functions (zooming, panning, redrawing, ...), but it is often faster to
> write, what map one would like to see, then to click it in the gui.
>
> Would it be possible to make run this monitors in background as daemons, so
> they
> would "observe" the png files (png1-png7) and redraw them selve every
> time, the files would be changed?
>
> Jachym
>
> On Tue, Apr 25, 2006 at 12:49:19PM -0700, Michael Barton wrote:
>> With the move toward releasing GRASS 6.2, it?s time we had a new intro to
>> greet users starting GRASS.
>>
>> I?d hoped to make something really spiffy, easy for first time users to
>> navigate without getting confused about GRASS jargon, but still quick for
>> experienced users. Alas, I haven?t had the time to do all this before the
>> impending 6.2 feature freeze, but I did manage to update things somewhat
>> from the venerable, Spartan grey intro.
>>
>> I?ve rearranged the items on the intro screen to distinguish different
>> functions, changed the descriptions to make it clearer that locations are
>> for projections and mapsets are where a ?GIS? is stored, etc. I also added a
>> new button to create a projection location from a georeferenced file (uses
>> GDAL/OGR via g.proj). Finally, I added some color to the intro. No I didn?t
>> make it green, but I did add a nice GRASS graphic.
>>
>> Many thanks to Markus who helped me get this committed to the cvs, where it
>> now resides for your geospatial enjoyment.
>>
>> I think the next step would be to replace the g.setproj terminal screen for
>> defining projections with a nicer GUI one based on g.proj. Another thing
>> would be to add a search function to the excellent EPSG codes database.
>>
>> Cheers,
>> Michael
>> __________________________________________
>> Michael Barton, Professor of Anthropology
>> School of Human Evolution & Social Change
>> Center for Social Dynamics and Complexity
>> Arizona State University
>>
>> phone: 480-965-6213
>> fax: 480-965-7671
>> www: http://www.public.asu.edu/~cmbarton
>>
>
> --
> Jachym Cepicky
> e-mail: jachym.cepicky at centrum.cz
> URL: http://les-ejk.cz
> GPG: http://les-ejk.cz/gnupg_public_key/jachym_cepicky-gpg_public_key.asc
> -----------------------------------------
> OFFICE:
> GDF-Hannover
> Mengendamm 16d
> 30177 Hannover
> Germany
> e-mail: cepicky at gdf-hannover.de
> URL: http://gdf-hannover.de
> Tel.: +49 511-39088507
More information about the grass-user
mailing list