[GRASS-windows] winGRASS 6.4.0RC2-2 now with wxpython (OSGeo4W installer)

[Luigi Ponti]

Dear Markus,

On 24/01/2009 1.24, Markus Neteler wrote:
> Thanks to Jürgen E. Fischer from norbit/QGIS team the
> GRASS version in the OSGeo4W installer was improved to
> now start the new wxpython based graphical user interface [1].
>
> The new version in OSGeo4W is grass-6.4.0RC2-2.
>
> This is the first time that the new wxpython based GUI becomes
> widely available.
>
> Download:
>  http://download.osgeo.org/osgeo4w/osgeo4w-setup.exe
>
> GRASS is in the "advanced" section.
>
> Please test and report.
>
> Markus
>
> [1] Screenshots:
>  http://grass.osgeo.org/screenshots/gui.php#wxpython
> _______________________________________________
> grass-windows mailing list
> grass-windows at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-windows
>
>   
Using XP sp3:

1) No problem with the OSGeo4W installer for a CygWin user like me: many 
thanks to packagers! It has lots of useful stuff in the same bundle and 
you can choose which one to download. I hadn't tried it before and it is 
really luxury for Windows users.

2) Maybe the tcltk and/or python installation(s) should be selected by 
default when one chooses to install grass.

3) Tried out the wxpython gui and it started out no problem. However, 
there is no way to add a map layer -- no maps to select. In the 
GRASS/DOS command prompt, I noticed the infamous message "g.mlist is not 
recognised as an internal or external command, an executable program or 
a batch file", then I looked into the grass-6.4.0RC2\bin folder to find 
out that there is no executable called g.mlist.exe -- only g.list.exe. I 
recall g.mlist being a script in 6.3 but here there is neither a 
g.mlist.bat script in the bin folder nor a g.mlist bash script in the 
scripts folder.

4) I did not go much farther but: when you call a command (e.g. 
g.region) from the gui Cmd > input box with no argument, you get the 
usual module gui interface; but when you call the same command with a 
flag (e.g. -e) no output is printed to the Command output box.

Regards,

Luigi