[GRASS-user] Re: GRASS GUI assessment

[Benjamin Ducke]

On 06/01/2010 10:59 AM, Jenny Turner wrote:
>
> First of all, let me thank you for all your help on describing and commentying the GRASS GUI's.
>
> Regarding Benjamin Ducke:
> - Wxpython Vector Digitizer is not yet available in Windows right?
> - Regarding QGIS, if a GRASS function is not available at QGIS I have heard that it's quite easy to put in QGIS (just edit a python file and XML as far as I remember). right?

Not if the GRASS module in question does 3D data processing (voxel or 3D vector),
is an imagery module or takes multiple input maps (see the list I posted).
To support such GRASS functionality, the QGIS GRASS plugin needs to be extended at source
code level. There are hard limits to what the current QGIS GRASS plugin can do.

> - And comparing QGIS and WXPYTHON: Which one is more stable and usable?

QGIS is NOT a GRASS GUI. QGIS is a GIS on its own with an optional GRASS GUI interface
as a plugin. That QGIS GRASS plugin is pretty solid but it does not feel more stable or
mature to me, than the current wxPython based GUI for GRASS.

Ben

>
> Thanks,
>
> Jenny
>
>
> _______________________________________________
> grass-user mailing list
> grass-user at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-user



------
Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information.