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