On Tue, Feb 24, 2015 at 9:51 PM, Andrew <[email protected]> wrote: > Hi Radim, > > I would be willing to volunteer to help maintain the qgm and qgc files.
Great, I'll keep current config system also for GRASS 7. Radim > Andrew > > On Tue, Feb 24, 2015 at 12:28 AM, Radim Blazek <[email protected]> > wrote: >> >> Olá todos, >> >> I'am already preparing crowdfunding campaign for GRASS plugin upgrade. >> It will include: >> >> - qgisgrasslib upgrade to GRASS 7 >> - single build with both GRASS 6 and 7 (GRASS version chosen by >> environmental variables on start up) >> - move plugin browser functionality to standard QGIS browser (meta >> info widget, delete and rename action) >> - implement raster and vector import via browser drag and drop >> (including reprojection) >> - new/open/close location tools upgrade to GRASS 7 >> - region editor upgrade to GRASS 7 >> - upgrade GRASS shell to the last qtermwidget >> - modules GUI - my idea is to throw away the qgm and qgc definitions >> and auto generate GUI for modules with all options based on >> --interface-description only, also the list of modules would be auto >> generated for all modules. The reason is my impression that there are >> no volunteers willing to maintain qgm and qgc. If there are volunteers >> to do that (no programming, xml editing only) let me know and I'll >> include keeping of current system in the proposal. >> - vector editing overall upgrade and enhancement more integrated with >> standard QGIS tools >> - standard editing tools (e.g. node tool) >> - snapping to other layers >> - undo/redo >> - attribute forms >> - possibility to change topological symbology via standard style >> dialog >> - standard rendering of not edited layers based on edited map >> (i.e. draw filled polygons on background during editing) >> >> I am currently coding proof of concept for vector editing to be sure >> that it is feasible at all. I hope to launch the campaign in about 2-3 >> weeks. >> >> Radim >> >> On Mon, Feb 23, 2015 at 10:06 PM, Pedro Venâncio >> <[email protected]> wrote: >> > Olá Paolo, >> > >> > >> >> this will require a reasonable amount of work. I have raised the issue >> >> several times; sadly it seems nobody is willing to invest the necessary >> >> resources on this. >> > >> > >> > Despite the great advantages of GRASS commands in Processing, I think >> > that >> > the GRASS plugin still plays an important role and is an excellent >> > interface >> > for GRASS. For those who still like to use the paradigm of locations, >> > mapsets and the GRASS topological model, GRASS plugin is very important, >> > because then it allows to use all QGIS tools, for example, to create >> > layouts >> > using the Composer, etc. >> > >> > If no one is interested in making the port of the plugin for GRASS 7, we >> > could try through a crowdfounding initiative. Who was behind the initial >> > creation of GRASS plugin? >> > >> > >> > >> >> >> >> BTW, would you mind giving us a list of the missing modules in >> >> Processing? AFAIK these should be only obsolete and useless ones, but >> >> if >> >> there is some genuinely missing we should be able to fix this rather >> >> easily. >> > >> > >> > >> > I've been checking the differences and they are indeed few. Please see >> > the >> > spreadsheet attached. >> > >> > Some commands seem that were adaptations of other algorithms, made for >> > Processing, as they are not in the 6 manual, or in the 7: >> > r.cost.full.raster, r.drain.coordinate, r.terraflow.short, >> > v.surf.rst.cvdev.line, v.surf.rst.line, v.transform.pointsfile. >> > >> > Others seem that have been removed from GRASS 7 (r.average, r.bilinear, >> > r.bitpattern, r.surf.idw2), as they are not in the GRASS 7 manual. >> > >> > There are five that seem important to me, which are in GRASS 7, in >> > Processing GRASS 6, but not in Processing GRASS 7: r.out.xyz, r.ros, >> > r.spread, r.univar, v.kernel. >> > >> > Finally, there are two commands that are on GRASS 7 and were not in 6: >> > r.viewshed (which replace r.los) and r.relief (which replace >> > r.shaded.relief). >> > >> > >> > Thanks! >> > >> > Best regards, >> > Pedro Venâncio >> > >> > >> > _______________________________________________ >> > Qgis-developer mailing list >> > [email protected] >> > http://lists.osgeo.org/mailman/listinfo/qgis-developer >> _______________________________________________ >> Qgis-developer mailing list >> [email protected] >> http://lists.osgeo.org/mailman/listinfo/qgis-developer > > _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
