[GRASS5] GRASS extension manager proposal

[Michael Barton]

I thought that this might be worth discussing in a broader venue.


> Hamish,
> 
> Just after sending my last reply, I had a thought. We could develop a new
> naming standard for all commands along this line as a next step. For
> example...
> 
> <modeling
> r.mod.topmodel
> r.mod.basin fill
> 
> <reports
> r.rep.cats
> r.rep.stats
> 
> <overlay
> r.ovl.patch
> 
> <develop
> r.dev.digit
> 
> etc.
> 

On 12/16/04 4:13 PM, "Michael Barton" <michael.barton at asu.edu> wrote:

> Indeed. This is a nice organizational plan to build on. In many senses, we are
> already halfway to this kind of self-organizing system. However, the
> complexity of GRASS (and any high-end GIS) means that we need more 2nd and 3rd
> order divisions as you note here.
> 
> Michael
> 
> 
> On 12/16/04 4:00 PM, "Hamish" <hamish_nospam at yahoo.com> wrote:
> 
>>> The ultimate objective is to make a GUI that is more or less
>>> self-generating.
>> 
>> 
>> see how the help pages organize themseleves based on r.* etc. to form these:
>> http://grass.ibiblio.org/grass57/manuals/html57_user/raster.html
>> 
>> 
>> r.in.* etc might be a quick further refinement.
>> 
>> 
>> 
>> H
> 
> ______________________________
> Michael Barton, Professor of Anthropology
> School of Human, Evolution and Social Change
> Arizona State University
> Tempe, AZ  85287-2402
> USA
> 
> voice: 480-965-6262; fax: 480-965-7671
> www: http://www.public.asu.edu/~cmbarton

______________________________
Michael Barton, Professor of Anthropology
School of Human, Evolution and Social Change
Arizona State University
Tempe, AZ  85287-2402
USA

voice: 480-965-6262; fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton