[Qgis-developer] Thank you all for the great HF!!

[Alessandro Pasotti]

Hi,

I wish to thank everybody for the great organization, it was nice to meet
you again, I'm just sorry I couldn't greet everybody of you before leaving
(too much beer and too late ;)


-- 
Alessandro Pasotti
w3:   www.itopen.it
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Thank you all for the great HF!!

[Werner Macho]

Hi!

I have to say .. Same from me
Thanks for the great Hackfest and the nice discussions - I think we all did
a huge step forward in the right direction.
It was greatly organized and I had a lot of fun finding my way home with
Radim in the night. :)
Special thanks to Matthias for his prompt reaction on every "problem" I
found in his branch :)
And as Alessandro already said .. Sorry for not saying goodbye to everybody
.. I also had to leave early.
Somebody kept me drinking beer .. You know who you are.

Hope to see you all next time!

Just to be sure that work on the new webpage will not get lost I attach the
3 main "topics" we decided in Freemind format to be further discussed and -
converted to a nice looking webpage.

regards
Werner


On Mon, Apr 15, 2013 at 9:20 AM, Alessandro Pasotti wrote:

> Hi,
>
> I wish to thank everybody for the great organization, it was nice to meet
> you again, I'm just sorry I couldn't greet everybody of you before leaving
> (too much beer and too late ;)
>
>
> --
> Alessandro Pasotti
> w3:   www.itopen.it
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>


QGIS_Webpage_structure.mm
Description: Binary data
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Missing plugins

[Alexander Bruy]

Hi Paolo,

note that AutoGCP plugin needs also QGIS with AutoGCP library
bundled. This library is unmaintained now and original authors have
no plans to support it.

We tried to adopt this plugin and library to latest QGIS with some
success. But also have no resources to fix existing bugs and
maintain its code.

Moreover similar functionality (image coregistration) now available
in GDAL. It requires some work and improvement but IMO it is much
better to use GDAL than another 3rd party library. Maybe AutoGCP
plugin should be dropped and new one, linked with GDAL should be
developed (maybe based on existing code).

On Sat, 13 Apr 2013 16:52:46 +0200
Paolo Cavallini  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Hi all.
> This is a list of the plugins available only in the old repo, after
> removing those who are superseded by others or otherwise useless:
> 
> AutoGCP 0.5

-- 
Alexander Bruy
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Wiki cleanup

[Werner Macho]

Hi paolo!

well - there should be a release checklist - just to have a list to hold on
to ..
but I guess we would only need one that could be copied and
extended/adjusted as the release cycle is not a fixed one.

You'd have to ask Tim if he'd like to keep the old things - but for me they
are only there for "historical" purposes and can be deleted.
(As long as we have the newest version somewhere)
Probably the latest announcement should also stay (older ones apply to the
same things as above)

But as I am writing this - It could be probably nice to have some kind of
historic page .. but again .. there is already the wikipedia page about
QGIS where all release dates are written .. so .. I'd delete those old
pages of our own wiki ..

kind regards
Werner



On Sun, Apr 14, 2013 at 12:53 PM, Paolo Cavallini wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Il 14/04/2013 12:30, Werner Macho ha scritto:
> > Hi In my opinion we should just sum up those information.. Merge
> > all similar parts to have one (and probably the newest)
> > information. Make the information "timeless" and delete all old
> > parts.. So it's somehow consolidating and getting rid of old and
> > useless things.
>
> Agreed: would you classify e.g. release checklist and announcements as
> old and useless? Should I delete them, or?
> All the best.
> - --
> Paolo Cavallini - Faunalia
> www.faunalia.eu
> Full contact details at www.faunalia.eu/pc
> Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.12 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAlFqipoACgkQ/NedwLUzIr6U9wCeISS5YLEvSvob66rninYF4hwJ
> Ep8AoIhbqTMig52/TvB4MgjRysjoJJ30
> =Qu+F
> -END PGP SIGNATURE-
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Thank you all for the great HF!!

[Victor Olaya]

I agree 100%. Awesome hackfest, and great organization. You did a
great job organizing this. I am looking forward to participating in
the next hackfest :-)

Cheers
Victor

2013/4/15 Werner Macho :
> Hi!
>
> I have to say .. Same from me
> Thanks for the great Hackfest and the nice discussions - I think we all did
> a huge step forward in the right direction.
> It was greatly organized and I had a lot of fun finding my way home with
> Radim in the night. :)
> Special thanks to Matthias for his prompt reaction on every "problem" I
> found in his branch :)
> And as Alessandro already said .. Sorry for not saying goodbye to everybody
> .. I also had to leave early.
> Somebody kept me drinking beer .. You know who you are.
>
> Hope to see you all next time!
>
> Just to be sure that work on the new webpage will not get lost I attach the
> 3 main "topics" we decided in Freemind format to be further discussed and -
> converted to a nice looking webpage.
>
> regards
> Werner
>
>
> On Mon, Apr 15, 2013 at 9:20 AM, Alessandro Pasotti 
> wrote:
>>
>> Hi,
>>
>> I wish to thank everybody for the great organization, it was nice to meet
>> you again, I'm just sorry I couldn't greet everybody of you before leaving
>> (too much beer and too late ;)
>>
>>
>> --
>> Alessandro Pasotti
>> w3:   www.itopen.it
>>
>> ___
>> Qgis-developer mailing list
>> Qgis-developer@lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] value tool plugin error

[skampus]

Issue #7617 has been reported by stefano campus. 


Bug #7617: Python error
Author: stefano campus 
Status: New 
Priority: Normal 
Assigned to: 
Category: 
Target version: 
Patch supplied: No 
Value tool version: 0.5.3 on qgis master Errore durante l'esecuzione di
codice Python: cfe43dc

Errore durante l'esecuzione di codice Python:

Traceback (most recent call last):
File "C:\Users\skampus/.qgis2/python/plugins\valuetool\valuewidget.py", line
359, in printValue
if layer.dataProvider().isNoDataValue ( iband, doubleValue ):
AttributeError: 'QgsRasterDataProvider' object has no attribute
'isNoDataValue'

Versione Python:
2.7.2 (default, Jun 12 2011, 15:08:59) [MSC v.1500 32 bit (Intel)]

Versione di QGIS:
1.9.0-Master Master, cfe43dc





--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/value-tool-plugin-error-tp5046974.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] value tool plugin error

[skampus]

bug reported in "User Plugins » Valuetool"...



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/value-tool-plugin-error-tp5046974p5046976.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Python Documentation

[Matthias Kuhn]

Hi all,

As already mentioned at the Hackfest, I would really like to see a
Python API documentation.

At the moment, there is only the standard API documentation available,
which lists lots of functions, which are available for core development
only, sometimes the signature is not the same (e.g. a method might
return a tuple for two return values in python and take a reference
where it will write the result value into in C++) and it can be, that
some python-specific accessors are available (e.g. attributes as a dict,
constructor as __init__ )

This does not make it very easy to develop python plugins (I'm sometimes
reading sip-Files to know, what I'm supposed to do).

I would propose, we add a second API documentation, targeted at python
developers. I tried today to compile a python API with doxygen from the
sip files. This kind of works and lists only the methods which are
really available, but still in a C++ style (you shouldn't know if it's a
pointer, reference or whatsoever in python). Of course all this stuff
could also be described in the comments, but it would be nice to have
something like the PyQt documentation [1]

Does anybody know, how to produce such an output?
And would there be somebody willing to take over the lead and/or
maintenance for this? It would be a nice thing to have for the plugin
community.

Best regards,
Matthias

http://pyqt.sourceforge.net/Docs/PyQt4/classes.html
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] [Qgis-user] [Qgis-psc] Logo

[Antonio Locandro]

>From the logos so far I would vote for #64 or #50, I guess #50 Works better 
>for me it looks a Little better looking the spacing of the letters, but that 
>can be refined in #64, also I like a bit more the tone for #50 plus I like the 
>idea #55 of T-shirt for the Project

