[GRASSGUI] Re: managing layer and properties

[Daniel Calvelo]

On 3/19/07, Michael Barton <michael.barton at asu.edu> wrote:
[...]
> In terms of the most effective use of our time, I'd propose the following.
> Why don't we start with using the existing autogenerated gui panels--and
> upgrading menuform to make it nice (use select.Select for maps and other gis
> elements, add notebook tabs and icons like in the TclTk GUI, etc). The
> latter needs doing anyway. Taking this route first, I think that we could be
> up and running very quickly with a full-featured wxGRASS in short order. The
> sooner we have something that is 80%+ useable, the sooner we can have
> widespread testing, and maybe get some additional help in writing the
> separate modules for georeferencing, profiling, and the like.

I've started looking into this. So far, it does seem easy to get a
gis.m-like interface. As Glynn pointed out, it remains to be seen
whether the current expressive power of --interface-description is
enough for correct user experience.

BTW, I'm striving at keeping menuform.py an independent component, so
tying it into the display manager should be done by inheritance from
menuform.py, or the latter be an instance of a more abstract
definition of a command builder.

[...]

Daniel.

-- 
-- Daniel Calvelo Aros