Re: [Qgis-developer] A common set of functions for QGIS plugins

2015-11-03 Thread Victor Olaya
>
> A definite +1 on this.
> Also maybe a parent QGISPlugin class all plugins would inherit from ?

This is a good idea, and it would be easy to modify the Plugin Builder
plugin to generate plugin skeletons using that class

>
> As a side note on plugin, but important, Hugo intends at the hackfest to
> propose and discuss having plugins be Python modules, so that we can use
> PIP to deal with module and plugins dependencies.
> This would solve this problem and let us use common Python tools, be it
> on the plugin side, or the module management side, and ease packaging
> also for the distributions.
>

Sounds good as well. In case you do a small meeting for discussing
that (and also with other meetings that might happen), could it be
possibel to participate via skype/google hangout?
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] A common set of functions for QGIS plugins

2015-11-03 Thread Vincent Picavet (ml)
Hello Victor,

A definite +1 on this.
Also maybe a parent QGISPlugin class all plugins would inherit from ?

As a side note on plugin, but important, Hugo intends at the hackfest to
propose and discuss having plugins be Python modules, so that we can use
PIP to deal with module and plugins dependencies.
This would solve this problem and let us use common Python tools, be it
on the plugin side, or the module management side, and ease packaging
also for the distributions.

Vincent

On 02/11/2015 23:53, Nathan Woodrow wrote:
> Hey Victor,
> 
> Just added you with write access to my project if you want.  I don't
> really mind if you wanted to work on the same one together.  My
> motivations were the same as you in the end.  Mainly just flesh
> something out in a sandbox and then we can add it to core once we have
> it nutted out.
> 
> Regards,
> 
> On Tue, Nov 3, 2015 at 8:43 AM, Victor Olaya  > wrote:
> 
> Hey Nathan
> 
> I knew about your project...but forgot about it :-) Sorry for that.
> 
> What would you suggest doing? merging them maybe? I like that idea. In
> the end, the plan is just to have a sandbox to add those functions and
> eventually move them to core (btw, qgis.py sounds good to me...)
> 
> I can make a PR to your repo if you think it is a good idea, and we
> keep on working there.
> 
> Let me know also if you have ideas about what to add to fill those
> modules with useful stuff
> 
> Cheers!
> 
> 2015-11-02 14:29 GMT+01:00 Nathan Woodrow  >:
> > Hey Victor,
> >
> > Working on the same kind of thing over here:
> > https://github.com/NathanW2/parfait
> >
> > IMO I would rather see a new module and not put it in qgis.utils. 
> Something
> > like qgis.py or qgis.wrappers or something like that that.
> >
> > - Nathan
> >
> > On Mon, Nov 2, 2015 at 11:20 PM, Victor Olaya  > wrote:
> >>
> >> >
> >> > I'm in two minds as to whether it would be a good thing to have an
> >> > 'official' one. While I can see the use, surely if these things are
> >> > useful
> >> > then they should be included in the mainline API with proper API
> >> > guarantees?
> >> > I'm not sure I'd want to rely on a library that doesn't have an API
> >> > guarantee, and if you're making the guarantee then why not in
> core? If
> >> > they
> >> > are *required* for a plugin to be accepted, then they must be
> in core
> >> > and
> >> > have an API guarantee.
> >> >
> >>
> >> My ideas is definitely to put this into core (that's what I wrote in
> >> my email when i detailed the plans that i have for this), but I have
> >> started it as a separate repo to make it easier to collaborate and to
> >> start moving ASAP.
> >>
> >> I could write a QEP with this idea, get it approved, throw a bunch of
> >> empty py modules in qgis.utils and then start working, but I like to
> >> first do some work, get people into it, and then do the bureucracy to
> >> pass this to core (I am sure no one will say no to this once a nice
> >> collection of functions is ready)
> >>
> >> I will wait for other people to voice their opinion, and if most
> >> people agree on going taht other way, I have nothing against 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

Re: [Qgis-developer] Add multiple frames to a composer attribute table using PyQGIS

2015-11-03 Thread James Stott
Hi Nyall,

Thanks very much for the advice. It is working now.

That was an excellent tip about checking the unit tests.

James

On Sun, 1 Nov 2015 at 10:23 Nyall Dawson  wrote:

