Re: [Qgis-developer] SIP API Update

[Etienne Tourigny]

On Thu, May 30, 2013 at 11:41 PM, Nathan Woodrow wrote:

> Etienne,
>
> If self.attrStr() is something like QVariant(value) then you need to
> remove the QVariant() bit call.
>

that probably was the problem, it works now, many thanks.


>
> - Nathan
>
>
> On Fri, May 31, 2013 at 12:39 PM, Nathan Woodrow wrote:
>
>> Yeah they both return QVariant but that is auto converted to a Python
>> object by SIP.
>>
>> Not sure what is going on there I'll look into it.
>>
>> I get the right return result if I called feature.attribute().
>>
>> Which platform are you on?
>>
>> - Nathan
>>
>>
>> On Fri, May 31, 2013 at 12:30 PM, Etienne Tourigny <
>> etourigny@gmail.com> wrote:
>>
>>>
>>>
>>> On Thu, May 30, 2013 at 3:12 AM, Nathan Woodrow wrote:
>>>
 Hey all,

 I have decided to manage the SIP API update process so that we can have
 it done by 2.0.  This is an important update as leaving it for later will
 break every plugin yet again at later date which just leaves a really bad
 taste for people to deal with. A few plugin authors have already expressed
 that they would not be impressed having to do another major update again in
 the future. And I agree.

 So having said that this is the current plan:

 - I have created a branch with the SIP API v2 update
  - Update all the core plugins in the sipapi-udate[0] branch over the
 next couple of days
 -  Merge into master

 I couldn't update all the core plugins myself BUT it would be a lot
 easier if I could call on the plugin authors to run though their own code
 and do the quick update.  The risk of me doing it is that I might break
 something and not know it.  You know your code best so the help would be
 greatly appreciated.

 I updated most of the console code and Salvatore has already cleaned
 the rest up for me so that is one thing out of the way.

 And here comes the kicker: I would like to do this as quickly as we can
 so to reduce the gap between master and the branch.  The sooner we merge it
 to master the sooner we can open it to wider testing, but I don't expect to
 run into any major issues when we do.

 If you are not aware of what benefits the SIP API update will bring
 here is a quick example:

 Before:

 >>> str(yourlineedit.text().toString())
 'Hello World'
 >>> feature["column"].toInt()[0]
 100

 After

 >>> yourlineedit.text()
 'Hello World'
 >>> feature["column"]
 1000

>>>
>>> I am trying to update a plugin (tileindex) using your branch and I get
>>> the following an error
>>>
>>>  fileName = feature[self.attrStr]
>>>
>>> TypeError: PyQt4.QtCore.QVariant represents a mapped type and cannot be
>>> instantiated
>>>
>>>
>>> It seems that feature[], as well as feature.attribute() return a
>>> QVariant (defined in qgsfeature.sip), which is incompatible with SIP API v2.
>>>
>>>
>>> How can this be fixed in the plugin or qgis?
>>>
>>>
>>>
 It will make life for us and plugin authors a hell of a lot easier.

 I have put together a quick guide[1] with some examples.  It is open
 edit so feel free to add any notes you have. It might be good to turn it
 into a plugin translate guide for future plugin authors moving to 2.0.

 Regards,
 Nathan

 [0] https://github.com/qgis/Quantum-GIS/tree/sipapi-update
 [1]
 https://docs.google.com/document/d/1S85DMEC71AOzTkF1_EpnF0dhVb2On2EVq4E5s1EXoNM/edit?usp=sharing





 ___
 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] SIP API Update

[Nathan Woodrow]

Etienne,

Basically QVariant no longer exits in PyQt so if you have from PyQt4.QtCore
import QVariant you can remove it, or if you have: myvalue = QVariant(10)
change it to myvalue = 10.

- Nathan


On Fri, May 31, 2013 at 12:41 PM, Nathan Woodrow wrote:

> Etienne,
>
> If self.attrStr() is something like QVariant(value) then you need to
> remove the QVariant() bit call.
>
> - Nathan
>
>
> On Fri, May 31, 2013 at 12:39 PM, Nathan Woodrow wrote:
>
>> Yeah they both return QVariant but that is auto converted to a Python
>> object by SIP.
>>
>> Not sure what is going on there I'll look into it.
>>
>> I get the right return result if I called feature.attribute().
>>
>> Which platform are you on?
>>
>> - Nathan
>>
>>
>> On Fri, May 31, 2013 at 12:30 PM, Etienne Tourigny <
>> etourigny@gmail.com> wrote:
>>
>>>
>>>
>>> On Thu, May 30, 2013 at 3:12 AM, Nathan Woodrow wrote:
>>>
 Hey all,

 I have decided to manage the SIP API update process so that we can have
 it done by 2.0.  This is an important update as leaving it for later will
 break every plugin yet again at later date which just leaves a really bad
 taste for people to deal with. A few plugin authors have already expressed
 that they would not be impressed having to do another major update again in
 the future. And I agree.

 So having said that this is the current plan:

 - I have created a branch with the SIP API v2 update
  - Update all the core plugins in the sipapi-udate[0] branch over the
 next couple of days
 -  Merge into master

 I couldn't update all the core plugins myself BUT it would be a lot
 easier if I could call on the plugin authors to run though their own code
 and do the quick update.  The risk of me doing it is that I might break
 something and not know it.  You know your code best so the help would be
 greatly appreciated.

 I updated most of the console code and Salvatore has already cleaned
 the rest up for me so that is one thing out of the way.

 And here comes the kicker: I would like to do this as quickly as we can
 so to reduce the gap between master and the branch.  The sooner we merge it
 to master the sooner we can open it to wider testing, but I don't expect to
 run into any major issues when we do.

 If you are not aware of what benefits the SIP API update will bring
 here is a quick example:

 Before:

 >>> str(yourlineedit.text().toString())
 'Hello World'
 >>> feature["column"].toInt()[0]
 100

 After

 >>> yourlineedit.text()
 'Hello World'
 >>> feature["column"]
 1000

>>>
>>> I am trying to update a plugin (tileindex) using your branch and I get
>>> the following an error
>>>
>>>  fileName = feature[self.attrStr]
>>>
>>> TypeError: PyQt4.QtCore.QVariant represents a mapped type and cannot be
>>> instantiated
>>>
>>>
>>> It seems that feature[], as well as feature.attribute() return a
>>> QVariant (defined in qgsfeature.sip), which is incompatible with SIP API v2.
>>>
>>>
>>> How can this be fixed in the plugin or qgis?
>>>
>>>
>>>
 It will make life for us and plugin authors a hell of a lot easier.

 I have put together a quick guide[1] with some examples.  It is open
 edit so feel free to add any notes you have. It might be good to turn it
 into a plugin translate guide for future plugin authors moving to 2.0.

 Regards,
 Nathan

 [0] https://github.com/qgis/Quantum-GIS/tree/sipapi-update
 [1]
 https://docs.google.com/document/d/1S85DMEC71AOzTkF1_EpnF0dhVb2On2EVq4E5s1EXoNM/edit?usp=sharing





 ___
 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] SIP API Update

[Nathan Woodrow]

Etienne,

If self.attrStr() is something like QVariant(value) then you need to remove
the QVariant() bit call.

- Nathan


On Fri, May 31, 2013 at 12:39 PM, Nathan Woodrow wrote:

> Yeah they both return QVariant but that is auto converted to a Python
> object by SIP.
>
> Not sure what is going on there I'll look into it.
>
> I get the right return result if I called feature.attribute().
>
> Which platform are you on?
>
> - Nathan
>
>
> On Fri, May 31, 2013 at 12:30 PM, Etienne Tourigny <
> etourigny@gmail.com> wrote:
>
>>
>>
>> On Thu, May 30, 2013 at 3:12 AM, Nathan Woodrow wrote:
>>
>>> Hey all,
>>>
>>> I have decided to manage the SIP API update process so that we can have
>>> it done by 2.0.  This is an important update as leaving it for later will
>>> break every plugin yet again at later date which just leaves a really bad
>>> taste for people to deal with. A few plugin authors have already expressed
>>> that they would not be impressed having to do another major update again in
>>> the future. And I agree.
>>>
>>> So having said that this is the current plan:
>>>
>>> - I have created a branch with the SIP API v2 update
>>>  - Update all the core plugins in the sipapi-udate[0] branch over the
>>> next couple of days
>>> -  Merge into master
>>>
>>> I couldn't update all the core plugins myself BUT it would be a lot
>>> easier if I could call on the plugin authors to run though their own code
>>> and do the quick update.  The risk of me doing it is that I might break
>>> something and not know it.  You know your code best so the help would be
>>> greatly appreciated.
>>>
>>> I updated most of the console code and Salvatore has already cleaned the
>>> rest up for me so that is one thing out of the way.
>>>
>>> And here comes the kicker: I would like to do this as quickly as we can
>>> so to reduce the gap between master and the branch.  The sooner we merge it
>>> to master the sooner we can open it to wider testing, but I don't expect to
>>> run into any major issues when we do.
>>>
>>> If you are not aware of what benefits the SIP API update will bring here
>>> is a quick example:
>>>
>>> Before:
>>>
>>> >>> str(yourlineedit.text().toString())
>>> 'Hello World'
>>> >>> feature["column"].toInt()[0]
>>> 100
>>>
>>> After
>>>
>>> >>> yourlineedit.text()
>>> 'Hello World'
>>> >>> feature["column"]
>>> 1000
>>>
>>
>> I am trying to update a plugin (tileindex) using your branch and I get
>> the following an error
>>
>>  fileName = feature[self.attrStr]
>>
>> TypeError: PyQt4.QtCore.QVariant represents a mapped type and cannot be
>> instantiated
>>
>>
>> It seems that feature[], as well as feature.attribute() return a QVariant
>> (defined in qgsfeature.sip), which is incompatible with SIP API v2.
>>
>>
>> How can this be fixed in the plugin or qgis?
>>
>>
>>
>>> It will make life for us and plugin authors a hell of a lot easier.
>>>
>>> I have put together a quick guide[1] with some examples.  It is open
>>> edit so feel free to add any notes you have. It might be good to turn it
>>> into a plugin translate guide for future plugin authors moving to 2.0.
>>>
>>> Regards,
>>> Nathan
>>>
>>> [0] https://github.com/qgis/Quantum-GIS/tree/sipapi-update
>>> [1]
>>> https://docs.google.com/document/d/1S85DMEC71AOzTkF1_EpnF0dhVb2On2EVq4E5s1EXoNM/edit?usp=sharing
>>>
>>>
>>>
>>>
>>>
>>> ___
>>> 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] SIP API Update

