[GRASS-dev] Re: [GRASS GIS] #580: WinGRASS: $GISBASE/etc/gui/scripts/ require something like $(EXE) to run

[GRASS GIS]

#580: WinGRASS: $GISBASE/etc/gui/scripts/ require something like $(EXE) to run
---------------------------+------------------------------------------------
  Reporter:  hamish        |       Owner:  grass-dev at lists.osgeo.org
      Type:  defect        |      Status:  new                      
  Priority:  blocker       |   Milestone:  6.4.0                    
 Component:  wxGUI         |     Version:  6.4.0 RCs                
Resolution:                |    Keywords:  wingrass                 
  Platform:  MSWindows XP  |         Cpu:  Unspecified              
---------------------------+------------------------------------------------
Comment (by cmbarton):

 Replying to [comment:19 hamish]:
 > > Replying to [comment:15 cmbarton]:
 > > > Why can't windows use g.gui gui=[guiplatform] -nu?
 >
 > Replying to [comment:16 cnielsen]:
 > > This command does work in the msys command prompt (native
 > > installer r40049), with this followed by g.gui &, you can
 > > switch back and forth with no problem.
 >
 >  * this is hardly as user friendly as a GUI which asks: "use Wx", "use
 Tcl", or "use text" & restart. these wrapper scripts are not designed for
 power users who are comfortable with the command line.
 >  * the default osgeo4w build does not give the user a msys prompt,
 although I guess you could try the Cmd> prompt if you knew the exact magic
 incantation.[[BR]]
 [[BR]]
 I agree. Given that this is aimed at users who are not so command-
 sophisticated and certainly using the GUI menus, maybe this is better done
 by a small, quick method inside the GUI code. It should work for all
 platforms that way.[[BR]]
 [[BR]]

 >  * v.type from a GUI is impossible and needs a wrapper.[[BR]]
 [[BR]]
 Yes. This needs a script. Or v.type needs to be rewritten a little so that
 it parses intelligently.[[BR]]
 [[BR]]
 >
 >
 > > > There is a problem running python scripts in GRASS for Windows.
 >
 > it's just a bug, and not a fundamental problem. mere details can and
 will be fixed.
 >
 > > > A regular Python installation will properly put Python in
 > > > the registry so that it can be called to execute scripts.
 >
 > we ''should'' have the equivalent already set up in the msinstaller
 > startup batch files and scripts to associate .py with a suitable
 python.exe.  check this bug's previous comments & grep the msinstaller
 scripts for more.  but that isn't working for some reason.[[BR]]
 [[BR]]
 IIRC, Glynn said that it is necessary to alter the Windows registry for it
 to work. That is why doing a regular Python installation is preferable.
 Currently, no Python script works.[[BR]]
 [[BR]]
 Michael
 >
 >
 > Hamish

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/580#comment:24>
GRASS GIS <http://grass.osgeo.org>