> On 1 November 2015 at 20:09, James Stott  wrote:
> > I have an attribute table that is around two hundred rows of data (but
> only
> > two columns wide). I would like to add an attribute table to a composer
> with
> > this data, and to do this I need to add multiple frames so I can add the
> > whole attribute table to one page. Doing this manually in the composer I
> > just add 5 frames side by side to one composer page, and I manage to get
> all
> > my data on one page.
> >
> > I cannot figure out how to add an attribute table with multiple frames
> to a
> > composer using PyQGIS. I am problably missing something really obvious,
> but
> > I am stuck here.
> >
> > When I try to define a QgsComposerFrame, I am told that I must specify
> the
> > QgsComposerMultiFrame it belongs to:
> >
> > QgsComposerFrame (QgsComposition *c, QgsComposerMultiFrame *mf, qreal x,
> > qreal y, qreal width, qreal height)
> >
> > How do I create the QgsComposerMultiFrame. It is an abstract class, I am
> > told that it is an abstract class and cannot be instantiated. If I try
> >
> > multiFrame = QgsComposerMultiFrame(myCompositionTable, False)
> >
> > I get the following error when I run my code.
> >
> > qgis._core.QgsComposerMultiFrame represents a C++ abstract class and
> cannot
> > be instantiated
>
> You create a QgsComposerAttributeTableV2 instead, which derives from
> QgsComposerMultiFrame. Here's some c++ code which does this, which
> should be pretty straightforward to translate to Python:
>
>
> mComposerAttributeTable = new QgsComposerAttributeTableV2(
> mComposition, false );
> mComposition->addMultiFrame( mComposerAttributeTable );
>
> mFrame1 = new QgsComposerFrame( mComposition, mComposerAttributeTable,
> 5, 5, 100, 30 );
> mFrame2 = new QgsComposerFrame( mComposition, mComposerAttributeTable,
> 5, 40, 100, 30 );
>
> mComposerAttributeTable->addFrame( mFrame1 );
> mComposerAttributeTable->addFrame( mFrame2 );
>
> mComposition->addComposerTableFrame( mComposerAttributeTable, mFrame1 );
> mComposition->addComposerTableFrame( mComposerAttributeTable, mFrame2 );
>
> mComposerAttributeTable->setVectorLayer( mVectorLayer );
> mComposerAttributeTable->setDisplayOnlyVisibleFeatures( false );
> mComposerAttributeTable->setMaximumNumberOfFeatures( 10 );
> mComposerAttributeTable->setContentFont(
> QgsFontUtils::getStandardTestFont() );
> mComposerAttributeTable->setHeaderFont(
> QgsFontUtils::getStandardTestFont() );
> mComposerAttributeTable->setBackgroundColor( Qt::yellow );
>
> When in doubt for something like this and you can't find any examples
> online, a good last resort to check is in the QGIS unit tests:
> https://github.com/qgis/QGIS/tree/master/tests/src
> (or in this case
>
> https://github.com/qgis/QGIS/blob/master/tests/src/core/testqgscomposertablev2.cpp
> )
>
> They are filled with minimal test cases such as this which are useful
> for seeing how various classes are intended to be used.
>
> Nyall
>
>
>
>
> >
> > I cant find any documentation or examples on how to do this. So if
> someone
> > could shed some light on this it would be most appreciated. I am happy to
> > write up a bit of documentation once I have managed to do this.
> >
> > Many thanks,
> >
> > James
> >
> > ___
> > 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] PluginBuilder writes a wrong import inside .py

2015-11-03 Thread Geo DrinX
Hello all,


probably you just know, but I found that "PluginBuilder"  plugin for QGIS
writes at line 26  of the main  .py  file the following code:


import resources


I think this is wrong,  because in run it returns a python error.


The correct code is:


import resources_rc


I hope this helps to create new and useful plugins .


Thank you in advance for attention

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

Re: [Qgis-developer] A common set of functions for QGIS plugins

2015-11-03 Thread Vincent Picavet (ml)
Hello Victor,

A definite +1 on this.
Also maybe a parent QGISPlugin class all plugins would inherit from ?

As a side note on plugin, but important, Hugo intends at the hackfest to
propose and discuss having plugins be Python modules, so that we can use
PIP to deal with module and plugins dependencies.
This would solve this problem and let us use common Python tools, be it
on the plugin side, or the module management side, and ease packaging
also for the distributions.

Vincent

