[GRASS-dev] Re: More xtnmenu stuff

[William Kyngesburye]

On Sep 23, 2007, at 7:40 PM, Michael Barton wrote:

>> (and could change if we decide
>> on a GRASS_XTN_PATH base path instead of multiple GRASS_ADDON_* vars)
>
> I'd recommend keeping the xtnmenu.dat file in GRASS_ADDON_ETC  
> because that
> is already an existing GRASS environmental variable.
>
> I'd also recommend using GRASS_ADDON_PATH for the same reason.  
> Anything
> listed in GRASS_ADDON_PATH will automatically run from the command  
> line and
> from in scripts (like the GUI) without an explicit path specification.
>
I don't mean the actual location of xtnmenu.dat would change, just  
the env variable used to locate it.  Currently we have:

GRASS_ADDON_PATH - been around a while, should be left as is
GRASS_ADDON_ETC - fairly new addition

but will probably need soon:

GRASS_ADDON_HELP

And with the possibility of use the makefile fragments for building  
and installing extensions (I'm close), we will need to know where  
scripts/ and lib/ are.

My suggestion is to have one base for all this: GRASS_XTN_PATH (stil  
multiple paths).  Then the various places that need them use  
subfolders (bin, lib, docs, etc, scripts) from there.


>>
>> And, for the cases where people do install addons in the GRASS
>> installation, you might want to check for xtnmenu.dat in GISBASE.
>
> No. This is the idea of a standard--so we don't have to check all  
> the places
> that people *might* try to put a menu file. If it is not in the  
> standard
> local (which is anywhere, but must be a place specified in  
> GRASS_ADDON_ETC),
> then it won't show up in the GUI.

Just a thought.

-----
William Kyngesburye <kyngchaos*at*kyngchaos*dot*com>
http://www.kyngchaos.com/

All generalizations are dangerous, even this one.