Re: [Qgis-developer] QgsRunProcess: forwarding the finished() signal?
2012/12/6 Rafael Varela Pet rafael.var...@gmail.com I think that it would be useful if QgsRunProcess::processExit() [1] forwards the finished() signal [2] sent by QProcess, so a plugin that runs an external process could detect when the process exits. Should I file an enhancement request or there's already a method to achieve this? Finally I've filed a request for this: http://hub.qgis.org/issues/6844 Best regards, -- Rafael Varela ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Proposal for organizing algorithms in SEXTANTE
2012/12/7 Victor Olaya vola...@gmail.com: Hi all Hi Victor I have been doing some work to have an alternative organization of algorithms in the SEXTANTE toolbox, targeted at the non-advanced users. I can be now be enabled in the SEXTANTE configuration. When this is active, algorithms do not appear as belonging to a provider, but just under a common branch simply called algorithms. All available algorithms are classified in categories, independently of their origin. This gives a more homogeneous interface and should make it easier for users to select the algorithm they need. I think this is important to make it easier and more intuitive to use SEXTANTE and the (very) large number or algorithms it currently contains, and it is an area that we should work on. This homogeneous interface requires some extra work to be done: - Defining a set of categories, based on a criteria that is agreed as the best one (or even define several of them, according to different criteria, such as field of application, type of data it needs, etc). - Define categories for each algorithm, and also alternative names, since now they do not follow a similar pattern (GRASS ones, for instance, are too verbose). This is stored independently of the algorithms and their names, so it can be used as a decoration, and different naming schemes can be used, or a different classification. Since no classification has been defined yet, now all algorithms use their normal undecorated name and group name, but the functionality is already there, and ready to A third task will round this up, but implies clearly a larger amount of work: - Write help files for algorithms using a common template. A single help file written in RestructuredText, that can be turned into HTML to display basic ideas about each algorithm, like a description of the process or an explanation about the meaning of each input and output. Algorithms already documented (like GRASS ones), should be easily adapted to this in some automated way. I plan to write some kind of script to automate the creation of the basic files for all remaining algorithms, including parameter names, etc. I don't know if could be useful but here [0] you can find a Python script to obtain topics about GRASS commands and also a classification of each modules. You can find the result here [1] [0] http://trac.osgeo.org/grass/browser/grass/trunk/man/build_topics.py [1] http://grass.osgeo.org/grass70/manuals/topics.html Victor Regards -- ciao Luca http://gis.cri.fmach.it/delucchi/ www.lucadelu.org ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Is there already a fix for bug #6638?
Hi Could someone tell me if this [1] pull request will fix the bug #6638 'Cannot set custom form with python for vector layer' [2] (which I think is a blocker btw)? If so, when can we expect it to be merged in master? (Alternatively, can someone guide me on how to find out if a particular pull request is merged into master?) kind regards Josef [1] https://github.com/qgis/Quantum-GIS/pull/320https://github.com/qgis/Quantum-GIS/commit/9183adce9f257a097fc54e5a8a700e4d494b2962 [2] http://hub.qgis.org/issues/6638 ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Strange integer column value within SpatiaLite database
Hi, I found something strange with data in a table within a SpatiaLite database. As you can see in this image [1], viewing the table in QSpatiaLite, the column GEO_COD (integer) appears well. The same column, when viewed in the QGIS attribute table, appears with values totally different. Can anyone find an explanation? I leave the database in question in order to test [2]. I'm using QGIS master on Xubuntu 12.04. Best regards, Pedro Venâncio [1] http://goo.gl/s8toX [2] http://goo.gl/RNRmb ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Is there already a fix for bug #6638?
Hi, this code has been merged Link [1] tells you that it has been merged 24 days ago with the commit number in question. Go to pull requests and choose a random pull request to see, what an open pull request looks like. Thank you for the link to the issue report, that somehow escaped my attention. It's closed now. Regards, Matthias On 12/09/2012 10:50 PM, Josef K wrote: Hi Could someone tell me if this [1] pull request will fix the bug #6638 'Cannot set custom form with python for vector layer' [2] (which I think is a blocker btw)? If so, when can we expect it to be merged in master? (Alternatively, can someone guide me on how to find out if a particular pull request is merged into master?) kind regards Josef [1] https://github.com/qgis/Quantum-GIS/pull/320 https://github.com/qgis/Quantum-GIS/commit/9183adce9f257a097fc54e5a8a700e4d494b2962 [2] http://hub.qgis.org/issues/6638 ___ 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