On 02/11/2015 23:53, Nathan Woodrow wrote:
> Hey Victor,
> 
> Just added you with write access to my project if you want.  I don't
> really mind if you wanted to work on the same one together.  My
> motivations were the same as you in the end.  Mainly just flesh
> something out in a sandbox and then we can add it to core once we have
> it nutted out.
> 
> Regards,
> 
> On Tue, Nov 3, 2015 at 8:43 AM, Victor Olaya  > wrote:
> 
> Hey Nathan
> 
> I knew about your project...but forgot about it :-) Sorry for that.
> 
> What would you suggest doing? merging them maybe? I like that idea. In
> the end, the plan is just to have a sandbox to add those functions and
> eventually move them to core (btw, qgis.py sounds good to me...)
> 
> I can make a PR to your repo if you think it is a good idea, and we
> keep on working there.
> 
> Let me know also if you have ideas about what to add to fill those
> modules with useful stuff
> 
> Cheers!
> 
> 2015-11-02 14:29 GMT+01:00 Nathan Woodrow  >:
> > Hey Victor,
> >
> > Working on the same kind of thing over here:
> > https://github.com/NathanW2/parfait
> >
> > IMO I would rather see a new module and not put it in qgis.utils. 
> Something
> > like qgis.py or qgis.wrappers or something like that that.
> >
> > - Nathan
> >
> > On Mon, Nov 2, 2015 at 11:20 PM, Victor Olaya  > wrote:
> >>
> >> >
> >> > I'm in two minds as to whether it would be a good thing to have an
> >> > 'official' one. While I can see the use, surely if these things are
> >> > useful
> >> > then they should be included in the mainline API with proper API
> >> > guarantees?
> >> > I'm not sure I'd want to rely on a library that doesn't have an API
> >> > guarantee, and if you're making the guarantee then why not in
> core? If
> >> > they
> >> > are *required* for a plugin to be accepted, then they must be
> in core
> >> > and
> >> > have an API guarantee.
> >> >
> >>
> >> My ideas is definitely to put this into core (that's what I wrote in
> >> my email when i detailed the plans that i have for this), but I have
> >> started it as a separate repo to make it easier to collaborate and to
> >> start moving ASAP.
> >>
> >> I could write a QEP with this idea, get it approved, throw a bunch of
> >> empty py modules in qgis.utils and then start working, but I like to
> >> first do some work, get people into it, and then do the bureucracy to
> >> pass this to core (I am sure no one will say no to this once a nice
> >> collection of functions is ready)
> >>
> >> I will wait for other people to voice their opinion, and if most
> >> people agree on going taht other way, I have nothing against 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

Re: [Qgis-developer] PluginBuilder writes a wrong import inside .py

2015-11-03 Thread Pirmin Kalberer
Hi Roberto,

Am Dienstag, 3. November 2015, 10.49:24 schrieb Geo DrinX:
> 
> 
> probably you just know, but I found that "PluginBuilder"  plugin for QGIS
> writes at line 26  of the main  .py  file the following code:
> 
> 
> import resources
> 
> 
> I think this is wrong,  because in run it returns a python error.
> 
> 
> The correct code is:
> 
> 
> import resources_rc
> 
> 
> I hope this helps to create new and useful plugins .

Please open an issue at
https://github.com/g-sherman/Qgis-Plugin-Builder

Regards
Pirmin

-- 
Pirmin Kalberer
Sourcepole  -  Linux & Open Source Solutions
http://www.sourcepole.com

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

Re: [Qgis-developer] PluginBuilder writes a wrong import inside .py

2015-11-03 Thread Anita Graser
On Tue, Nov 3, 2015 at 10:49 AM, Geo DrinX  wrote:

> Hello all,
>
>
> probably you just know, but I found that "PluginBuilder"  plugin for QGIS
> writes at line 26  of the main  .py  file the following code:
>
>
> import resources
>
>
> I think this is wrong,  because in run it returns a python error.
>
>
> The correct code is:
>
>
> import resources_rc
>

​Hi Roberto,
Afaik, the plugin builder code is not wrong. You just have to adjust the
name of the output file when compiling the resources.
Best wishes,
Anita​





>
>
> I hope this helps to create new and useful plugins .
>
>
> Thank you in advance for attention
>
> Roberto
>
> ___
> 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] A common set of functions for QGIS plugins

2015-11-03 Thread Geo DrinX
Great Victor !

+1

:)



2015-11-02 13:52 GMT+01:00 Victor Olaya :

