On Tue, Aug 18, 2015 at 9:39 PM, Vaclav Petras <[email protected]> wrote: >> > I wonder why UI is not generated on the fly or during compilation? To >> > maintain manually UI in QGIS is complicated and the result will be >> > always out-of-date. Just 2 my cents, Martin >> >> UI is generated on the fly when a module UI is opened. It is using >> options description printed by GRASS module (--interface-description) >> combined with options definition for the module in QGIS (.qgm file). >> The additional options definition in QGIS is mainly for two purposes: >> >> 1) limit number of options not to frighten users, some GRASS modules >> are also represented as multiple items with predefined options > > Hi Radim and Martin, > > I guess that one of the reasons for QGIS interface for GRASS. Anyway, is > there a option of not using .qgm file and using --interface-description > only? This would not only enable some of the hidden features but more > importantly, it would enable to use of modules from GRASS GIS Addons > repository. > >> 2) define relations between options (e.g. type or column option >> relation with input vector) or special options which has dedicated >> widget in UI (e.g. GDAL/OGR input). > > This should be defined in GRASS GIS. If it is missing in GRASS or in the > --interface-description then it is a bug which should be solved.
How can I recognize G_OPT_V_TYPE in --interface-description? It does not have gisprompt. Radim _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
