Hi, 2008/2/9, Martin Landa <[EMAIL PROTECTED]>: > > > I remember there was discussion about renaming wxgrass [1]. Before > > > wxgui will be used by users, I would like to raise this question > > > again. > > ... > > > [1] > > > http://lists.osgeo.org/pipermail/grass-dev/2007-August/032604.html > > > > the whole thread, more ideas: > > http://thread.gmane.org/gmane.comp.gis.grass.devel/21880 > > > > > > > I think we should rename wxgrass script to wxgui > > > > +1, although it is a bit generic? > > eg possible namespace collision with python-gnuradio. [apt-file search] > > (that seems just to be a directory name, but ...) > > I guess as long as it's an internal grass module and not in /usr/bin > > it's ok? > > hm, wxgui is maybe too much generic name. When we have g.gui, we don't > need to copy wxgrass/wxgui script to $GISBASE/scripts. $GISBASE/etc/wx > (or better $GISBASE/etc/wxpython) would be sufficient place . The > wxgui will be started via g.gui type=wxpython. > > > > and create module like g.gui or whatever (?) > > > > +0 for the name. Sounds ok. > > > > I suppose g.gui will be a script, and it should use the normal parser > > unless there is some big reason not to. So --tcltk option would become > > g.gui gui=[wxpy|tcltk|oldtcltk] > > or whatever names you like, with the default set to ... > > > > IIUC d.m and gis.m will be dropped for GRASS 7. I think it is ok to > > +1 > > > mandate Python for GRASS 7 but we should keep it optional for GRASS 6. > > .... So what language to write g.gui in? > > Both /bin/sh + .bat versions depending on platform via Makefile magic? > > Do it in C? > > Not sure, I wrote draft in C > > http://trac.osgeo.org/grass/ticket/43
I summarized the issues on wiki http://grass.gdf-hannover.de/wiki/WxPython-based_GUI_for_GRASS#Issues Martin -- Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa * _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