Would you consider eliminating  the worst looking ones my vote for worst are 
#134 #121 #105 #82 #81 #79 #67 #68 #74 #66 #40 #41 #34 #35 #37 #38 #13 #6 #5 I 
would like to see #64 with a globe within the "Q" very light colors, just to 
see it that could work #91 for some reason it quite doesn't looks so good the 
marker withing the Q, looks a Little bit off for me Just my thoughts
 
  ___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] [Qgis-user] [Qgis-psc] Logo

[Larry Shaffer]

Hi Nathan,

On Sun, Apr 14, 2013 at 11:43 PM, Nathan Woodrow wrote:

> What do people think of
> http://99designs.com.au/logo-design/contests/qgis-needs-logo-210397/entries/115
>  and
> http://99designs.com.au/logo-design/contests/qgis-needs-logo-210397/entries/117
>

Well, I don't like it. First off, I don't get it. At a glance, I have no
idea what it's trying to convey or why there is so much text.

Secondly, I think it is imperative for a logo design to offer a shortened
square aspect, e.g. for an icon. The Q in QGIS obviously lends itself to
this, and IMO works well for it; so I think a design that leverages that
single character will be more versatile, than say one that only works well
for a web site header.

Regards,

Larry



> On Mon, Apr 15, 2013 at 3:32 PM, Paolo Cavallini wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Il 15/04/2013 03:14, Nathan Woodrow ha scritto:
>> > Hey All,
>>
>> >
>> http://99designs.com.au/logo-design/contests/qgis-needs-logo-210397/entries/64
>>
>> In
>> >
>> this case the logo as we use it now would be the "Q", that is a
>> black circle with the green arrow, right?
>> Thanks Nathan for managing this.
>> All the best.
>> - --
>> Paolo Cavallini - Faunalia
>> www.faunalia.eu
>> Full contact details at www.faunalia.eu/pc
>> Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
>> -BEGIN PGP SIGNATURE-
>> Version: GnuPG v1.4.12 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>
>> iEYEARECAAYFAlFrkP4ACgkQ/NedwLUzIr5+wgCePXM1yyku1L6tiV58VMljNQpH
>> jnUAnjee/MUuExfhmbo2U11nhrbzRwfG
>> =QeyB
>> -END PGP SIGNATURE-
>> ___
>> Qgis-developer mailing list
>> Qgis-developer@lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Distance Matrix tool doesn't work in master

[Anita Graser]

Hi,

There is a regression in the Distance Matrix tool:  
http://hub.qgis.org/issues/7618


It only calculates distances for the first point in the layer. It works  
fine in 1.8.


Best wishes,
Anita
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] [Qgis-user] [Qgis-psc] Logo

[Tim Sutton]

Hi



On Mon, Apr 15, 2013 at 10:52 PM, Larry Shaffer  wrote:
> Hi Nathan,
>
> On Sun, Apr 14, 2013 at 11:43 PM, Nathan Woodrow 
> wrote:
>>
>> What do people think of
>> http://99designs.com.au/logo-design/contests/qgis-needs-logo-210397/entries/115
>> and
>> http://99designs.com.au/logo-design/contests/qgis-needs-logo-210397/entries/117
>
>
> Well, I don't like it. First off, I don't get it. At a glance, I have no
> idea what it's trying to convey or why there is so much text.
>
> Secondly, I think it is imperative for a logo design to offer a shortened
> square aspect, e.g. for an icon. The Q in QGIS obviously lends itself to
> this, and IMO works well for it; so I think a design that leverages that
> single character will be more versatile, than say one that only works well
> for a web site header.
>

Here is my doodle at a Q based logo that is round and will work well
in such contexts:

https://plus.google.com/u/0/101650015976513787909/posts/1XkMMsEMV6m

Regards

Tim

> Regards,
>
> Larry
>
>
>>
>> On Mon, Apr 15, 2013 at 3:32 PM, Paolo Cavallini 
>> wrote:
>>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> Il 15/04/2013 03:14, Nathan Woodrow ha scritto:
>>> > Hey All,
>>>
>>> >
>>> > http://99designs.com.au/logo-design/contests/qgis-needs-logo-210397/entries/64
>>>
>>> In
>>> >
>>> this case the logo as we use it now would be the "Q", that is a
>>> black circle with the green arrow, right?
>>> Thanks Nathan for managing this.
>>> All the best.
>>> - --
>>> Paolo Cavallini - Faunalia
>>> www.faunalia.eu
>>> Full contact details at www.faunalia.eu/pc
>>> Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
>>> -BEGIN PGP SIGNATURE-
>>> Version: GnuPG v1.4.12 (GNU/Linux)
>>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>>
>>> iEYEARECAAYFAlFrkP4ACgkQ/NedwLUzIr5+wgCePXM1yyku1L6tiV58VMljNQpH
>>> jnUAnjee/MUuExfhmbo2U11nhrbzRwfG
>>> =QeyB
>>> -END PGP SIGNATURE-
>>> ___
>>> Qgis-developer mailing list
>>> Qgis-developer@lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>>
>>
>> ___
>> Qgis-developer mailing list
>> Qgis-developer@lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>



--
Tim Sutton - QGIS Project Steering Committee Member (Release  Manager)
==
Please do not email me off-list with technical
support questions. Using the lists will gain
more exposure for your issues and the knowledge
surrounding your issue will be shared with all.

Visit http://linfiniti.com to find out about:
 * QGIS programming and support services
 * Mapserver and PostGIS based hosting plans
 * FOSS Consulting Services
Skype: timlinux
Irc: timlinux on #qgis at freenode.net
==
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Thank you all for the great HF!!

[Tim Sutton]

Hi

Could someone write up a blog post or similar highlighting the key
activities that happened at the hackfest? Us poor souls who were not
there are starved for details :-)

Regards

Tim

On Mon, Apr 15, 2013 at 3:26 PM, Victor Olaya  wrote:
> I agree 100%. Awesome hackfest, and great organization. You did a
> great job organizing this. I am looking forward to participating in
> the next hackfest :-)
>
> Cheers
> Victor
>
> 2013/4/15 Werner Macho :
>> Hi!
>>
>> I have to say .. Same from me
>> Thanks for the great Hackfest and the nice discussions - I think we all did
>> a huge step forward in the right direction.
>> It was greatly organized and I had a lot of fun finding my way home with
>> Radim in the night. :)
>> Special thanks to Matthias for his prompt reaction on every "problem" I
>> found in his branch :)
>> And as Alessandro already said .. Sorry for not saying goodbye to everybody
>> .. I also had to leave early.
>> Somebody kept me drinking beer .. You know who you are.
>>
>> Hope to see you all next time!
>>
>> Just to be sure that work on the new webpage will not get lost I attach the
>> 3 main "topics" we decided in Freemind format to be further discussed and -
>> converted to a nice looking webpage.
>>
>> regards
>> Werner
>>
>>
>> On Mon, Apr 15, 2013 at 9:20 AM, Alessandro Pasotti 
>> wrote:
>>>
>>> Hi,
>>>
>>> I wish to thank everybody for the great organization, it was nice to meet
>>> you again, I'm just sorry I couldn't greet everybody of you before leaving
>>> (too much beer and too late ;)
>>>
>>>
>>> --
>>> Alessandro Pasotti
>>> w3:   www.itopen.it
>>>
>>> ___
>>> Qgis-developer mailing list
>>> Qgis-developer@lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>>
>>
>>
>> ___
>> Qgis-developer mailing list
>> Qgis-developer@lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer



-- 
Tim Sutton - QGIS Project Steering Committee Member (Release  Manager)
==
Please do not email me off-list with technical
support questions. Using the lists will gain
more exposure for your issues and the knowledge
surrounding your issue will be shared with all.

