[GRASS-dev] Python GUI toolkits

[Michael Barton]

I agree. Let's see if we can port what we've got now and see how current
problems can be fixed. I'm not in the least opposed to reopening the UI
design discussion. This would be very healthy and productive. I  just think
we need to focus on one enormous step at a time. And switching GUI platforms
after 15 years is pretty big. My hope is to maintain the more or less
unidirected, organized chaos that has been so productive over the past year.

Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton



> From: Hamish <hamish_nospam at yahoo.com>
> Date: Fri, 9 Jun 2006 21:47:33 +1200
> To: Michael Barton <michael.barton at asu.edu>
> Cc: <grass-dev at grass.itc.it>
> Subject: Re: [GRASS-dev] Python GUI toolkits
> 
> 
> If we can pick wxWidgets or pyGTK, then we can start with the frontends:
> 
> py.digit (r.+v.), py.rectify (incl points, groups, v.trans, the new i.3
> code, i.ortho?,..), py.profile, py.psmap, py.mapset, py.projection,
> py.startup ... After that & we are all better informed we can worry
> about replacing gis.m. --with-python can be optional until things are
> well ready.
> 
> Managable small steps.
>