Re: [Qgis-developer] user-defined symbology defaults + project templates
On Mon, Jul 16, 2012 at 11:49 PM, Nathan Woodrow madman...@gmail.com wrote: On Tue, Jul 17, 2012 at 1:19 AM, Etienne Tourigny etourigny@gmail.com wrote: I'm glad others see this as useful! Any idea when these changes will be available, and if should I wait before adding my changes to master? In the meantime, I could perhaps push what I have done. Currently, the button changes the selected symbol, but it could be modified to open the symbol lists. I just thought this way was a bit faster. The reasons I suggested not using a combobox is because with long names the combobox grows and pushes the size of the dialog box out, although with a button you are going to have the same issue I guess. I'm happy for a commit of what you have so far and then we can rework it once the GSoC stuff is in master. Right, it's pretty simple anyway so not hard to modify afterward. I'll just make sure the combobox does not grow if the names are long. Cheers I like the idea of multiple templates to choose from, but I would still like a way to change the global defaults (see answer to Denis). +1 as long it is obvious that the defaults have been changed. Any idea on how to manage the template list from a UI perspective? Just have a file sector and have the user place/save the files there, and then a dynamic menu which lists these files? I would have a folder called 'project_templates in the .qgis folder and the list could be read from there by default, you could also have a place in the global settings where you could define other folders to look for templates. I might store projects on a network folder so that other people can access them so it would be good to be able to tell QGIS to look in there too. - Nathan ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] user-defined symbology defaults + project templates
I've pushed to a slightly modified version of both features. 1) Added default vector transparency for projects ; ui tweaks Would there be any thing else to add to vector defaults? Also, how about raster defaults? Perhaps the entire Rasters section from the main options dialog? 2) Save the default template to $HOME/.qgis/default.qgs (see UI in Options-General-Project Files) Next would be to implement a template folder (both saving and loading) and UI for custom template folder(s) - perhaps a single folder is good enough to make it simple? cheers, Etienne On Tue, Jul 17, 2012 at 8:44 AM, Etienne Tourigny etourigny@gmail.com wrote: On Mon, Jul 16, 2012 at 11:49 PM, Nathan Woodrow madman...@gmail.com wrote: On Tue, Jul 17, 2012 at 1:19 AM, Etienne Tourigny etourigny@gmail.com wrote: I'm glad others see this as useful! Any idea when these changes will be available, and if should I wait before adding my changes to master? In the meantime, I could perhaps push what I have done. Currently, the button changes the selected symbol, but it could be modified to open the symbol lists. I just thought this way was a bit faster. The reasons I suggested not using a combobox is because with long names the combobox grows and pushes the size of the dialog box out, although with a button you are going to have the same issue I guess. I'm happy for a commit of what you have so far and then we can rework it once the GSoC stuff is in master. Right, it's pretty simple anyway so not hard to modify afterward. I'll just make sure the combobox does not grow if the names are long. Cheers I like the idea of multiple templates to choose from, but I would still like a way to change the global defaults (see answer to Denis). +1 as long it is obvious that the defaults have been changed. Any idea on how to manage the template list from a UI perspective? Just have a file sector and have the user place/save the files there, and then a dynamic menu which lists these files? I would have a folder called 'project_templates in the .qgis folder and the list could be read from there by default, you could also have a place in the global settings where you could define other folders to look for templates. I might store projects on a network folder so that other people can access them so it would be good to be able to tell QGIS to look in there too. - Nathan ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] user-defined symbology defaults + project templates
Hey Etienne, I like the ideas but I do some have some comments on the implementation from a UI point of view. I like being able to set the default symbols for a project, that will come in very handy. What I would do here however is have a button with a icon and text rather than a combobox. The button would open the symbol selector and let the user select a symbol. We are redoing the symbol manager and symbol selector in the current GSoC, so I think the new version will work well here. The new symbol manager allows for grouping and searching so you wouldn't have to scroll though a massive list of symbols. For the templates thing I think that is a great idea however maybe we can expand it a bit more and make it more flexible. What I think we could do is rather then having a single default temple we could have a template search path/s and give the user a list of .qgs files in these folders. To handle this in the UI I would have New Project From Temple... menu item that has a sub menu listing all the templates, if would also add a drop down menu to the New Project toolbar button to let people select the template from the toolbar. Thoughts? - Nathan On Sun, Jul 15, 2012 at 7:10 AM, Etienne Tourigny etourigny@gmail.com wrote: Hi all, There are 2 interrelated topics that I have been thinking about and have come up with a solution, and I would like to get other's feedback before proceeding further. 1) Default symbol styles are not user configurable - for example new polygons are always filled with a random color, new point symbols are always small red dots, etc. I see 2 ways to change this - either global or project based. I think project based is better because defaults in a given project are probably not best for all projects. So I have implemented the interface and back-end to select default symbology (point, line, polygon) and color ramps for a project, and all new symbols have identical properties. See attached screenshot for an idea. Should probably also add options for rasters (i.e. what's already in the prefs, plus default renderer style). 2) New project defaults may not be ideal for all users - see background discussion below which deals with default composer templates. A solution to this is to have a default project (template) which is loaded when a new project is created. My solution allows to select the default project template and also adds a UI to load a blank project. I realize this may cause some problems, but it's nicer than to have to manually load a project template after creating a new project (or opening qgis for the first time). This, combined with the symbology defaults, means that a user can define his personal symbology defaults and have them always loaded when a new project is created. Any ideas/comments? Etienne Background discussion: http://lists.osgeo.org/pipermail/qgis-user/2012-June/017443.html My branch which implements solutions for these 2 issues: https://github.com/etiennesky/Quantum-GIS/tree/symbology-default ___ 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] user-defined symbology defaults + project templates
Hi, I think this is pretty useful! In parallel to templates, how about adding a button in the project settings, to make these settings as global default settings? Greetings, Denis On 07/14/2012 11:10 PM, Etienne Tourigny wrote: Hi all, There are 2 interrelated topics that I have been thinking about and have come up with a solution, and I would like to get other's feedback before proceeding further. 1) Default symbol styles are not user configurable - for example new polygons are always filled with a random color, new point symbols are always small red dots, etc. I see 2 ways to change this - either global or project based. I think project based is better because defaults in a given project are probably not best for all projects. So I have implemented the interface and back-end to select default symbology (point, line, polygon) and color ramps for a project, and all new symbols have identical properties. See attached screenshot for an idea. Should probably also add options for rasters (i.e. what's already in the prefs, plus default renderer style). 2) New project defaults may not be ideal for all users - see background discussion below which deals with default composer templates. A solution to this is to have a default project (template) which is loaded when a new project is created. My solution allows to select the default project template and also adds a UI to load a blank project. I realize this may cause some problems, but it's nicer than to have to manually load a project template after creating a new project (or opening qgis for the first time). This, combined with the symbology defaults, means that a user can define his personal symbology defaults and have them always loaded when a new project is created. Any ideas/comments? Etienne Background discussion: http://lists.osgeo.org/pipermail/qgis-user/2012-June/017443.html My branch which implements solutions for these 2 issues: https://github.com/etiennesky/Quantum-GIS/tree/symbology-default ___ 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] user-defined symbology defaults + project templates
Hi Etienne, This, combined with the symbology defaults, means that a user can define his personal symbology defaults and have them always loaded when a new project is created. Any ideas/comments? very nice ideas! I would add the possibility to allow the level of transparency for both the filling of polygons and the level of transparency of the selection color. At this moment are by default both 100% solid and this is not handy in may cases. A certain amount of transparency for polygon filling helps a lot to quickly see if there are overlapped areas. Making the selection color a bit transparent is necessary because it can hide polygons that are below other ones, or even cause to select polygons by mistake (using the select features by rectangle tool, in opposition to the select single feature tool). cheers -- Giovanni -- ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] user-defined symbology defaults + project templates
On Mon, Jul 16, 2012 at 5:04 AM, Nathan Woodrow madman...@gmail.com wrote: Hey Etienne, I like the ideas but I do some have some comments on the implementation from a UI point of view. I like being able to set the default symbols for a project, that will come in very handy. What I would do here however is have a button with a icon and text rather than a combobox. The button would open the symbol selector and let the user select a symbol. We are redoing the symbol manager and symbol selector in the current GSoC, so I think the new version will work well here. The new symbol manager allows for grouping and searching so you wouldn't have to scroll though a massive list of symbols. I'm glad others see this as useful! Any idea when these changes will be available, and if should I wait before adding my changes to master? In the meantime, I could perhaps push what I have done. Currently, the button changes the selected symbol, but it could be modified to open the symbol lists. I just thought this way was a bit faster. For the templates thing I think that is a great idea however maybe we can expand it a bit more and make it more flexible. What I think we could do is rather then having a single default temple we could have a template search path/s and give the user a list of .qgs files in these folders. To handle this in the UI I would have New Project From Temple... menu item that has a sub menu listing all the templates, if would also add a drop down menu to the New Project toolbar button to let people select the template from the toolbar. Thoughts? I like the idea of multiple templates to choose from, but I would still like a way to change the global defaults (see answer to Denis). Any idea on how to manage the template list from a UI perspective? Just have a file sector and have the user place/save the files there, and then a dynamic menu which lists these files? - Etienne - Nathan On Sun, Jul 15, 2012 at 7:10 AM, Etienne Tourigny etourigny@gmail.com wrote: Hi all, There are 2 interrelated topics that I have been thinking about and have come up with a solution, and I would like to get other's feedback before proceeding further. 1) Default symbol styles are not user configurable - for example new polygons are always filled with a random color, new point symbols are always small red dots, etc. I see 2 ways to change this - either global or project based. I think project based is better because defaults in a given project are probably not best for all projects. So I have implemented the interface and back-end to select default symbology (point, line, polygon) and color ramps for a project, and all new symbols have identical properties. See attached screenshot for an idea. Should probably also add options for rasters (i.e. what's already in the prefs, plus default renderer style). 2) New project defaults may not be ideal for all users - see background discussion below which deals with default composer templates. A solution to this is to have a default project (template) which is loaded when a new project is created. My solution allows to select the default project template and also adds a UI to load a blank project. I realize this may cause some problems, but it's nicer than to have to manually load a project template after creating a new project (or opening qgis for the first time). This, combined with the symbology defaults, means that a user can define his personal symbology defaults and have them always loaded when a new project is created. Any ideas/comments? Etienne Background discussion: http://lists.osgeo.org/pipermail/qgis-user/2012-June/017443.html My branch which implements solutions for these 2 issues: https://github.com/etiennesky/Quantum-GIS/tree/symbology-default ___ 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] user-defined symbology defaults + project templates
On Mon, Jul 16, 2012 at 5:11 AM, Denis Rouzaud denis.rouz...@gmail.com wrote: Hi, I think this is pretty useful! In parallel to templates, how about adding a button in the project settings, to make these settings as global default settings? That's the idea of having a Default template, when you create a new project it loads that project file. I saw it as the simplest way to treat user defaults, without having to mess too much with the back-end. However, I see now that it's probably not the best way to deal with user defaults. Should these user defaults be saved to user configuration (QGis.conf), or a special Default.qgs file in the.qgis directory, or in a user-defined template file? How would one proceed than, if for example, global defaults are overridden by the user, and a specific template is loaded? First load the global defaults, then the user defaults, then the specific template? cheers Etienne Greetings, Denis On 07/14/2012 11:10 PM, Etienne Tourigny wrote: Hi all, There are 2 interrelated topics that I have been thinking about and have come up with a solution, and I would like to get other's feedback before proceeding further. 1) Default symbol styles are not user configurable - for example new polygons are always filled with a random color, new point symbols are always small red dots, etc. I see 2 ways to change this - either global or project based. I think project based is better because defaults in a given project are probably not best for all projects. So I have implemented the interface and back-end to select default symbology (point, line, polygon) and color ramps for a project, and all new symbols have identical properties. See attached screenshot for an idea. Should probably also add options for rasters (i.e. what's already in the prefs, plus default renderer style). 2) New project defaults may not be ideal for all users - see background discussion below which deals with default composer templates. A solution to this is to have a default project (template) which is loaded when a new project is created. My solution allows to select the default project template and also adds a UI to load a blank project. I realize this may cause some problems, but it's nicer than to have to manually load a project template after creating a new project (or opening qgis for the first time). This, combined with the symbology defaults, means that a user can define his personal symbology defaults and have them always loaded when a new project is created. Any ideas/comments? Etienne Background discussion: http://lists.osgeo.org/pipermail/qgis-user/2012-June/017443.html My branch which implements solutions for these 2 issues: https://github.com/etiennesky/Quantum-GIS/tree/symbology-default ___ 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] user-defined symbology defaults + project templates
On Tue, Jul 17, 2012 at 1:19 AM, Etienne Tourigny etourigny@gmail.com wrote: I'm glad others see this as useful! Any idea when these changes will be available, and if should I wait before adding my changes to master? In the meantime, I could perhaps push what I have done. Currently, the button changes the selected symbol, but it could be modified to open the symbol lists. I just thought this way was a bit faster. The reasons I suggested not using a combobox is because with long names the combobox grows and pushes the size of the dialog box out, although with a button you are going to have the same issue I guess. I'm happy for a commit of what you have so far and then we can rework it once the GSoC stuff is in master. I like the idea of multiple templates to choose from, but I would still like a way to change the global defaults (see answer to Denis). +1 as long it is obvious that the defaults have been changed. Any idea on how to manage the template list from a UI perspective? Just have a file sector and have the user place/save the files there, and then a dynamic menu which lists these files? I would have a folder called 'project_templates in the .qgis folder and the list could be read from there by default, you could also have a place in the global settings where you could define other folders to look for templates. I might store projects on a network folder so that other people can access them so it would be good to be able to tell QGIS to look in there too. - Nathan ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] user-defined symbology defaults + project templates
On Tue, Jul 17, 2012 at 1:20 AM, Etienne Tourigny etourigny@gmail.com wrote: How would one proceed than, if for example, global defaults are overridden by the user, and a specific template is loaded? First load the global defaults, then the user defaults, then the specific template? For me the template should overwrite everything. If I go File- New Project From Template - My Template then it will take priority over anything I have set anywhere else. - Nathan ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