Visit http://linfiniti.com to find out about:
 * QGIS programming and support services
 * Mapserver and PostGIS based hosting plans
 * FOSS Consulting Services
Skype: timlinux
Irc: timlinux on #qgis at freenode.net
==
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Postponement of 2.0 API freeze until April 22

[Tim Sutton]

Hi All

According to our release roadmap (see below) we should be entering API
freeze today. However there are some bad inconsistencies in the API.
Here is an example from QgsCoordinateTransform:

['ForwardTransform', 'ReverseTransform', 'TransformDirection',
'__class__', '__delattr__', '__dict__', '__doc__', '__format__',
'__getattr__', '__getattribute__', '__hash__', '__init__',
'__module__', '__new__', '__reduce__', '__reduce_ex__', '__repr__',
'__setattr__', '__sizeof__', '__str__', '__subclasshook__',
'__weakref__', 'blockSignals', 'childEvent', 'children', 'connect',
'connectNotify', 'customEvent', 'deleteLater', 'destCRS', 'destroyed',
'disconnect', 'disconnectNotify', 'dumpObjectInfo', 'dumpObjectTree',
'dynamicPropertyNames', 'emit', 'event', 'eventFilter', 'findChild',
'findChildren', 'inherits', 'initialise', 'installEventFilter',
'invalidTransformInput', 'isInitialised', 'isShortCircuited',
'isWidgetType', 'killTimer', 'metaObject', 'moveToThread',
'objectName', 'parent', 'property', 'pyqtConfigure', 'readXML',
'receivers', 'removeEventFilter', 'sender', 'senderSignalIndex',
'setDestCRS', 'setDestCRSID', 'setObjectName', 'setParent',
'setProperty', 'setSourceCrs', 'signalsBlocked', 'sourceCrs',
'startTimer', 'staticMetaObject', 'thread', 'timerEvent', 'tr',
'trUtf8', 'transform', 'transformBoundingBox', 'transformCoords',
'transformInPlace', 'writeXML']


So we have setSourceCrs and setDestCRS - pretty much conforming to the
principle of *most* surprise. I just mention this as an example to go
along with this appeal: Lets extend the API freeze until the 22nd and
spend a few days going over your favourite classes to make sure the
public API is logical and consistent, otherwise we are going to be
stuck making band aid fixes for the next 5 years :-P

Updated roadmap:


1 April 2013 - Feature freeze - no new features in master.
22 April 2013 - API Freeze - no changes to API except where it is in
direct response to broken functionality.
30 April - GUI Freeze and String freeze - no changes to ui or strings
except where required for critical bug fixes. Call for translations.
1 June 2013 - Branch 2.0, code freeze (except for packaging related
changes), call for packaging.
7 June 2013 - Public release of 2.0

Regards



--
Tim Sutton - QGIS Project Steering Committee Member (Release  Manager)
==
Please do not email me off-list with technical
support questions. Using the lists will gain
more exposure for your issues and the knowledge
surrounding your issue will be shared with all.

Visit http://linfiniti.com to find out about:
 * QGIS programming and support services
 * Mapserver and PostGIS based hosting plans
 * FOSS Consulting Services
Skype: timlinux
Irc: timlinux on #qgis at freenode.net
==
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Thank you all for the great HF!!

[Pēteris Brūns]

Hi all!

Thanks a lot for 100% positive feedback. It was realy great to host such 
event with so much great people.

We hope to join you all next time already in another role!

Regards,
--
pb

On 2013.04.15. 20:19, Tim Sutton wrote:

Hi

Could someone write up a blog post or similar highlighting the key
activities that happened at the hackfest? Us poor souls who were not
there are starved for details :-)

Regards

Tim

On Mon, Apr 15, 2013 at 3:26 PM, Victor Olaya  wrote:

I agree 100%. Awesome hackfest, and great organization. You did a
great job organizing this. I am looking forward to participating in
the next hackfest :-)

Cheers
Victor

2013/4/15 Werner Macho :

Hi!

I have to say .. Same from me
Thanks for the great Hackfest and the nice discussions - I think we all did
a huge step forward in the right direction.
It was greatly organized and I had a lot of fun finding my way home with
Radim in the night. :)
Special thanks to Matthias for his prompt reaction on every "problem" I
found in his branch :)
And as Alessandro already said .. Sorry for not saying goodbye to everybody
.. I also had to leave early.
Somebody kept me drinking beer .. You know who you are.

Hope to see you all next time!

Just to be sure that work on the new webpage will not get lost I attach the
3 main "topics" we decided in Freemind format to be further discussed and -
converted to a nice looking webpage.

regards
Werner


On Mon, Apr 15, 2013 at 9:20 AM, Alessandro Pasotti 
wrote:

Hi,

I wish to thank everybody for the great organization, it was nice to meet
you again, I'm just sorry I couldn't greet everybody of you before leaving
(too much beer and too late ;)


--
Alessandro Pasotti
w3:   www.itopen.it

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer



___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer


___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer




___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] [Qgis-user] [Qgis-psc] Logo

[Barry Rowlingson]

One thing about this logo is to make sure it doesn't look anything
like any other existing mappy s/w logos or any other product with
"Quantum" in the name. Doing a google image search for "Quantum logo"
will show you about 200 different corporate logos with 'Quantum' in
the name!

Barry


On Mon, Apr 15, 2013 at 6:18 PM, Tim Sutton  wrote:
> Hi
>
>
>
> On Mon, Apr 15, 2013 at 10:52 PM, Larry Shaffer  
> wrote:
>> Hi Nathan,
>>
>> On Sun, Apr 14, 2013 at 11:43 PM, Nathan Woodrow 
>> wrote:
>>>
>>> What do people think of
>>> http://99designs.com.au/logo-design/contests/qgis-needs-logo-210397/entries/115
>>> and
>>> http://99designs.com.au/logo-design/contests/qgis-needs-logo-210397/entries/117
>>
>>
>> Well, I don't like it. First off, I don't get it. At a glance, I have no
>> idea what it's trying to convey or why there is so much text.
>>
>> Secondly, I think it is imperative for a logo design to offer a shortened
>> square aspect, e.g. for an icon. The Q in QGIS obviously lends itself to
>> this, and IMO works well for it; so I think a design that leverages that
>> single character will be more versatile, than say one that only works well
>> for a web site header.
>>
>
> Here is my doodle at a Q based logo that is round and will work well
> in such contexts:
>
> https://plus.google.com/u/0/101650015976513787909/posts/1XkMMsEMV6m
>
> Regards
>
> Tim
>
>> Regards,
>>
>> Larry
>>
>>
>>>
>>> On Mon, Apr 15, 2013 at 3:32 PM, Paolo Cavallini 
>>> wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Il 15/04/2013 03:14, Nathan Woodrow ha scritto:
 > Hey All,

 >
 > http://99designs.com.au/logo-design/contests/qgis-needs-logo-210397/entries/64

 In
 >
 this case the logo as we use it now would be the "Q", that is a
 black circle with the green arrow, right?
 Thanks Nathan for managing this.
 All the best.
 - --
 Paolo Cavallini - Faunalia
 www.faunalia.eu
 Full contact details at www.faunalia.eu/pc
 Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.12 (GNU/Linux)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

 iEYEARECAAYFAlFrkP4ACgkQ/NedwLUzIr5+wgCePXM1yyku1L6tiV58VMljNQpH
 jnUAnjee/MUuExfhmbo2U11nhrbzRwfG
 =QeyB
 -END PGP SIGNATURE-
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>>
>>>
>>>
>>> ___
>>> Qgis-developer mailing list
>>> Qgis-developer@lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>>
>>
>>
>> ___
>> Qgis-developer mailing list
>> Qgis-developer@lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>
>
>
> --
> Tim Sutton - QGIS Project Steering Committee Member (Release  Manager)
> ==
> Please do not email me off-list with technical
> support questions. Using the lists will gain
> more exposure for your issues and the knowledge
> surrounding your issue will be shared with all.
>
> Visit http://linfiniti.com to find out about:
>  * QGIS programming and support services
>  * Mapserver and PostGIS based hosting plans
>  * FOSS Consulting Services
> Skype: timlinux
> Irc: timlinux on #qgis at freenode.net
> ==
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Is ftools Union broken?

