Another reason beyond the one that I mentioned to Luca is that we went
through many potential interface development languages 2 years ago,
decided on wxPython, and the wxPython is now almost complete. It would
be an enormous time sink to do this all over again.
Michael
______________________________
Michael Barton, Professor
Professor of Anthropology
Director of Graduate Studies
School of Human Diversity & Social Change
Center for Social Dynamics & Complexity
Arizona State University
Tempe, AZ 85287-2402
USA
voice: 480-965-6262; fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton
On Jan 25, 2008, at 6:14 AM, G. Allegri wrote:
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.
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) :-)
Anyway, I'm sure you have good reasons for having chosen wxWindow
fro Grass.
Giovanni
2008/1/25, Luca Casagrande <[EMAIL PROTECTED]>:
On Jan 24, 2008 4:28 PM, Michael Barton <[EMAIL PROTECTED]>
wrote:
> Since the new GUI will be in Python, I strongly suggest that we
start
> developing new scripts in Python and for anyone with time on their
> hands ;-) start to create Python versions of existing scripts. The
> more scripts that are available in Python, the more people will make
> sure that Python is installed and will take a look at it, which will
> lead to more scripts in Python, etc...
Hi Michael,
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?
Thank you very much
Luca
_______________________________________________
grass-user mailing list
[EMAIL PROTECTED]
http://lists.osgeo.org/mailman/listinfo/grass-user
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
