I've been meaning to ask about wxgrass and CLI stuff - you're obviously working on a GUI psuedo-terminal for running commands the old-fashioned CLI way. I take it there is/will be no need for something like 'grass-xterm-wrapper', and any place that the TclTk GUI used that this pseudo terminal will work in wxgrass?

PS. did you ever get a chance to try my Terminal-enabled version of grass-xterm-wrapper? I've been lazy in committing it, so you'd have to dig it out of the email, or maybe I should just commit it anyways. It's in my binaries and I haven't heard of any problems yet...

On Jun 6, 2007, at 3:12 PM, Michael Barton wrote:

I got the CLI for wxgrass working again. You can type in any command (GRASS or shell).

Non-GRASS commands will simply be passed to the shell.

GRASS commands without arguments (e.g. g.region) will open their properties dialogs for non-display commands. d.* commands without arguments will add a layer to the GUI layer tree and open their respective properties dialog (e.g., d.rast).

GRASS commands with arguments (e.g., g.region rast=elevation.10m) will be passed to the GRASS command shell for processing. d.* commands with arguments (e.g., d.rast elevation.10m) will display their results in the currently selected map display. Multiple display commands separated by commas will send overlaying graphic results to the current map display (e.g., d.rast elevation. 10m,d.vect roads color=red).

Michael


-----
William Kyngesburye <kyngchaos*at*kyngchaos*dot*com>
http://www.kyngchaos.com/

"History is an illusion caused by the passage of time, and time is an illusion caused by the passage of history."

- Hitchhiker's Guide to the Galaxy


_______________________________________________
grass-dev mailing list
[email protected]
http://grass.itc.it/mailman/listinfo/grass-dev

Reply via email to