[Anita Graser]

Hi,

Ftools Union seems broken in Master. The resulting layer does not contain  
areas which are only covered by the second layer. The attribute table is  
also messed up. Can you confirm?


Best wishes,
Anita
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Is ftools Union broken?

[Werner Macho]

Iirc there is already a patch in github
Am 15.04.2013 21:39 schrieb "Anita Graser" :

> Hi,
>
> Ftools Union seems broken in Master. The resulting layer does not contain
> areas which are only covered by the second layer. The attribute table is
> also messed up. Can you confirm?
>
> Best wishes,
> Anita
> __**_
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/**mailman/listinfo/qgis-**developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] unpack error in Sextante Raster Layer Statistics

[Anita Graser]

Hi, I've tried different raster layers, but in all cases Sextante raster  
layer statistics fails with:


Traceback (most recent call last):
  File  
"C:\OSGeo4W\apps\qgis-dev\python\plugins\sextante\core\GeoAlgorithm.py",  
line 147, in execute

self.processAlgorithm(progress)
  File  
"C:\OSGeo4W\apps\qgis-dev\python\plugins\sextante\algs\RasterLayerStatistics.py",  
line 64, in processAlgorithm

for v in values:
  File "C:\OSGeo4W\apps\qgis-dev\python\plugins\sextante\tools\raster.py",  
line 38, in scanraster

values = struct.unpack('f' * band.XSize, scanline)
error: unpack requires a string argument of length 7016

Should I file a ticket?

Anita
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Error in Sextante Distance Matrix

[Anita Graser]

Hi,

Sextante distance matrix in nightly fails with:

Traceback (most recent call last):
  File  
"C:\OSGeo4W\apps\qgis-dev\python\plugins\sextante\core\GeoAlgorithm.py",  
line 147, in execute

self.processAlgorithm(progress)
  File  
"C:\OSGeo4W\apps\qgis-dev\python\plugins\sextante\algs\ftools\PointDistance.py",  
line 98, in processAlgorithm
self.regularMatrix(inLayer, inField, targetLayer, targetField,  
nPoints, progress)
  File  
"C:\OSGeo4W\apps\qgis-dev\python\plugins\sextante\algs\ftools\PointDistance.py",  
line 166, in regularMatrix

total = 100.0 / float(features)
AttributeError: Features instance has no attribute '__float__'

Should i file a ticket?

Anita
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] unpack error in Sextante Raster Layer Statistics

[Pedro Venâncio]

Hi Anita,

Not confirmed here on Linux, with QGIS master just compiled.

Regards,
Pedro





- Original Message -
From: Anita Graser 

Hi, I've tried different raster layers, but in all cases Sextante raster  
layer statistics fails with:

Traceback (most recent call last):
   File  
"C:\OSGeo4W\apps\qgis-dev\python\plugins\sextante\core\GeoAlgorithm.py",  
line 147, in execute
     self.processAlgorithm(progress)
   File  
"C:\OSGeo4W\apps\qgis-dev\python\plugins\sextante\algs\RasterLayerStatistics.py",
  
line 64, in processAlgorithm
     for v in values:
   File "C:\OSGeo4W\apps\qgis-dev\python\plugins\sextante\tools\raster.py",  
line 38, in scanraster
     values = struct.unpack('f' * band.XSize, scanline)
error: unpack requires a string argument of length 7016

Should I file a ticket?

Anita
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] [Python] QgsFeatureIterator for geometryless PostgreSQL-Layer

[Martin Dobias]

On Fri, Apr 12, 2013 at 10:33 AM, Jürgen E.  wrote:
>> Recently I have been wondering whether it would not be better to
>> actually stop using flags and replace them by usual getter/setter
>> functions. My main concern is the setSubsetOfAttributes() function: it
>> also sets the flag, so the users may end up with a weird behavior,
>> e.g.:
>> QgsFeatureRequest().setSubsetOfAttributes( ["name","type"], fields
>> ).setFlags( NoGeometry )
>> That would fetch all attributes... because the setFlags overrides the
>> previously set SubsetOfAttributes flag.
>
> Yes, I've also thought about that, but somehow missed to speak up - but IIRC
> (;)) I migrated everything accordingly.
>
> Given that the flags need qualification it's even shorter to use the
> getter/setters API-wise.

That's right.
Thinking about it again, we should really fix the API before 2.0. It
seems you have ported that correctly (btw. many thanks for that!), but
ordinary users that do not read c++ code will sooner or later struggle
with it. I'm adding that to my todo list :-)


>> Also, the way how things are done right now, providers need to
>> implement fetching of attributes in this way (pseudo-code):
>> if using subset of attributes:
>>   for each attribute from subset:
>> fetch attribute
>> else:
>>   for each attribute from provider:
>> fetch attribute
>
>> This is quite annoying, we should probably have a simple array where
>> each value would indicate whether to fetch attribute with that index
>> or not (by default all values would be true). The fetching would be
>> simplified to:
>> for each attribute from provider:
>>   if attribute should be fetched:
>> fetch attribute
>
>> What do you think? :-)
>
> Don't they just all do:
>
> subsetOfAttributes ? mRequest.subsetOfAttributes() : P->attributeIndexes()

Not really. Usually there's the kind of code I have mentioned above.
In theory we could change it to use the attributeIndexes() call.

> Can't we move that to a requestedAttributes() in QgsAbstractFeatureIterator 
> and
> just iterate over the result?

Yes we can :-)


> BTW what about parallel iterators?  I suppose there were problems and thats 
> why
> you added the "active iterators" - do you recall which providers were affected
> and how?

I have modified providers to have pointers to active iterators because
of two reasons:
1. if the user asks for a second iterator and the provider does not
support multiple iterators, the first one has to be closed - they
would not behave correctly if used together
2. if the layer is deleted for whatever reason, we must ensure that
any iterators that may still exist will be closed - they would cause
crashes otherwise

As of now, all providers support only one iterator per provider
instance. For parallel iterators (N iterators, one thread) we could
have a provider capability indicating whether they are supported or
not. Providers supporting parallel iterators would not close the
previously active iterators - instead they would only keep them in the
list of active iterators.

When we add multi-threaded rendering, things will get a bit more
complex. Providers allowing parallel iterators should be fine - they
will just need some locking of the list of active iterators. There
will be a slight problem with providers allowing just one iterator: in
a different thread we cannot simply close the currently active
iterator (from a different thread) as that would be a run condition. I
guess we will have to define the behavior in the following way - when
the provider is asked for a new iterator, it will:
a. wait for the active iterator to get closed - if it comes from a
different thread
b. close the old iterator - in case it comes from the same thread
This should ensure that the rendering (or processing) thread will wait
until GUI thread finishes what it wants (and vice versa), while still
keeping the current behavior when dealing with only one thread. We
will just need to explicitly assign iterators with the threads that
asks for them.
Btw. the case b is really just a sanity check for invalid code - it
should not happen in production environment - if it does, there is
something wrong with the application logic.

Maybe during the porting of providers to support multi-threaded
environment we will find out that it will be easier to simply update
all providers to allow multiple iterators instead of adding the
support for the case of N threads and one iterator - that is yet
something that needs investigation.

Regards
Martin
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] problem with feature request and updateFeature

[Martin Dobias]

Going back to the older thread

On Sat, Mar 23, 2013 at 7:19 PM, Jürgen E.  wrote:
> On Sat, 23. Mar 2013 at 09:49:28 +1000, Nathan Woodrow wrote:
>> Well the feature itself knows what values it started with. Every update in
>> QgsFeature goes though the setAttribute, etc, call, you can just have an
>> internal dictionary that logs when one of values is changed using those
>> methods.
>
> Sure, you could do that.  But what for?  Just for updateFeature?  That method
> is not even used anywhere.
>
> And one instance of QgsFeature is often used as buffer, so the tracking would
> have to be reset at some point (setValid? setFeatureId?).
>
> IMHO one needs to be aware that currently multiple iterators are not working
> for now.  Maybe Martin can comment on this - I guess he has plans continue to
> work on this and the current state is for the time being.

Maybe we should simply remove the updateFeature() function (or at
least clearly document the side effect of issuing a request to the
provider). Because of that request, even if the function worked in the
nextFeature() loop, it would be highly inefficient to update features
in such loop due to the many separate queries to the backend.

Another reason for its removal would be that we do not use it anywhere
in QGIS codebase and it's questionable to what extent it worked before
the new vector API merge. For example, several providers used the same
cursor for featureAtId() and nextFeature(), so the featureAtId() call
during nextFeature() loop would re-create the cursor. Moreover,
although OGR has a separate API calls for featureAtId(), OGR drivers
that do not have efficient implementation of "get-feature-at-id" will
simply fall back to internal "get-next-feature" loop, invalidating the
reading state of nextFeature() loop.

I have commented on multiple iterators in the other thread.

Martin
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Remove editing functions from QgsVectorLayer

[Martin Dobias]

Hi

right now, all the basic vector layer editing operations are
implemented within QgsVectorLayerEditBuffer class and the "advanced"
operations (composed of one or more basic operations) are implemented
in QgsVectorLayerEditUtils class. The main class, QgsVectorLayer still
contains editing functions and only proxies them to these new classes.

I think we should probably remove those editing functions from
QgsVectorLayer. The advantage should be two-fold:
1. fewer functions -> easier to grasp and understand the class
2. sometimes people try to call editing functions without editing mode
being turned on: these issues should go away since they would quickly
find out that QgsVectorLayerEditBuffer does not exist if editing is
not turned on.

>From the editing functions we would keep only startEditing(),
commitChanges(), commitErrors(), rollback() as they take care of edit
buffer management. The rest of the functions (addFeatures(),
changeGeometry() etc) would go to /dev/null.

Any comments / suggestions / objections?

Regards
Martin
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Remove editing functions from QgsVectorLayer

[Nathan Woodrow]

What would be the API calls in order to add a new feature to a layer and
commit the result?

- Nathan


On Tue, Apr 16, 2013 at 8:29 AM, Martin Dobias  wrote:

> Hi
>
> right now, all the basic vector layer editing operations are
> implemented within QgsVectorLayerEditBuffer class and the "advanced"
> operations (composed of one or more basic operations) are implemented
> in QgsVectorLayerEditUtils class. The main class, QgsVectorLayer still
> contains editing functions and only proxies them to these new classes.
>
> I think we should probably remove those editing functions from
> QgsVectorLayer. The advantage should be two-fold:
> 1. fewer functions -> easier to grasp and understand the class
> 2. sometimes people try to call editing functions without editing mode
> being turned on: these issues should go away since they would quickly
> find out that QgsVectorLayerEditBuffer does not exist if editing is
> not turned on.
>
> From the editing functions we would keep only startEditing(),
> commitChanges(), commitErrors(), rollback() as they take care of edit
> buffer management. The rest of the functions (addFeatures(),
> changeGeometry() etc) would go to /dev/null.
>
> Any comments / suggestions / objections?
>
> Regards
> Martin
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] problem with feature request and updateFeature

[Nathan Woodrow]

I asked Jurgen to add the updateFeature a while ago in order to make the
API feel a bit cleaner. My issue was that you could update the attribute
values on the feature but you then still call changeFeatureAttribute for
each attribute which seems really crap.  I really only want to update the
feature and give it to the layer to handle calling the
changeFeatureAttribute calls with the id, index, value stuff.

- Nathan


On Tue, Apr 16, 2013 at 8:13 AM, Martin Dobias  wrote:

> Going back to the older thread
>
> On Sat, Mar 23, 2013 at 7:19 PM, Jürgen E.  wrote:
> > On Sat, 23. Mar 2013 at 09:49:28 +1000, Nathan Woodrow wrote:
> >> Well the feature itself knows what values it started with. Every update
> in
> >> QgsFeature goes though the setAttribute, etc, call, you can just have an
> >> internal dictionary that logs when one of values is changed using those
> >> methods.
> >
> > Sure, you could do that.  But what for?  Just for updateFeature?  That
> method
> > is not even used anywhere.
> >
> > And one instance of QgsFeature is often used as buffer, so the tracking
> would
> > have to be reset at some point (setValid? setFeatureId?).
> >
> > IMHO one needs to be aware that currently multiple iterators are not
> working
> > for now.  Maybe Martin can comment on this - I guess he has plans
> continue to
> > work on this and the current state is for the time being.
>
> Maybe we should simply remove the updateFeature() function (or at
> least clearly document the side effect of issuing a request to the
> provider). Because of that request, even if the function worked in the
> nextFeature() loop, it would be highly inefficient to update features
> in such loop due to the many separate queries to the backend.
>
> Another reason for its removal would be that we do not use it anywhere
> in QGIS codebase and it's questionable to what extent it worked before
> the new vector API merge. For example, several providers used the same
> cursor for featureAtId() and nextFeature(), so the featureAtId() call
> during nextFeature() loop would re-create the cursor. Moreover,
> although OGR has a separate API calls for featureAtId(), OGR drivers
> that do not have efficient implementation of "get-feature-at-id" will
> simply fall back to internal "get-next-feature" loop, invalidating the
> reading state of nextFeature() loop.
>
> I have commented on multiple iterators in the other thread.
>
> Martin
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] [Qgis-user] [Qgis-psc] Logo

[Nathan Woodrow]

Hey Larry,

Thanks for the feedback. I had the same feelings but kind of like the
design, maybe just not for QGIS :)

- Nathan


On Tue, Apr 16, 2013 at 1:52 AM, Larry Shaffer wrote:

> Hi Nathan,
>
> On Sun, Apr 14, 2013 at 11:43 PM, Nathan Woodrow wrote:
>
>> What do people think of
>> http://99designs.com.au/logo-design/contests/qgis-needs-logo-210397/entries/115
>>  and
>> http://99designs.com.au/logo-design/contests/qgis-needs-logo-210397/entries/117
>>
>
> Well, I don't like it. First off, I don't get it. At a glance, I have no
> idea what it's trying to convey or why there is so much text.
>
> Secondly, I think it is imperative for a logo design to offer a shortened
> square aspect, e.g. for an icon. The Q in QGIS obviously lends itself to
> this, and IMO works well for it; so I think a design that leverages that
> single character will be more versatile, than say one that only works well
> for a web site header.
>
> Regards,
>
> Larry
>
>
>
>>  On Mon, Apr 15, 2013 at 3:32 PM, Paolo Cavallini 
>> wrote:
>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> Il 15/04/2013 03:14, Nathan Woodrow ha scritto:
>>> > Hey All,
>>>
>>> >
>>> http://99designs.com.au/logo-design/contests/qgis-needs-logo-210397/entries/64
>>>
>>> In
>>> >
>>> this case the logo as we use it now would be the "Q", that is a
>>> black circle with the green arrow, right?
>>> Thanks Nathan for managing this.
>>> All the best.
>>> - --
>>> Paolo Cavallini - Faunalia
>>> www.faunalia.eu
>>> Full contact details at www.faunalia.eu/pc
>>> Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
>>> -BEGIN PGP SIGNATURE-
>>> Version: GnuPG v1.4.12 (GNU/Linux)
>>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>>
>>> iEYEARECAAYFAlFrkP4ACgkQ/NedwLUzIr5+wgCePXM1yyku1L6tiV58VMljNQpH
>>> jnUAnjee/MUuExfhmbo2U11nhrbzRwfG
>>> =QeyB
>>> -END PGP SIGNATURE-
>>> ___
>>> Qgis-developer mailing list
>>> Qgis-developer@lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>>
>>
>>
>> ___
>> Qgis-developer mailing list
>> Qgis-developer@lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>>
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Icon theme update

[Larry Shaffer]

Hi,

So, I've pushed a large update to master that condenses down the default
icon theme by overriding it with the gis theme (the theme voted to be the
replacement). I apologize if the change is abrupt, but it needed done with
enough time to edit/fix things before 2.0 release.

I did this in the following manner:

1) Copied the gis theme over the default theme. Any files of same name were
replaced, missing files added. The was done for plugins that also managed
icon sets per theme (grass, georeferencer and ftools).

The state of previous icon theme sets and directory structure are preserved
as a download here [0] (saves switching local or browsing online git repo
to find replaced/removed ones). These can be added back to source
directory, for reference, or not.

2) Updated all appropriate .qrc and .ui files that referenced old theme
paths.

3) Switched some icons to improve consistency (mostly to + and - icons for
table widget row editing)

4) Proofed every dialog I could think of, though I'm sure I missed
something. This was from both running from build directory and from
installed app on Mac.

5) Added some code to ensure any old saved theme choice now goes to
default. No theme support code was removed.

6) Updated CMakeList.txt files to ensure SVGs are also copied on install.


Where to go from here:

* Please, let me know if I made a mistake somewhere.

* We now have a single set of icons on which to work and update. Icons
should be updated, especially those that don't match current theme.

* Moving to SVG can be aided by leaving the getThemeIcon/Pixmap calls and
referencing the file by base name, without extension, e.g.
QgsApplication::getThemePixmap( "pie-chart" ). When using this technique,
as soon as a .png is replaced with a .svg in a .qrc resource file, it is
auto-found, without having to edit anymore code. Let me know if this
approach should be used.

[0] http://drive.dakotacarto.com/qgis/QGIS-images_pre-gis-theme-switch.zip

Regards,

Larry
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Icon theme update

[Noli Sicad]

Hi Larry,

What is the summary of this posting?

Does mean that we can use themes in QGIS 2.0?

I like to revive my nkids theme for QGIS 2.0 as option for Mac OS X
QGIS, is this possible?

Thanks.

Noli



On 4/16/13, Larry Shaffer  wrote:
> Hi,
>
> So, I've pushed a large update to master that condenses down the default
> icon theme by overriding it with the gis theme (the theme voted to be the
> replacement). I apologize if the change is abrupt, but it needed done with
> enough time to edit/fix things before 2.0 release.
>
> I did this in the following manner:
>
> 1) Copied the gis theme over the default theme. Any files of same name were
> replaced, missing files added. The was done for plugins that also managed
> icon sets per theme (grass, georeferencer and ftools).
>
> The state of previous icon theme sets and directory structure are preserved
> as a download here [0] (saves switching local or browsing online git repo
> to find replaced/removed ones). These can be added back to source
> directory, for reference, or not.
>
> 2) Updated all appropriate .qrc and .ui files that referenced old theme
> paths.
>
> 3) Switched some icons to improve consistency (mostly to + and - icons for
> table widget row editing)
>
> 4) Proofed every dialog I could think of, though I'm sure I missed
> something. This was from both running from build directory and from
> installed app on Mac.
>
> 5) Added some code to ensure any old saved theme choice now goes to
> default. No theme support code was removed.
>
> 6) Updated CMakeList.txt files to ensure SVGs are also copied on install.
>
>
> Where to go from here:
>
> * Please, let me know if I made a mistake somewhere.
>
> * We now have a single set of icons on which to work and update. Icons
> should be updated, especially those that don't match current theme.
>
> * Moving to SVG can be aided by leaving the getThemeIcon/Pixmap calls and
> referencing the file by base name, without extension, e.g.
> QgsApplication::getThemePixmap( "pie-chart" ). When using this technique,
> as soon as a .png is replaced with a .svg in a .qrc resource file, it is
> auto-found, without having to edit anymore code. Let me know if this
> approach should be used.
>
> [0] http://drive.dakotacarto.com/qgis/QGIS-images_pre-gis-theme-switch.zip
>
> Regards,
>
> Larry
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Hard feature freeze

[Tim Sutton]

Hi Folks

Please note that we now need to go into 'hard feature freeze' - we
need to get teh API neat and tidy and finalise the GUI etc. If you
bring new feature patches (even if they are ready to use), they
represent a distraction from the API, GUI and string cleanup work that
needs to be happening over the next month to get QGIS release ready.

Thanks for your understanding in this.

Regards

Tim

--
Tim Sutton - QGIS Project Steering Committee Member (Release  Manager)
==
Please do not email me off-list with technical
support questions. Using the lists will gain
more exposure for your issues and the knowledge
surrounding your issue will be shared with all.

Visit http://linfiniti.com to find out about:
 * QGIS programming and support services
 * Mapserver and PostGIS based hosting plans
 * FOSS Consulting Services
Skype: timlinux
Irc: timlinux on #qgis at freenode.net
==
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] qgis nightly crashing

[maning sambale]

Updating from latest build today, and everything is working now.  Thanks!

On Mon, Apr 15, 2013 at 9:57 AM, maning sambale
 wrote:
> Hi,
>
> Updating from nightly build in Ubuntu Precise today, I can't load my
> projects.  Even adding a vector layer in a new project makes it crash.
>  The error from terminal is below:
>
> Warning: loading of qt translation failed 
> [/usr/share/qt4/translations/qt_en_PH]
> /usr/bin/qgis.bin: symbol lookup error: /usr/bin/qgis.bin: undefined
> symbol: _ZNK10QgsProject13readListEntryERK7QStringS2_11QStringListPb
>
> Everything worked OK since two days ago.
> --
> cheers,
> maning
> --
> "Freedom is still the most radical idea of all" -N.Branden
> wiki: http://esambale.wikispaces.com/
> blog: http://epsg4253.wordpress.com/
> --



-- 
cheers,
maning
--
"Freedom is still the most radical idea of all" -N.Branden
wiki: http://esambale.wikispaces.com/
blog: http://epsg4253.wordpress.com/
--
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Icon theme update

[Larry Shaffer]

Hi Noli,

On Mon, Apr 15, 2013 at 7:00 PM, Noli Sicad  wrote:

> Hi Larry,
>
> What is the summary of this posting?
>

Some time ago, devs voted to move to the 'gis' theme as the default, i.e.
not just the one selected by default but also the only theme supported by
the project. Even after this update, you may notice the icons are still
hodge-podge with inconsistent ones needing work. Due to lack of developers
to maintain multiple project-supported themes, it is best to have only one,
so that a concerted effort can be made to keep it complete and cohesive.

Does mean that we can use themes in QGIS 2.0?
>

No theme support code was removed, only the gis theme condensed upon the
current default (because many default icons are still used) and old project
themes removed. However, there has been talk of removing all theme support,
but I can't speak to the state of that decision.

I like to revive my nkids theme for QGIS 2.0 as option for Mac OS X
> QGIS, is this possible?
>

I'm not entirely sure, but to use a different theme than the default, you
will need to add it to the appropriate source directories, edit the .qrc
files and compile the source again. For example, nkids has been in the
source themes directory for awhile, but not choose-able in the gui because
it is not been made part of compiled-in resource system.

I did add some code to push any old saved theme choice over to the new
default, so if you did add a revamped nkids theme, maybe considering giving
it a new name as well.


If I am misunderstanding the current state of decisions regarding the move
forward for icon themes, somebody please correct me (see also [0]).

Regards,

Larry

[0] http://hub.qgis.org/issues/7551

Thanks.
>
> Noli
>
>
>
> On 4/16/13, Larry Shaffer  wrote:
> > Hi,
> >
> > So, I've pushed a large update to master that condenses down the default
> > icon theme by overriding it with the gis theme (the theme voted to be the
> > replacement). I apologize if the change is abrupt, but it needed done
> with
> > enough time to edit/fix things before 2.0 release.
> >
> > I did this in the following manner:
> >
> > 1) Copied the gis theme over the default theme. Any files of same name
> were
> > replaced, missing files added. The was done for plugins that also managed
> > icon sets per theme (grass, georeferencer and ftools).
> >
> > The state of previous icon theme sets and directory structure are
> preserved
> > as a download here [0] (saves switching local or browsing online git repo
> > to find replaced/removed ones). These can be added back to source
> > directory, for reference, or not.
> >
> > 2) Updated all appropriate .qrc and .ui files that referenced old theme
> > paths.
> >
> > 3) Switched some icons to improve consistency (mostly to + and - icons
> for
> > table widget row editing)
> >
> > 4) Proofed every dialog I could think of, though I'm sure I missed
> > something. This was from both running from build directory and from
> > installed app on Mac.
> >
> > 5) Added some code to ensure any old saved theme choice now goes to
> > default. No theme support code was removed.
> >
> > 6) Updated CMakeList.txt files to ensure SVGs are also copied on install.
> >
> >
> > Where to go from here:
> >
> > * Please, let me know if I made a mistake somewhere.
> >
> > * We now have a single set of icons on which to work and update. Icons
> > should be updated, especially those that don't match current theme.
> >
> > * Moving to SVG can be aided by leaving the getThemeIcon/Pixmap calls and
> > referencing the file by base name, without extension, e.g.
> > QgsApplication::getThemePixmap( "pie-chart" ). When using this technique,
> > as soon as a .png is replaced with a .svg in a .qrc resource file, it is
> > auto-found, without having to edit anymore code. Let me know if this
> > approach should be used.
> >
> > [0]
> http://drive.dakotacarto.com/qgis/QGIS-images_pre-gis-theme-switch.zip
> >
> > Regards,
> >
> > Larry
> >
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Icon theme update

[Noli Sicad]

Hi Larry,

OK. Thanks for clarification.

I understand the decision to have a one theme. That's is fine.
However, I like to do my own compile version with nkids in Mac OS X
later on. Is it possible. I like to see first are the set of icons
needs to be done.

Thanks.

Noli




On 4/16/13, Larry Shaffer  wrote:
> Hi Noli,
>
> On Mon, Apr 15, 2013 at 7:00 PM, Noli Sicad  wrote:
>
>> Hi Larry,
>>
>> What is the summary of this posting?
>>
>
> Some time ago, devs voted to move to the 'gis' theme as the default, i.e.
> not just the one selected by default but also the only theme supported by
> the project. Even after this update, you may notice the icons are still
> hodge-podge with inconsistent ones needing work. Due to lack of developers
> to maintain multiple project-supported themes, it is best to have only one,
> so that a concerted effort can be made to keep it complete and cohesive.
>
> Does mean that we can use themes in QGIS 2.0?
>>
>
> No theme support code was removed, only the gis theme condensed upon the
> current default (because many default icons are still used) and old project
> themes removed. However, there has been talk of removing all theme support,
> but I can't speak to the state of that decision.
>
> I like to revive my nkids theme for QGIS 2.0 as option for Mac OS X
>> QGIS, is this possible?
>>
>
> I'm not entirely sure, but to use a different theme than the default, you
> will need to add it to the appropriate source directories, edit the .qrc
> files and compile the source again. For example, nkids has been in the
> source themes directory for awhile, but not choose-able in the gui because
> it is not been made part of compiled-in resource system.
>
> I did add some code to push any old saved theme choice over to the new
> default, so if you did add a revamped nkids theme, maybe considering giving
> it a new name as well.
>
>
> If I am misunderstanding the current state of decisions regarding the move
> forward for icon themes, somebody please correct me (see also [0]).
>
> Regards,
>
> Larry
>
> [0] http://hub.qgis.org/issues/7551
>
> Thanks.
>>
>> Noli
>>
>>
>>
>> On 4/16/13, Larry Shaffer  wrote:
>> > Hi,
>> >
>> > So, I've pushed a large update to master that condenses down the
>> > default
>> > icon theme by overriding it with the gis theme (the theme voted to be
>> > the
>> > replacement). I apologize if the change is abrupt, but it needed done
>> with
>> > enough time to edit/fix things before 2.0 release.
>> >
>> > I did this in the following manner:
>> >
>> > 1) Copied the gis theme over the default theme. Any files of same name
>> were
>> > replaced, missing files added. The was done for plugins that also
>> > managed
>> > icon sets per theme (grass, georeferencer and ftools).
>> >
>> > The state of previous icon theme sets and directory structure are
>> preserved
>> > as a download here [0] (saves switching local or browsing online git
>> > repo
>> > to find replaced/removed ones). These can be added back to source
>> > directory, for reference, or not.
>> >
>> > 2) Updated all appropriate .qrc and .ui files that referenced old theme
>> > paths.
>> >
>> > 3) Switched some icons to improve consistency (mostly to + and - icons
>> for
>> > table widget row editing)
>> >
>> > 4) Proofed every dialog I could think of, though I'm sure I missed
>> > something. This was from both running from build directory and from
>> > installed app on Mac.
>> >
>> > 5) Added some code to ensure any old saved theme choice now goes to
>> > default. No theme support code was removed.
>> >
>> > 6) Updated CMakeList.txt files to ensure SVGs are also copied on
>> > install.
>> >
>> >
>> > Where to go from here:
>> >
>> > * Please, let me know if I made a mistake somewhere.
>> >
>> > * We now have a single set of icons on which to work and update. Icons
>> > should be updated, especially those that don't match current theme.
>> >
>> > * Moving to SVG can be aided by leaving the getThemeIcon/Pixmap calls
>> > and
>> > referencing the file by base name, without extension, e.g.
>> > QgsApplication::getThemePixmap( "pie-chart" ). When using this
>> > technique,
>> > as soon as a .png is replaced with a .svg in a .qrc resource file, it
>> > is
>> > auto-found, without having to edit anymore code. Let me know if this
>> > approach should be used.
>> >
>> > [0]
>> http://drive.dakotacarto.com/qgis/QGIS-images_pre-gis-theme-switch.zip
>> >
>> > Regards,
>> >
>> > Larry
>> >
>>
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Is there anybody interested whether QGIS 2.0 will support non-Latin1 Shapefiles?

[Sanghee Shin]

Dear Borys,

Most of all thanks for your efforts. 

Actually that encoding issue highly affected Korean QGIS users badly and 
reduced usability. I'm not a developer, however I can help you by testing and 
giving you test files. Also I'll share your efforts with Korean developers as 
well. 

Thanks again. 

Sanghee

2013. 4. 12., 오후 8:30, Borys Jurgiel  작성:

> Hi All,
> 
> As most of us know, QGIS 1.8 and 1.9 *in fact doesn't support Shapefiles* 
> with 
> encodings other than Latin-1. Assuming that all recent QGIS versions use GDAL 
> 1.9, *the last usable version was 1.7.3* (at least for windows users in 
> Poland). Thanks to the 'ignore shapefile encoding' workaround, QGIS built 
> against GDAL 1.9 is at least able to open other encodings, however, the 'Save 
> layer as' action still creates corrupted files unless you know how to trick 
> the 
> encoding selector as well as the layer creating options.
> 
> From my point of view it's just an *incredible regression*, as QGIS just 
> doesn't support Shapefiles in most languages for a year or so. If there is 
> anybody else interested in bringing back support for at least UTF-8 and 
> cp12xx 
> in QGIS 2.0 plase join me ;)) and review the pull request:
> 
> https://github.com/qgis/Quantum-GIS/pull/492#issuecomment-16282081
> 
> Maybe someone have a better solution? Maybe someone can provide the test 
> files 
> Jürgen suggested? I don't believe nobody cares whether QGIS 2.0 supports not 
> Latin-1 Shapefiles or not.
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] WMS Server plugin

[Marco Hugentobler]

Hi Barry

You can use the QGIS cloud plugin to publish web maps without having 
apache / fcgi server installed on the local machine.


Regards,
Marco

On 14.04.2013 18:21, Barry Rowlingson wrote:

Did I dream it, or was there once a plugin that offered up the layers
of a running Qgis Desktop as a WMS (or some other W?S)?

I was hoping for a lightweight way of offering Qgis maps as a web
service without needing apache and the qgis fcgi map server.

Can't find anything like it now. Did I dream it?

Barry
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer



--
Dr. Marco Hugentobler
Sourcepole -  Linux & Open Source Solutions
Weberstrasse 5, CH-8004 Zürich, Switzerland
marco.hugentob...@sourcepole.ch http://www.sourcepole.ch
Technical Advisor QGIS Project Steering Committee

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Remove editing functions from QgsVectorLayer

[Martin Dobias]

On Tue, Apr 16, 2013 at 12:53 AM, Nathan Woodrow  wrote:
> What would be the API calls in order to add a new feature to a layer and
> commit the result?

layer.startEditing()
layer.editBuffer().addFeature( feature )
layer.commitChanges()

Anyway if someone wants to add a new feature permanently, it should be
rather done this way:
layer.dataProvider().addFeatures( [feature] )
It's more efficient and it does not mess with the editing state of the
layer (imagine you are editing a layer and a plugin action will commit
all your changes without asking!).

Martin
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] problem with feature request and updateFeature

[Martin Dobias]

On Tue, Apr 16, 2013 at 1:01 AM, Nathan Woodrow  wrote:
> I asked Jurgen to add the updateFeature a while ago in order to make the API
> feel a bit cleaner. My issue was that you could update the attribute values
> on the feature but you then still call changeFeatureAttribute for each
> attribute which seems really crap.  I really only want to update the feature
> and give it to the layer to handle calling the changeFeatureAttribute calls
> with the id, index, value stuff.

I understand the motivation, but unless we have change tracking in
QgsFeature there is little sense to keep the function. And as Jürgen
has noted, adding such tracking just for this particular function does
not seem right.

Martin
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Wiki cleanup

[Marco Hugentobler]

Hi Paolo

I've updated the code maintainers list. Is 
https://github.com/qgis/QGIS-Documentation/tree/master/source/docs/qgis_governance 
the right place to add it in the docs?


Regards,
Marco

On 14.04.2013 12:06, Paolo Cavallini wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi all.
I started cleanup of the wiki.
What sould we do with the old, historic material? A number of pages
are about the release checklist and release specifications for old
versions. Moreover, the list is not complete.
I think this is static information of very little practical use, so we
could either remove it from the web (perhaps keeping it somewhere as a
backup text file), or move it to Governance docs.
The problem in keeping it accessible is that users will get confused
by obsolete information.
Please let me know your opinion, so I can do most of the cleanup today.
Not an huge task once we decided the guidelines.
Thanks.
- -- 
Paolo Cavallini - Faunalia

www.faunalia.eu
Full contact details at www.faunalia.eu/pc
Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlFqf6AACgkQ/NedwLUzIr75rwCdEc6na2rIBcqFciT5yoaS/68G
ITAAniIKJPwvDSwupE/5vAsdPgPNlYeG
=UK9G
-END PGP SIGNATURE-
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer



--
Dr. Marco Hugentobler
Sourcepole -  Linux & Open Source Solutions
Weberstrasse 5, CH-8004 Zürich, Switzerland
marco.hugentob...@sourcepole.ch http://www.sourcepole.ch
Technical Advisor QGIS Project Steering Committee

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] [Python] QgsFeatureIterator for geometryless PostgreSQL-Layer

[Jürgen E . Fischer]

Hi Martin,

On Mon, 15. Apr 2013 at 23:45:20 +0200, Martin Dobias wrote:
> > BTW what about parallel iterators?  I suppose there were problems and thats
> > why you added the "active iterators" - do you recall which providers were
> > affected and how?
 
> I have modified providers to have pointers to active iterators because of two
> reasons: 1. if the user asks for a second iterator and the provider does not
> support multiple iterators, the first one has to be closed - they would not
> behave correctly if used together

IMHO that's not ok.  If the provider doesn't support multiple iterators, the
second on should be rejected - forcing the caller to close the other one first.

As we lost the ability to do featureAtId while iterating a layer, we now have a
couple of places, where stuff behaves strange and it's not really obvious that
it's causes by a setFilterFid request killing a surrounding iteration.

Rejecting it wouldn't cure that, but at least make is show (ok, that's what the
error message does also do that now).  And unless we get the parallel
setFilterFid request back, we'll need to identify and rewrite the looping code.


Jürgen

-- 
Jürgen E. Fischer norBIT GmbH   Tel. +49-4931-918175-31
Dipl.-Inf. (FH)   Rheinstraße 13Fax. +49-4931-918175-50
Software Engineer D-26506 Norden   http://www.norbit.de
committ(ed|ing) to Quantum GIS IRC: jef on FreeNode 


-- 
norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
Rheinstrasse 13, 26506 Norden
GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Wiki cleanup

[Tim Sutton]

Hi

On Mon, Apr 15, 2013 at 2:52 PM, Werner Macho  wrote:
> Hi paolo!
>
> well - there should be a release checklist - just to have a list to hold on
> to ..
> but I guess we would only need one that could be copied and
> extended/adjusted as the release cycle is not a fixed one.
>
> You'd have to ask Tim if he'd like to keep the old things - but for me they
> are only there for "historical" purposes and can be deleted.
> (As long as we have the newest version somewhere)
> Probably the latest announcement should also stay (older ones apply to the
> same things as above)
>

Please keep the old release checklists for a while - I often refer
back to them. I am migrating the checklist processing into the
governance docs so eventually we can delete them.

Regards

Tim

> But as I am writing this - It could be probably nice to have some kind of
> historic page .. but again .. there is already the wikipedia page about QGIS
> where all release dates are written .. so .. I'd delete those old pages of
> our own wiki ..
>
> kind regards
> Werner
>
>
>
> On Sun, Apr 14, 2013 at 12:53 PM, Paolo Cavallini 
> wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Il 14/04/2013 12:30, Werner Macho ha scritto:
>> > Hi In my opinion we should just sum up those information.. Merge
>> > all similar parts to have one (and probably the newest)
>> > information. Make the information "timeless" and delete all old
>> > parts.. So it's somehow consolidating and getting rid of old and
>> > useless things.
>>
>> Agreed: would you classify e.g. release checklist and announcements as
>> old and useless? Should I delete them, or?
>> All the best.
>> - --
>> Paolo Cavallini - Faunalia
>> www.faunalia.eu
>> Full contact details at www.faunalia.eu/pc
>> Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
>> -BEGIN PGP SIGNATURE-
>> Version: GnuPG v1.4.12 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>
>> iEYEARECAAYFAlFqipoACgkQ/NedwLUzIr6U9wCeISS5YLEvSvob66rninYF4hwJ
>> Ep8AoIhbqTMig52/TvB4MgjRysjoJJ30
>> =Qu+F
>> -END PGP SIGNATURE-
>
>
>
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>



--
Tim Sutton - QGIS Project Steering Committee Member (Release  Manager)
==
Please do not email me off-list with technical
support questions. Using the lists will gain
more exposure for your issues and the knowledge
surrounding your issue will be shared with all.

Visit http://linfiniti.com to find out about:
 * QGIS programming and support services
 * Mapserver and PostGIS based hosting plans
 * FOSS Consulting Services
Skype: timlinux
Irc: timlinux on #qgis at freenode.net
==
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer