xgrass

[James Darrell McCauley]

Simon Cox (s.cox at dem.csiro.au) writes on 16 March 1995:
>I notice a lot of (new?) users are going for the xgrass interface onto
>grass.  My understanding was that development (& support?) for xgrass had
>stopped in favour of LAS tcltkgrass.  However, tcltkgrass has still not
>made its official debut ... or has it?  Can someone elucidate, and then the
>poor souls struggling with xgrass will know whether their's is wasted
>effort, in the long run?

yes, if someone associated with TclTkGRASS can give an update, it
would be much appreciated. Particularly, will the UNIX version
be freely available? Any target dates? The subject seems to be
taboo, but I'm sure that there are several just as curious as
Simon and myself.

There are also at least two other GUIs being developed (not by LAS). 
I have personal knowledge of one of them, but I'm not at liberty to 
discuss any details. 

I don't know that development XGRASS was stopped "in favour of" of
LAS' project. Rather, development stopped because funding dried
up. There may be a better case for XGRASS funding if there weren't
other GUIs being developed, but... My understanding of "support" for
XGRASS is that diffs may be incorporated if sent to grassbug at zorro but
other bug reports may received less attention (a lot of significant
changes are occuring to more basic elements of GRASS, e.g., relational
database access, vector API, sites API. these demand more attention at
present).

just one man's understanding--standard disclaimers apply. 
-- 
James Darrell McCauley, PhD        http://soils.ecn.purdue.edu/~mccauley/
Dept of Agricultural Engineering   mccauley at ecn.purdue.edu
Purdue University            new-> tel: 317.494.1198 fax: 317.496.1115