I would have asked the same question as Luca. Wouldn't it be more profitable using QT, as it is already the way Python script are written in QGis? I know the two projects are independent, but having a common GUI language could improve the development of scripts in both the environments and the portability of them.
<br>My impression is that wxWindow is a bit easier to manage then QT, but since many of us write scripts for QGis too, it would be better to learn well one system (QT) then two (QT and wxWindow) :-)<br><br>Anyway, I'm sure you have good reasons for having chosen wxWindow fro Grass.
<br><br>Giovanni<br><br><div><span class="gmail_quote">2008/1/25, Luca Casagrande <<a href="mailto:luca.casagrande@gmail.com">luca.casagrande@gmail.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Jan 24, 2008 4:28 PM, Michael Barton <<a href="mailto:michael.barton@asu.edu">michael.barton@asu.edu</a>> wrote:<br><br>> Since the new GUI will be in Python, I strongly suggest that we start<br>> developing new scripts in Python and for anyone with time on their
<br>> hands ;-) start to create Python versions of existing scripts. The<br>> more scripts that are available in Python, the more people will make<br>> sure that Python is installed and will take a look at it, which will
<br>> lead to more scripts in Python, etc...<br><br>Hi Michael,<br><br>I have started studying python more deeper for using it in pyWPS and<br>for creating new Qgis modules (with QT).<br>Just for knowing, is there any reason for using wxWindow instead of Qt
<br>for the new GUI?<br>is it a matter of license?<br><br>Thank you very much<br><br>Luca<br>_______________________________________________<br>grass-user mailing list<br><a href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org
</a><br><a href="http://lists.osgeo.org/mailman/listinfo/grass-user">http://lists.osgeo.org/mailman/listinfo/grass-user</a><br></blockquote></div><br>