[GRASS-dev] Re: [GRASS GIS] #570: startup problem with standalone GRASS install

[Glynn Clements]

Moritz Lennert wrote:

> >  When GRASS is started from the menu shortcut, there is still an empty dos
> >  CLI in the background.
> 
> AFAIK, this DOS CLI is necessary for the functioning of GRASS, notably 
> running the temp file cleaning operations at the end. So, until we have 
> reengineered the Windows startup logic, I don't think we can get rid of it.

If enough users are likely to want to use the wxPython GUI as the main
interface, I'd consider adding a Python-based startup as an
alternative to grassXX[.bat] and Init.{sh,bat}.

This should be invoked via pythonw on Windows, and should redirect
std{out,err} to files. Also, if GISBASE isn't already defined, set it
from a registry key.

A command-line-only interface is of relatively little use on Windows,
due to the absence of monitors.

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