[GRASS-dev] Re: GRASS-dev] Re: Shell scripts

[Michael Barton]

There is not really anything to show in a screenshot. It's the same  
output window we now have in the wxPython GUI. The only difference is  
that you would be able to type into it as well as have output shown in  
it. I've attached a diff you can use to modify gouput.py in GRASS 6.5  
and see what I'm talking about.

IPython seems nice but is not appropriate in this context. IPython is  
a Python shell. We don't need that. We need a GRASS and general  
purpose shell.


Michael


-------------- next part --------------
A non-text attachment was scrubbed...
Name: console_example.diff
Type: application/octet-stream
Size: 2467 bytes
Desc: not available
Url : http://lists.osgeo.org/pipermail/grass-dev/attachments/20091206/bf8e7977/console_example.obj
-------------- next part --------------




On Dec 6, 2009, at 9:27 PM, grass-dev-request at lists.osgeo.org wrote:

> ate: Sun, 06 Dec 2009 23:51:17 +0100
> From: Tim Michelsen <timmichelsen at gmx-topmail.de>
> Subject: [GRASS-dev] Re: GRASS-dev] Re: Shell scripts
> To: grass-dev at lists.osgeo.org
> Message-ID: <hfhch5$q2m$1 at ger.gmane.org>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Michael Barton schrieb:
>> 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.
> could you please show a example screenshot?
>
> The advatage of IPython is that it is scriptable.
>
> some examples:
> http://www.mail-archive.com/python-list@python.org/msg171278.html
> http://old.nabble.com/Embedding-Basemap-in-a-wx-app-td20588673.html
> http://old.nabble.com/Embedding-IPython-in-wx- 
> tc16868791.html#a16877948
>