Showing SEXTANTE, GDAL Tools, fTools in the menu is the implementation model leaking into the UI. The users don't care how it's implemented as long as it works.
- Nathan On Mon, Aug 12, 2013 at 9:04 AM, Tim Sutton <[email protected]> wrote: > Hi > > > On Mon, Aug 12, 2013 at 12:14 AM, Alex Mandel > <[email protected]>wrote: > >> So is the proposal to change Analysis to Processing? >> I don't think there's a reason to remove the SEXTANTE branding as >> SEXTANTE does exist outside a QGIS context, ftools is another story >> since that only exists in QGIS. I'm split on GDAL Tools, since it is >> good to make sure users know what underlying tool is being used (ie in >> the event they want to use the command line). >> >> As for the Vector, Raster, etc menus... it's expected that over time >> plugins will sort themselves into those menus in order to add >> organization and make it more obvious what a tool does. It also makes >> the generic plugins section smaller so that you don't have to wade >> through 100 plugins to find the one you want. >> >> The same applies for Analysis or Processing, I expect other analysis and >> processing tools to exist that are not SEXTANTE but end up on the list, >> in which case being able to tell it apart from what's there remains >> important. >> >> To me this is a UI question, not a core vs. non-core/c++ vs. python >> question. ie: How do we organize and arrange menus to maximize discovery >> of tools and ease workflow (fewer clicks or faster nav to the correct >> tool). >> >> Analysis or Processing are both fine to me so +0 or maybe Advanced ....? >> >> > The issue is more that in plugin manager you see all these strangely named > things which don't match their corresponding user interface components... > > Also users of the API have to deal with these naming ideosychrasies - it > would be much nicer to do geoprocessing.* than sextante.* > > > Regards > > Tim > > > >> Thanks, >> Alex >> >> On 08/10/2013 10:53 PM, Saber Razmjooei wrote: >> > +1 for changing name. >> > I like GRASS menus, it has all the analytical modules under vector and >> > raster menu. Can similar thing be done with SEXTANTE? >> > >> > Cheers >> > Saber >> > >> > On 2013-08-10 12:23, Alexander Bruy wrote: >> >> +1 from me to renaming. >> >> >> >> Maybe we can use "Processing" or "GeoProcessing" as new name. >> >> >> >> 2013/8/10 Nathan Woodrow <[email protected]>: >> >>> +1 from me too. >> >>> >> >>> Personally I find the core plugin concept unnecessary. If it's core it >> >>> shouldn't be a plugin and should just be part of the main program. >> >>> It can >> >>> still be Python that is fine however users shouldn't have to turn >> >>> them on >> >>> and off they should just be there and be transparent. >> >>> >> >>> IMO we should aim to kill of all C++ core plugins in 2.1 and make >> >>> them core >> >>> features.Things like the geometry checking, spatial join, >> georeferencer >> >>> should all be core features and have C++ and Python APIs that the >> >>> user can >> >>> use. >> >>> >> >>> - Nathan >> > >> > >> > -- >> > This email and any files transmitted with it are confidential and >> > intended solely for the use of the individual or entity to whom they are >> > addressed. If you have received this email in error please notify the >> > system manager. This message contains confidential information and is >> > intended only for the individual named. If you are not the named >> > addressee you should not disseminate, distribute or copy this e-mail. >> > Please notify the sender immediately by e-mail if you have received this >> > e-mail by mistake and delete this e-mail from your system. If you are >> > not the intended recipient you are notified that disclosing, copying, >> > distributing or taking any action in reliance on the contents of this >> > information is strictly prohibited. >> > >> > Whilst reasonable care has been taken to avoid virus transmission, no >> > responsibility for viruses is taken and it is your responsibility to >> > carry out such checks as you feel appropriate. >> > >> > Saber Razmjooei and Peter Wells trading as Lutra Consulting. >> > _______________________________________________ >> > 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 >> > > > > -- > Tim Sutton - QGIS Project Steering Committee Member (Release Manager) > ============================================== > Please do not email me off-list with technical > support questions. Using the lists will gain > more exposure for your issues and the knowledge > surrounding your issue will be shared with all. > > Irc: timlinux on #qgis at freenode.net > ============================================== > > _______________________________________________ > 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
