[GRASS-dev] Current state of GUIs on Win32

[Michael Barton]

Benjamin,

A couple of responses. See below

Michael

On Mar 7, 2008, at 10:00 AM, grass-dev-request at lists.osgeo.org wrote:

> Date: Fri, 07 Mar 2008 16:13:03 +0000
> From: Benjamin Ducke <benjamin.ducke at ufg.uni-kiel.de>
> Subject: [GRASS-dev] Current state of GUIs on Win32
> To: GRASS devel <grass-dev at grass.itc.it>
> Message-ID: <47D1698F.6040109 at ufg.uni-kiel.de>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi all,
>
> (not sure, but my last email seems to have disappeared somehow,
> so here goes another try).
>
> I have been trying the current versions of the GUIs (Tcl/Tk and
> WxWidgets) using GRASS 6.3.rc5 on Win32 (MinGW/MSYS Build).
>
> They all have a number of issues that make them less than a
> pleasant experience for Windows users right now:
>
> 1. Tcl/Tk
>
> Version 8.5.1 (GPL) works fine, NVIZ starts up, can visualize 3D DEM.
> Hangs when trying to add a vector points map.
> Tk 8.5.1 has new widgets that are closer to the Win native ones.
> NVIZ uses those, but the module forms and gis.m don't, resulting in
> a strange look and feel.

The current GUI is based on TclTk 8.4.14 or so. As some people have  
noted, it may work with 8.5, but there is no guarantee about it. Given  
that we are replacing this GUI, I don't think it is worth the effort  
to update the GUI to 8.5.

>
>
> 2. WxPython
>
> I installed Python 2.5 and WxPython 2.8. I found that I also had to
> install the Python Extensions for Windows from here:
>
> 	http://sourceforge.net/project/showfiles.php?group_id=78018
>
> Doing grass63 -wxpython then gave me:

AFAIK, the error reported below was fixed in the svn trunk a week or  
so back. I saw a note from Martin to that effect. Please let us know  
if that is not the case.

Michael

>
>
>
> Starting GRASS ...
> Traceback (most recent call last):
>   File "C:/msys/1.0/local/grass-6.3.0RC5/etc/wxpython/gis_set.py",  
> line
> 690, in <module>
>     GRASSStartUp = StartUp(0)
>   File
> "C:\msys\1.0\local\python\Lib\site-packages\wx-2.8-msw-unicode\wx 
> \_core.py",
> line 7836, in __init__
>     self._BootstrapApp()
>   File
> "C:\msys\1.0\local\python\Lib\site-packages\wx-2.8-msw-unicode\wx 
> \_core.py",
> line 7433, in _BootstrapApp
>     return _core_.PyApp__BootstrapApp(*args, **kwargs)
>   File "C:/msys/1.0/local/grass-6.3.0RC5/etc/wxpython/gis_set.py",  
> line
> 674, in OnInit
>     StartUp = GRASSStartup()
>   File "C:/msys/1.0/local/grass-6.3.0RC5/etc/wxpython/gis_set.py",  
> line
> 45, in __init__
>     self.grassrc  = self._read_grassrc()
>   File "C:/msys/1.0/local/grass-6.3.0RC5/etc/wxpython/gis_set.py",  
> line
> 356, in _read_grassrc
>     key, val = line.split(":")
> ValueError: too many values to unpack
> Error in GUI startup. If necessary, please
> report this error to the GRASS developers.
> Switching to text mode now.
> Hit RETURN to continue...
>
>
> According to some Python forums:
>
> The "too many values to unpack" indicates you don't have enough
> variables in the [for (...) in <var>: ] construct.
>
> ... so is the WxPython GUI broken in RC5?
>
> Anybody had better luck with WxPython on Win yet?
>
> Cheers,
>
> Benjamin
>
>
> -- 
> Benjamin Ducke
> Senior Applications Support and Development Officer
>
> Oxford Archaeological Unit Limited
> Janus House
> Osney Mead
> OX2 0ES
> Oxford, U.K.
>
> Tel.: ++44 (0)1865 263 800
> benjamin.ducke at oxfordarch.co.uk
>
>