Re: [Qgis-developer] Adding plugins to core?
Il 05/04/2014 18:59, Alex Mandel ha scritto: Perhaps the proposal is really, which plugins to ship by default? Which sounds the same but is slightly different or could be interpreted differently as add the plugins to core. right, thanks for clarifying. I'm +1 for adding a few more default plugins to the distribution, especially if they are very common in usage. Remember though, there is a trade-off, putting too many things in the default interface is overwhelming for some levels of users. It makes GIS more daunting than it needs to be. Agreed, that's why I was calling for a common decision. My suggestion is to disable by default those with a complex interface (e.g. CAD Tools). I suggest to do it for 2.4, at least for the three most popular: http://plugins.qgis.org/plugins/openlayers_plugin/ http://plugins.qgis.org/plugins/tablemanager/ http://plugins.qgis.org/plugins/mmqgis/ In my experience, these are effectively hidden features for many QGIS users. All the best. -- 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] Building on OSX - QgsAbstractFeatureIteratorFromSource
Environment: OSX Lion This is a frustrating one. The other day after following the build instructions I was able to build the main QGIS src tree successfully. However, today I had to make a fresh build (of just the main tree) and kept getting stuck here: /dev/cpp/QGIS/src/core/qgsvectorlayerfeatureiterator.cpp:87: error: class ‘QgsVectorLayerFeatureIterator’ does not have any field named ‘QgsAbstractFeatureIteratorFromSource’ /dev/cpp/QGIS/src/core/qgsvectorlayerfeatureiterator.cpp:88: error: no matching function for call to ‘QgsAbstractFeatureIteratorFromSourceQgsVectorLayerFeatureSource::QgsAbstractFeatureIteratorFromSource()’ It is almost certainly something environmental and likely trivial, but being new to the dev. environment I post this here in the hope someone can point me in the right direction quickly. Thank you. -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Building-on-OSX-QgsAbstractFeatureIteratorFromSource-tp5133371.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] Adding plugins to core?
Hi, I agree there are some plugin which could be added by default, whenever QGIS has no approaching feature like Openlayers plugin. For some plugins such as tablemanager, I think we would better add the features in core, to let the user modify the fields in the Fields tab of the layer properties, and not in an other plugin dialog. 2014-04-06 8:36 GMT+02:00 Paolo Cavallini cavall...@faunalia.it: Il 05/04/2014 18:59, Alex Mandel ha scritto: Perhaps the proposal is really, which plugins to ship by default? Which sounds the same but is slightly different or could be interpreted differently as add the plugins to core. right, thanks for clarifying. I'm +1 for adding a few more default plugins to the distribution, especially if they are very common in usage. Remember though, there is a trade-off, putting too many things in the default interface is overwhelming for some levels of users. It makes GIS more daunting than it needs to be. Agreed, that's why I was calling for a common decision. My suggestion is to disable by default those with a complex interface (e.g. CAD Tools). I suggest to do it for 2.4, at least for the three most popular: http://plugins.qgis.org/plugins/openlayers_plugin/ http://plugins.qgis.org/plugins/tablemanager/ http://plugins.qgis.org/plugins/mmqgis/ In my experience, these are effectively hidden features for many QGIS users. All the best. -- 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] Adding plugins to core?
Paolo Don't you think that adding mmqgis plugin into core will cause a lot of confusion, considering that its algorithms are already integrated in Processing (even with bug fixes in some cases)? I agree that it would be a great thing to have the OpenLayers plugin (or at least a similalar functionality) available by default in core 2014-04-06 16:10 GMT+02:00 kimaidou kimai...@gmail.com: Hi, I agree there are some plugin which could be added by default, whenever QGIS has no approaching feature like Openlayers plugin. For some plugins such as tablemanager, I think we would better add the features in core, to let the user modify the fields in the Fields tab of the layer properties, and not in an other plugin dialog. 2014-04-06 8:36 GMT+02:00 Paolo Cavallini cavall...@faunalia.it: Il 05/04/2014 18:59, Alex Mandel ha scritto: Perhaps the proposal is really, which plugins to ship by default? Which sounds the same but is slightly different or could be interpreted differently as add the plugins to core. right, thanks for clarifying. I'm +1 for adding a few more default plugins to the distribution, especially if they are very common in usage. Remember though, there is a trade-off, putting too many things in the default interface is overwhelming for some levels of users. It makes GIS more daunting than it needs to be. Agreed, that's why I was calling for a common decision. My suggestion is to disable by default those with a complex interface (e.g. CAD Tools). I suggest to do it for 2.4, at least for the three most popular: http://plugins.qgis.org/plugins/openlayers_plugin/ http://plugins.qgis.org/plugins/tablemanager/ http://plugins.qgis.org/plugins/mmqgis/ In my experience, these are effectively hidden features for many QGIS users. All the best. -- 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 ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] How to get renderComplete painter reference
Hi, I need the painter from the renderComplete signal? Could you help me with the correct syntax? I have: self.iface.mapCanvas().renderComplete.connect(self.waitAfterRenderComplete) and def waitAfterRenderComplete(self, painter): but waitAfterRenderComplete does not receive a painter. Thanks and best wishes, Anita -- anitagraser.com ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] [Processing] field calculator: area
Hello, Is there a way to process area for each polygon in the field calculator in the processing/Sextant plugin? Thanks, Y. -- Yves Jacolin ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] How to get renderComplete painter reference
On 4/6/2014 11:08 AM, Anita Graser wrote: Hi, I need the painter from the renderComplete signal? Could you help me with the correct syntax? I have: self.iface.mapCanvas().renderComplete.connect(self.waitAfterRenderComplete) and def waitAfterRenderComplete(self, painter): but waitAfterRenderComplete does not receive a painter. Thanks and best wishes, Anita Good to see development on this plugin. Many thanks from someone that uses Time Manger. Garibaldi ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] How to get renderComplete painter reference
Anita, just saw you commited a fix. Thanks! May I suggest a small improvement? You should calculate the time it took, in ms, to render canvas and deduce that ms value from the animationFrameLength ms value in your singleShot call: QTimer.singleShot(self.animationFrameLength,self.playAnimation) Currently if you have a 1000ms frame length and canvas rendering takes 500ms, each frame will last 1500ms. Deducing the 500ms canvas rendering time from frame length will fix this. If rendering ms frame length ms, that'd allow you to skip singleShot and render next frame immediately. Cheers and thanks again. Math On 6 Apr 2014 23:08, Anita Graser anitagra...@gmx.at wrote: Hi, I need the painter from the renderComplete signal? Could you help me with the correct syntax? I have: self.iface.mapCanvas().renderComplete.connect(self. waitAfterRenderComplete) and def waitAfterRenderComplete(self, painter): but waitAfterRenderComplete does not receive a painter. Thanks and best wishes, Anita -- anitagraser.com ___ 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] Adding plugins to core?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 06/04/2014 16:40, Victor Olaya ha scritto: Don't you think that adding mmqgis plugin into core will cause a lot of confusion, considering that its algorithms are already integrated in Processing (even with bug fixes in some cases)? oh. right. why then keeping it also separated? could the author be asked to merge his job in Processing? I think keeping both may be confusing. I agree that it would be a great thing to have the OpenLayers plugin (or at least a similalar functionality) available by default in core It seems that we all agree on this could you write the list, so we'll ask Pirmin? All the best. - -- Paolo Cavallini - www.faunalia.eu Corsi QGIS e PostGIS: http://www.faunalia.eu/training.html -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlNCL10ACgkQ/NedwLUzIr5Q0wCfXcLVKlCujzZLoj7RN6wtYvAR pmwAoJTOQNEVjanuGmTVGYNjoyKjbVUJ =at1A -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Adding plugins to core?
On 7 April 2014 14:53, Paolo Cavallini cavall...@faunalia.it wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I agree that it would be a great thing to have the OpenLayers plugin (or at least a similalar functionality) available by default in core It seems that we all agree on this could you write the list, so we'll ask Pirmin? All the best. I'm not 100% sure on this, but isn't the OpenLayers plugin a bit legally murky? I'm pretty sure that it's either violating the Google maps terms of service or if not, it's cutting it pretty close. I know the Viking GPS program ran into issues back in 2008 with their in-built support for google maps layers [1][2] and were forced to remove this support. Having OpenLayers as a non-official plugin gives us some distance from issues like this - if we make this a core feature then we are effectively endorsing this functionality and may be opening ourselves to potential legal issues. Nyall [1] http://sourceforge.net/p/viking/mailman/viking-devel/thread/492ffe74.6060...@gmail.com/ [2] http://sourceforge.net/p/viking/mailman/message/20797817/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
