wxGUI toolboxes

Main article: wiki:wxGUIDevelopment/Toolboxes

Toolboxes as GUI-only concept.

Toolbox approach discussed at the GRASS Community Code Sprint 2012

At the sprint in Prague 2012 the toolbox approach with different repositories as well as the approach using "--with-toolbox/--without-toolbox" configure statements at compile time have been discussed. The major drawback of these solutions is the their complexity and the problem of cross dependencies between modules.

A new approach has been suggested using XML files to describe toolboxes and special directory structure to hide unneeded modules from the user.

The idea is to have a binary directory containing only modules that are listed in a XML file that defines what core modules should be available and what toolboxes should be used. The XML file will be used by the GUI to create menu listings for the selected modules. All modules that are deactivated in the XML file will be held in a directory that is not available in the users binary path, but in the binary search path of modules. Hence unneeded modules are invisible at the command line and in the GUI, but still available for modules that might call other modules.

New toolboxes and core modules can be simply added to the search path and the GUI by editing the XML definition and calling g.extension. The module g.extension will simply links/copy the hidden modules into the binary directory that is visible by the user or move deselected modules in the hidden directory. The GUI will always analyzes the XML toolbox configuration file for menu generation.

The configuration XML file will include a list of core modules for general, raster, image, voxel and vector processing as well as the definition of toolboxes. Toolboxes are defined by their type (raster, vector, ...) a short description and a list of modules. Modules can be defined in several different toolboxes.

The GRASS development team should provide several pre-defined XML toolbox configuration files as for hydrological modeling, vector processing, terrain modeling, image analysis, ..., and WPS server. Using this approach the repository structure must not be changed. The build system has to be modified to use the XML toolbox file to decide where to copy the binary modules and scripts. g.extension has to be extended to link/copy selected modules in the users binary search path and to remove modules from them. GRASS will be build as usual.

Original approach

Hi all!

That rather radical ideas I present here are rather for future, at least for GRASS 8,
but I'd like present it now for long-term reflection.

Probably all notice that for over two years there is big increase in add-on repository
(including me). There are modules of different quality: from fully GRASS toolsets,
to shell or python scripts, from  actively developed tools to abandoned,
from all-purpose tools to very specialized etc. I also think that that activity
will be grown due to substitute shell script by python

Similar situation is in main GRASS branch: there are modules for all like conversion tools,
interpolation methods, georeferencing etc, and very specialized modules for very limited
group of users (like wild fire), there are also some modules out of date.

I'm not enthusiastic about moving new modules into main branch. Almost every module has
different coding style and it will lasting in future that GRASS would be difficult to maintain.
On the other hand some people complains that some interesting modules are only available as
add-ons (I assume for some reasons they cannot install it)

So my suggestion is to rearrange future GRASS form two layers (main branch/add-on) into
three layers architecture:

1) GRASS core layer: much limited limited than now, only GIS environment and basic,
all-puropse tools, slow changes, great stability
2) GRASS toolset layer: oficcial GRASS thematic tools and toolsets (like terrain analysis,
hydrological analysis, photo-interpretation, landscape analysis etc,) every toolset with its
maintainer, rapid development, new ready to use tools after quality control may appear here,
also some of current main branch tool shall be moved to that layer
3) GRASS community layer:  everything else like experimental, actively development new tools,
that what do not pass quality control, simple scripts, etc....

What benefits:
for developers and contributors: much clear situation and better publication path.
Toolset layer should be much more open for new tools than current GRASS main branch

for users: faster access to new tools.
There is no doubt that new tools are faster developed (less risk) than GRASS core
Binaries with toolsets could be maintained as separate apt/urpmi/pacman/yum/exe etc packages,
so it may appear in linux repository separetly form GRASS core.

There is only loose ideas. Most of them are of course taken from R (core/toolsets/rest of packages;
separate core and package development) but I think it is worth of some discuss ...


