+1 I understand the importance and the need to give all the best to the core dev, as there are many parts that need to be mantained/updated/refactored/built (ie the raster core code in qgis...), but I support a boost to the 'joints' of the systems integration. as I think that their integration is a leading factor for their diffusion and presence in the end-user community. I'm happy to see the proposal from Paolo about a found raising for qgis-grass-plugin, and I hope I will be able to contribute (also economically). The other important (foundamental, in my opinion) issue is the Windows support. I've tried to give a help for the Osgeo4w stack some time ago, but I've wasted all my time in trying to solve Windows Vista's problems... without very good results!
have a nice day, giovanni 2009/5/4 Nikos Alexandris <nikos.alexand...@felis.uni-freiburg.de>: > On Mon, 2009-05-04 at 08:49 +0200, Paolo Cavallini wrote: > ---%<--- >> I would therefore respectfully suggest devs, form the users perspective, >> to consider concentrating on the best of each world, reducing the >> duplication of efforts, and improving the (already good) interaction >> between the two programs. > ---%<--- > > +1 to that from an end-user like me. > > I would like also to mention OpenEV. It is the fastest geodata viewer > [period]. I don't know the coding background and the differences for > among QGIS, GRASS and OpenEV, but why not use it, create interaction > with it _or_ use parts of its code _or_ just look at some of its > attractive features? > > Kindest regards, Nikos > > _______________________________________________ > Qgis-user mailing list > qgis-u...@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-user > _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev