dumb question:
is it possible for the grass 6.4.0 native grass installer for MS-Windows
to ship with both Tcl/Tk gis.m and the wxPython GUI?
.... i.e. give the user a choice & a backup plan ...
Hamish
This installer does ship with both. Although I thought there were
enough desktop icons already (with and without msys), in the start
menu there is an "Old GUI" option that will start a fully functional
tcltk with nviz. Or if you want to still use msys, just open the msys
desktop icon and change the argument from
"/grass/bin/grass64 -wxpython"
to
"/grass/bin/grass64 -tcltk"
Question for those who are testing: do you prefer the msys version
(with a functioning terminal) or the other one (which runs
grass64.bat)? Both is probably confusing, but I don't want to remove
the older grass64.bat option without consultation from those who
created it on their specific reasons for it.
-Colin
On Thu, Apr 9, 2009 at 4:21 AM, Hamish <hamish_b@yahoo.com> wrote:
dumb question:
is it possible for the grass 6.4.0 native grass installer for MS-Windows
to ship with both Tcl/Tk gis.m and the wxPython GUI?.... i.e. give the user a choice & a backup plan ...
Hamish
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
On Thu, 9 Apr 2009, Colin Nielsen wrote:
Question for those who are testing: do you prefer the msys version
(with a functioning terminal) or the other one (which runs
grass64.bat)? Both is probably confusing, but I don't want to remove
the older grass64.bat option without consultation from those who
created it on their specific reasons for it.
The reason for it is so GRASS can be started on Windows without having to install Msys. Msys is only needed for a few scripts - with GRASS 7 where all the scripts have been converted to Python there should be no need for Msys at all. Helena's argument about it being helpful to have a mini-Unix environment with familiar Unix commands is very valid though. But for testing/development purposes I think it's best to leave the Msys commands out of the PATH as having them installed can hide Unix-isms in GRASS - there was quite a bit of work went into removing these a couple of years ago and making GRASS truly native on Windows without the need for Msys.
Hope that clarifies things a bit?
Paul
just a note that the msys version is used a lot in my class although I haven't
really included it into assignments - I just let the students know that it exists and what
they can do with and it quickly gets used a lot for automating workflows.
And it has the advantage of introducing people to linux.
I don't have a problem at all with having both versions and two icons - it was clearly explained
on Marco's web page and did not cause too much confusion.
Helena
On Apr 9, 2009, at 9:17 AM, Paul Kelly wrote:
On Thu, 9 Apr 2009, Colin Nielsen wrote:
Question for those who are testing: do you prefer the msys version
(with a functioning terminal) or the other one (which runs
grass64.bat)? Both is probably confusing, but I don't want to remove
the older grass64.bat option without consultation from those who
created it on their specific reasons for it.The reason for it is so GRASS can be started on Windows without having to install Msys. Msys is only needed for a few scripts - with GRASS 7 where all the scripts have been converted to Python there should be no need for Msys at all. Helena's argument about it being helpful to have a mini-Unix environment with familiar Unix commands is very valid though. But for testing/development purposes I think it's best to leave the Msys commands out of the PATH as having them installed can hide Unix-isms in GRASS - there was quite a bit of work went into removing these a couple of years ago and making GRASS truly native on Windows without the need for Msys.
Hope that clarifies things a bit?Paul
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Yes that does clarify things and I figured there probably had been a
good reason for converting to a .bat file.
So given that lots of people like msys for various reasons, but that
we should make sure that is not required, is there a consensus as to
how should I set up the installer in terms of desktop and start menu
icons?
(As a side note when trying to use the GUI menu to switch the default
GUI I get the following error:
Traceback (most recent call last):
File "c:/GIS/GRASS-6-SVN/etc/wxpython/wxgui.py", line 515,
in OnMenuCmd
menuform.GUI().ParseCommand(cmd, parentframe=self)
File
"c:\GIS\GRASS-6-SVN\etc\wxpython\gui_modules\menuform.py",
line 1716, in ParseCommand
xml.sax.parseString( getInterfaceDescription(cmd[0]),
handler )
File
"c:\GIS\GRASS-6-SVN\etc\wxpython\gui_modules\menuform.py",
line 1657, in getInterfaceDescription
raise IOError, _("Unable to fetch interface description for
command '%s'.") % cmd
IOError
:
Unable to fetch interface description for command
'g.change.gui.py'.
)
-Colin
On Thu, Apr 9, 2009 at 9:17 AM, Paul Kelly
<paul-grass@stjohnspoint.co.uk> wrote:
On Thu, 9 Apr 2009, Colin Nielsen wrote:
Question for those who are testing: do you prefer the msys version
(with a functioning terminal) or the other one (which runs
grass64.bat)? Both is probably confusing, but I don't want to remove
the older grass64.bat option without consultation from those who
created it on their specific reasons for it.The reason for it is so GRASS can be started on Windows without having to
install Msys. Msys is only needed for a few scripts - with GRASS 7 where all
the scripts have been converted to Python there should be no need for Msys
at all. Helena's argument about it being helpful to have a mini-Unix
environment with familiar Unix commands is very valid though. But for
testing/development purposes I think it's best to leave the Msys commands
out of the PATH as having them installed can hide Unix-isms in GRASS - there
was quite a bit of work went into removing these a couple of years ago and
making GRASS truly native on Windows without the need for Msys.
Hope that clarifies things a bit?Paul