[GRASS-dev] GUI toolkits

[Jachym Cepicky]

The way, QGIS is controled, completly differs from the way, GRASS is
controled. People (like me) like the way and will never use QGIS, because it is something strange.

I thing, GRASS should not be about nice and featurefull GUI. But it
should have "high-toned" GUI - something, which would do things
"the GRASS way", something, which would be fast, small (on diskspace
and on the screen). 

Personally I thing, that the new gis.m is too "overstuffed", but as I
did nothing, I say nothing, but "thank you", Michael and Cedric, well
done!

I do not want to be forsed to use QGIS, when I want to digitize my data,
I do not want to be forsed to use QGIS, when I want display my data. 
I do want "just rectify" my new raster image and so on.
That's IMHO all, the "new" gui should be about (freedom?).

QGIS and GRASS are looking like Ubuntu and Debian these days to me.

Jachym

P.S. My apologize, if I misunderstand something.

On Sun, May 28, 2006 at 04:15:20PM +0200, Paolo Cavallini wrote:
> At 05:51, domenica 28 maggio 2006, Trevor Wiens has probably written:
> 
> > 1. QGIS and GRASS have different goals and target different audiences.
> > Thus abandoning a GRASS specific GUI reduces the ability of GRASS
> > developers to guide and develop the tools they want and need.
> 
> I do not understand this. GRASS is very much about powerful GIS analyses. QGIS 
> is especially aimed at geobrowsing. The integration of the two makes the easy 
> yet powerful freeGIS most user (actual and potential) want and need.
> 
> > 2. GRASS is primarily written in C so if we want to use a compiled
> > language, C would be the natural choice.
> 
> Right, but do you think separating analysis (in C) from GUI (in C++/Qt) would 
> cause problems?
> 
> > 3. C++ would reduce the number of contributors. Establishing a nice
> > interpreted environment could increase the ease of development for
> > future modules.
> 
> Tapping from the relatively large and very active developer base of QGIS 
> actually increases the number of contributors, leaving grass developers to 
> concentrate on analysis (see e.g. recent discussions on rater data format, 
> and the TODO list on vectors sent by Radim) rather than reinventing the 
> wheel.
> 
> > Personally, I use QGIS as viewer of shapefiles or PostGIS files, but not
> > for anything else; I prefer GRASS.
> 
> GIS is very much about interoperability, so being able to use shapefiles and 
> postgis and grass in the same environment is a big plus. Have you tried e.g. 
> printing a simple map recently?
> 
> All the best.
> pc
> -- 
> Paolo Cavallini
> email+jabber: cavallini at faunalia.it
> www.faunalia.it
> Piazza Garibaldi 5 - 56025 Pontedera (PI), Italy   Tel: (+39)348-3801953
> 
> _______________________________________________
> grass-dev mailing list
> grass-dev at grass.itc.it
> http://grass.itc.it/mailman/listinfo/grass-dev

-- 
Jachym Cepicky
e-mail: jachym.cepicky at centrum.cz
URL: http://les-ejk.cz
GPG: http://les-ejk.cz/gnupg_public_key/jachym_cepicky-gpg_public_key.asc
-----------------------------------------   
OFFICE:                                     
GDF-Hannover
Mengendamm 16d
30177 Hannover
Germany
e-mail: cepicky at gdf-hannover.de
URL:    http://gdf-hannover.de
Tel.:   +49 511-39088507
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.osgeo.org/pipermail/grass-dev/attachments/20060528/8feb65f6/attachment.bin