[QGIS-Developer] Improvement to the plugin manager's upgradeable plugins details

Alessandro Pasotti apasotti at gmail.com
Sat Mar 9 04:13:57 PST 2019


I like the idea, I'm just worried about the increased size of the XML on
option A: we don't have any control over the changelog size (well, we could
truncate the changelog if it's too long but I don't know if that makes much
sense).



On Sat, Mar 9, 2019 at 11:38 AM Mathieu Pellerin <nirvn.asia at gmail.com>
wrote:

> Greetings,
>
> While applying a couple of commits to QGIS' plugin manager, I would like
> to fix a long-standing UX issue with it, namely that plugins that show a
> newer version available do _not_ show the latest changelog but rather the
> changelog of the currently installed plugin version.
>
> It'd much nicer, and exciting for users, to show what's new _prior to_
> hitting the [ update plugin ] button.
>
> For that to happen, we'd need either: a/ add the changelog information in
> the repository XML file fetched (i.e.
> https://plugins.qgis.org/plugins/plugins.xml?qgis=3.6), or b/ add a
> method to fetch changelog strings from the repository site (for e.g.,
> https://plugins.qgis.org/plugins/changelog.xml?names=plugin1,plugin2,plugin3
> ).
>
> Unless adding the short changelog to the repository XML adds too many MBs,
> I'd vote for option A.
>
> Thoughts?
>
> Mathieu
> _______________________________________________
> QGIS-Developer mailing list
> QGIS-Developer at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer



-- 
Alessandro Pasotti
w3:   www.itopen.it
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20190309/d6b05163/attachment-0001.html>


More information about the QGIS-Developer mailing list