I want to point out that ‘assisted scripting’ and command line learning is already available in the current (new and still not quite finished) GIS Manager. The command console records all commands run by the GUI and keeps a running history of commands and their output. By clicking on any command in the history window, it is put into the command console at the bottom where you can modify it and run it. Type ‘til your heart’s content. You can also cut and paste individual commands into a script if you want to build one. I realize that GRASS and its interface is changing rapidly, sometimes on a weekly basis. But we are trying to maintain (and improve) a robust command line while making a much more usable GUI.
Michael
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University
phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton
From: grass-dev-request@grass.itc.it
Reply-To: grass-dev@grass.itc.it
Date: Fri, 9 Jun 2006 06:25:01 +0200
To: grass-dev@grass.itc.it
Subject: grass-dev Digest, Vol 2, Issue 20
From: Yann Chemin ychemin@gmail.com
Date: Fri, 9 Jun 2006 11:24:55 +0700
To: grass-dev@grass.itc.it
Subject: Re: [GRASS-dev] Python GUI toolkits
Each time we finish a GRASS GIS lab session (3-4 hours), i run the script of the whole lab in 1-2 minutes in front of the students, you should see their reaction!
Such “assisted” scripting capability would be a serious advantage for fastening the learning curve to advanced level processing. Aggreed, not all processing can be done scripting-side, but surely a lot can be done. Besides, GRASS GIS is changing fast, having a way to list & pick-up commands can really help out here.