> Hi all,
>
> We have discussed sometimes in here about the need of having some
> common functions for plugin developers, to avoid all plugins having to
> reimplement those functions, sometimes not in the most correct way. It
> will also bring some homogeneity to plugins, which I think it is a
> good thing.
>
> With the changes that will be coming to QGIS soon, I think this is a
> good idea to work on, and I have started a small project here to
> create a set of Python modules with those common functions.
>
> https://github.com/volaya/qgiscommons
>
> Not much yet, but I plan to work on that and make it grow during this
> week. With the Hackfest coming, I think it is a good time to ask other
> devs to contribute...
>
> May plan of action is as follows:
>
> - Work on implementing a comprehensive set of functions and classes,
> hopefully with the help of other devs
>
> - Adapt Processing to use it and replace the current set of utilities
> that Processing (like many plugins) has.
>
> - Create a QEP to elevate this set of functions and classes to the
> qgis.utils module, so it has more visibility and it becomes a part of
> QGIS core.
>
> Following this, I believe the next steps that we could take could be:
>
> - Documenting this clearly in the PyCookbook, so all devs are aware of
> this.
>
> - Enforcing the use of common functions and classes, and even request
> it before a plugin is accepted for publishing
>
>
> Since we will be transitioning to Qt5/Python3, this set of common
> functions sounds also like a good place to add all kinds of utilities
> that might help this migration for existing plugins.
>
> Let me know your thoughts
>
> Even if you cannot contribute the code of a function to the repo, feel
> free to open an issue recommending functions that you consider should
> be in there. I will be working on this and will implement all those
> ideas if they sound interesting and useful for other people
>
>
> Thanks in advance
> ___
> 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] PluginBuilder writes a wrong import inside .py

2015-11-03 Thread Worth Lutz

This is not fixed.

Some background info:

http://gis.stackexchange.com/questions/139625/qgis-plugin-problems-importing-resources-resources-rc-file-plugin-doasnt-l/155599#155599

This is a problem with  "uic.loadUiType".

I have have determined that if you save your "ui" file in QT designer 
with the resources open after you have added a resource, you get this error.


This is because  QT designer adds

   
  
   

at the end of the file and this causes uic.loadUiType to look for a 
"resources_rc" as "_rc" is a default suffix.


I think closing the resource browser before saving the "ui" file in QT 
Designer will keep this added resources lines from being added to the 
end of the "ui" file.


*Worth Lutz*


On 11/3/2015 6:03 AM, Richard Duivenvoorde wrote:

On 03-11-15 11:45, Anita Graser wrote:

On Tue, Nov 3, 2015 at 10:49 AM, Geo DrinX > wrote:

 Hello all,

 probably you just know, but I found that "PluginBuilder"  plugin for
 QGIS  writes at line 26  of the main  .py  file the following code:

 import resources

 I think this is wrong,  because in run it returns a python error.

 The correct code is:

 import resources_rc

​Hi Roberto,
Afaik, the plugin builder code is not wrong. You just have to adjust the
name of the output file when compiling the resources.
Best wishes,
Anita​

Hi Roberto,

I've had this issue also some time ago, but according to Gary it should
be fixed:

https://github.com/g-sherman/Qgis-Plugin-Builder/issues/34

Note off course that plugins build with an older version of the builder
still will have the problem.
If you still have this problem with a current plugin, please report back
at the issuelist at Github

Regards,

Richard Duivenvoorde

___
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] [Linux Mint] QGIS Master 3d93237

2015-11-03 Thread Luigi Pirelli
just to confirm that partially reverting:

https://github.com/qgis/QGIS/commit/cd0eb05deddc610a1a79c40163504efddfe3da3a#diff-b19637a490515a065417f10b2ef58bbb:

using PyString_check instead of PyUnicode_check solve on Ubuntu 15.15
and Python 2.7.10.

my solution is in src/python/qgspythonutilsimpl.cpp:381

  /* And it should be a string all ready to go - duplicate it. */
  if ( !PyUnicode_CheckExact( obResult ) )
  if ( !PyString_Check( obResult ) )
TRACEBACK_FETCH_ERROR( "getvalue() did not return a string" );

regards
Luigi Pirelli

**
* LinkedIn: https://www.linkedin.com/in/luigipirelli
* Elance: https://www.elance.com/s/edit/luigipirelli/
* GitHub: https://github.com/luipir
* Stackexchange: http://gis.stackexchange.com/users/19667/luigi-pirelli
* Mastering QGIS:
https://www.packtpub.com/application-development/mastering-qgis
**


On 26 October 2015 at 23:10, Matthias Kuhn  wrote:
> Do you have any evidence that it's the PyUnicode_Check? I think that
> should be supported by Python 2.7 as well.
>
> The other error by Richard from IRC  (PyUnicode_AsUTF8) makes more
> sense, since it's not supported by 2.7 but it should be ifdef'd, strange
> that this happens. Maybe re-running cmake would help??
>
> On 10/26/2015 06:57 PM, Luigi Pirelli wrote:
>> Python 2.7.10 (default, Oct 14 2015, 16:09:02)
>> [GCC 5.2.1 20151010] on linux2
>>
>> and
>>
>> Python 3.4.3+ (default, Oct 14 2015, 16:03:50)
>> [GCC 5.2.1 20151010] on linux
>> Luigi Pirelli
>>
>> **
>> * LinkedIn: https://www.linkedin.com/in/luigipirelli
>> * Elance: https://www.elance.com/s/edit/luigipirelli/
>> * GitHub: https://github.com/luipir
>> * Stackexchange: http://gis.stackexchange.com/users/19667/luigi-pirelli
>> * Mastering QGIS:
>> https://www.packtpub.com/application-development/mastering-qgis
>> **
>>
>>
>> On 26 October 2015 at 17:53, Matthias Kuhn  wrote:
>>> Hi Luigi,
>>>
>>> What's the python version on your system?
>>>
>>> Matthias
>>>
>>> On 10/26/2015 10:32 AM, Luigi Pirelli wrote:
 Hi Mathias

 seems related with this your commit about Python3 compatbility

 cd0eb05deddc610a1a79c40163504efddfe3da3a

 src/python/qgspythonutilsimpl.cpp
 -  if ( !PyString_Check( obResult ) )
 +  if ( !PyUnicode_Check( obResult ) )
  TRACEBACK_FETCH_ERROR( "getvalue() did not return a string" );


 Luigi Pirelli

 **
 * LinkedIn: https://www.linkedin.com/in/luigipirelli
 * Elance: https://www.elance.com/s/edit/luigipirelli/
 * GitHub: https://github.com/luipir
 * Stackexchange: http://gis.stackexchange.com/users/19667/luigi-pirelli
 * Mastering QGIS:
 https://www.packtpub.com/application-development/mastering-qgis
 **


 On 25 October 2015 at 22:06, Luigi Pirelli  wrote:
> confirmed also ubuntu 15.10 and just pulled the qgis code.
>
> last log messages was oading the python module:
>
> src/app/qgisapp.cpp: 7911: (loadPythonSupport) [3ms] load library
> /home/ginetto/PROGRAMMING/QGIS-2.0-master/build/output/lib/qgispython
> (2.13.0)
>
> regards
> Luigi Pirelli
>
> **
> * LinkedIn: https://www.linkedin.com/in/luigipirelli
> * Elance: https://www.elance.com/s/edit/luigipirelli/
> * GitHub: https://github.com/luipir
> * Stackexchange: http://gis.stackexchange.com/users/19667/luigi-pirelli
> * Mastering QGIS:
> https://www.packtpub.com/application-development/mastering-qgis
> **
>
>
> On 25 October 2015 at 15:42, João Gaspar  
> wrote:
>> Hi guys,
>>
>> today after compile and install the master version when i open QGIS 
>> Master
>> and he give me this error:
>>
>> Couldn't load PyQGIS.
>> Python support will be disabled.
>>
>>
>> getvalue() did not return a string
>>
>> Python version:
>> 2.7.6 (default, Jun 22 2015, 18:01:27)
>> [GCC 4.8.2]
>>
>> QGIS version:
>> 2.13.0-Master 'Master', 3d93237
>>
>> Python path:
>> ['/home/joao/apps/share/qgis/python', u'/home/joao/.qgis2/python',
>> u'/home/joao/.qgis2/python/plugins',
>> 

[Qgis-developer] 2.5D rendering crowdfunding

2015-11-03 Thread Paolo Cavallini
Hi all,
regarding:
http://www.opengis.ch/2015/11/02/qgis-crowdfunding-2-5d-rendering
I remember Minoru had plans for a complete rewrite of qgis2threejs,
using native Qt 3D functions: would it be worthwhile to check also this
approach before starting to code?
All the best, and thanks.
-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] R: QgsBrowserDockWidget

2015-11-03 Thread Enrico Ferreguti
Hi Luigi, 
Contributing to core development is for now far from my skills. I was looking 
for a convenient way to browse available datasouces without to deal with qt gui 
engineering that is sometimes makes feel like reinventing the wheel. Thanks 
anyway.

Regards
Enrico Ferreguti

- Messaggio originale -
Da: "Luigi Pirelli" 
Inviato: ‎03/‎11/‎2015 18:11
A: "Enrico Ferreguti" 
Cc: "qgis-developer" 
Oggetto: Re: [Qgis-developer] QgsBrowserDockWidget

Hi Enrico,

I found other base classes in app that can be simply ported to library
without or with not so much code rewrite (e.g the identify widget).
I don't know about this class (seems there is only a qgisapp reference
using it's singleton), but usually is due the fact that it is a work
and developer would have time to do this.

in my opinion, feel free to do pull request... and hopefully adding test ;)

regards

Luigi Pirelli

**
* LinkedIn: https://www.linkedin.com/in/luigipirelli
* Elance: https://www.elance.com/s/edit/luigipirelli/
* GitHub: https://github.com/luipir
* Stackexchange: http://gis.stackexchange.com/users/19667/luigi-pirelli
* Mastering QGIS:
https://www.packtpub.com/application-development/mastering-qgis
**