Criticism from the GRASS Wiki Tooboxes talk page:

  • One of our best selling points vs. the competition is that you don't have to buy expensive addon toolboxes to have it do what you want to do.
  • It makes it a lot harder for new users to get started with what they want to do. Even when done well it's a brittle system dependent on 100% uptime servers etc. which in practice do not exist.
    • Comment: I don't see any problem here. We can distribute several packages of GRASS. It will give us just more flexibility. One of the packages could contain all (or all fundamental) toolboxes already installed. Basically we could publish two packages - 'minimal' with only core modules installed to give user freedom to decide (install) which toolboxes/modules he/she wants and 'standard' with all major toolboxes included.
  • Non-"core" modules will be neglected by the core devs and die from bit rot. (outside of grep's reach)
  • Those "non-core" modules have personally led me into all new ideas and directions outside of my normal field of study, which has rather positively affected the direction of my career and let me solve problems in novel ways for my peers that only cross-discipline tools/perspective could introduce us to.
  • Our download size is only about 25ish megs. that's tiny. Docs are bigger than code. Windows deps "aren't our fault" and switching to a different distribution model won't help that much at all.
  • Rather than focus development I fear it will dilute it. Divided we fall..
  • Big change is big work which could more productively be funneled into more critical pursuits. (I am not against needed change, but very against change-for-change's-sake.)

Proposed toolboxes

Toolbox is a topic-based set of modules used for solving common GIS analysis, like hydrology, networking, LRS, etc.

Managing toolboxes

This section describes how toolboxes in addons currently works. This can be part of the documentation. However, it this might be changed with the wxGUI toolboxes.

g.extension is designed to manage locally installed GRASS Addons. It allows to install single addons modules and also toolboxes (flag -t). Note that toolbox support is experimental.

  • list available toolboxes
g.extension -tl
List of available extensions (toolboxes):
Hydrology (HY)
  • list available modules from Addons
g.extension -l
List of available extensions (modules):
  • install new toolbox ("Hydrology")
g.extension -t extension=HY
  • install single module from "Hydrology" toolbox

Module g.extension also allows to list installed extensions

  • toolboxes
g.extension -ta
List of installed extensions (toolboxes):
  • or modules
g.extension -a
List of installed extensions (modules):
  • remove locally installed toolbox
g.extension -ft extension=HY operation=remove
  • remove single module
g.extension -f operation=remove

List of toolboxes

Toolbox name Toolbox code Description Correlate toolbox
3D Raster R3 All r3.* modules
3D Visualization V3 nviz_cmd
Atmospheric tools AT Subset of image processing tool
Cartography CA, ps.output
Database DB All db.* modules Vector analysis
Geostatistcal GS v.krige maybe other
Hydrology HY r.watershed, r.terraflow,* modules in addons, maybe other, r.flow, r.sim.water, r.sim.sediment Raster analysis
Image Processing IM All i.* modules, selected r.* modules
Interoperability tools IO All the various import/export modules except for GDAL/OGR Raster analysis, Vector analysis, Image Processing, Database
Landscape analysis LA All* modules, maybe other Raster analysis
Lidar analysis LI All v.lidar.* modules,,
Linear Reference Systems LS All v.lrs.* modules Vector analysis
Network analysis NA All* modules, maybe other Vector analysis
Raster analysis RA A lot of basic r.* modules (like r.buffer, r.reclass, r.fillnull...)
Terrain analysis TA Different kind of analysis: soil (r.sun,), terrain (r.slope.aspect, r.los), geomorphometry (r.param.scale) Raster analysis
Vector analysis VA A lot of basic v.* modules (like v.buffer, v.centroid, v.overlay...) Database

How to implement

Proposal 1

  • add html tag <param> in the description.html with these options:
    <param name = "core"> for core module
    <param name = "tool" value="tool_code/codes"> for toolbox
    <param name = "addons" [value="tool_code/codes"]> for addons, value is optional
  • create a script to generate a xml file for each toolbox
  • add toolbox option in g.extension to read the xml and install the modules

Proposal 2

  • modules (currently only Addons) are described (name, description, keywords, files) in metadata XML file called modules.xml - this file is auto-generated, see trac page for details
  • similarly toolboxes are described (name, code, correlate modules, list of modules) in toolboxes.xml - this file is manually manageable via SVN

g.extension reads (from remote server modules.xml when listing available modules (-l), and toolboxes.xml when listing available toolboxes (-lt). When installing toolbox using g.extension the module reads toolboxes.xml and installs in the loop given list of modules. When all modules are installed it also updates local metadata files - GRASS_ADDON_BASE/modules.xml and GRASS_ADDON_BASE/toolboxes.xml. These local metadata files are checked when listing locally installed toolboxes or single modules (-a or -ta).

Proposal 3

Use a modified version of pip (a tool for installing and managing Python packages)

With Pip you can add/change repository, compile C/Fortran module, manage dependencies, install from some version control system (use URLs like hg+http://domain/repo -- or prefix git+, svn+ etc), and using virtualenv

Last modified 4 years ago Last modified on Apr 30, 2013 6:58:14 AM