Hi all.
As we have discussed in the HF, it is good to add the plugins of general
use, well written, to master. I would therefore invite the plugin
developers to suggest their plugin for inclusion.
I cast my vote for the Atlas plugin, also as a form of gratitude for our
French hosts, that are greatl
Would moving to master imply a loss of flexibility? I mean, currently
any update/fix to a python plugin
is immediately made available to users. Would moving plugins to master
imply that users have to wait
for the next release or compile themselves?
Agus
El día 15 de abril de 2012 16:23, Paolo Ca
If I understand correctly, after moving to master plugin will
be updated directly in master, as now done with fTools and
GDALTools
2012/4/15 Agustin Lobo :
> Would moving to master imply a loss of flexibility? I mean, currently
> any update/fix to a python plugin
> is immediately made available to
Hi Agustin,
On Sun, Apr 15, 2012 at 1:03 PM, Agustin Lobo wrote:
> Would moving to master imply a loss of flexibility? I mean, currently
> any update/fix to a python plugin
> is immediately made available to users. Would moving plugins to master
> imply that users have to wait
> for the next rel
> This confirms what I've seen in the past: if a core plugin is released via
> a user repository channel, and the user installs it, the installed user
> plugin takes precedence over the core module of the same package name (e.g.
> fTools user plugin is used instead of fTools core plugin).
>
> So,
Hi
On Sun, Apr 15, 2012 at 10:55 PM, Borys Jurgiel wrote:
>> This confirms what I've seen in the past: if a core plugin is released via
>> a user repository channel, and the user installs it, the installed user
>> plugin takes precedence over the core module of the same package name (e.g.
>> fToo
how about creating more dependencies to python-libs, ... by adding
plugins to core? I think this should be taken in focus of this
discussion. IMHO it's not good to add plugins to core that make it
necessary to install e.g. mysql with qgis.
Marco
Am 15.04.2012 22:55, schrieb Borys Jurgiel:
>> This
Marco Bernasocchi (mobile)
http://opengis.ch
On Apr 16, 2012 9:17 AM, "Marco Lechner - FOSSGIS e.V." <
marco.lech...@fossgis.de> wrote:
>
> how about creating more dependencies to python-libs, ... by adding
> plugins to core? I think this should be taken in focus of this
> discussion. IMHO it's not
Am 16.04.2012 09:45, schrieb Marco Bernasocchi:
>
> Marco Bernasocchi (mobile)
> http://opengis.ch
> On Apr 16, 2012 9:17 AM, "Marco Lechner - FOSSGIS e.V."
> mailto:marco.lech...@fossgis.de>> wrote:
> >
> > how about creating more dependencies to python-libs, ... by adding
> > plugins to core? I t
Hi,
+1 from me to include DB Manager plugin
+0 from me to include Atlas plugin
--
Alexander Bruy
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
Il 16/04/2012 10:00, Alexander Bruy ha scritto:
> +1 from me to include DB Manager plugin
> +0 from me to include Atlas plugin
thanks - among other plugins, statist and group statis are of general
use, and I would like to see them in master.
all the best.
--
Paolo Cavallini
See: http://www.faunal
2012/4/16 Paolo Cavallini :
> thanks - among other plugins, statist and group statis are of general
> use, and I would like to see them in master.
> all the best.
Statist has external dependency — matplotlib package (used to build
histogram). Maybe it is better to rewrite in C++ and use QWT for
gr
Il 16/04/2012 10:21, Alexander Bruy ha scritto:
>
> Statist has external dependency — matplotlib package (used to build
> histogram). Maybe it is better to rewrite in C++ and use QWT for
> graphics?
in any case, integrating group stats is a must
all the best.
--
Paolo Cavallini
See: http://www.fa
I think there are 2 different issues here:
1. The functionality of a given plugin should be in QGIS core
2. An specific plugin, covering a core functionality, fulfills the
requirements to be in QGIS core
We should agree on a list for 1 and a set of criteria for 2
The criteria for 2 could be, at le
On Mon, Apr 16, 2012 at 7:18 PM, Agustin Lobo wrote:
> I think there are 2 different issues here:
> 1. The functionality of a given plugin should be in QGIS core
> 2. An specific plugin, covering a core functionality, fulfills the
> requirements to be in QGIS core
>
> We should agree on a list for
15 matches
Mail list logo