[Nathan Woodrow]

Yeah they both return QVariant but that is auto converted to a Python
object by SIP.

Not sure what is going on there I'll look into it.

I get the right return result if I called feature.attribute().

Which platform are you on?

- Nathan


On Fri, May 31, 2013 at 12:30 PM, Etienne Tourigny
wrote:

>
>
> On Thu, May 30, 2013 at 3:12 AM, Nathan Woodrow wrote:
>
>> Hey all,
>>
>> I have decided to manage the SIP API update process so that we can have
>> it done by 2.0.  This is an important update as leaving it for later will
>> break every plugin yet again at later date which just leaves a really bad
>> taste for people to deal with. A few plugin authors have already expressed
>> that they would not be impressed having to do another major update again in
>> the future. And I agree.
>>
>> So having said that this is the current plan:
>>
>> - I have created a branch with the SIP API v2 update
>>  - Update all the core plugins in the sipapi-udate[0] branch over the
>> next couple of days
>> -  Merge into master
>>
>> I couldn't update all the core plugins myself BUT it would be a lot
>> easier if I could call on the plugin authors to run though their own code
>> and do the quick update.  The risk of me doing it is that I might break
>> something and not know it.  You know your code best so the help would be
>> greatly appreciated.
>>
>> I updated most of the console code and Salvatore has already cleaned the
>> rest up for me so that is one thing out of the way.
>>
>> And here comes the kicker: I would like to do this as quickly as we can
>> so to reduce the gap between master and the branch.  The sooner we merge it
>> to master the sooner we can open it to wider testing, but I don't expect to
>> run into any major issues when we do.
>>
>> If you are not aware of what benefits the SIP API update will bring here
>> is a quick example:
>>
>> Before:
>>
>> >>> str(yourlineedit.text().toString())
>> 'Hello World'
>> >>> feature["column"].toInt()[0]
>> 100
>>
>> After
>>
>> >>> yourlineedit.text()
>> 'Hello World'
>> >>> feature["column"]
>> 1000
>>
>
> I am trying to update a plugin (tileindex) using your branch and I get the
> following an error
>
>  fileName = feature[self.attrStr]
>
> TypeError: PyQt4.QtCore.QVariant represents a mapped type and cannot be
> instantiated
>
>
> It seems that feature[], as well as feature.attribute() return a QVariant
> (defined in qgsfeature.sip), which is incompatible with SIP API v2.
>
>
> How can this be fixed in the plugin or qgis?
>
>
>
>> It will make life for us and plugin authors a hell of a lot easier.
>>
>> I have put together a quick guide[1] with some examples.  It is open edit
>> so feel free to add any notes you have. It might be good to turn it into a
>> plugin translate guide for future plugin authors moving to 2.0.
>>
>> Regards,
>> Nathan
>>
>> [0] https://github.com/qgis/Quantum-GIS/tree/sipapi-update
>> [1]
>> https://docs.google.com/document/d/1S85DMEC71AOzTkF1_EpnF0dhVb2On2EVq4E5s1EXoNM/edit?usp=sharing
>>
>>
>>
>>
>>
>> ___
>> 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] SIP API Update

[Etienne Tourigny]

On Thu, May 30, 2013 at 3:12 AM, Nathan Woodrow  wrote:

> Hey all,
>
> I have decided to manage the SIP API update process so that we can have it
> done by 2.0.  This is an important update as leaving it for later will
> break every plugin yet again at later date which just leaves a really bad
> taste for people to deal with. A few plugin authors have already expressed
> that they would not be impressed having to do another major update again in
> the future. And I agree.
>
> So having said that this is the current plan:
>
> - I have created a branch with the SIP API v2 update
>  - Update all the core plugins in the sipapi-udate[0] branch over the next
> couple of days
> -  Merge into master
>
> I couldn't update all the core plugins myself BUT it would be a lot easier
> if I could call on the plugin authors to run though their own code and do
> the quick update.  The risk of me doing it is that I might break something
> and not know it.  You know your code best so the help would be greatly
> appreciated.
>
> I updated most of the console code and Salvatore has already cleaned the
> rest up for me so that is one thing out of the way.
>
> And here comes the kicker: I would like to do this as quickly as we can so
> to reduce the gap between master and the branch.  The sooner we merge it to
> master the sooner we can open it to wider testing, but I don't expect to
> run into any major issues when we do.
>
> If you are not aware of what benefits the SIP API update will bring here
> is a quick example:
>
> Before:
>
> >>> str(yourlineedit.text().toString())
> 'Hello World'
> >>> feature["column"].toInt()[0]
> 100
>
> After
>
> >>> yourlineedit.text()
> 'Hello World'
> >>> feature["column"]
> 1000
>

I am trying to update a plugin (tileindex) using your branch and I get the
following an error

 fileName = feature[self.attrStr]

TypeError: PyQt4.QtCore.QVariant represents a mapped type and cannot be
instantiated


It seems that feature[], as well as feature.attribute() return a QVariant
(defined in qgsfeature.sip), which is incompatible with SIP API v2.


How can this be fixed in the plugin or qgis?



> It will make life for us and plugin authors a hell of a lot easier.
>
> I have put together a quick guide[1] with some examples.  It is open edit
> so feel free to add any notes you have. It might be good to turn it into a
> plugin translate guide for future plugin authors moving to 2.0.
>
> Regards,
> Nathan
>
> [0] https://github.com/qgis/Quantum-GIS/tree/sipapi-update
> [1]
> https://docs.google.com/document/d/1S85DMEC71AOzTkF1_EpnF0dhVb2On2EVq4E5s1EXoNM/edit?usp=sharing
>
>
>
>
>
> ___
> 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] SIP API Update

[Etienne Tourigny]

so plugin authors would potentially need to maintain 2 versions of their
plugins, on for qgis <= 1.8 and one for qgis >=2.0.

This is probably easier than adding a bunch of if statements where sip1 and
spi2 need different syntax I guess,

cheers
Etienne

On Thu, May 30, 2013 at 6:07 AM, Nathan Woodrow  wrote:

> On Thu, May 30, 2013 at 7:04 PM, Sandro Santilli  wrote:
>
>> Plugin authors want to maintain support for multiple qgis versions,
>> so changing an API is really only _more_ work, not _less_.
>>
>> Is there any facility to deal with that ?
>>
>
> The new plugin manager can handle different versions of the same plugin.
> With the new vector API this is already the case so changing SIP isn't
> going to hurt much more.
>
> - Nathan
>
>
> ___
> 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] SIP API Update

[Nathan Woodrow]

Crash should be fixed now.

- Nathan


On Fri, May 31, 2013 at 1:17 AM, Nathan Woodrow  wrote:

> Hey all,
>
> There is currently a issue in the new sip branch with calling
> QgsMapLayerRegistry.instance().mapLayers() making QGIS crash. I know
> where the issue is and will try to fix it ASAP.
>
> If anyone knows sip and can lend a hand that would be great. The crash
> is in conversions.sip QMap.
>
> Sent from some fancy phone looking thingo
> From: Matthias Kuhn
> Sent: 30/05/2013 7:10 PM
> To: Sandro Santilli
> Cc: qgis-developer@lists.osgeo.org; Nathan Woodrow
> Subject: Re: [Qgis-developer] SIP API Update
> On Don 30 Mai 2013 11:04:18 CEST, Sandro Santilli wrote:
> > On Thu, May 30, 2013 at 04:12:15PM +1000, Nathan Woodrow wrote:
> >
> >> If you are not aware of what benefits the SIP API update will bring
> here is
> >> a quick example:
> >>
> >> Before:
> >>
> > str(yourlineedit.text().toString())
> >> 'Hello World'
> > feature["column"].toInt()[0]
> >> 100
> >>
> >> After
> >>
> > yourlineedit.text()
> >> 'Hello World'
> > feature["column"]
> >> 1000
> >>
> >> It will make life for us and plugin authors a hell of a lot easier.
> >
> > Plugin authors want to maintain support for multiple qgis versions,
> > so changing an API is really only _more_ work, not _less_.
> >
> > Is there any facility to deal with that ?
>
> There is this link from Marco Bernasocchi:
>
> http://spyder-ide.blogspot.ch/2011/06/pyqt-api-1-pyqt-api-2-and-pyside.html
>
> This abstraction layer along with another one for the vector layer API
> changes would make a nice little help for developers targetting
> multiple versions.
>
> Matthias
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] using hub.qgis.org git repository

