Hi,
what exactly do you mean by autopackaging ? The new repo now offers
API for uploading new versions of plugins - automatic deployment with
a script should not be a problem anymore.
I have got a patch for Plugin-Builder plugins which adds a plugin_upload.py
script (using repo API), and a
Hi Maxim
On Sat, Jan 14, 2012 at 11:00 PM, Maxim Dubinin s...@gis-lab.info wrote:
We've been asked why don't we move our plugins to official repo. The
reason is that autopackaging is unavailable. We maintain 16 plugins
and it will be a pain to switch to manual. If someone doesn't like the
MD On Sat, Jan 14, 2012 at 11:00 PM, Maxim Dubinin s...@gis-lab.info wrote:
We've been asked why don't we move our plugins to official repo. The
reason is that autopackaging is unavailable. We maintain 16 plugins
and it will be a pain to switch to manual. If someone doesn't like the
idea
Il 13/01/2012 18:26, Paolo Cavallini ha scritto:
I think we should come out with an unified solution, and make it available in
the
easiest possible way for plugin developers.
Ticket opened:
http://hub.qgis.org/issues/4811
All the best.
--
Paolo Cavallini - Faunalia
www.faunalia.eu
Full
We've been asked why don't we move our plugins to official repo. The
reason is that autopackaging is unavailable. We maintain 16 plugins
and it will be a pain to switch to manual. If someone doesn't like the
idea for some reason, it would make sense to add on/off switch
for
Il 11/01/2012 08:58, Alexander Bruy ha scritto:
Right, there is a simple solution for SVN at GIS-Lab, description can
be found here http://gis-lab.info/qa/qgis-repo-update.html (sorry, only
Russian now, but Google translate available from right panel).
There is another solution for SVN
On Jan 10, 2012, at 8:54 PM, Tim Sutton wrote:
Bash hater :-) Ok yes we could rewrite it in python easily enough I
think. Not sure when I will get around to it.
Regards
Tim
Not me, I use it all the time. But we have to keep your 100,000 Windows users
happy...
-gary
Hi
On Wed, Dec 28, 2011 at 5:15 PM, Paolo Cavallini cavall...@faunalia.it wrote:
8snip-
- also, an autopackaging script should be activated (see other thread)
You mean like this?
https://github.com/timlinux/VectorTransparency/blob/master/release.sh
8snip-
Regards
On Jan 10, 2012, at 10:29 AM, Tim Sutton wrote:
Hi
On Wed, Dec 28, 2011 at 5:15 PM, Paolo Cavallini cavall...@faunalia.it
wrote:
8snip-
- also, an autopackaging script should be activated (see other thread)
You mean like this?
HI
On Wed, Jan 11, 2012 at 2:08 AM, Gary Sherman gsher...@geoapt.com wrote:
On Jan 10, 2012, at 10:29 AM, Tim Sutton wrote:
Hi
On Wed, Dec 28, 2011 at 5:15 PM, Paolo Cavallini cavall...@faunalia.it
wrote:
8snip-
- also, an autopackaging script should be activated (see
Il 11/01/2012 06:54, Tim Sutton ha scritto:
Bash hater :-) Ok yes we could rewrite it in python easily enough I
think. Not sure when I will get around to it.
There are already solutions for this around, at least in Faunalia and GIS-Lab I
think. Please let's share them and come out with a
Right, there is a simple solution for SVN at GIS-Lab, description can
be found here http://gis-lab.info/qa/qgis-repo-update.html (sorry, only
Russian now, but Google translate available from right panel).
There is another solution for SVN published at GIS-Lab blogs [0] (in
Russian). And finally I
Il 28/12/2011 16:15, Paolo Cavallini ha scritto:
Hi all.
I recently realized that even core QGISsers do not have the plugin situation
clear in
mind. No surprise, as I think we all find it quite complex. I think with a
reasonable
effort we can simplify it, with obvious advantages both for
Hi all.
I recently realized that even core QGISsers do not have the plugin situation
clear in
mind. No surprise, as I think we all find it quite complex. I think with a
reasonable
effort we can simplify it, with obvious advantages both for developers and
users.
These are the necessary steps.
+1 on both infrastructure suggestions and guidelines.
Both will help users and developers alike. Users will get more consistent
plugins and they should be able to report bugs/crashes much more easily
than is currently possible.
Developers should get better feedback, nice automation (such as the
On Wed, Dec 28, 2011 at 04:15:05PM +0100, Paolo Cavallini wrote:
- add on individual plugin pages on http://plugins.qgis.org:
...
. user rating
I was thinking that a download count could probably serve as an
automatic user rating indication.
--strk;
,--o-.
| __/ |Thank you
Il 28/12/2011 17:25, Sandro Santilli ha scritto:
I was thinking that a download count could probably serve as an
automatic user rating indication.
downloads are a measure of interest, rating is a measure of appreciation.
a plugin with a very attractive name, who suggests a general use, will
One of the shortcomings is the lack of documentation for individual plugins.
This needs to be addressed since a plugin with no documentation often is not
usable. Some simple plugins can be completely documented in a single line of
description, however, I have found others that require more
Il 28/12/2011 18:32, Gary Sherman ha scritto:
One of the shortcomings is the lack of documentation for individual plugins.
This needs to be addressed since a plugin with no documentation often is not
usable. Some simple plugins can be completely documented in a single line of
description,
19 matches
Mail list logo
