[GRASS-user] v.coordinate.sh - improve this script?

Martin Landa landa.martin at gmail.com
Fri Jan 25 09:37:46 EST 2008


Hi Luca,

2008/1/25, Luca Casagrande <luca.casagrande at gmail.com>:

[snip]

> I have started studying python more deeper for using it in pyWPS and
> for creating new Qgis modules (with QT).
> Just for knowing, is there any reason for using wxWindow instead of Qt
> for the new GUI?
> is it a matter of license?

which graphical toolkit to use for native GRASS GUI has been discussed
in grass-dev ML several times in the past. At the end it was decided
to use wxWidgets:

* powerful Python binding (know as wxPython).
* uses native platform SDK (native look and feel)
* Free OpenGL widget for NVIZ replacement

see

http://grass.gdf-hannover.de/wiki/GRASS_GUI
http://grass.gdf-hannover.de/wiki/WxPython-based_GUI_for_GRASS
http://www.nabble.com/v.digit%3A-Qt-or-wxWidgets-to4472391.html#a4472391
http://www.nabble.com/Platform-for-next-generation-UI-to2114044.html#a2115028
http://www.nabble.com/Discussing-new-GUI-toolkit%3A-v.pydigit-to4637114.html#a4642371
http://www.nabble.com/Python-GUI-toolkits-to4755513.html#a4788219

etc.

Since native wxPython GUI is under development more then one year it
makes hard to switch to PyQT now. wxPython seems to be a good choice
at the end, at least from my point of view.

Regards, Martin

-- 
Martin Landa <landa.martin at gmail.com> * http://gama.fsv.cvut.cz/~landa *


More information about the grass-user mailing list