[GRASSGUI] qgis interface alike
Daniel Calvelo
dca.gis at gmail.com
Sun Mar 25 12:59:18 EDT 2007
Hi all,
The current wx-based development of a GRASS GUI follows the line of
tcltkgrass, d.m, gis.m and provides graphical interactive access to
the whole GRASS functionality.
The approach taken by Radim in the QGIS GRASS plugin is rather
different: he provides full CLI access for advanced use on the one
hand, and on the other he provides graphical shortcuts for common
operations, needing a reduced set of parameters (the rest using either
defaults or special values according to each "shortcut").
I was thinking about leveraging Radim's work, building a Python parser
for his .qgm format, basically reusing qgis-grass plugin's module tree
and providing this same "fast" commands for the wx-based interface.
But we're talking about different philosophies here. How do you think
both could be merged in a way that wouldn't be unintuitive to a new
GRASS user? Would separating the interface in "basic" and "advanced"
functionality be desirable? Can the qgis plugin interface make sense
as a "quick toolbox" alongside the heavier wxgui? Would this
integration be worthwhile from a user standpoint?
Daniel.
--
-- Daniel Calvelo Aros
More information about the grass-gui
mailing list