[GRASS-dev] [GRASS GIS] #3177: Automatically register addons in GUI
GRASS GIS
trac at osgeo.org
Fri Mar 2 07:13:28 PST 2018
#3177: Automatically register addons in GUI
--------------------------+----------------------------------
Reporter: sbl | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: minor | Milestone: 7.4.1
Component: Addons | Version: unspecified
Resolution: | Keywords: g.extension,Makefile
CPU: Unspecified | Platform: All
--------------------------+----------------------------------
Comment (by annakrat):
Replying to [comment:3 hellik]:
> Replying to [comment:2 martinl]:
> > Already done, Addons are visible in Modules tab (after restarting the
GUI). Time to close this issue?
>
> AFAIK only C addons are added to the Modules tab, but not python addons;
behaviour seen in winGRASS.
I am not sure if there is a separate ticket for this, but I looked at the
problem and I don't quite understand the logic behind it. Basically when
scanning for available addons, the toolboxes run g.extension -ag and look
if "executable" exists. For Python scripts it's not there:
{{{
grass.read_command('g.extension', quiet=True, flags='ag')
name=r.lake.series
description=Fills lake at given point(s) to given levels.
keywords=raster,hydrology,hazard,flood
executables=
name=r.stream.distance
description=Calculates distance to and elevation above streams and outlet.
The module can work in stream mode where target are streams and outlets
mode where targets are outlets.
keywords=raster,hydrology,stream network,watercourse distance
executables=r.stream.distance
name=i.superpixels.slic
description=Perform image segmentation using the SLIC segmentation method.
keywords=imagery,segmentation,superpixels,SLIC
executables=i.superpixels.slic
}}}
So the question is why the executable is not there, which is in
g.extension:
https://trac.osgeo.org/grass/browser/grass/trunk/scripts/g.extension/g.extension.py#L413
I don't understand the condition there to exclude scripts folder on
windows.
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3177#comment:4>
GRASS GIS <https://grass.osgeo.org>
More information about the grass-dev
mailing list