On 3 November 2015 at 15:49, Enrico Ferreguti  wrote:
> Hi all.
>
> I notice that QgsBrowserDockWidget class is not included in python bindings.
> It would be great to have access to browser panel items from plugins.
> Is it intentional or an issue?
>
> Regards.
> Enrico Ferreguti
>
> ___
> 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] QgsBrowserDockWidget

2015-11-03 Thread Luigi Pirelli
Hi Enrico,

I found other base classes in app that can be simply ported to library
without or with not so much code rewrite (e.g the identify widget).
I don't know about this class (seems there is only a qgisapp reference
using it's singleton), but usually is due the fact that it is a work
and developer would have time to do this.

in my opinion, feel free to do pull request... and hopefully adding test ;)

regards

Luigi Pirelli

**
* LinkedIn: https://www.linkedin.com/in/luigipirelli
* Elance: https://www.elance.com/s/edit/luigipirelli/
* GitHub: https://github.com/luipir
* Stackexchange: http://gis.stackexchange.com/users/19667/luigi-pirelli
* Mastering QGIS:
https://www.packtpub.com/application-development/mastering-qgis
**


On 3 November 2015 at 15:49, Enrico Ferreguti  wrote:
> Hi all.
>
> I notice that QgsBrowserDockWidget class is not included in python bindings.
> It would be great to have access to browser panel items from plugins.
> Is it intentional or an issue?
>
> Regards.
> Enrico Ferreguti
>
> ___
> 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] 2.5D rendering crowdfunding

2015-11-03 Thread Minoru Akagi
Hi Paolo,

My plan is just to make interactive preview using Qt5 QWebView.
Continue to use JavaScript and three.js library.

Regards,
Minoru

2015-11-04 3:48 GMT+09:00 Paolo Cavallini :
> Hi all,
> regarding:
> http://www.opengis.ch/2015/11/02/qgis-crowdfunding-2-5d-rendering
> I remember Minoru had plans for a complete rewrite of qgis2threejs,
> using native Qt 3D functions: would it be worthwhile to check also this
> approach before starting to code?
> All the best, and thanks.
> --
> Paolo Cavallini - www.faunalia.eu
> QGIS & PostGIS courses: http://www.faunalia.eu/training.html
> ___
> 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] Any processing folks interested in pairing with a new QGIS developer?

2015-11-03 Thread Michael Kirk
Hi Victor,

Thank you for the offer. I’m looking at the paper Anita referenced now. Thanks 
Anita!

Let me know when you’d like to meet. I’m in Los Angeles (GMT - 8). Generally 
speaking, I’m available 18:00 to 3:00 your time, but given 24 hours notice, I 
can be available whenever you’d like between 15:00-9:00 your time.

M

> On Nov 2, 2015, at 11:38 PM, Victor Olaya  wrote:
> 
> Hey Michael
> 
> I will be happy to help on that. To start with, I would propose a
> quick hangout to discuss the Processing architecture (reading the
> paper Anita mentioned beforehand will help). What time zone are you
> in? I am on Paris one (GMT + 1)
> 
> 2015-11-03 8:16 GMT+01:00 Anita Graser :
>> Hi Michael,
>> 
>> If you haven't yet, you might be able to get an overview of the whole
>> framework by reading Victor Olaya's and my paper on Processing:
>> http://www.mdpi.com/2220-9964/4/4/2219
>> 
>> Best wishes
>> Anita
>> 
>> On Nov 3, 2015 2:16 AM, "Michael Kirk"  wrote:
>>> 
>>> Hello!
>>> 
>>> I’m dipping my toes into the code behind the processing toolkit. In
>>> particular, I’m interested in improving the Vector tools in the processing
>>> toolkit.
>>> 
>>> I am an experienced developer, but have spent most of the last decade
>>> writing web software. I’m making some progress, but not feeling very
>>> productive so far. When getting involved with new client projects, I find it
>>> really productive to pair with a developer who’s more familiar with the
>>> project. I’ve never tried this with an OSS project before, but are there any
>>> QGIS developers working on the processing module who are willing to mentor
>>> me by letting me remotely sit in with them on a programming session? I can
>>> be flexible so as to accommodate your schedule and programming style.
>>> 
>>> I feel that a couple of hours of your time would save me many days of
>>> orientation, while not costing you much. In fact, I’ve found a pair
>>> programmer improves my productivity even when the person I’m working with is
>>> completely unfamiliar with the project. Think of me as a sentient linter ;)
>>> 
>>> I typically use mostly shell tools (vim+tmux) for remote terminal and
>>> google hangouts for voice/video and occasional desktop sharing, but will use
>>> whatever you prefer.
>>> 
>>> Thanks for any support!
>>> 
>>> regards,
>>> Michael Kirk
>>> ___
>>> 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] 2.5D rendering crowdfunding

