Hi

> 
> > I would like to know your opinion about this idea: removing Processing
> > from the QGIS plugins repo.
> >
> > Rationale for this: we have always tried to release new version of
> > Processing between releases of QGIS, to provide more updates when
> > important fixes are made or interesting functionality is added. This
> > sounds good in theory, but it has proven to be difficult to handle.
> > The main reason for this is that having the same plugin in the
> > installation folder and the user folder leads to strange behaviour
> > sometimes, and confusion for users. The Plugin Manager doesn't seem to
> > be prepared for this circumstance, and sometimes fails when updating.
> >
> > I think that maybe is a good idea to handle processing as a core
> > plugin, and forget about releasing it outside of QGIS releases.
> > Processing should not be in the plugins repo, to avoid confusion.
> > Basically, what other core plugins do.
> >
> > I still see a lot of messages with installation issues and failures,
> > and I think it is not a good thing.
> >
> > What are your thoughts on this?
> 
> 

A big +1 from me too. There is another reason to adopt this approach - it is 
hard to build something relying that if the user has QGIS version X they will 
also have processing algorithm Y - which is something we are running into here 
with our plugin development.

Regards

Tim
—






Tim Sutton

Co-founder: Kartoza
Project chair: QGIS.org

Visit http://kartoza.com <http://kartoza.com/> to find out about open source:

Desktop GIS programming services
Geospatial web development
GIS Training
Consulting Services

Skype: timlinux
IRC: timlinux on #qgis at freenode.net


Kartoza is a merger between Linfiniti and Afrispatial

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

_______________________________________________
Qgis-developer mailing list
[email protected]
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Reply via email to