[Alex Mandel]

On 05/30/2013 03:42 PM, Ricardo Filipe Soares Garcia da wrote:

Hi list

I created a new plugin in hub.qgis.org and I'd like to use a git
repository. I've done this in the past and had no problems but now I am
having dificulties pushing the initial commit to gitosis.qgis.org

In redmine I created the repository and added my SSH key. Then I
initialized my git repo locally and added the remote repo using the URL
that redmine gave me. I did my first commit and now I want to push it to
the remote repository. I keep getting an error about not having permission
when I input my password.

What could be the problem?

Must I first upload the code and ask for approval in order to get the
remote repository created?

The plugin's name is 'Conefor inputs'.



The first sign the something isn't right is if gitosis asks you for a 
password. It uses ssh keys which at most will ask you to unlock your 
local passphrase for the key in use.


Can you please list the git commands you ran.
Also what's the output of:
git remote -v

Thanks,
Alex

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

[Qgis-developer] using hub.qgis.org git repository

[Ricardo Filipe Soares Garcia da]

Hi list

I created a new plugin in hub.qgis.org and I'd like to use a git
repository. I've done this in the past and had no problems but now I am
having dificulties pushing the initial commit to gitosis.qgis.org

In redmine I created the repository and added my SSH key. Then I
initialized my git repo locally and added the remote repo using the URL
that redmine gave me. I did my first commit and now I want to push it to
the remote repository. I keep getting an error about not having permission
when I input my password.

What could be the problem?

Must I first upload the code and ask for approval in order to get the
remote repository created?

The plugin's name is 'Conefor inputs'.


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

Re: [Qgis-developer] SIP API Update

[Nathan Woodrow]

Hey all,

There is currently a issue in the new sip branch with calling
QgsMapLayerRegistry.instance().mapLayers() making QGIS crash. I know
where the issue is and will try to fix it ASAP.

If anyone knows sip and can lend a hand that would be great. The crash
is in conversions.sip QMap.

Sent from some fancy phone looking thingo
From: Matthias Kuhn
Sent: 30/05/2013 7:10 PM
To: Sandro Santilli
Cc: qgis-developer@lists.osgeo.org; Nathan Woodrow
Subject: Re: [Qgis-developer] SIP API Update
On Don 30 Mai 2013 11:04:18 CEST, Sandro Santilli wrote:
> On Thu, May 30, 2013 at 04:12:15PM +1000, Nathan Woodrow wrote:
>
>> If you are not aware of what benefits the SIP API update will bring here is
>> a quick example:
>>
>> Before:
>>
> str(yourlineedit.text().toString())
>> 'Hello World'
> feature["column"].toInt()[0]
>> 100
>>
>> After
>>
> yourlineedit.text()
>> 'Hello World'
> feature["column"]
>> 1000
>>
>> It will make life for us and plugin authors a hell of a lot easier.
>
> Plugin authors want to maintain support for multiple qgis versions,
> so changing an API is really only _more_ work, not _less_.
>
> Is there any facility to deal with that ?

There is this link from Marco Bernasocchi:

http://spyder-ide.blogspot.ch/2011/06/pyqt-api-1-pyqt-api-2-and-pyside.html

This abstraction layer along with another one for the vector layer API
changes would make a nice little help for developers targetting
multiple versions.

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

[Qgis-developer] First time compilation

[Joao Machiana]