2015-11-03 Thread Matthias Kuhn
Hi Paolo,

The impact of this project is much bigger than this, 2.5D rendering is
just the showcase for

 * on-the-fly transformation of geometries while rendering (or with some
small additions also to create geometries based on attributes)
 * being able to specify the rendering order
 * styling the parts of multi-geometries individually
 * enhancements to the expression engine
 * style variables

Finally, in contrast to qgis2threejs it is all built around core
components of QGIS, so it will also be available e.g. on QGIS server.

In short: sponsoring this project is a long-term investment into QGIS
capabilities.

http://www.opengis.ch/2015/11/02/qgis-crowdfunding-2-5d-rendering


All the best,
Matthias

On 11/03/2015 07:48 PM, Paolo Cavallini wrote:
> Hi all,
> regarding:
> http://www.opengis.ch/2015/11/02/qgis-crowdfunding-2-5d-rendering
> I remember Minoru had plans for a complete rewrite of qgis2threejs,
> using native Qt 3D functions: would it be worthwhile to check also this
> approach before starting to code?
> All the best, and thanks.




signature.asc
Description: OpenPGP digital signature
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] QgsBrowserDockWidget

2015-11-03 Thread Enrico Ferreguti
Hi all.

I notice that QgsBrowserDockWidget class is not included in python bindings.
It would be great to have access to browser panel items from plugins.
Is it intentional or an issue?

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

[Qgis-developer] Ubuntu Wily: Compile from source troubles with QWT

2015-11-03 Thread Neumann, Andreas
 

Hi, 

Every time Ubuntu is upgraded I run into troubles with qwt. 

Now I upgraded to Ubuntu Wily and compile fails because of some qwt
issue. I get: 

- 

