Re: [Qgis-developer] Toolbar and Panel defaults
Hi Pirmin, On Tue, 09. Jul 2013 at 22:55:18 +0200, Pirmin Kalberer wrote: Toolbars: -Turn off Advanced Digitizing -Move Label to second row Panels: -Turn on Layer order and Browser in a tabbed view with Layers Print composer: -Place all toolbars in one row In case anyone missed it: scripts/mkuidefaults.py produces src/app/ui_defaults.h from the current settings. So updating it should be easy, once it's decides what should be the default. Not sure if the data contains pixel coordinates and if the screen resolution might therefore be an issue... Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de committ(ed|ing) to QGISIRC: jef on FreeNode -- norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH Rheinstrasse 13, 26506 Norden GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502 ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] map rendering time much longer on windows than on ubuntu
Hi all, Thanks for your reply. I have noticed it seems that postgres request are much longer from the win computer than from ubuntu (on the same external server of course). I timed this request: Ubuntu: 100% about 45 ms Win: 50-70% about 45ms, 30-50% between 250 and 700ms, sometime even more. I googled without finding anything relevant... Have someone experience something similar? Also, I'd like to try to remove the debug info. Is the correct way to do this: in environment variables: add a QGIS_DEBUG variable with -1 value in the user variables? Cheers, Denis ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] map rendering time much longer on windows than on ubuntu
Hi Denis, On Wed, 10. Jul 2013 at 09:52:33 +0200, Denis Rouzaud wrote: Also, I'd like to try to remove the debug info. Is the correct way to do this: in environment variables: add a QGIS_DEBUG variable with -1 value in the user variables? That would still produce the output, but not show it. Not sure if the pure production alone also has a noticable impact. But the production of the output doesn't really explain, why the same requests are sometimes slower. Maybe looking at the output would help here ;) Otherwise getting rid of debugging output completely would require a Release build (which would not include -DQGISDEBUG). Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de committ(ed|ing) to QGISIRC: jef on FreeNode -- norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH Rheinstrasse 13, 26506 Norden GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502 ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] SEXTANTE: R output?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all. On current master, example R scripts apparently run without issues, but no output is shown in the Results window. The resulting html is of the type: font face=courier h2 R Output/h2 /font or img src=/tmp/sextante/rrasterhistogram18a1cdc6d0734098bc728452ee90d3a6.html.png/ but the png is not there. Any suggestion? 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 Icedove - http://www.enigmail.net/ iEYEARECAAYFAlHdKMEACgkQ/NedwLUzIr7wjwCbBSZveJkEDRFsXLiWsA+ZvXIc etcAn0VRyo/H5oY1J3ceFMf+hgl9MTn0 =CfWk -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] SEXTANTE: R output?
Hi, What's your R version? http://hub.qgis.org/issues/8012 On Wed, Jul 10, 2013 at 10:26 AM, Paolo Cavallini cavall...@faunalia.itwrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all. On current master, example R scripts apparently run without issues, but no output is shown in the Results window. The resulting html is of the type: font face=courier h2 R Output/h2 /font or img src=/tmp/sextante/rrasterhistogram18a1cdc6d0734098bc728452ee90d3a6.html.png/ but the png is not there. Any suggestion? 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 Icedove - http://www.enigmail.net/ iEYEARECAAYFAlHdKMEACgkQ/NedwLUzIr7wjwCbBSZveJkEDRFsXLiWsA+ZvXIc etcAn0VRyo/H5oY1J3ceFMf+hgl9MTn0 =CfWk -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] SEXTANTE: R output?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 10/07/2013 11:28, Filipe Dias ha scritto: What's your R version? http://hub.qgis.org/issues/8012 oh, you're right: $ aptitude show r-base Pacchetto: r-base Nuovo: s￬ Stato: non installato Versione: 3.0.1-3 sorry I forgot. Any hope to have it fixed? 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 Icedove - http://www.enigmail.net/ iEYEARECAAYFAlHdKlgACgkQ/NedwLUzIr5rVACgs8T7ngInUgjyCLxQVI/UTA7h y4cAoJutFEk5EBoFPnqWL/uNN6o8SLla =yGDR -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] SEXTANTE: R output?
I believe Victor Olaya is looking into it. On Wed, Jul 10, 2013 at 10:33 AM, Paolo Cavallini cavall...@faunalia.itwrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 10/07/2013 11:28, Filipe Dias ha scritto: What's your R version? http://hub.qgis.org/issues/8012 oh, you're right: $ aptitude show r-base Pacchetto: r-base Nuovo: s￬ Stato: non installato Versione: 3.0.1-3 sorry I forgot. Any hope to have it fixed? 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 Icedove - http://www.enigmail.net/ iEYEARECAAYFAlHdKlgACgkQ/NedwLUzIr5rVACgs8T7ngInUgjyCLxQVI/UTA7h y4cAoJutFEk5EBoFPnqWL/uNN6o8SLla =yGDR -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] SEXTANTE: R output?
Yes, Filipe reported that and I hope I can fix it soon. I didn't have much time these last days, but let's see if I can work on it later today. Sorry for that Thanks for your help! Victor p.s. One question: Is R 3.0 now more common than 2.x among R users? Should we make 3.0 the target version in SEXTANTE? 2013/7/10 Filipe Dias filipesd...@gmail.com: I believe Victor Olaya is looking into it. On Wed, Jul 10, 2013 at 10:33 AM, Paolo Cavallini cavall...@faunalia.it wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 10/07/2013 11:28, Filipe Dias ha scritto: What's your R version? http://hub.qgis.org/issues/8012 oh, you're right: $ aptitude show r-base Pacchetto: r-base Nuovo: s￬ Stato: non installato Versione: 3.0.1-3 sorry I forgot. Any hope to have it fixed? 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 Icedove - http://www.enigmail.net/ iEYEARECAAYFAlHdKlgACgkQ/NedwLUzIr5rVACgs8T7ngInUgjyCLxQVI/UTA7h y4cAoJutFEk5EBoFPnqWL/uNN6o8SLla =yGDR -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] qgis-webclient - sample data 200M
Hi, I just wanted to update my fork of the qgis-web-client from master and found following error message: Total 64 (delta 45), reused 0 (delta 0) remote: Error code: 5e0226a6eeb7f2d80768c4e7996297dc remote: warning: Error GH413: Large files detected. remote: warning: See http://git.io/iEPt8g for more information. remote: warning: File data/SR_50M.tif is 55.70 MB; this is larger than GitHub's recommended maximum file size of 50 MB remote: error: File data/HYP_50M_SR_W.tif is 166.94 MB; this exceeds GitHub's file size limit of 100 MB Can I tell github to change the accepted file size or would it be possible to use smaller test data? 167M - HYP_50M_SR_W.tif 56M - SR_50M.tif Regards Otto ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] qgis-webclient - sample data 200M
Hi Otto, Thank you for pointing this out. Isn't this just a warning? If you have a good test project with smaller data to share I am happy to replace it with a smaller project. I just did not have the time to work on the sample project. Anyway - the file could be checked out by hand or it can just be ignored. Andreas Am 10.07.2013 11:49, schrieb Otto Dassau: Hi, I just wanted to update my fork of the qgis-web-client from master and found following error message: Total 64 (delta 45), reused 0 (delta 0) remote: Error code: 5e0226a6eeb7f2d80768c4e7996297dc remote: warning: Error GH413: Large files detected. remote: warning: See http://git.io/iEPt8g for more information. remote: warning: File data/SR_50M.tif is 55.70 MB; this is larger than GitHub's recommended maximum file size of 50 MB remote: error: File data/HYP_50M_SR_W.tif is 166.94 MB; this exceeds GitHub's file size limit of 100 MB Can I tell github to change the accepted file size or would it be possible to use smaller test data? 167M - HYP_50M_SR_W.tif 56M - SR_50M.tif Regards Otto ___ 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] SEXTANTE: R output?
According to the release notes R 3.0 should be faster than previous versions with big data so I guess it would make sense to make it the target version. However, most R users tend to wait a while to update. Would it be to difficult to support both R3.0 and R 3 ? On Wed, Jul 10, 2013 at 10:43 AM, Paolo Cavallini cavall...@faunalia.itwrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 10/07/2013 11:39, Victor Olaya ha scritto: Yes, Filipe reported that and I hope I can fix it soon. I didn't have much time these last days, but let's see if I can work on it later today. Sorry for that thanks p.s. One question: Is R 3.0 now more common than 2.x among R users? Should we make 3.0 the target version in SEXTANTE? At least on Debian, yes: http://packages.debian.org/search?keywords=r-basesearchon=names 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 Icedove - http://www.enigmail.net/ iEYEARECAAYFAlHdLNoACgkQ/NedwLUzIr4bBwCfX9MLuiOhmLcsIplQMBpLNwqo PSwAnjkmGv/eLmuwKCHhLHAuzTZqGtXw =cyHN -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] qgis-webclient - sample data 200M
Hi Andreas, for 50M to 100M you get a warning, but the HYP_50M_SR_W.tif is 166.94 MB and that's too much. For both files I resampled output files from 0.03 to 0.08 degree pixel resolution. That is 4500 x 2250 instead of 10800, 5400 pixel. Still sufficient I think. Both would now be below 50M of size. Is that ok? Then I would commit the changes. Regards Otto Am Wed, 10 Jul 2013 12:09:47 +0200 schrieb Andreas Neumann a.neum...@carto.net: Hi Otto, Thank you for pointing this out. Isn't this just a warning? If you have a good test project with smaller data to share I am happy to replace it with a smaller project. I just did not have the time to work on the sample project. Anyway - the file could be checked out by hand or it can just be ignored. Andreas Am 10.07.2013 11:49, schrieb Otto Dassau: Hi, I just wanted to update my fork of the qgis-web-client from master and found following error message: Total 64 (delta 45), reused 0 (delta 0) remote: Error code: 5e0226a6eeb7f2d80768c4e7996297dc remote: warning: Error GH413: Large files detected. remote: warning: See http://git.io/iEPt8g for more information. remote: warning: File data/SR_50M.tif is 55.70 MB; this is larger than GitHub's recommended maximum file size of 50 MB remote: error: File data/HYP_50M_SR_W.tif is 166.94 MB; this exceeds GitHub's file size limit of 100 MB Can I tell github to change the accepted file size or would it be possible to use smaller test data? 167M - HYP_50M_SR_W.tif 56M - SR_50M.tif Regards Otto ___ 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 -- Geoinformatik Büro Dassau - http://www.gbd-consult.de FOSSGIS consulting , training , support and analysis Ackerstrasse 144c , D - 40233 Düsseldorf , Germany Tel: +49-(0)211-47468178 , Mobil: +49-(0)171-4687540 -- Community Advisor - QGIS Project Steering Committee ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] qgis-webclient - sample data 200M
Hi Otto, Yes - please go ahead. Thanks, Andreas Am 10.07.2013 13:07, schrieb Otto Dassau: Hi, thanks for the link. Here is the content in short: GitHub warns you when you push a file larger than 50 MB. We'll reject pushes containing files larger than 100 MB. We do this for a few reasons. To fix the problem, you'll first want to remove the large file from git: # Stage our giant file for removal, but leave it on disk git rm --cached giant_file # Amend the previous commit with your change # Simply making a new commit won't work, as you need to remove the file from # the # unpushed history as well git commit --amend -CHEAD # Push our rewritten, smaller commit git push I can do that and apply the smaller, resampled files, if that's ok. Regards Otto Am Wed, 10 Jul 2013 12:50:45 +0200 schrieb Tim Sutton li...@linfiniti.com: Hi I know gh recently reduced their maximum hosted file size - see https://help.github.com/articles/working-with-large-files Regards Tim On Wed, Jul 10, 2013 at 12:30 PM, Otto Dassau das...@gbd-consult.de wrote: Hi Andreas, for 50M to 100M you get a warning, but the HYP_50M_SR_W.tif is 166.94 MB and that's too much. For both files I resampled output files from 0.03 to 0.08 degree pixel resolution. That is 4500 x 2250 instead of 10800, 5400 pixel. Still sufficient I think. Both would now be below 50M of size. Is that ok? Then I would commit the changes. Regards Otto Am Wed, 10 Jul 2013 12:09:47 +0200 schrieb Andreas Neumann a.neum...@carto.net: Hi Otto, Thank you for pointing this out. Isn't this just a warning? If you have a good test project with smaller data to share I am happy to replace it with a smaller project. I just did not have the time to work on the sample project. Anyway - the file could be checked out by hand or it can just be ignored. Andreas Am 10.07.2013 11:49, schrieb Otto Dassau: Hi, I just wanted to update my fork of the qgis-web-client from master and found following error message: Total 64 (delta 45), reused 0 (delta 0) remote: Error code: 5e0226a6eeb7f2d80768c4e7996297dc remote: warning: Error GH413: Large files detected. remote: warning: See http://git.io/iEPt8g for more information. remote: warning: File data/SR_50M.tif is 55.70 MB; this is larger than GitHub's recommended maximum file size of 50 MB remote: error: File data/HYP_50M_SR_W.tif is 166.94 MB; this exceeds GitHub's file size limit of 100 MB Can I tell github to change the accepted file size or would it be possible to use smaller test data? 167M - HYP_50M_SR_W.tif 56M - SR_50M.tif Regards Otto ___ 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 -- Geoinformatik Büro Dassau - http://www.gbd-consult.de FOSSGIS consulting , training , support and analysis Ackerstrasse 144c , D - 40233 Düsseldorf , Germany Tel: +49-(0)211-47468178 , Mobil: +49-(0)171-4687540 -- Community Advisor - QGIS Project Steering Committee ___ 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] map rendering time much longer on windows than on ubuntu
Hi Jürgen, Effectively, I noticed the postgres difference from the command line, so nothing related to QGIS...I'll try to investigate the question with our IT . The problem is that QGIS is almost unusable in these conditions, with rendering time of about 2s! Is there an easy way to produce a windows installer? By easy I mean from my compilation environment on ubuntu? Or do I need to compile on Windows? Thanks, Denis On 07/10/2013 10:19 AM, Jürgen E. Fischer wrote: Hi Denis, On Wed, 10. Jul 2013 at 09:52:33 +0200, Denis Rouzaud wrote: Also, I'd like to try to remove the debug info. Is the correct way to do this: in environment variables: add a QGIS_DEBUG variable with -1 value in the user variables? That would still produce the output, but not show it. Not sure if the pure production alone also has a noticable impact. But the production of the output doesn't really explain, why the same requests are sometimes slower. Maybe looking at the output would help here ;) Otherwise getting rid of debugging output completely would require a Release build (which would not include -DQGISDEBUG). Jürgen ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] CyberTracker integration
Hi Augustin, Yes, I recall. Thanks, that was good work! I'll take a look at OruxMaps and Spatialite. We often get queries to add more GIS functionality to CyberTracker both for the desktop and the PDA. While it would be nice to keep it simple, it seems like over time people will want to do more and more away from their desktop. Especially as we start seeing tablets which are about as fast as desktops from a few years ago. Cheers, -Justin -Original Message- From: Agustin Lobo [mailto:alobolis...@gmail.com] Sent: Tuesday, July 9, 2013 10:19 AM To: Justin Steventon Cc: qgis-developer Subject: Re: [Qgis-developer] CyberTracker integration Hi Justin, I'm using both programs (well, actually, just starting with cybertracker) (I'm the one who collaborated to solvve the problem of running CT on Mac) I think you should keep CT as simple as possible, not only because of the low-literate users but also because in the field you want to have what you need and only what you need. The CT approach in which you design your own template is very good. What I can see as an advantage is an efficient way of trasnfering the info collected with CT to Qgis, perhaps through a spatialite object or some other open spatial database. But I would not add gis capabilites to CT. Regarding the ability of having more mapping capabilities in the field, I wonder if you could make use of Oruxmaps, it works very well on Android, I use it a lot in the field and for navigating the aerial campaigns. Agus On Mon, Jul 8, 2013 at 5:14 PM, Justin Steventon jus...@steventon.com wrote: Hi Antonio, One area of difference with CyberTracker is that it captures data as name+value pairs. Converting to shape file attributes therefore tends name+to be lossy. Alternatively, one data set point might be able to populate several shape file attributes. I’m not sure how to deal with this yet, but my thinking is that we would go simple and fully automatic first. The integration involves converting a shape to a data model, sending the data model to CyberTracker and managing the return of the data. For the purposes of analysis, I’m thinking that any feature that CyberTracker has that is not in QGIS yet, would be built in parallel over time. We have relatively simple charts (like effort, distance travelled, etc), but also something called Index of Abundance which would be nice to have open (if it’s not already there). Cheers, -Justin From: Antonio Locandro [mailto:antoniolocan...@hotmail.com] Sent: Sunday, July 7, 2013 9:13 PM To: Justin Steventon Cc: qgis-developer@lists.osgeo.org Subject: RE: [Qgis-developer] CyberTracker integration Thats understandable the differences, now Justin can you specify more about how would you like to make the integration I am thinking you would probably want to do the data collection using CyberTracker, then export it or download it to be used within QGIS. Now what is it that you would want to do with the data inside QGIS? Depending on your goals you may want to create a plugin that would take the data and do certain predefined analysis Regards Antonio Locandro From: jus...@steventon.com To: antoniolocan...@hotmail.com; madman...@gmail.com CC: qgis-developer@lists.osgeo.org Subject: RE: [Qgis-developer] CyberTracker integration Date: Sun, 7 Jul 2013 13:47:37 -0700 Hi Antonio, Yes, similar to Fulcrum. I’ve been following them for a while now and think they are doing a lot of things right. They’re missing a few components that are important for us, e.g. full offline (for security) and support for a number of in-field scenarios. It’s possible these features will be created over time. The proprietary nature of Fulcrum would tend to turn off some potential groups in the same way as it occasionally has for us. So far, we have not seen meaningful support for low literate users in any major product. As more and more folks have smart phones, this may pick up. Cheers, -Justin From: Antonio Locandro [mailto:antoniolocan...@hotmail.com] Sent: Sunday, July 7, 2013 8:54 AM To: Justin Steventon; 'Nathan Woodrow' Cc: qgis-developer@lists.osgeo.org Subject: RE: [Qgis-developer] CyberTracker integration Hi Justin I think your project seems a little bit similar to http://fulcrumapp.com/ http://fulcrumapp.com/features/ for field data collection, maybe just missing the part for people who can read or write What they do is capture data using custom forms on the field and then you sync over the internet on the cloud, once on a computer you can export the data to use with GIS software and create PDF reports Probably a similar approach? Antonio Locandro From: jus...@steventon.com To: madman...@gmail.com Date: Sat, 6 Jul 2013 23:07:25 -0700 CC: qgis-developer@lists.osgeo.org Subject: Re: [Qgis-developer] CyberTracker
[Qgis-developer] Grid masking: saga in sextante
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all. What is supposed to do this command? I cannot see an effect. BTW: shipping hundreds of complex tools without any documentation is really embarrassing, perhaps we should find a way to fix it. All the best, and thanks. - -- Paolo Cavallini - Faunalia www.faunalia.eu Full contact details at www.faunalia.eu/pc Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlHdcBsACgkQ/NedwLUzIr4UGQCgrMN25V/SfZHs+jeffaYoDahW ggMAn1MtB6XJKjkYq0Rd6kYvOFNxaUkP =G6jU -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Sextante: Split vector layer by attribute example script
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I consistently get: === Traceback (most recent call last): File /usr/share/qgis/python/plugins/sextante/core/GeoAlgorithm.py, line 147, in execute self.processAlgorithm(progress) File /usr/share/qgis/python/plugins/sextante/script/ScriptAlgorithm.py, line 213, in processAlgorithm exec(script) in ns File string, line 20, in module AttributeError: 'QgsVectorDataProvider' object has no attribute 'select' === Sorry for flooding. Should I open a ticket? 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 Icedove - http://www.enigmail.net/ iEYEARECAAYFAlHdc3UACgkQ/NedwLUzIr77xQCgkltT3lGBNSNM/H2shojIb7vG E04An2rqhnrX3ACLH5AZ5jOEh2EBm5X2 =bScg -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qgis-developer Digest, Vol 93, Issue 21
Hi Victor, If you find something that was working before and now it doesn't, please report. I update QGIS master on Windows/Osgeo4W, downloaded SAGA 2.1 and configured properly SEXTANTE to use it. I have not success running any SAGA raster module (ex: split rgb bands, supervised classification). For what it matters my installation noe fails to run also OTB modules (that previously worked without issues, like kmean unsupervised classification). I'm missing something? thanks in advance -- Giovanni -- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qgis-developer Digest, Vol 93, Issue 21
Hey Giovanni, when you say any raster module...it means those two ones only? supervised classification has changed in SAGA 2.1, so it shouldn't work, and split rgb is a very special module, not actually a SAGA one, but one that relies on some SAGA funcitonality... Do you have problems with other algorithms? I just tested some geomorphoometry ones and they were working fine. Thanks for your report! 2013/7/10 Giovanni Manghi giovanni.man...@faunalia.pt: Hi Victor, If you find something that was working before and now it doesn't, please report. I update QGIS master on Windows/Osgeo4W, downloaded SAGA 2.1 and configured properly SEXTANTE to use it. I have not success running any SAGA raster module (ex: split rgb bands, supervised classification). For what it matters my installation noe fails to run also OTB modules (that previously worked without issues, like kmean unsupervised classification). I'm missing something? thanks in advance -- Giovanni -- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qgis-developer Digest, Vol 93, Issue 21
Hi Victor, On Wed, Jul 10, 2013 at 7:11 PM, Victor Olaya vola...@gmail.com wrote: Hey Giovanni, when you say any raster module...it means those two ones only? supervised classification has changed in SAGA 2.1, so it shouldn't work, and split rgb is a very special module, not actually a SAGA one, but one that relies on some SAGA funcitonality... Do you have problems with other algorithms? I just tested some geomorphoometry ones and they were working fine. you are right, I was too fast saying any, anyway I have issue with a few modules I tested (like tri, tpi, vrm) and not with others (slope, aspect, curvature). It seems that others do not have issues also with OTB, so maybe it is a local issue, but I don't know what it can be. cheers! ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Qgis-developer Digest, Vol 93, Issue 21
Please, if you can make a list of those modules that have changed and now do not work, it will be of great help. I planned to do a diff with the module description that SAGA produces...but the output format has changed, so this is not a good solution :-( Thanks! 2013/7/10 Giovanni Manghi giovanni.man...@faunalia.pt: Hi Victor, On Wed, Jul 10, 2013 at 7:11 PM, Victor Olaya vola...@gmail.com wrote: Hey Giovanni, when you say any raster module...it means those two ones only? supervised classification has changed in SAGA 2.1, so it shouldn't work, and split rgb is a very special module, not actually a SAGA one, but one that relies on some SAGA funcitonality... Do you have problems with other algorithms? I just tested some geomorphoometry ones and they were working fine. you are right, I was too fast saying any, anyway I have issue with a few modules I tested (like tri, tpi, vrm) and not with others (slope, aspect, curvature). It seems that others do not have issues also with OTB, so maybe it is a local issue, but I don't know what it can be. cheers! ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Python plugins in QGIS_PLUGINPATH not appearing in Plugin Manager
Hi, I'm developing a python plugin and I found a bug in Plugin Manager. I found out that QGIS is not loading the plugin from QGIS_PLUGINPATH. That's because that plugin is not enabled and mentioned in QSettings(). The actual problem is that plugins in QGIS_PLUGINPATH are not appearing in the Plugin Manager so those cannot be enabled. Do you confirm this? Do I file a bug report? I managed to get my plugin loaded when I manually added the needed setting in windows registry. BR, Lauri ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Toolbar and Panel defaults
Hi Jürgen, Am Mittwoch, 10. Juli 2013, 08.38:38 schrieb Jürgen E. Fischer: On Tue, 09. Jul 2013 at 22:55:18 +0200, Pirmin Kalberer wrote: Toolbars: -Turn off Advanced Digitizing -Move Label to second row Panels: -Turn on Layer order and Browser in a tabbed view with Layers Print composer: -Place all toolbars in one row In case anyone missed it: scripts/mkuidefaults.py produces src/app/ui_defaults.h from the current settings. Didn't know that. Updated the script to support composer UI defaults. So updating it should be easy, once it's decides what should be the default. Not sure if the data contains pixel coordinates and if the screen resolution might therefore be an issue... Let's try: https://github.com/qgis/Quantum-GIS/pull/710 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] Qgis-developer Digest, Vol 93, Issue 21
I've reported a change in the command of intersection of polygons in SAGA GIS v2.1, I have also tried to build a patch for correction: http://hub.qgis.org/issues/8239 In the new API SAGA GIS v2.1 has changed overlapping polygons, now the Polygons Intersects function is divided into six separate functions: Intersect, Identify, Difference, Symmetrical Difference, Union and Update. I attached the path with the new SAGA descriptions of the six features for Sextante, So I think it is not necessary the PolygonIntersection.txt file. Regards, Samuel Mesa. 2013/7/10 Victor Olaya vola...@gmail.com Please, if you can make a list of those modules that have changed and now do not work, it will be of great help. I planned to do a diff with the module description that SAGA produces...but the output format has changed, so this is not a good solution :-( Thanks! 2013/7/10 Giovanni Manghi giovanni.man...@faunalia.pt: Hi Victor, On Wed, Jul 10, 2013 at 7:11 PM, Victor Olaya vola...@gmail.com wrote: Hey Giovanni, when you say any raster module...it means those two ones only? supervised classification has changed in SAGA 2.1, so it shouldn't work, and split rgb is a very special module, not actually a SAGA one, but one that relies on some SAGA funcitonality... Do you have problems with other algorithms? I just tested some geomorphoometry ones and they were working fine. you are right, I was too fast saying any, anyway I have issue with a few modules I tested (like tri, tpi, vrm) and not with others (slope, aspect, curvature). It seems that others do not have issues also with OTB, so maybe it is a local issue, but I don't know what it can be. cheers! ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- --- .~. / v \ //\\ /( )\ ^`~'^ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Toolbar and Panel defaults
H Pirmin, On Wed, Jul 10, 2013 at 3:29 PM, Pirmin Kalberer pi...@sourcepole.comwrote: Hi Jürgen, Am Mittwoch, 10. Juli 2013, 08.38:38 schrieb Jürgen E. Fischer: On Tue, 09. Jul 2013 at 22:55:18 +0200, Pirmin Kalberer wrote: Toolbars: -Turn off Advanced Digitizing -Move Label to second row Panels: -Turn on Layer order and Browser in a tabbed view with Layers Print composer: -Place all toolbars in one row In case anyone missed it: scripts/mkuidefaults.py produces src/app/ui_defaults.h from the current settings. Didn't know that. Updated the script to support composer UI defaults. Couple of other ideas comments, too: * Currently there are no side toolbars by default. Many apps utilize the left side toolbar for critical tools. To me, such tools in a GIS app are the canvas navigation tools. So whenever I to an initial setup of QGIS, I always put the Map Navigation toolbar on the left. * Similarly, I always place the Plugins toolbar on the right side. There is currently a bug that sets that toolbar to not be shown on a default install (that should be fixed). I would like to hear feedback on those two suggestions for default side toolbars. Following your suggestions (and mine), the default window would look similar to this (on Mac) [0]. +1 for removing Advanced Digitizing toolbar as a default, as all of the functions are available in the Edit menu already. If needed, the user can show that toolbar. Another major layout issue is what the layout looks like after turning on all core plugins [1]. Then, what it looks like when all those plugin toolbars are shown [2]. This needs some work. [0] http://drive.dakotacarto.com/qgis/qgis_default.png [1] http://drive.dakotacarto.com/qgis/qgis_default_core-plugins_no-extra-toolbars.png [2] http://drive.dakotacarto.com/qgis/qgis_default_core-plugins_with-toolbars.png Regards, Larry So updating it should be easy, once it's decides what should be the default. Not sure if the data contains pixel coordinates and if the screen resolution might therefore be an issue... Let's try: https://github.com/qgis/Quantum-GIS/pull/710 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 ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Toolbar and Panel defaults
Having the nav toolbar on the side would be ideal if you could dock it on the right side of the layers panel. I'm not a fan of having to go all the way over the layer panel to access the navigation tools. - Nathan On Thu, Jul 11, 2013 at 8:49 AM, Larry Shaffer lar...@dakotacarto.comwrote: H Pirmin, On Wed, Jul 10, 2013 at 3:29 PM, Pirmin Kalberer pi...@sourcepole.comwrote: Hi Jürgen, Am Mittwoch, 10. Juli 2013, 08.38:38 schrieb Jürgen E. Fischer: On Tue, 09. Jul 2013 at 22:55:18 +0200, Pirmin Kalberer wrote: Toolbars: -Turn off Advanced Digitizing -Move Label to second row Panels: -Turn on Layer order and Browser in a tabbed view with Layers Print composer: -Place all toolbars in one row In case anyone missed it: scripts/mkuidefaults.py produces src/app/ui_defaults.h from the current settings. Didn't know that. Updated the script to support composer UI defaults. Couple of other ideas comments, too: * Currently there are no side toolbars by default. Many apps utilize the left side toolbar for critical tools. To me, such tools in a GIS app are the canvas navigation tools. So whenever I to an initial setup of QGIS, I always put the Map Navigation toolbar on the left. * Similarly, I always place the Plugins toolbar on the right side. There is currently a bug that sets that toolbar to not be shown on a default install (that should be fixed). I would like to hear feedback on those two suggestions for default side toolbars. Following your suggestions (and mine), the default window would look similar to this (on Mac) [0]. +1 for removing Advanced Digitizing toolbar as a default, as all of the functions are available in the Edit menu already. If needed, the user can show that toolbar. Another major layout issue is what the layout looks like after turning on all core plugins [1]. Then, what it looks like when all those plugin toolbars are shown [2]. This needs some work. [0] http://drive.dakotacarto.com/qgis/qgis_default.png [1] http://drive.dakotacarto.com/qgis/qgis_default_core-plugins_no-extra-toolbars.png [2] http://drive.dakotacarto.com/qgis/qgis_default_core-plugins_with-toolbars.png Regards, Larry So updating it should be easy, once it's decides what should be the default. Not sure if the data contains pixel coordinates and if the screen resolution might therefore be an issue... Let's try: https://github.com/qgis/Quantum-GIS/pull/710 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 ___ 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] Toolbar and Panel defaults
Hi Nathan, On Wed, Jul 10, 2013 at 4:51 PM, Nathan Woodrow madman...@gmail.com wrote: Having the nav toolbar on the side would be ideal if you could dock it on the right side of the layers panel. I'm not a fan of having to go all the way over the layer panel to access the navigation tools. That's a very good point. What about the Navigation toolbar on the right, with the Plugin toolbar filling the empty space at right on the first row of horizontal toolbars? Here's my reasoning. Nav tools are quickly accessible, and when a new user downloads/installs a plugin, there is already space to show it (assuming that plugin loads a tool button into the Plugins toolbar). Then the user can move toolbars to their liking. Any other ideas? [0] http://drive.dakotacarto.com/qgis/qgis_default_nav-tools-right.png Regards, Larry - Nathan On Thu, Jul 11, 2013 at 8:49 AM, Larry Shaffer lar...@dakotacarto.comwrote: H Pirmin, On Wed, Jul 10, 2013 at 3:29 PM, Pirmin Kalberer pi...@sourcepole.comwrote: Hi Jürgen, Am Mittwoch, 10. Juli 2013, 08.38:38 schrieb Jürgen E. Fischer: On Tue, 09. Jul 2013 at 22:55:18 +0200, Pirmin Kalberer wrote: Toolbars: -Turn off Advanced Digitizing -Move Label to second row Panels: -Turn on Layer order and Browser in a tabbed view with Layers Print composer: -Place all toolbars in one row In case anyone missed it: scripts/mkuidefaults.py produces src/app/ui_defaults.h from the current settings. Didn't know that. Updated the script to support composer UI defaults. Couple of other ideas comments, too: * Currently there are no side toolbars by default. Many apps utilize the left side toolbar for critical tools. To me, such tools in a GIS app are the canvas navigation tools. So whenever I to an initial setup of QGIS, I always put the Map Navigation toolbar on the left. * Similarly, I always place the Plugins toolbar on the right side. There is currently a bug that sets that toolbar to not be shown on a default install (that should be fixed). I would like to hear feedback on those two suggestions for default side toolbars. Following your suggestions (and mine), the default window would look similar to this (on Mac) [0]. +1 for removing Advanced Digitizing toolbar as a default, as all of the functions are available in the Edit menu already. If needed, the user can show that toolbar. Another major layout issue is what the layout looks like after turning on all core plugins [1]. Then, what it looks like when all those plugin toolbars are shown [2]. This needs some work. [0] http://drive.dakotacarto.com/qgis/qgis_default.png [1] http://drive.dakotacarto.com/qgis/qgis_default_core-plugins_no-extra-toolbars.png [2] http://drive.dakotacarto.com/qgis/qgis_default_core-plugins_with-toolbars.png Regards, Larry So updating it should be easy, once it's decides what should be the default. Not sure if the data contains pixel coordinates and if the screen resolution might therefore be an issue... Let's try: https://github.com/qgis/Quantum-GIS/pull/710 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 ___ 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] Toolbar and Panel defaults
I think on the right is fine. To me that feels better that all the way over on the left. It's a real bugger that we can't make Qt dock the toolbars inside something else, seems you are constrained to QMainWindow. - Nathan On Thu, Jul 11, 2013 at 9:05 AM, Larry Shaffer lar...@dakotacarto.comwrote: Hi Nathan, On Wed, Jul 10, 2013 at 4:51 PM, Nathan Woodrow madman...@gmail.comwrote: Having the nav toolbar on the side would be ideal if you could dock it on the right side of the layers panel. I'm not a fan of having to go all the way over the layer panel to access the navigation tools. That's a very good point. What about the Navigation toolbar on the right, with the Plugin toolbar filling the empty space at right on the first row of horizontal toolbars? Here's my reasoning. Nav tools are quickly accessible, and when a new user downloads/installs a plugin, there is already space to show it (assuming that plugin loads a tool button into the Plugins toolbar). Then the user can move toolbars to their liking. Any other ideas? [0] http://drive.dakotacarto.com/qgis/qgis_default_nav-tools-right.png Regards, Larry - Nathan On Thu, Jul 11, 2013 at 8:49 AM, Larry Shaffer lar...@dakotacarto.comwrote: H Pirmin, On Wed, Jul 10, 2013 at 3:29 PM, Pirmin Kalberer pi...@sourcepole.comwrote: Hi Jürgen, Am Mittwoch, 10. Juli 2013, 08.38:38 schrieb Jürgen E. Fischer: On Tue, 09. Jul 2013 at 22:55:18 +0200, Pirmin Kalberer wrote: Toolbars: -Turn off Advanced Digitizing -Move Label to second row Panels: -Turn on Layer order and Browser in a tabbed view with Layers Print composer: -Place all toolbars in one row In case anyone missed it: scripts/mkuidefaults.py produces src/app/ui_defaults.h from the current settings. Didn't know that. Updated the script to support composer UI defaults. Couple of other ideas comments, too: * Currently there are no side toolbars by default. Many apps utilize the left side toolbar for critical tools. To me, such tools in a GIS app are the canvas navigation tools. So whenever I to an initial setup of QGIS, I always put the Map Navigation toolbar on the left. * Similarly, I always place the Plugins toolbar on the right side. There is currently a bug that sets that toolbar to not be shown on a default install (that should be fixed). I would like to hear feedback on those two suggestions for default side toolbars. Following your suggestions (and mine), the default window would look similar to this (on Mac) [0]. +1 for removing Advanced Digitizing toolbar as a default, as all of the functions are available in the Edit menu already. If needed, the user can show that toolbar. Another major layout issue is what the layout looks like after turning on all core plugins [1]. Then, what it looks like when all those plugin toolbars are shown [2]. This needs some work. [0] http://drive.dakotacarto.com/qgis/qgis_default.png [1] http://drive.dakotacarto.com/qgis/qgis_default_core-plugins_no-extra-toolbars.png [2] http://drive.dakotacarto.com/qgis/qgis_default_core-plugins_with-toolbars.png Regards, Larry So updating it should be easy, once it's decides what should be the default. Not sure if the data contains pixel coordinates and if the screen resolution might therefore be an issue... Let's try: https://github.com/qgis/Quantum-GIS/pull/710 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 ___ 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] Toolbar and Panel defaults
+1 to hide it, someone might find it useful but most users will associate layer order with visibility/rendering Sent from Samsung tabletTim Sutton li...@linfiniti.com wrote:Hi On Tue, Jul 9, 2013 at 10:55 PM, Pirmin Kalberer pi...@sourcepole.com wrote: Panels: -Turn on Layer order and Browser in a tabbed view with Layers IMHO Layer order is an advanced feature and should be hidden by default - novice users are heavily confused by the fact that the legend order and the render order can be managed separately. Regards Tim -- 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 -- 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. Irc: timlinux on #qgis at freenode.net ==___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Toolbar and Panel defaults
I've never liked side bar tools but since I will be able to move it I wouldn't be unhappy if that's the default Sent from Samsung tabletLarry Shaffer lar...@dakotacarto.com wrote:H Pirmin, On Wed, Jul 10, 2013 at 3:29 PM, Pirmin Kalberer pi...@sourcepole.com wrote: Hi Jürgen, Am Mittwoch, 10. Juli 2013, 08.38:38 schrieb Jürgen E. Fischer: On Tue, 09. Jul 2013 at 22:55:18 +0200, Pirmin Kalberer wrote: Toolbars: -Turn off Advanced Digitizing -Move Label to second row Panels: -Turn on Layer order and Browser in a tabbed view with Layers Print composer: -Place all toolbars in one row In case anyone missed it: scripts/mkuidefaults.py produces src/app/ui_defaults.h from the current settings. Didn't know that. Updated the script to support composer UI defaults. Couple of other ideas comments, too: * Currently there are no side toolbars by default. Many apps utilize the left side toolbar for critical tools. To me, such tools in a GIS app are the canvas navigation tools. So whenever I to an initial setup of QGIS, I always put the Map Navigation toolbar on the left. * Similarly, I always place the Plugins toolbar on the right side. There is currently a bug that sets that toolbar to not be shown on a default install (that should be fixed). I would like to hear feedback on those two suggestions for default side toolbars. Following your suggestions (and mine), the default window would look similar to this (on Mac) [0]. +1 for removing Advanced Digitizing toolbar as a default, as all of the functions are available in the Edit menu already. If needed, the user can show that toolbar. Another major layout issue is what the layout looks like after turning on all core plugins [1]. Then, what it looks like when all those plugin toolbars are shown [2]. This needs some work. [0] http://drive.dakotacarto.com/qgis/qgis_default.png [1] http://drive.dakotacarto.com/qgis/qgis_default_core-plugins_no-extra-toolbars.png [2] http://drive.dakotacarto.com/qgis/qgis_default_core-plugins_with-toolbars.png Regards, Larry So updating it should be easy, once it's decides what should be the default. Not sure if the data contains pixel coordinates and if the screen resolution might therefore be an issue... Let's try: https://github.com/qgis/Quantum-GIS/pull/710 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 ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Toolbar and Panel defaults
Could we add the possibility to close toolbars by undocking them and hitting an x in the window I prefer the right for navigation than left Sent from Samsung tabletLarry Shaffer lar...@dakotacarto.com wrote:Hi Nathan, On Wed, Jul 10, 2013 at 4:51 PM, Nathan Woodrow madman...@gmail.com wrote: Having the nav toolbar on the side would be ideal if you could dock it on the right side of the layers panel. I'm not a fan of having to go all the way over the layer panel to access the navigation tools. That's a very good point. What about the Navigation toolbar on the right, with the Plugin toolbar filling the empty space at right on the first row of horizontal toolbars? Here's my reasoning. Nav tools are quickly accessible, and when a new user downloads/installs a plugin, there is already space to show it (assuming that plugin loads a tool button into the Plugins toolbar). Then the user can move toolbars to their liking. Any other ideas? [0] http://drive.dakotacarto.com/qgis/qgis_default_nav-tools-right.png Regards, Larry - Nathan On Thu, Jul 11, 2013 at 8:49 AM, Larry Shaffer lar...@dakotacarto.com wrote: H Pirmin, On Wed, Jul 10, 2013 at 3:29 PM, Pirmin Kalberer pi...@sourcepole.com wrote: Hi Jürgen, Am Mittwoch, 10. Juli 2013, 08.38:38 schrieb Jürgen E. Fischer: On Tue, 09. Jul 2013 at 22:55:18 +0200, Pirmin Kalberer wrote: Toolbars: -Turn off Advanced Digitizing -Move Label to second row Panels: -Turn on Layer order and Browser in a tabbed view with Layers Print composer: -Place all toolbars in one row In case anyone missed it: scripts/mkuidefaults.py produces src/app/ui_defaults.h from the current settings. Didn't know that. Updated the script to support composer UI defaults. Couple of other ideas comments, too: * Currently there are no side toolbars by default. Many apps utilize the left side toolbar for critical tools. To me, such tools in a GIS app are the canvas navigation tools. So whenever I to an initial setup of QGIS, I always put the Map Navigation toolbar on the left. * Similarly, I always place the Plugins toolbar on the right side. There is currently a bug that sets that toolbar to not be shown on a default install (that should be fixed). I would like to hear feedback on those two suggestions for default side toolbars. Following your suggestions (and mine), the default window would look similar to this (on Mac) [0]. +1 for removing Advanced Digitizing toolbar as a default, as all of the functions are available in the Edit menu already. If needed, the user can show that toolbar. Another major layout issue is what the layout looks like after turning on all core plugins [1]. Then, what it looks like when all those plugin toolbars are shown [2]. This needs some work. [0] http://drive.dakotacarto.com/qgis/qgis_default.png [1] http://drive.dakotacarto.com/qgis/qgis_default_core-plugins_no-extra-toolbars.png [2] http://drive.dakotacarto.com/qgis/qgis_default_core-plugins_with-toolbars.png Regards, Larry So updating it should be easy, once it's decides what should be the default. Not sure if the data contains pixel coordinates and if the screen resolution might therefore be an issue... Let's try: https://github.com/qgis/Quantum-GIS/pull/710 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 ___ 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
