Hi all,
within the WinGRASS installer (6.3.0-4, to be released) I created a new StartMenu item: GRASS Command Line
here’s a screenshot of the new GRASS start menu: http://www.webalice.it/marco.pasetti/temp/New-WinGRASS-StartMenu.png
it’s a link to the batch file grass63-cmd.bat, that’s simply as follows:
@echo off
grass63 -text
the problem is: when I launch GRASS in text mode (with -text), then the .grassrc6 file has “text” as default “launch mode”; that means that launching the “classic” grass63.bat link will result in launching GRASS in text mode again… and I fear that the standard windows user won’t know how to launch grass with the tcltk GUI, or if he knows, it will be disappointed to need to hack the .grassrc6 file to let the GUI work again;
I figured the following “walk around”: create a new simple batch file: grass63-gui.bat:
@echo off
grass63 -tcltk
and replace the grass63.bat link in the menu with a link pointing to grass63-gui.bat.
Do you think that there are better solutions?
Many thanks,
Marco
Marco Pasetti wrote:
within the WinGRASS installer (6.3.0-4, to be released) I created a new
StartMenu item: GRASS Command Line
here's a screenshot of the new GRASS start menu:
http://www.webalice.it/marco.pasetti/temp/New-WinGRASS-StartMenu.png
it's a link to the batch file grass63-cmd.bat, that's simply as follows:
@echo off
grass63 -text
the problem is: when I launch GRASS in text mode (with -text), then the
.grassrc6 file has "text" as default "launch mode"; that means that
launching the "classic" grass63.bat link will result in launching GRASS
in text mode again... and I fear that the standard windows user won't
know how to launch grass with the tcltk GUI, or if he knows, it will be
disappointed to need to hack the .grassrc6 file to let the GUI work
again;
I figured the following "walk around": create a new simple batch file:
grass63-gui.bat:
@echo off
grass63 -tcltk
and replace the grass63.bat link in the menu with a link pointing to
grass63-gui.bat.
Do you think that there are better solutions?
I don't see a problem with explicitly passing the -text and -tcltk
switches whenever you start GRASS. The default will then only matter
if the user starts GRASS manually from a console.
Also, I'm not sure there's any point to having the batch files. You
can just include the -text or -tcltk switch in the shortcut's command.
--
Glynn Clements <glynn@gclements.plus.com>
Hi Glynn,
I don't see a problem with explicitly passing the -text and -tcltk
switches whenever you start GRASS. The default will then only matter
if the user starts GRASS manually from a console.
Also, I'm not sure there's any point to having the batch files. You
can just include the -text or -tcltk switch in the shortcut's command.
yes, you're right. I'll include the -text/-tcltk into the shortcut's command.
Thanks
Marco
Glynn:
I don't see a problem with explicitly passing the
-text and -tcltk switches whenever you start GRASS.
The default will then only matter if the user starts GRASS
manually from a console.
note that using those switches at all will reset the default.
Hamish
Dear Robert,
How to run WinGRASS with non-english interface?
I tried different methods without success.
http://www.nabble.com/-GRASS5--Re%3A--GRASSLIST%3A5600--How-to-start-GRASS-in-another-language--p8590987.html
sincerely,
--
Robert Szczepanek
I'm not sure about it, but I suppose that the locale var settings need GRASS built with NLS support... that is currently unsupported in MS-Windows.
NLS support in WinGRASS is already into the to-do list.
I Cc'ed the message to the dev-list for a confirmation.
Regards,
Marco
On Tue, 19 Aug 2008, Marco Pasetti wrote:
Dear Robert,
How to run WinGRASS with non-english interface?
I tried different methods without success.
http://www.nabble.com/-GRASS5--Re%3A--GRASSLIST%3A5600--How-to-start-GRASS-in-another-language--p8590987.html
sincerely,
--
Robert Szczepanek
I'm not sure about it, but I suppose that the locale var settings need GRASS built with NLS support... that is currently unsupported in MS-Windows.
Do you mean without installing extra software? Using the NLS packages on GnuWin32 it works fine and I had it working successfully on my local machine 8 months ago. It didn't require any modifications to the GRASS source. As far as I remember all that was required was to set the LANG environment variable (right-click on My Computer, Properties, Advanced, Environment Variables), e.g. setting LANG to "de" gave messages in German.
Paul