[ 31%] Built target pycore 
CMakeFiles/qgis_gui.dir/raster/qgsrasterhistogramwidget.cpp.o: In
function `QgsRasterHistogramWidget::refreshHistogram()': 
/home/an/dev/QGIS/src/gui/raster/qgsrasterhistogramwidget.cpp:358:
undefined reference to `QwtPlot::insertLegend(QwtAbstractLegend*,
QwtPlot::LegendPosition, double)' 
/home/an/dev/QGIS/src/gui/raster/qgsrasterhistogramwidget.cpp:362:
undefined reference to `QwtPlot::setAxisAutoScale(int, bool)' 
/home/an/dev/QGIS/src/gui/raster/qgsrasterhistogramwidget.cpp:513:
undefined reference to `QwtPlotHistogram::QwtPlotHistogram(QString
const&)' 
/home/an/dev/QGIS/src/gui/raster/qgsrasterhistogramwidget.cpp:516:
undefined reference to `QwtPlotHistogram::setPen(QPen const&)' 
/home/an/dev/QGIS/src/gui/raster/qgsrasterhistogramwidget.cpp:518:
undefined reference to `QwtPlotHistogram::setBrush(QBrush const&)' 
/home/an/dev/QGIS/src/gui/raster/qgsrasterhistogramwidget.cpp:584:
undefined reference to `QwtPlotCurve::setSamples(QVector
const&)' 
/home/an/dev/QGIS/src/gui/raster/qgsrasterhistogramwidget.cpp:589:
undefined reference to
`QwtPlotHistogram::setSamples(QVector const&)' 
/home/an/dev/QGIS/src/gui/raster/qgsrasterhistogramwidget.cpp:631:
undefined reference to `QwtPlotMarker::QwtPlotMarker(QString const&)' 
/home/an/dev/QGIS/src/gui/raster/qgsrasterhistogramwidget.cpp:633:
undefined reference to `QwtPlotMarker::QwtPlotMarker(QString const&)' 
/home/an/dev/QGIS/src/gui/raster/qgsrasterhistogramwidget.cpp:640:
undefined reference to `QwtPlotPicker::QwtPlotPicker(QWidget*)' 
/home/an/dev/QGIS/src/gui/raster/qgsrasterhistogramwidget.cpp:645:
undefined reference to
`QwtPickerDragPointMachine::QwtPickerDragPointMachine()' 
/home/an/dev/QGIS/src/gui/raster/qgsrasterhistogramwidget.cpp:657:
undefined reference to `QwtPlotZoomer::QwtPlotZoomer(QWidget*, bool)' 
/home/an/dev/QGIS/src/gui/raster/qgsrasterhistogramwidget.cpp:659:
undefined reference to
`QwtPickerDragRectMachine::QwtPickerDragRectMachine()' 
CMakeFiles/qgis_gui.dir/raster/qgsrasterhistogramwidget.cpp.o: In
function `QgsRasterHistogramWidget::histoSaveAsImage(QString const&,
int, int, int)': 
/home/an/dev/QGIS/src/gui/raster/qgsrasterhistogramwidget.cpp:717:
undefined reference to `QwtPlotRenderer::QwtPlotRenderer(QObject*)' 
/home/an/dev/QGIS/src/gui/raster/qgsrasterhistogramwidget.cpp:719:
undefined reference to
`QwtPlotRenderer::setDiscardFlags(QFlags)'

/home/an/dev/QGIS/src/gui/raster/qgsrasterhistogramwidget.cpp:720:
undefined reference to
`QwtPlotRenderer::setLayoutFlags(QFlags)' 
/home/an/dev/QGIS/src/gui/raster/qgsrasterhistogramwidget.cpp:724:
undefined reference to `QwtPlotRenderer::render(QwtPlot*, QPainter*,
QRectF const&) const' 
/home/an/dev/QGIS/src/gui/raster/qgsrasterhistogramwidget.cpp:717:
undefined reference to `QwtPlotRenderer::~QwtPlotRenderer()' 
/home/an/dev/QGIS/src/gui/raster/qgsrasterhistogramwidget.cpp:717:
undefined reference to `QwtPlotRenderer::~QwtPlotRenderer()' 
CMakeFiles/qgis_gui.dir/raster/qgsrasterhistogramwidget.cpp.o: In
function `findClosestTickVal(double, QwtScaleDiv const*, int)': 
/home/an/dev/QGIS/src/gui/raster/qgsrasterhistogramwidget.cpp:1068:
undefined reference to `QwtScaleDiv::upperBound() const' 
CMakeFiles/qgis_gui.dir/symbology-ng/qgsgraduatedhistogramwidget.cpp.o:
In function
`QgsGraduatedHistogramWidget::QgsGraduatedHistogramWidget(QWidget*)': 
/home/an/dev/QGIS/src/gui/symbology-ng/qgsgraduatedhistogramwidget.cpp:61:
undefined reference to `QwtPlotPicker::QwtPlotPicker(QWidget*)' 
/home/an/dev/QGIS/src/gui/symbology-ng/qgsgraduatedhistogramwidget.cpp:65:
undefined reference to
`QwtPickerDragPointMachine::QwtPickerDragPointMachine()' 
CMakeFiles/qgis_gui.dir/qgshistogramwidget.cpp.o: In function
`QgsHistogramWidget::drawHistogram()': 
/home/an/dev/QGIS/src/gui/qgshistogramwidget.cpp:200: undefined
reference to `QwtPlot::setAxisAutoScale(int, bool)' 
/home/an/dev/QGIS/src/gui/qgshistogramwidget.cpp:201: undefined
reference to `QwtPlot::setAxisAutoScale(int, bool)' 
/home/an/dev/QGIS/src/gui/qgshistogramwidget.cpp:256: undefined
reference to `QwtPlotHistogram::setSamples(QVector
const&)' 
/home/an/dev/QGIS/src/gui/qgshistogramwidget.cpp:286: undefined
reference to `QwtPlotHistogram::setSamples(QVector
const&)' 
/home/an/dev/QGIS/src/gui/qgshistogramwidget.cpp:296: undefined
reference to `QwtPlotMarker::QwtPlotMarker(QString const&)' 
/home/an/dev/QGIS/src/gui/qgshistogramwidget.cpp:309: undefined
reference to `QwtPlotMarker::QwtPlotMarker(QString const&)' 
/home/an/dev/QGIS/src/gui/qgshistogramwidget.cpp:321: undefined
reference to `QwtPlotMarker::QwtPlotMarker(QString const&)' 
/home/an/dev/QGIS/src/gui/qgshistogramwidget.cpp:330: undefined
reference to `QwtPlotMarker::QwtPlotMarker(QString const&)' 
CMakeFiles/qgis_gui.dir/qgshistogramwidget.cpp.o: In function

Re: [Qgis-developer] Ubuntu Wily: Compile from source troubles with QWT

2015-11-03 Thread Jürgen E . Fischer
Hi Andreas,

On Tue, 03. Nov 2015 at 14:57:23 +0100, Neumann, Andreas wrote:
> Every time Ubuntu is upgraded I run into troubles with qwt. 

Anything wrong with our wily packages?
 

Jürgen

-- 
Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
Software Engineer   D-26506 Norden http://www.norbit.de
QGIS release manager (PSC)  GermanyIRC: jef on FreeNode 



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