Re: [Qgis-developer] Error in packaging
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 27/01/2014 23:01, Pedro Venâncio ha scritto: I already managed to compile. I think it was corrected by Jurgen on this commit: https://github.com/qgis/QGIS/commit/587be8cde99142e67aa236e47985110a9a74ebc7 You're still having the same problem? confirmed, it works now. thanks Juergen! - -- 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/ iEYEARECAAYFAlLneHMACgkQ/NedwLUzIr4ZzgCeLrYcTDTlb8m1IvXhRNyUAygu YXEAoK6/pKQ0oEpfIWHXN+tpIqR9U1qX =OipD -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Consistency in adding layers (especially OGC)
Hi List, This may be too late for 2.2 (some are features), but something that's bugging me no end is the complete lack of consistency between all the dialogs for the OGC services. Below I've created a somewhat exhaustive list of differences-that-shouldn't-be between the way they behave - mostly the add-layer dialog. However, rather than rectify the issues, would it maybe make more sense to just create a single new dialog from scratch and use that instead? Ideally for all formats, but if necessary, just the OGC stuff. What are the plans relating to add-layer dialogs? Is there a preferred option? Or will/desire to create a universal dialog for adding layers? Cheers, Jonathan - *Adding Layers:* Add/Close buttons For WCS these are the wrong way around! Layer Title|Name: - For WMS, WCS - use the layer Title rather than the layer Name when adding to the layers list (WFS WMTS already do this). - Either add Use title for layer name checkbox to WMS/WMTS, WCS, or remove from WFS. - WMS seems to allow you to fill in a Layer name - add to other dialogs? If so, make it more obvious what it does. Filter: Add Filter function for WMS, WMTS, WCS (already exists for WFS). Differentiate windows: http://hub.qgis.org/issues/9193 Tabs: WCS: Remove Layers tab as pointless. WMS/WMTS - I have no idea what Server Search or Layer order do - never seen them active. CRS: All - Make CRS section same between dialogs. WMS - why is Tile Size and Feature limit for GetFeatureInfo inside the CRS box? Format: WCS or WMS/WMTS - Use same method for selecting format. One uses dropdown (WCS), one uses checkboxes. I guess WFS doesn't need this option. Column list: All - In list of layers, use same order of columns and same selection of columns. WCS, WMS - Column widths autodetected. (Already done for WMTS, WFS) Caching: WCS / WFS - Offer same method for choosing caching settings. Add Layer: WFS - Don't close the dialog. Or Do close it for WMS/WMTS and WCS. - *Create Connection*: WMS/WMTS - says Create a new WMS connection - should say WMTS too. WCS/WFS - Referer option (in WMS already) WFS - Connection details not in bold (is on WMS/WCS) - *Metadata*: Following on from this ticket - http://hub.qgis.org/issues/8870 - suggested changes to layer properties - Metadata: WMS, WMTS and WCS: - Don't list entire Get Capabilities in properties, only the section for that particular layer. WFS already does this. - All OGC Services - Populate the Description/attribution/metadataURL from the GetCapabilities. -- This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Consistency in adding layers (especially OGC)
Hey Jonathan, Yes this is a bit of a known issue. It has always been a goal of mine to try and tackle the issue of refactoring the whole lot into single dialog. I have some early dialog mockups floating around that you might be able to find, although I would tweak it a bit now. If you have some ideas for a new single UI it would be good to have a look, or even if you just have ideas on what you want to see. - Nathan On Tue, Jan 28, 2014 at 8:03 PM, Jonathan Moules jonathanmou...@warwickshire.gov.uk wrote: Hi List, This may be too late for 2.2 (some are features), but something that's bugging me no end is the complete lack of consistency between all the dialogs for the OGC services. Below I've created a somewhat exhaustive list of differences-that-shouldn't-be between the way they behave - mostly the add-layer dialog. However, rather than rectify the issues, would it maybe make more sense to just create a single new dialog from scratch and use that instead? Ideally for all formats, but if necessary, just the OGC stuff. What are the plans relating to add-layer dialogs? Is there a preferred option? Or will/desire to create a universal dialog for adding layers? Cheers, Jonathan - *Adding Layers:* Add/Close buttons For WCS these are the wrong way around! Layer Title|Name: - For WMS, WCS - use the layer Title rather than the layer Name when adding to the layers list (WFS WMTS already do this). - Either add Use title for layer name checkbox to WMS/WMTS, WCS, or remove from WFS. - WMS seems to allow you to fill in a Layer name - add to other dialogs? If so, make it more obvious what it does. Filter: Add Filter function for WMS, WMTS, WCS (already exists for WFS). Differentiate windows: http://hub.qgis.org/issues/9193 Tabs: WCS: Remove Layers tab as pointless. WMS/WMTS - I have no idea what Server Search or Layer order do - never seen them active. CRS: All - Make CRS section same between dialogs. WMS - why is Tile Size and Feature limit for GetFeatureInfo inside the CRS box? Format: WCS or WMS/WMTS - Use same method for selecting format. One uses dropdown (WCS), one uses checkboxes. I guess WFS doesn't need this option. Column list: All - In list of layers, use same order of columns and same selection of columns. WCS, WMS - Column widths autodetected. (Already done for WMTS, WFS) Caching: WCS / WFS - Offer same method for choosing caching settings. Add Layer: WFS - Don't close the dialog. Or Do close it for WMS/WMTS and WCS. - *Create Connection*: WMS/WMTS - says Create a new WMS connection - should say WMTS too. WCS/WFS - Referer option (in WMS already) WFS - Connection details not in bold (is on WMS/WCS) - *Metadata*: Following on from this ticket - http://hub.qgis.org/issues/8870 - suggested changes to layer properties - Metadata: WMS, WMTS and WCS: - Don't list entire Get Capabilities in properties, only the section for that particular layer. WFS already does this. - All OGC Services - Populate the Description/attribution/metadataURL from the GetCapabilities. This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation. ___ 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] Consistency in adding layers (especially OGC)
Hi Nathan, Unfortunately my talent lies with finding flaws and suggesting tweaks/improvements to things rather than designing UI's. I'm more than happy to offer feedback. Is there any way to spur this along? We have a limited amount of commercial support (we're a local authority going through austerity measures- budgets dwindling); this would be good to see in 2.4 if possible. Cheers, Jonathan On 28 January 2014 10:39, Nathan Woodrow madman...@gmail.com wrote: Hey Jonathan, Yes this is a bit of a known issue. It has always been a goal of mine to try and tackle the issue of refactoring the whole lot into single dialog. I have some early dialog mockups floating around that you might be able to find, although I would tweak it a bit now. If you have some ideas for a new single UI it would be good to have a look, or even if you just have ideas on what you want to see. - Nathan On Tue, Jan 28, 2014 at 8:03 PM, Jonathan Moules jonathanmou...@warwickshire.gov.uk wrote: Hi List, This may be too late for 2.2 (some are features), but something that's bugging me no end is the complete lack of consistency between all the dialogs for the OGC services. Below I've created a somewhat exhaustive list of differences-that-shouldn't-be between the way they behave - mostly the add-layer dialog. However, rather than rectify the issues, would it maybe make more sense to just create a single new dialog from scratch and use that instead? Ideally for all formats, but if necessary, just the OGC stuff. What are the plans relating to add-layer dialogs? Is there a preferred option? Or will/desire to create a universal dialog for adding layers? Cheers, Jonathan - *Adding Layers:* Add/Close buttons For WCS these are the wrong way around! Layer Title|Name: - For WMS, WCS - use the layer Title rather than the layer Name when adding to the layers list (WFS WMTS already do this). - Either add Use title for layer name checkbox to WMS/WMTS, WCS, or remove from WFS. - WMS seems to allow you to fill in a Layer name - add to other dialogs? If so, make it more obvious what it does. Filter: Add Filter function for WMS, WMTS, WCS (already exists for WFS). Differentiate windows: http://hub.qgis.org/issues/9193 Tabs: WCS: Remove Layers tab as pointless. WMS/WMTS - I have no idea what Server Search or Layer order do - never seen them active. CRS: All - Make CRS section same between dialogs. WMS - why is Tile Size and Feature limit for GetFeatureInfo inside the CRS box? Format: WCS or WMS/WMTS - Use same method for selecting format. One uses dropdown (WCS), one uses checkboxes. I guess WFS doesn't need this option. Column list: All - In list of layers, use same order of columns and same selection of columns. WCS, WMS - Column widths autodetected. (Already done for WMTS, WFS) Caching: WCS / WFS - Offer same method for choosing caching settings. Add Layer: WFS - Don't close the dialog. Or Do close it for WMS/WMTS and WCS. - *Create Connection*: WMS/WMTS - says Create a new WMS connection - should say WMTS too. WCS/WFS - Referer option (in WMS already) WFS - Connection details not in bold (is on WMS/WCS) - *Metadata*: Following on from this ticket - http://hub.qgis.org/issues/8870 - suggested changes to layer properties - Metadata: WMS, WMTS and WCS: - Don't list entire Get Capabilities in properties, only the section for that particular layer. WFS already does this. - All OGC Services - Populate the Description/attribution/metadataURL from the GetCapabilities. This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
[Qgis-developer] crash during diagram creation
Hi guys, I'm trying to create some diagram, but I notice that qgis crashes if the diagram are histogram styled. No problem with pie chart and text diagram. Running qgis master on a debian machine. Should I open a ticket? Cheers Matteo ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] crash during diagram creation
Ciao Matteo, Please open a ticket and attach sample data/steps to reproduce. Any crash should be treated as a bug. Best Matthias On Tue 28 Jan 2014 12:38:22 PM CET, Matteo Ghetta wrote: Hi guys, I'm trying to create some diagram, but I notice that qgis crashes if the diagram are histogram styled. No problem with pie chart and text diagram. Running qgis master on a debian machine. Should I open a ticket? Cheers Matteo ___ 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] Consistency in adding layers (especially OGC)
+1 to create an universal dialog for adding layers (or folder of files/layers) I have resolved the same problem in a personal application integrating all formats and types in a single loading form. Basically each provider offers a PropertyPage collection to build the ConnectionString that each provider know to open. I attach a short video to show the idea (~2.5 mb). http://www.filedropper.com/GenericCadgisLoadingDialog Best Regards Alvaro De: Jonathan Moules jonathanmou...@warwickshire.gov.uk Para: Nathan Woodrow madman...@gmail.com CC: qgis-developer@lists.osgeo.org qgis-developer@lists.osgeo.org Enviado: Martes 28 de enero de 2014 11:57 Asunto: Re: [Qgis-developer] Consistency in adding layers (especially OGC) Hi Nathan, Unfortunately my talent lies with finding flaws and suggesting tweaks/improvements to things rather than designing UI's. I'm more than happy to offer feedback. Is there any way to spur this along? We have a limited amount of commercial support (we're a local authority going through austerity measures- budgets dwindling); this would be good to see in 2.4 if possible. Cheers, Jonathan On 28 January 2014 10:39, Nathan Woodrow madman...@gmail.com wrote: Hey Jonathan, Yes this is a bit of a known issue. It has always been a goal of mine to try and tackle the issue of refactoring the whole lot into single dialog. I have some early dialog mockups floating around that you might be able to find, although I would tweak it a bit now. If you have some ideas for a new single UI it would be good to have a look, or even if you just have ideas on what you want to see. - Nathan On Tue, Jan 28, 2014 at 8:03 PM, Jonathan Moules jonathanmou...@warwickshire.gov.uk wrote: Hi List, This may be too late for 2.2 (some are features), but something that's bugging me no end is the complete lack of consistency between all the dialogs for the OGC services. Below I've created a somewhat exhaustive list of differences-that-shouldn't-be between the way they behave - mostly the add-layer dialog. However, rather than rectify the issues, would it maybe make more sense to just create a single new dialog from scratch and use that instead? Ideally for all formats, but if necessary, just the OGC stuff. What are the plans relating to add-layer dialogs? Is there a preferred option? Or will/desire to create a universal dialog for adding layers? Cheers, Jonathan - Adding Layers: Add/Close buttons For WCS these are the wrong way around! Layer Title|Name: - For WMS, WCS - use the layer Title rather than the layer Name when adding to the layers list (WFS WMTS already do this). - Either add Use title for layer name checkbox to WMS/WMTS, WCS, or remove from WFS. - WMS seems to allow you to fill in a Layer name - add to other dialogs? If so, make it more obvious what it does. Filter: Add Filter function for WMS, WMTS, WCS (already exists for WFS). Differentiate windows: http://hub.qgis.org/issues/9193 Tabs: WCS: Remove Layers tab as pointless. WMS/WMTS - I have no idea what Server Search or Layer order do - never seen them active. CRS: All - Make CRS section same between dialogs. WMS - why is Tile Size and Feature limit for GetFeatureInfo inside the CRS box? Format: WCS or WMS/WMTS - Use same method for selecting format. One uses dropdown (WCS), one uses checkboxes. I guess WFS doesn't need this option. Column list: All - In list of layers, use same order of columns and same selection of columns. WCS, WMS - Column widths autodetected. (Already done for WMTS, WFS) Caching: WCS / WFS - Offer same method for choosing caching settings. Add Layer: WFS - Don't close the dialog. Or Do close it for WMS/WMTS and WCS. - Create Connection: WMS/WMTS - says Create a new WMS connection - should say WMTS too. WCS/WFS - Referer option (in WMS already) WFS - Connection details not in bold (is on WMS/WCS) - Metadata: Following on from this ticket - http://hub.qgis.org/issues/8870 - suggested changes to layer properties - Metadata: WMS, WMTS and WCS: - Don't list entire Get Capabilities in properties, only the section for that particular layer. WFS already does this. - All OGC Services - Populate the Description/attribution/metadataURL from the GetCapabilities. This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.
Re: [Qgis-developer] Consistency in adding layers (especially OGC)
Sorry, I forgot to mention that the interface is in Spanish, but I think you can guess the concept. Alvaro De: A Huarte ahuart...@yahoo.es Para: Jonathan Moules jonathanmou...@warwickshire.gov.uk; Nathan Woodrow madman...@gmail.com CC: qgis-developer@lists.osgeo.org qgis-developer@lists.osgeo.org Enviado: Martes 28 de enero de 2014 16:19 Asunto: Re: [Qgis-developer] Consistency in adding layers (especially OGC) +1 to create an universal dialog for adding layers (or folder of files/layers) I have resolved the same problem in a personal application integrating all formats and types in a single loading form. Basically each provider offers a PropertyPage collection to build the ConnectionString that each provider know to open. I attach a short video to show the idea (~2.5 mb). http://www.filedropper.com/GenericCadgisLoadingDialog Best Regards Alvaro De: Jonathan Moules jonathanmou...@warwickshire.gov.uk Para: Nathan Woodrow madman...@gmail.com CC: qgis-developer@lists.osgeo.org qgis-developer@lists.osgeo.org Enviado: Martes 28 de enero de 2014 11:57 Asunto: Re: [Qgis-developer] Consistency in adding layers (especially OGC) Hi Nathan, Unfortunately my talent lies with finding flaws and suggesting tweaks/improvements to things rather than designing UI's. I'm more than happy to offer feedback. Is there any way to spur this along? We have a limited amount of commercial support (we're a local authority going through austerity measures- budgets dwindling); this would be good to see in 2.4 if possible. Cheers, Jonathan On 28 January 2014 10:39, Nathan Woodrow madman...@gmail.com wrote: Hey Jonathan, Yes this is a bit of a known issue. It has always been a goal of mine to try and tackle the issue of refactoring the whole lot into single dialog. I have some early dialog mockups floating around that you might be able to find, although I would tweak it a bit now. If you have some ideas for a new single UI it would be good to have a look, or even if you just have ideas on what you want to see. - Nathan On Tue, Jan 28, 2014 at 8:03 PM, Jonathan Moules jonathanmou...@warwickshire.gov.uk wrote: Hi List, This may be too late for 2.2 (some are features), but something that's bugging me no end is the complete lack of consistency between all the dialogs for the OGC services. Below I've created a somewhat exhaustive list of differences-that-shouldn't-be between the way they behave - mostly the add-layer dialog. However, rather than rectify the issues, would it maybe make more sense to just create a single new dialog from scratch and use that instead? Ideally for all formats, but if necessary, just the OGC stuff. What are the plans relating to add-layer dialogs? Is there a preferred option? Or will/desire to create a universal dialog for adding layers? Cheers, Jonathan - Adding Layers: Add/Close buttons For WCS these are the wrong way around! Layer Title|Name: - For WMS, WCS - use the layer Title rather than the layer Name when adding to the layers list (WFS WMTS already do this). - Either add Use title for layer name checkbox to WMS/WMTS, WCS, or remove from WFS. - WMS seems to allow you to fill in a Layer name - add to other dialogs? If so, make it more obvious what it does. Filter: Add Filter function for WMS, WMTS, WCS (already exists for WFS). Differentiate windows: http://hub.qgis.org/issues/9193 Tabs: WCS: Remove Layers tab as pointless. WMS/WMTS - I have no idea what Server Search or Layer order do - never seen them active. CRS: All - Make CRS section same between dialogs. WMS - why is Tile Size and Feature limit for GetFeatureInfo inside the CRS box? Format: WCS or WMS/WMTS - Use same method for selecting format. One uses dropdown (WCS), one uses checkboxes. I guess WFS doesn't need this option. Column list: All - In list of layers, use same order of columns and same selection of columns. WCS, WMS - Column widths autodetected. (Already done for WMTS, WFS) Caching: WCS / WFS - Offer same method for choosing caching settings. Add Layer: WFS - Don't close the dialog. Or Do close it for WMS/WMTS and WCS. - Create Connection: WMS/WMTS - says Create a new WMS connection - should say WMTS too. WCS/WFS - Referer option (in WMS already) WFS - Connection details not in bold (is on WMS/WCS) - Metadata: Following on from this ticket - http://hub.qgis.org/issues/8870 - suggested changes to layer properties - Metadata: WMS, WMTS and WCS: - Don't list entire Get Capabilities in properties, only the section for that particular layer. WFS already does this. - All OGC Services - Populate the Description/attribution/metadataURL from the GetCapabilities. This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be
[Qgis-developer] User Interface Design (UX) Guidelines for QGIS?
Hi, Are there any User Interface Design (UX) Guidelines for QGIS? Is there a need to define/refine/adapt ones? I didn't find much for QGIS in this mailing list and elsewhere. --Stefan P.S. Here are some generic ones I can recommend: * (Graphical) User Interface (UI/GUI) Design with Qt: http://qt-project.org/doc/qt-4.8/qt-gui-concepts.html * Windows 8 App UX Guidelines: http://msdn.microsoft.com/en-us/library/windows/apps/hh465424.aspx ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] User Interface Design (UX) Guidelines for QGIS?
Am 28.01.2014, 16:29 Uhr, schrieb Stefan Keller sfkel...@gmail.com: Hi, Are there any User Interface Design (UX) Guidelines for QGIS? Is there a need to define/refine/adapt ones? Hi Stefan, You can find the HIG (Human Interface Guidelines) starting on line 1441 of https://github.com/qgis/QGIS/blob/master/doc/CODING.t2t Best wishes, Anita I didn't find much for QGIS in this mailing list and elsewhere. --Stefan P.S. Here are some generic ones I can recommend: * (Graphical) User Interface (UI/GUI) Design with Qt: http://qt-project.org/doc/qt-4.8/qt-gui-concepts.html * Windows 8 App UX Guidelines: http://msdn.microsoft.com/en-us/library/windows/apps/hh465424.aspx ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- anitagraser.com ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Consistency in adding layers (especially OGC)
The QgsWCSSourceSelect was written as subclass of QgsOWSSourceSelect with intention to use later the QgsOWSSourceSelect also for other services but I never got time to finish that. I am not even sure if it is the right way, maybe it is easier to just keep it visually in sync. Radim On Tue, Jan 28, 2014 at 11:03 AM, Jonathan Moules jonathanmou...@warwickshire.gov.uk wrote: Hi List, This may be too late for 2.2 (some are features), but something that's bugging me no end is the complete lack of consistency between all the dialogs for the OGC services. Below I've created a somewhat exhaustive list of differences-that-shouldn't-be between the way they behave - mostly the add-layer dialog. However, rather than rectify the issues, would it maybe make more sense to just create a single new dialog from scratch and use that instead? Ideally for all formats, but if necessary, just the OGC stuff. What are the plans relating to add-layer dialogs? Is there a preferred option? Or will/desire to create a universal dialog for adding layers? Cheers, Jonathan - Adding Layers: Add/Close buttons For WCS these are the wrong way around! Layer Title|Name: - For WMS, WCS - use the layer Title rather than the layer Name when adding to the layers list (WFS WMTS already do this). - Either add Use title for layer name checkbox to WMS/WMTS, WCS, or remove from WFS. - WMS seems to allow you to fill in a Layer name - add to other dialogs? If so, make it more obvious what it does. Filter: Add Filter function for WMS, WMTS, WCS (already exists for WFS). Differentiate windows: http://hub.qgis.org/issues/9193 Tabs: WCS: Remove Layers tab as pointless. WMS/WMTS - I have no idea what Server Search or Layer order do - never seen them active. CRS: All - Make CRS section same between dialogs. WMS - why is Tile Size and Feature limit for GetFeatureInfo inside the CRS box? Format: WCS or WMS/WMTS - Use same method for selecting format. One uses dropdown (WCS), one uses checkboxes. I guess WFS doesn't need this option. Column list: All - In list of layers, use same order of columns and same selection of columns. WCS, WMS - Column widths autodetected. (Already done for WMTS, WFS) Caching: WCS / WFS - Offer same method for choosing caching settings. Add Layer: WFS - Don't close the dialog. Or Do close it for WMS/WMTS and WCS. - Create Connection: WMS/WMTS - says Create a new WMS connection - should say WMTS too. WCS/WFS - Referer option (in WMS already) WFS - Connection details not in bold (is on WMS/WCS) - Metadata: Following on from this ticket - http://hub.qgis.org/issues/8870 - suggested changes to layer properties - Metadata: WMS, WMTS and WCS: - Don't list entire Get Capabilities in properties, only the section for that particular layer. WFS already does this. - All OGC Services - Populate the Description/attribution/metadataURL from the GetCapabilities. This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation. ___ 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] PlugIn Approval: VoGisProfilTool 1.8.5
Hi, please approve new version. http://plugins.qgis.org/plugins/VoGisProfilTool/ As suggested by Paolo Cavallini ( https://github.com/BergWerkGIS/VoGIS-Profil-Tool/issues/1) I've moved the menu entry to the Raster menu. Regards, Wilhelm ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Plugin approval : GéoFoncier
Hi, I've submitted a new version of the plugin. It's only for few minor bugs. The login/password are in the readme. Thanks Etienne 2014-01-13 Tim Sutton li...@linfiniti.com: Hi On Tue, Jan 14, 2014 at 12:08 AM, Etienne Trimaille etienne.trimai...@gmail.com wrote: Hi, I've seen the other thread about VoGIS Profiltool. Do we should write a mail for asking an approval ? Because I uploaded my first plugin last Tuesday and I don't have any news. Actually, I don't really know in my plugin is is in the queue. http://plugins.qgis.org/plugins/GeoFoncierConsultation/ Could you provide me with a login so I can test the service? Please send off-list to t...@qgis.org Thanks Tim Regards, Etienne ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Tim Sutton - QGIS Project Steering Committee Member == 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] New composer's title
Hi Jürgen, Can the work outlined below, to move the interrupting dialog's functionality to top of Composer's Composition Panel, be included with 2.2 release? Regards, Larry On Sun, Jan 26, 2014 at 9:04 AM, kimaidou kimai...@gmail.com wrote: Hi Larry +1 for your proposal ! 2014-01-26 Larry Shaffer lar...@dakotacarto.com Hi, So, to recap: +1 to remove the annoying, interrupting new name dialog, and +1 for moving its functionality to the top of the Composition Panel A non-editable field displaying the name and a simple edit button next to it that opens up the same rename dialog as is found in the Composer Manager would be all that is needed. I suggest the continued use of the rename dialog since it offers validation that the name is unique among existing composers names, and allows for quickly building a name off of an existing name. If this change (not really a feature) will be allowed for 2.2 release, I can commit the work today. Regards, Larry On Sat, Jan 25, 2014 at 4:13 PM, Larry Shaffer lar...@dakotacarto.comwrote: Hi, I specifically added that dialog, since so many times my composers resulted in unrecognizable names. I believe without it many users will suffer from this as well. However, I'm not necessarily keen on its implementation, but wish not to remove the functionality, just move it elsewhere. The new naming functionality (e.g. to quickly base a name off of an existing composer, etc.) is already part of Composer Manager, so nothing needs changed there. A better solution when creating a new composer, and gently nudging the user to set a name for it, might be to move the dialog's widget functionality to a 'Name' field at the top of the Composition panel. Then, when a user creates a new composer and the main window is shown, set keyboard focus to that field and set its background to a color to signify the user should consider entering a unique name (e.g. pale yellow). The background could be on a singleshot timer so that it fades out after a bit. This would only be when creating a new Composer; and, since the field could already have a generated name inputted, the user can just choose to ignore it. This also means that GUI scripts don't have to deal with the current interim dialog. Regards, Larry On Sat, Jan 25, 2014 at 2:54 AM, Andreas Neumann a.neum...@carto.netwrote: Hi, +1 for removing it. Maybe an auto-generated name that does not clash with existing composer names would be useful - which the user can later on rename. The user will have to set paper format anyway. In this step he can also set the composer name. Andreas Am 25.01.2014 09:04, schrieb kimaidou: Hi Martin +1 for removing it, as it is a step I usually skip too. But only if we provide a input field in the composer properties tab to allow to add/change the name directly in the opened composer (above the paper size for example). This way I won't need to open the composer manager only to rename it afterwards. Michael 2014/1/25 Martin Dobias wonder...@gmail.com Hi Is there any good reason for the small pop-up dialog asking for composer name when user wants to create a new composer? There is the composer manager where the composer can be renamed at any time, so to me it looks like an unnecessary step and I would be happy to remove it :-) Regards Martin ___ 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 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] [QGIS-UX] User Interface Design (UX) Guidelines for QGIS?
Hi Anita and Jürgen Vielen Dank! That's a starting point. There remains still much to say, like where to place QButtonBox for OK / Cancel / Help?, what default font size, etc. Is it wrong to point at least to UI Design with Qt for further reading in the Developers guide for QGIS? -Stefan Am 28. Januar 2014 18:56 schrieb Jürgen E. j...@norbit.de: Hi, On Tue, 28. Jan 2014 at 17:42:13 +0100, Anita Graser wrote: You can find the HIG (Human Interface Guidelines) starting on line 1441 of https://github.com/qgis/QGIS/blob/master/doc/CODING.t2t BTW we also have a HTML version of that online: http://htmlpreview.github.io/?https://raw.github.com/qgis/QGIS/master/doc/CODING.html#toc60 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 QGIS PSC member (RM) Germany IRC: 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 mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Lidar data into QGIS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all. Lidar data in LAS format are increasingly widespread. Leaving aside all 3D frenzy, we would be interested in simply displaying them in QGIS, with their useful attributes (classification and intensity), either with a native driver or through an available library. All the licensing issues around libLAS/LSTools are a bit obscure to me, so I wonder if someone has already dealt with this. Any hint would be appreciated. Thanks in advance. 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/ iEYEARECAAYFAlLoAUQACgkQ/NedwLUzIr4zpgCePUoYkVf+xtWE5n0GNskWL256 0S4An34ARAD3dTfyktHatc9UuQeCb/sm =3Pbv -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] [QGIS-UX] User Interface Design (UX) Guidelines for QGIS?
Hi On Tue, Jan 28, 2014 at 9:07 PM, Stefan Keller sfkel...@gmail.com wrote: Hi Anita and Jürgen Vielen Dank! That's a starting point. There remains still much to say, like where to place QButtonBox for OK / Cancel / Help?, what default font size, etc. Is it wrong to point at least to UI Design with Qt for further reading in the Developers guide for QGIS? We need to have much more complete guidelines (preferably with visuals illustrating how different design situations should be handled). I believe that the UX are going to tackle something like that. Posting to external docs may also be worthwhile in the short term. Regards Tim -Stefan Am 28. Januar 2014 18:56 schrieb Jürgen E. j...@norbit.de: Hi, On Tue, 28. Jan 2014 at 17:42:13 +0100, Anita Graser wrote: You can find the HIG (Human Interface Guidelines) starting on line 1441 of https://github.com/qgis/QGIS/blob/master/doc/CODING.t2t BTW we also have a HTML version of that online: http://htmlpreview.github.io/?https://raw.github.com/qgis/QGIS/master/doc/CODING.html#toc60 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 QGIS PSC member (RM) Germany IRC: 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 mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Tim Sutton - QGIS Project Steering Committee Member == 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
[Qgis-developer] Plugin [425] realcentroid approval notification.
Plugin realcentroid approval by anitagraser. The plugin version [425] realcentroid 0.1 is now approved Link: http://plugins.qgis.org/plugins/realcentroid/ ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Lidar data into QGIS
Hi Paolo, On Tue, Jan 28, 2014 at 12:13 PM, Paolo Cavallini cavall...@faunalia.itwrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all. Lidar data in LAS format are increasingly widespread. Leaving aside all 3D frenzy, we would be interested in simply displaying them in QGIS, with their useful attributes (classification and intensity), either with a native driver or through an available library. All the licensing issues around libLAS/LSTools are a bit obscure to me, so I wonder if someone has already dealt with this. Any hint would be appreciated. Have you looked into PDAL [0][1]? It is already in OSGeo4W 32-bit, though apparently not in 64-bit yet [2][3]. On the Mac side, it is already available in the Homebrew package manager [4]. It appears to be BSD 3-Clause licensed. Not entirely sure of its full API, but seems to be an ideal candidate for a Processing provider, yes? While I am not a Lidar guru by any means, it looks like the JSON output from PDAL [5] is also an input for three.js [6], e.g. Qgis2threejs PyQGIS plugin. So that is fairly interesting... may be possible to load in a clipped .las file and visualize your map canvas on it? That would be very cool. [0] http://www.pdal.io/ [1] https://github.com/PDAL/PDAL/ [2] http://osdir.com/ml/osgeo4w-development/2013-06/msg5.html [3] http://download.osgeo.org/osgeo4w/versions_diff-x86-x86_64.html [4] https://github.com/Homebrew/homebrew/blob/master/Library/Formula/pdal.rb [5] http://www.pdal.io/tutorial/reading.html#javascript-output [6] http://threejs.org/docs/#Reference/Loaders/GeometryLoader, http://threejs.org/docs/#Reference/Loaders/JSONLoader Regards, Larry Thanks in advance. 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/ iEYEARECAAYFAlLoAUQACgkQ/NedwLUzIr4zpgCePUoYkVf+xtWE5n0GNskWL256 0S4An34ARAD3dTfyktHatc9UuQeCb/sm =3Pbv -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] Cad-Input for QGIS prototype
Hi ! Thanks for all the replies !! I updated the plugin which should work on mac/linux now, please give it a try ! Do you think it's too soon to put it in the plugin repo as experimental at this stage ? *INPUT vs TOOLS* I understand one of the main concern is avoiding to have a CAD-plugins proliferation, and I totally agree. It's quite hard to draw the line on what can be packaged in one plugin and what should rather be kept in another one. I'd say we can distinguish between what really is about - INPUT (coordinates, snapping, constraints, mouse, units ...) and - TOOLS (extend, trim, offset, rotate, create shapes ...) In my opinion, mixing both in a unique plugin is a bad idea : - at long term, we may want to integrate the INPUT part in QGIS's core, as keeping TOOLS part as plugins may seem more relevant (easier to extend). - TOOLS are feature specific. Some of them will operate only on polygons, some other only on points, whereas INPUT should aim to be generally available as possible. - it's a conceptual soup Of course, INPUT would allow to do some things that could also be implemented as a specific TOOL. In Autocad, for instance, you can extend/trim a line either with the extend/trim tool, or by moving a vertex and taking advantage of the snapping system. That doesn't make one of them useless. INPUT can also enhance the way you use TOOLs. Take the rectangle-oval digitizing plugin : thanks to CadInput, you can (well, you could, if it worked better with drag-type tools) enter precise numeric input. *TOOLS plugin ideas* So I'd say packaging different CAD-tools in an unique and consistent plugin is another (urgent) task. A key point may be classification. IMO, a good start would be a toolbar by layer type (point, line, polygon) in which all tools would be ordered/separated by funtion type (create, reshape, merge/split, modify, delete...). The available toolbar would only show when editing the corresponding layer type. Native tools could be integrated in this classification as well. To get a polished and consistent user experience, I think we need some solid abstract tool classes, which takes care of how input is organised in terms of UI (common interface for point/segment/object/numeric input) and logic (operands then operation, or operation then operands). The QGIS C++ tool class leaves (too) much freedom to subclasses. A great work towards such a plugin would be to try to implement that base classe(s) in python. It would then be much easier for contributors to extend the tool set. And in the end, the base class could be implemented in C++. Well that was it ! Regards, Olivier PS: @Saber Razmjooei: I didn't find auto-trace (guess it's not approved yet?) @Leyan Yes it's a good idea. There is already a construction mode which allows to enter points without creating features. It could be made available even when not using an editTool... ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Lidar data into QGIS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 29/01/2014 02:41, Larry Shaffer ha scritto: Have you looked into PDAL [0][1]? It is already in OSGeo4W 32-bit, though apparently not in 64-bit yet [2][3]. On the Mac side, it is already available in the Homebrew package manager [4]. It appears to be BSD 3-Clause licensed. Not entirely sure of its full API, but seems to be an ideal candidate for a Processing provider, yes? Thanks a lot Larry. PDAL is certainly interesting, as it is used and supported by PostGIS [0]. Unfortunately is not (yet?) available on Debian-based OSs, but I guess this can change. What would be good is, rather than (or in addition to) a Processing provider, a data provider. I guess this should be developed from scratch, right? All the best. [0] http://boundlessgeo.com/2013/11/manage-lidar-postgis/ - -- 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/ iEYEARECAAYFAlLootoACgkQ/NedwLUzIr4QYACfbYb1U5mZ23HXpQfwKPa5CQ5w APgAn01fQKYgTJ42Pk46UXTc/acOK6Hc =4JIg -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Help for Feature #8925
Hi, I'm new to QGIS Developing and want to implement this feature (#8925). Can someone please help me finding the starting point? Which classes implement the export/import of styles? Thanks in advance! Sincerely, Kevin Fehrenbach! ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Cad-Input for QGIS prototype
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 29/01/2014 05:27, Olivier Dalang ha scritto: I didn't find auto-trace (guess it's not approved yet?) http://plugins.qgis.org/plugins/traceDigitize/ see: http://plugins.qgis.org/plugins/tags/digitizing/ (please note: not all plugins are tagged correctly, this should be improved). Thanks Olivier. - -- 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/ iEYEARECAAYFAlLoo5EACgkQ/NedwLUzIr5H5QCgnHe1BxMcTSOrnMwoLnXaLoAK Ds4An3AUrRH9PDPYvHlSdf+66FTi9yrT =jcW7 -END PGP SIGNATURE- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
[Qgis-developer] Data encryption
Hi List, I have a friend, not in South Africa, who has a need to bundle raster vector data with a map viewer, so that the entire package can be deployed via a DVD. The catch is that usage of the data bundled with this DVD, needs to expire after 12 months. So, does anyone know of a QGIS based solution - even if it comes with a proprietary encryption module that allows for an expiry date? I'd be curious if anyone has implemented such solution. I also think that there may be a possibility of fee for someone to develop such capability. Regards and thanks, Zoltan -- === Zoltan Szecsei PrGISc [PGP0031] Geograph (Pty) Ltd. GIS and Photogrammetric Service P.O. Box 7, Muizenberg 7950, South Africa. 65 Main Road, Muizenberg 7945 Western Cape, South Africa. 34° 6'16.35S 18°28'5.62E Tel: +27-21-7884897 Mobile: +27-83-6004028 Fax: +27-86-6115323 www.geograph.co.za === ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Help for Feature #8925
On 29 January 2014 07:42, Kevin Fehrenbach kevinfehrenb...@yahoo.de wrote: #8925 probably you can start following all SLD methods in: QgsMapLayer ciao Luigi Pirelli (luigi.pire...@faunalia.it - lui...@gmail.com) ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Data encryption
On 01/28/2014 10:53 PM, Zoltan Szecsei wrote: Hi List, I have a friend, not in South Africa, who has a need to bundle raster vector data with a map viewer, so that the entire package can be deployed via a DVD. The catch is that usage of the data bundled with this DVD, needs to expire after 12 months. So, does anyone know of a QGIS based solution - even if it comes with a proprietary encryption module that allows for an expiry date? I'd be curious if anyone has implemented such solution. I also think that there may be a possibility of fee for someone to develop such capability. Regards and thanks, Zoltan That's a pretty messed up product I wouldn't go anywhere near. But short answer is this isn't a QGIS specific thing it's DRM which the Video Game industry has plenty of solutions for, most of which are completely circumventable by smart computer users. Enjoy, Alex ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
