Future direction - GRASS GUI

[Wayne]

Hello,
I've been following this thread and would like to add my $.02.  I think like
everyone else that
a GUI interface would be nice, but the language to develope in should meet
several criteria.
1. easy to learn.
2. easy to maintain.
3. rapid developement
4. good API.
5. runs on multiple platforms.
Althought I'm new to the language, I think Python fits the bill. Here is a
language that
can be object or procedural and can replace awk, sed and do much more. I
think
in the not to distance future Pyhton will replace Perl and possible Jave.
I should also note that there has been some discussion on the Python news
group
about making GUI interfaces to ArcView. Maybe we can use some of thier stuff.

Wayne.

J.Simon Goodall wrote:

> Hello folks,
>
> Has anyone considered the alternative "Microimages" style,
> (http://www.microimages.com) I used their product TNTmips for a while when
> doing contract work and was very happy with the interface. Had to produce
> a lot of printed output and the layout tools where superb, absolute
> control.
>
> Their solution to the portable GUI is to have a X server under Windows
> that they programmed themselves, actually quite a few unixer's use it as a
> Windows X server. They have the same solution for the Mac. All their
> coding is done in unix and they use their own API, guess this simplifies
> the portability issue.
>
> Well, other things. I agree completely that GRASS should remain "modular"
> and easily scriptable, it's what provides flexibility that other programs
> don't have. Postgress and R seem good options as well.
>
> Hope all this finishes in a better GRASS, my $0.02 worth,
>
> Regards,
>
> Simon Goodall.
>
> --
> J.Simon Goodall, Lic. Ea.Viamonte, C.C.8, 9420 Rio Grande, TDF, Argentina.
> te:54.2964.430.861 fx:422.008 mob:15.614647 e-mail:sgoodall at global.com.ar