Hi all
I'm about to start using QGIS for some projects of my organization, but I'm
facing some problems (maybe they're not a problem at all)

I've set up the QGIS development platform.
I've downloaded and installed QGIS Lisboa apart. (not from OSGeo4W)
I've followed the "qgis-1.6.0_coding-compilation_guide" (line by line) and
I've been able to configure and generate the qgis source code to be
compiled.
I'm using cmake 2.8, and Visual Studio 2010 express edition
I could sucessfully compile the qgis source code.

But right now I want to compile the files in the code examples, and every
time I click configure on cmake, I receive the error:

CMake Error at cmake_find_rules/FindQGIS.cmake:135 (MESSAGE):

Could not find QGIS

Call Stack (most recent call first):

CMakeLists.txt:6 (FIND_PACKAGE)


I've tried change the paths in the file FindQGIS.cmake, but with resulting
in failure.

This may be a dumb question, but I'm stuck on it for two days.


Thanks in advance for anyhelp.

I've attached the FindQGIS.cmake file




-- 
*João X. Machiana*
Systems Analyst and Programmer


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

Re: [Qgis-developer] Python error in master

[Sandro Santilli]

On Thu, May 30, 2013 at 04:45:05PM +0200, Paolo Cavallini wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Il 28/05/2013 19:28, Paolo Cavallini ha scritto:
> 
> > thanks for your reply. My situation is a bit different:
> > * I have only Debian testing and unstable boxes, clean and up to date
> > *  python-sip 4.13.3-2
> > * I installed qgis from jef nightly repo
> 
> Just for the record:
> aptitude install sip-api-9.2
> solved the issue.

Is there anyone for qgis to detect such missing dependency
and report it to the user at runtime ?

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

Re: [Qgis-developer] Python error in master

[Paolo Cavallini]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Il 28/05/2013 19:28, Paolo Cavallini ha scritto:

> thanks for your reply. My situation is a bit different:
> * I have only Debian testing and unstable boxes, clean and up to date
> *  python-sip 4.13.3-2
> * I installed qgis from jef nightly repo

Just for the record:
aptitude install sip-api-9.2
solved the issue.
Thanks Juergen.
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/

iEYEARECAAYFAlGnZfEACgkQ/NedwLUzIr6f+ACgulW7CuvsFIYNvWY/2YX19MEk
ZCcAnjU8ZLto2LqUhCUIMfOPgvPdtnjq
=HVHW
-END PGP SIGNATURE-
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Coordination of Hackfest with FOSS4G

[Saber Razmjooei]

Hi all,

I think we will stick with the original plan as on the wiki. 

Regards,
Saber


-Original Message-
From: qgis-developer-boun...@lists.osgeo.org
[mailto:qgis-developer-boun...@lists.osgeo.org] On Behalf Of Tim Sutton
Sent: 29 May 2013 15:48
To: Barry Rowlingson
Cc: rich...@duif.net; qgis-developer@lists.osgeo.org
Subject: Re: [Qgis-developer] Coordination of Hackfest with FOSS4G

Hi



On Wed, May 29, 2013 at 3:39 PM, Barry Rowlingson
 wrote:
> On Wed, May 29, 2013 at 11:19 AM, Richard Duivenvoorde 
>  wrote:
>
>> if I understand correctly, Tuesday 17 and Wednesday 18 are the 
>> hackdays of foss4g which normally were done after the conference. But 
>> now combined with the workshops which normally preceded the conference.
>> My experience is that most core developers of the different foss4g 
>> projects show up on these days (and other interested shove by).
>>
>> QGIS hackfest was/is planned from 12 - 16
>>
>> Isn't this perfectly planned? We first hack for 4 day full steam on 
>> QGIS, and then optionally 2 extra days with some extra new people (OR 
>> you can choose to attend another hackbof (I'm very interested in 
>> OpenLayers and MapProxy for example).
>
>  I think there may be some confusion between the FOSS4G Hackathon and 
> the Code Sprints...
>
>  The Hackathon ("Hack Days") is a thing sponsored by The Met Office 
> where a bunch of random geeks get together to work on developing 
> solutions to problems, guided mainly by Met Office ideas.  The plan is 
> to be similar to the NHS Hack Day (where geeks work on projects for 
> health data and clinical procedure) or other "Random Hacks of 
> Kindness" (RHOK) projects.
>
> The Code Sprint is intended to be a free space for open-source project 
> devs and interested parties to get together and work on their 
> projects. FOSS4G supplies the room and the electricity and phone 
> numbers of local pizza places. We should be able to provide code 
> sprint facilities during the main conference as well as the special 
> code sprint day on the Sunday.
>
>  Now, I'm not saying QGIS couldn't run a code sprint during the 
> hackathon days (personally I think its a great idea, would have to run 
> it past the committee and make sure there's space) but that's not what 
> the hackathon is.
>
> http://2013.foss4g.org/programme/hackathon/
> http://2013.foss4g.org/programme/code-sprint/

Personally I would prefer to have the QGIS hackfest independent from the
FOSS4G - I think it will be a distraction on various levels to be at FOSS4G
- QGIS developers will get lured away to other groups and random people will
wander in and distract QGIS hackers from their geekery. If the hack days
coincide with workshop days it would be doubly bad as those wanting to
attend workshops would do so at the detriment to their QGIS hack time.

I appreciate that there would also be some advantages to Pirmin's suggestion
- encouraging interoperability with other projects and so on, but that could
also be facilitated at BOF sessions in the FOSS4G conference.

Regards

Tim

>
>  Hope that's all clear!
>
> Barry
> ___
> 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


--
This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If you have received this email in error please notify the system manager. This 
message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately 
by e-mail if you have received this e-mail by mistake and delete this e-mail 
from your system. If you are not the intended recipient you are notified 
that disclosing, copying, distributing or taking any action in reliance on the 
contents of this information is strictly prohibited.

Whilst reasonable care has been taken to avoid virus transmission, no 
responsibility for viruses is taken and it is your responsibility to carry out 
such checks as you feel appropriate.

Saber Razmjooei and Peter Wells trading as Lutra Consulti

Re: [Qgis-developer] SIP API Update

[Nathan Woodrow]

The old way e.g toInt()[0] will not work anymore hence why we have to
update everything.  The 1000 is a typo.

- Nathan


On Thu, May 30, 2013 at 7:07 PM, Jo  wrote:

> 2013/5/30 Sandro Santilli 
>
>> On Thu, May 30, 2013 at 04:12:15PM +1000, Nathan Woodrow wrote:
>>
>> > If you are not aware of what benefits the SIP API update will bring
>> here is
>> > a quick example:
>> >
>> > Before:
>> >
>> > >>> str(yourlineedit.text().toString())
>> > 'Hello World'
>> > >>> feature["column"].toInt()[0]
>> > 100
>> >
>> > After
>> >
>> > >>> yourlineedit.text()
>> > 'Hello World'
>> > >>> feature["column"]
>> > 1000
>> >
>> > It will make life for us and plugin authors a hell of a lot easier.
>>
>> Plugin authors want to maintain support for multiple qgis versions,
>> so changing an API is really only _more_ work, not _less_.
>>
>> Is there any facility to deal with that ?
>>
>
> Does the old way of doing it stop working? What I'm a bit  worried about
> is that the result is 100 before and 1000 after, but I guess that's a typo?
>
> It seems the code will be cleaner and more concise, that's certainly a
> good thing.
>
> Jo
>
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] SIP API Update

[Matthias Kuhn]

On Don 30 Mai 2013 11:04:18 CEST, Sandro Santilli wrote:
> On Thu, May 30, 2013 at 04:12:15PM +1000, Nathan Woodrow wrote:
>
>> If you are not aware of what benefits the SIP API update will bring here is
>> a quick example:
>>
>> Before:
>>
> str(yourlineedit.text().toString())
>> 'Hello World'
> feature["column"].toInt()[0]
>> 100
>>
>> After
>>
> yourlineedit.text()
>> 'Hello World'
> feature["column"]
>> 1000
>>
>> It will make life for us and plugin authors a hell of a lot easier.
>
> Plugin authors want to maintain support for multiple qgis versions,
> so changing an API is really only _more_ work, not _less_.
>
> Is there any facility to deal with that ?

There is this link from Marco Bernasocchi:

http://spyder-ide.blogspot.ch/2011/06/pyqt-api-1-pyqt-api-2-and-pyside.html

This abstraction layer along with another one for the vector layer API 
changes would make a nice little help for developers targetting 
multiple versions.

Matthias

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

Re: [Qgis-developer] SIP API Update

[Jo]

2013/5/30 Sandro Santilli 

> On Thu, May 30, 2013 at 04:12:15PM +1000, Nathan Woodrow wrote:
>
> > If you are not aware of what benefits the SIP API update will bring here
> is
> > a quick example:
> >
> > Before:
> >
> > >>> str(yourlineedit.text().toString())
> > 'Hello World'
> > >>> feature["column"].toInt()[0]
> > 100
> >
> > After
> >
> > >>> yourlineedit.text()
> > 'Hello World'
> > >>> feature["column"]
> > 1000
> >
> > It will make life for us and plugin authors a hell of a lot easier.
>
> Plugin authors want to maintain support for multiple qgis versions,
> so changing an API is really only _more_ work, not _less_.
>
> Is there any facility to deal with that ?
>

Does the old way of doing it stop working? What I'm a bit  worried about is
that the result is 100 before and 1000 after, but I guess that's a typo?

It seems the code will be cleaner and more concise, that's certainly a good
thing.

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

Re: [Qgis-developer] SIP API Update

[Nathan Woodrow]

On Thu, May 30, 2013 at 7:04 PM, Sandro Santilli  wrote:

> Plugin authors want to maintain support for multiple qgis versions,
> so changing an API is really only _more_ work, not _less_.
>
> Is there any facility to deal with that ?
>

The new plugin manager can handle different versions of the same plugin.
With the new vector API this is already the case so changing SIP isn't
going to hurt much more.

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

Re: [Qgis-developer] SIP API Update

[Sandro Santilli]

On Thu, May 30, 2013 at 04:12:15PM +1000, Nathan Woodrow wrote:

> If you are not aware of what benefits the SIP API update will bring here is
> a quick example:
> 
> Before:
> 
> >>> str(yourlineedit.text().toString())
> 'Hello World'
> >>> feature["column"].toInt()[0]
> 100
> 
> After
> 
> >>> yourlineedit.text()
> 'Hello World'
> >>> feature["column"]
> 1000
> 
> It will make life for us and plugin authors a hell of a lot easier.

Plugin authors want to maintain support for multiple qgis versions,
so changing an API is really only _more_ work, not _less_.

Is there any facility to deal with that ?

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

Re: [Qgis-developer] QGIS 2.0 and beyond

[Paolo Cavallini]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Il 30/05/2013 08:02, Luca Manganelli ha scritto:
> On Wed, May 29, 2013 at 10:16 PM, Sandro Santilli  > wrote:
> 
> Luca, what about taking the responsibility to maintain a stable branch ?
> I'd also love to see a 1.8.1 coming out :)
> 
> 
> It is not a bad idea. I'm pretty sure that if  QGIS 2.0 will be out soon, it 
> never
> will be used in production, due to critical bugs (we will wait at least for 
> 2.0.1 or
> 2.0.2).

As said, I think backporting fixes should really be important for the future of 
the
project, and power users should seriously consider hiring a developer to 
maintain 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/

iEYEARECAAYFAlGnCoIACgkQ/NedwLUzIr6+gACdHDa8zSPSiZfTHDRqx/6g+WKJ
pYoAn1ZdEdwc8FTI4rk+6BMwkV0WQtBD
=gdfy
-END PGP SIGNATURE-
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Adding a feature to a layer with joined fields

[Denis Rouzaud]

Hi Minoru,

Then I can't wait for your patches to be integrated!
Is there any reason why it's not accepted yet???

Also, it would be really nice to see joined fields automatically updated 
while changing the target field...


Cheers,

Denis



On 05/30/2013 09:05 AM, Minoru Akagi wrote:

Hi,

2013/5/30 Denis Rouzaud :

Hi all,

Regarding blocker #7072, I wonder if it really makes sense to have joined
fields than can be filled by the user in the edit form while creating a
feature. These fields should not be edited at all.
I would suggest not to show them at creation and to disable the joined
fields while editing.

What do you think?

I think it's right. In 1.8, joined fields are editable. Input values
are displayed in the attribute table, but their values are not saved
when I save the layer as a new file.
My patch[1] does not hide joined fields in new feature form, but it
makes joined fields uneditable. As soon as we create a new feature on
join layer, fields in the joined table are bind to the new feature
corresponding to the value of the target field. I believe that editing
join layer should work well with two patches[1][2].

[1] https://github.com/qgis/Quantum-GIS/pull/576
[2] https://github.com/qgis/Quantum-GIS/pull/546

Minoru


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

[Qgis-developer] SOCIS 2013

[Paolo Cavallini]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi all.
European students can apply for a grant:
http://sophia.estec.esa.int/socis2013/
similar to GSoC. Do not hesitate asking!
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/

iEYEARECAAYFAlGnAucACgkQ/NedwLUzIr4OsQCfXONmPxe+F+KAQ4h17W+7GFWF
toIAnA3WgGauR5lY9cJ0frmcSiZBbNKC
=LBCS
-END PGP SIGNATURE-
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Adding a feature to a layer with joined fields

[Minoru Akagi]

Hi,

2013/5/30 Denis Rouzaud :
> Hi all,
>
> Regarding blocker #7072, I wonder if it really makes sense to have joined
> fields than can be filled by the user in the edit form while creating a
> feature. These fields should not be edited at all.
> I would suggest not to show them at creation and to disable the joined
> fields while editing.
>
> What do you think?

I think it's right. In 1.8, joined fields are editable. Input values
are displayed in the attribute table, but their values are not saved
when I save the layer as a new file.
My patch[1] does not hide joined fields in new feature form, but it
makes joined fields uneditable. As soon as we create a new feature on
join layer, fields in the joined table are bind to the new feature
corresponding to the value of the target field. I believe that editing
join layer should work well with two patches[1][2].

[1] https://github.com/qgis/Quantum-GIS/pull/576
[2] https://github.com/qgis/Quantum-GIS/pull/546

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