I've been working on getting the wxPython prototype up and running to a
point where people can begin to really build on it. It's coming along, but
has a ways to go. But now since GRASS 6.2 and 6.3 are in the works, I need
to do some updates to the TclTk GUI.
I wanted to let you all know where I'm at with wxPython at the moment. I
don't like to put non-working code into the cvs. But if anyone wants to work
on this I can do it.
I moved the menu data object out of gism.py and into a separate module. This
works fine. It would probably be even better as an xml file, but I don't
know much about them from a coding standpoint. The new keywords could
perhaps be incorporated as a way to begin to automatically structure them.
I've refactored the code in gism.py and mapdisp.py to break it up into
separate classes, instead of a long list of functions. This broke the app,
of course, but is needed in the long run. I've got most of it put back
together. I'm currently stuck at how to switch different layer trees into
the layer page on the notebook when a map display is created or selected.
I've done a couple prototype options panels and got them bound to changesel
events in the layer tree. I'm building these as independent panels in
wxGlade. Right now they don't do anything except look good. But the event
handler stubs are there for each of the options widgets.
As best I can tell, the floating canvas could make a number of things easier
because it will so coordinate conversions, zooms, and pans automatically.
This just leaves it to us to do the GRASS-side rendering, cutting out a lot
Let me know if any of you want to work on any of this. I'll keep plugging
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University
> From: Trevor Wiens <[hidden email]>
> Date: Tue, 22 Aug 2006 22:37:36 -0600
> To: Michael Barton <[hidden email]>
> Subject: Re: wx.lib.floatcanvas
> I had a chance to look at this briefly tonight. Like Jachym, I'm not
> sure of it's direct applicability to the GRASS GUI, but it certainly
> lends itself as an object of study.
> Thanks for keeping an eye on these things. Python has many libraries
> for all sorts of things and it is often hard to keep track of all that
> is available.
> Similarly with the db front end tools, I examined them briefly and they
> may or may not be directly applicable, but they definitely prove the
> viability of wxPython as a platform with which a decent db interface
> can be written.
> Trevor Wiens [hidden email] >
> The significant problems that we face cannot be solved at the same
> level of thinking we were at when we created them.
> (Albert Einstein)