I lost track of the status of the wxPython gui in winGrass in all the emails of the past two weeks. Does the latest winGrass snapshot include it?
Jerry
Gerald Nelson
Professor, Dept. of Agricultural and Consumer Economics
University of Illinois, Urbana-Champaign
office: 217-333-6465
cell: 217-390-7888
315 Mumford Hall
1301 W. Gregory
Urbana, IL 61801
On Jan 27, 2008 4:15 PM, Gerald Nelson <gnelson@uiuc.edu> wrote:
I lost track of the status of the wxPython gui in winGrass in all the emails of the past two weeks. Does the latest winGrass snapshot include it?
Gerald,
it doesn't. The reason is that the RC branch does not include it
since it was branched off sime time ago (and the backporting
effort is too much).
AFAIK you could just copy over the wxPython gui from "trunk"
gui/wxpython/
and run it on MS-Windows since it does not contain pre-compiled
code.
Markus
On 27/01/08 16:28, Markus Neteler wrote:
AFAIK you could just copy over the wxPython gui from "trunk" gui/wxpython/ and run it on MS-Windows since it does not contain
pre-compiled code.
The last time I tried, there were issues with some python commands used being *nix specific and thus not working in windows. Haven't tried recently, though.
Moritz
Here's the process I went through
- downloaded the wx gui code from trunk
- placed it in the etc directory (not the gui directory)
- moved the script to the right place
- added python25 to the msys path. It's not there by default
- started grass63 from inside msys
- the tcltk gui starts
- from msys command line type wxgrass
- get the following error
Traceback (most recent call last):
File "c:/grass63RC4/grass-6.3.0RC4/etc/wx/wxgui.py", line 53, in <module>
import gui_modules.utils as utils
File "c:\grass63RC4\grass-6.3.0RC4\etc\wx\gui_modules\utils.py", line 23,
in <module>
import gcmd
File "c:\grass63RC4\grass-6.3.0RC4\etc\wx\gui_modules\gcmd.py", line 35,
in <module>
from win32file import ReadFile, WriteFile
ImportError: No module named win32file
Where should this be?
Jerry
-----Original Message-----
From: neteler.osgeo@gmail.com [mailto:neteler.osgeo@gmail.com] On Behalf Of
Markus Neteler
Sent: Sunday, January 27, 2008 9:29 AM
To: Gerald Nelson
Cc: GRASS developers list
Subject: Re: [GRASS-dev] wxPython gui and winGrass
On Jan 27, 2008 4:15 PM, Gerald Nelson <gnelson@uiuc.edu> wrote:
I lost track of the status of the wxPython gui in winGrass in all the
emails of the past two weeks. Does the latest winGrass snapshot include it?
Gerald,
it doesn't. The reason is that the RC branch does not include it
since it was branched off sime time ago (and the backporting
effort is too much).
AFAIK you could just copy over the wxPython gui from "trunk"
gui/wxpython/
and run it on MS-Windows since it does not contain pre-compiled
code.
Markus
On Jan 28, 2008 11:43 PM, Gerald Nelson <gnelson@uiuc.edu> wrote:
Here's the process I went through
- downloaded the wx gui code from trunk
- placed it in the etc directory (not the gui directory)
- moved the script to the right place
- added python25 to the msys path. It's not there by default
- started grass63 from inside msys
- the tcltk gui starts
- from msys command line type wxgrass
- get the following errorTraceback (most recent call last):
File "c:/grass63RC4/grass-6.3.0RC4/etc/wx/wxgui.py", line 53, in <module>
import gui_modules.utils as utils
File "c:\grass63RC4\grass-6.3.0RC4\etc\wx\gui_modules\utils.py", line 23,
in <module>
import gcmd
File "c:\grass63RC4\grass-6.3.0RC4\etc\wx\gui_modules\gcmd.py", line 35,
in <module>
from win32file import ReadFile, WriteFile
ImportError: No module named win32fileWhere should this be?
Could it be that you need to install this:
http://sourceforge.net/projects/pywin32/
?
Markus