We’ve been calling the wxPython interface to GRASS ‘wxgrass’ for the past 6 months or so. This is an informal reference and simply the name of the BASH script used to start the GUI. We came up with this to do something different from the current GUI init script “gis.m”.
However, before we begin distributing this GUI with GRASS, I think we should change the name of the script and how we reference this GUI. This past spring, it came to my attention that Francisco Alonso, Universidad de Murcia, has developed an application with a wxPython interface that incorporates GRASS commands. He calls this wxGRASS. It has been presented at a GIS conference in Spain and it’s web site is here: http://www.um.es/geograf/sigmur/wxgrass/wxGRASS.html.
It is a nice application with some good interface ideas. I and others have been in contact with Francisco and exchanged information about our wxPython interfaces. If time permits, he may even help with some of the GUI coding eventually.
Since he has used the term wxGRASS first, I think we should use another name our our GUI init script and informal reference to the wxPython interface for GRASS so as not to cause confusion. I’m open to suggestions.
Here are some initial ideas I’ve had: wxpg, wxpgrass, grasswx, grassgui (this could be the generic calling script for whatever is the current GRASS GUI), wxgui, wxpgui.
Michael
Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University
We've been calling the wxPython interface to GRASS 'wxgrass' for the
....
Here are some initial ideas I've had: wxpg, wxpgrass, grasswx, grassgui
(this could be the generic calling script for whatever is the current
GRASS GUI), wxgui, wxpgui.
I think it is the GRASS GUI, and should be called that. Who cares whet
programming language it was made in or what toolkit it uses. The TCL GUI
could be called old GUI when we switch. Until that time talking about
the new GUI and the old GUI should be pretty clear to everybody.
We've been calling the wxPython interface to GRASS 'wxgrass' for the past 6 months or so. This is an informal reference and simply the name of the BASH script used to start the GUI. We came up with this to do something different from the current GUI init script "gis.m".
However, before we begin distributing this GUI with GRASS, I think we should change the name of the script and how we reference this GUI. This past spring, it came to my attention that Francisco Alonso, Universidad de Murcia, has developed an application with a wxPython interface that incorporates GRASS commands. He calls this wxGRASS. It has been presented at a GIS conference in Spain and it's web site is here: <http://www.um.es/geograf/sigmur/wxgrass/wxGRASS.html>\.
It is a nice application with some good interface ideas. I and others have been in contact with Francisco and exchanged information about our wxPython interfaces. If time permits, he may even help with some of the GUI coding eventually.
Since he has used the term wxGRASS first, I think we should use another name our our GUI init script and informal reference to the wxPython interface for GRASS so as not to cause confusion. I'm open to suggestions.
Here are some initial ideas I've had: wxpg, wxpgrass, grasswx, grassgui (this could be the generic calling script for whatever is the current GRASS GUI), wxgui, wxpgui.
Michael
Hello,
I'm more or less only a temporal grass user, but I would also prefer Grass Gui or when this is too long g.gui .
Michael Barton schrieb:
>Here are some initial ideas I've had: wxpg, wxpgrass, grasswx, grassgui
>(this could be the generic calling script for whatever is the current
>GRASS GUI), wxgui, wxpgui.
+1 for the generic grassgui script. I think, it can´t get more precise.
wxpg and the like sound to me like w-x-postgres...
If, for whatever reason, there were _several_ guis, grassgui could start
either of these by a switch:
grassgui --wx (default)
grassgui --tcl
grassgui --qt
...
0.02 cent of a long-time lurker,
\flo
--
Mag. Florian Kindl
Institute of Geography
University of Innsbruck
We've been calling the wxPython interface to GRASS 'wxgrass' for the past 6
months or so.
and it's pretty good. Also consider the 'pygrass' combinations.
The g.gui suggestion is nice too. Simple and to the point.
2c,
Hamish
____________________________________________________________________________________
Choose the right car based on your needs. Check out Yahoo! Autos new Car Finder tool. http://autos.yahoo.com/carfinder/