[Qgis-developer] QGIS and GRASS 7.0.0

[Radim Blazek]

Hi,

On Tue, Feb 24, 2015 at 7:11 PM, Vaclav Petras <wenzeslaus at gmail.com> wrote:
>
> On Tue, Feb 24, 2015 at 3:28 AM, Radim Blazek <radim.blazek at gmail.com>
> wrote:
>>
>> - modules GUI - my idea is to throw away the qgm and qgc definitions
>> and auto generate GUI for modules with all options based on
>> --interface-description only, also the list of modules would be auto
>> generated for all modules.
>
>
> Hi Radim,
>
> it would be good if you can include GRASS Addons, too. There is a lot of
> requests for installing/running GRASS Addons from QGIS, e.g. at
> gis.stackexchange.com.

How can I get list of installed GRASS Addons?

> Also, there are some files in GRASS GIS which might be quite useful [1].
> toolboxes.xml [2]

The toolboxes.xml looks interesting, fortunately we have already
volunteer to maintain qgc (tree configuration).

Radim

> contains GRASS GIS modules sorted into different tooboxes.
> They are currently not part of the official API but it is just a matter of
> declaring them as part of API I guess [3]. GRASS wxGUI is using these files
> to create a menu and module tree in Search module tab. It is also a way to
> customize wxGUI [4] but that's not related to QGIS use case.
>
> Loading Addons dynamically to menu or module tree including their
> descriptions seems to be a bit challenging but if nothing else wxGUI can
> always run a module installed using g.extension (or custom user script) if
> it can run and give --interface-description.
>
> Best,
> Vaclav
>
> [1] http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/xml
> [2]
> http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/xml/toolboxes.xml
> [3]
> http://trac.osgeo.org/grass/browser/grass/trunk/gui/wxpython/docs/wxgui_sphinx/src/wxgui_toolboxes.rst
> [4] http://grass.osgeo.org/grass70/manuals/wxGUI.toolboxes.html