[GRASSGUI] standalone module use

[Glynn Clements]

Jachym Cepicky wrote:

> >  Having the module output show up IN the module notebook seems like a good
> > idea. But IMHO, if we go that way, then the output from a module dialog
> > should go there ALL the time. In that case, the only reason to have the
> > command output window in the GIS Manager is for shell commands and GRASS
> > commands run from the command line only (i.e., not from an autogenerated
> > dialog). In that case, we might as well get rid of the small command line
> > and turn the GIS Manager output window into a full Python terminal. This
> > would then be available on all platforms, obviating the need for a terminal
> > for GRASS. It will work the same and have access to the same abilities in
> > all platforms, regardless of whether they normally have a terminal window or
> > not.
> 
> Currently, I doubt, there is a way, how to build full featured
> terminal using python. However, if this would be possible, I would
> vote for it.

That depends upon what you mean by "full-featured".

I don't see any reason for wxgrass to try to provide a character-cell
terminal for curses-based programs. Even pty support is problematic
(not available on Windows, AFAICT).

-- 
Glynn Clements <glynn at gclements.plus.com>