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

Sun, 06 Dec 2009 20:41:06 -0800

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





Attachment:
console_example.diff

Description: Binary data






On Dec 6, 2009, at 9:27 PM, [email protected] wrote:


ate: Sun, 06 Dec 2009 23:51:17 +0100
From: Tim Michelsen <[email protected]>
Subject: [GRASS-dev] Re: GRASS-dev] Re: Shell scripts
To: [email protected]
Message-ID: <[email protected]>
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/[email protected]/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





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





















					Reply via email to