From the testing I've been doing, it looks like we can easily collapse the command entry functions into the StyledTextCtrl output window and do away with the separate command entry area. This tab completion of commands could be run through the STC tootip interface or possibly the autocomplete interface. I've mostly worked out how to get a listing of maps to insert using the STC autocompletion interface.

This makes for a simpler, cleaner, and potentially more functional CLI interface for the GUI. It seems like a good idea to head in that direction. What do you think?

Michael

On Dec 6, 2009, at 1:08 PM, [email protected] wrote:

Date: Sun, 6 Dec 2009 21:08:34 +0100
From: Martin Landa <[email protected]>
Subject: Re: [GRASS-dev] Re: Shell scripts
To: Tim Michelsen <[email protected]>
Cc: [email protected]
Message-ID:
       <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1

2009/12/6 Tim Michelsen <[email protected]>:
The p.* scripts are semi-functional and should be rewritten to Python. Not having d.mon/d.rast/d.vect/d.zoom commands is for me, Helena, others
the obstacle to not use GRASS 7 as primary version.
Since the needed (wx)GUI pieces are there, I still hope that someone skilled is rewriting it in Python. For us it is essential to continue with command line
in GRASS 7.
What about adding a IPython-like interactive console?
IPython has history, tab-completion and is emeddable.

btw, tab-completation for GRASS commands is partly implemented in 6.5+
(see gui/wxpython/gui_modules/prompt.py).

Martin

_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev

Reply via email to