#1420: wxGUI: modeller
-------------------------+--------------------------------------------------
Reporter: neteler | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 6.4.2
Component: Default | Version: svn-releasebranch64
Keywords: | Platform: Unspecified
Cpu: Unspecified |
-------------------------+--------------------------------------------------
While the new graphical modeller dynamically reads in
the available module list, the locally installed
Addons are not shown in the list.
In r48545 the addons modules are at least scanned. So it's possible to
call them from wxGUI cmd. It would be also good to add them dynamically to
the menu and enable to search for them by desc/keywords etc.
Replying to [comment:2 martinl]:
> In r48545 the addons modules are at least scanned.
do not scan $GRASS_ADDON_PATH/bin/ and $GRASS_ADDON_PATH/scripts/. rather
just scan $GRASS_ADDON_PATH. executables are (ie should be) symlinked back
into there if they happened to be installed to ./bin/ or ./scripts/. (I
see no reason why with a little more work bin/ and scripts/ couldn't be
skipped entirely, and save the trouble of the symlinking)
the $GRASS_ADDON_PATH variable is meant to be part of the $PATH variable,
it is not meant to be --prefix= or $ADDON_BASE. (see also William's
approach using $GRASS_ADDON_ETC found in lib/gis/find_etc.c and documented
in macosx/Readme.rtf)
Replying to [comment:3 hamish]:
> Replying to [comment:2 martinl]:
> > In r48545 the addons modules are at least scanned.
>
> do not scan $GRASS_ADDON_PATH/bin/ and $GRASS_ADDON_PATH/scripts/.
rather just scan $GRASS_ADDON_PATH. executables are (ie should be)
symlinked back into there if they happened to be installed to ./bin/ or
./scripts/. (I see no reason why with a little more work bin/ and scripts/
couldn't be skipped entirely, and save the trouble of the symlinking)
>
> the $GRASS_ADDON_PATH variable is meant to be part of the $PATH
variable, it is not meant to be --prefix= or $ADDON_BASE. (see also
William's approach using $GRASS_ADDON_ETC found in lib/gis/find_etc.c and
documented in macosx/Readme.rtf)
But that's the way how GRASS_ADDON_PATH currently works in G7. It's topic
for discussion of course. Basically this variables currently serves in G7
as GISBASE for Add-ons modules. This approach doesn't require adding new
and new variables for etc, html or man pages. It's the main advantage of
this approach, personally I don't know about disadvantages (please correct
me). In G7 everything is installed to the one place, by default
`$HOME/.grass7/addons` on GNU/Linux.