<div dir="ltr"><div><div><div><div><div>+1 for the proposed mockup, which would be great to have.<br><br></div>Perhaps something could be added to the import/export panel : some place where the user could access in one click the 5 last applied set of properties ? This could be optionnal, but could help the user to switch from one to another set of properties very easily. This means the user would have the possibility to give each "set" a name, so that he can distinguish sets. What about saving the couples name/set of properties in QGIS project file, like<br>
<br></div><sets_of_properties><br></div><div> <set name="one_set" datasource="./layerA_set_one_set.qset"><br> <set name="another_set" datasource="dbname=some_database user=bla password=*** table=styles id=1111"></div>
</sets_of_properties<br><br><br></div>Anyway, the idea of letting the user choose the properties to save/restore would be a great improvement without my proposal (which is a little bit off topic).<br><br></div>Michael<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-03-02 13:22 GMT+01:00 Mathieu Pellerin <span dir="ltr"><<a href="mailto:nirvn.asia@gmail.com" target="_blank">nirvn.asia@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">I like where it's going. Re check boxes, I'd love to see "intelligent" switch buttons beyond "check all" "uncheck all". A "check styling only" (symbology + label) button, a "check non - style only" button would be really useful. Like some media players do to check audio only vs video & audio.</p>
<div class="HOEnZb"><div class="h5">
<div class="gmail_quote">On 2 Mar 2014 19:11, "Nathan Woodrow" <<a href="mailto:madmanwoo@gmail.com" target="_blank">madmanwoo@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span style="font-size:13px;font-family:arial,sans-serif">The only thing I am missing in this mockup is the ability to<br>
</span><span style="font-size:13px;font-family:arial,sans-serif">check/uncheck all checkboxes. It is kind of boring having to uncheck a<br></span><span style="font-size:13px;font-family:arial,sans-serif">lot of checkboxes if just want the styling or labeling.</span></blockquote>
<div><br></div><div>Just an implementation detail. That is something I would add.</div><div><br></div><div>- Nathan</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Mar 2, 2014 at 10:06 PM, Andreas Neumann <span dir="ltr"><<a href="mailto:a.neumann@carto.net" target="_blank">a.neumann@carto.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Nathan,<br>
<br>
Yes - I like the idea of a separate tab for import/export of layer<br>
properties.<br>
<br>
I guess the "Save style" would then be renamed to "Save Property"?<br>
<br>
The only thing I am missing in this mockup is the ability to<br>
check/uncheck all checkboxes. It is kind of boring having to uncheck a<br>
lot of checkboxes if just want the styling or labeling.<br>
<br>
Cool - looking forward to these improvements!<br>
<br>
Andreas<br>
<br>
Am <a href="tel:02.03.2014%2011" value="+61203201411" target="_blank">02.03.2014 11</a>:58, schrieb Nathan Woodrow:<br>
<div><div>> Andreas,<br>
><br>
> Something like this is what I was thinking. (With a better UI of course)<br>
><br>
> <a href="http://i.imgur.com/2XbNqlp.png" target="_blank">http://i.imgur.com/2XbNqlp.png</a><br>
><br>
> - Nathan<br>
><br>
><br>
> On Sun, Mar 2, 2014 at 9:45 PM, Nathan Woodrow <<a href="mailto:madmanwoo@gmail.com" target="_blank">madmanwoo@gmail.com</a>> wrote:<br>
><br>
>> Hey Andreas,<br>
>><br>
>> I'm not 100% yet. I'm not sure what it is but I really hate the Load<br>
>> Style../Save Style buttons at the bottom of the dialog. I was thinking a<br>
>> new page in the properties dialog would be better with the title<br>
>> Import/Export. For me this would mean not having a open another dialog,<br>
>> which I really don't like the idea of, and we have more room to play with.<br>
>><br>
>> One of my goals is to be able to export just the style part in order to<br>
>> expand the Style Manager to handle prebuilt styles. I was planning on<br>
>> adding some Save and Load buttons on the style tab that would just load the<br>
>> style information from the .qml file.<br>
>><br>
>> - Nathan<br>
>><br>
>><br>
>> On Sun, Mar 2, 2014 at 9:39 PM, Andreas Neumann <<a href="mailto:a.neumann@carto.net" target="_blank">a.neumann@carto.net</a>>wrote:<br>
>><br>
>>> Hi,<br>
>>><br>
>>> How do you envisage to implement this?<br>
>>><br>
>>> Personally I would think it would be useful to have an export dialogue<br>
>>> where the user can choose (with checkboxes or a list widget) which<br>
>>> properties he wants to export:<br>
>>><br>
>>> * General properties (like the filtering, encoding, layer alias, scale<br>
>>> dependent visibility, CRS )<br>
>>> * Style properties<br>
>>> * Labeling properties<br>
>>> * Field properties (incl. display field properties)<br>
>>> * Actions<br>
>>> * Joins and Relations (see the new relations manager that Matthias<br>
>>> recently introduced)<br>
>>> * Diagrams<br>
>>> * Metadata<br>
>>><br>
>>> As a shortcut one should be able to export all at once without having to<br>
>>> press all checkboxes.<br>
>>><br>
>>> ---------------<br>
>>><br>
>>> When importing, the importer of the layer properties should list what is<br>
>>> available in the .qml file and offer just the available bits of the<br>
>>> layer properties. Again - a short cut to import all layer properties<br>
>>> would be useful.<br>
>>><br>
>>> Thanks,<br>
>>> Andreas<br>
>>><br>
>>> Am 01.03.2014 15:42, schrieb Anita Graser:<br>
>>>> Hi Michael,<br>
>>>><br>
>>>> Am 01.03.2014, 15:55 Uhr, schrieb kimaidou <<a href="mailto:kimaidou@gmail.com" target="_blank">kimaidou@gmail.com</a>>:<br>
>>>>> I also think it could be great to have a button<br>
>>>>> "save style". But the latest should not lie in the bottom of the layer<br>
>>>>> dialog, but instead in the Style tab only, to avoid confusion.<br>
>>>><br>
>>>> +1<br>
>>>><br>
>>>>> By the way, having a "save style" button could also lead to the<br>
>>>>> ability of<br>
>>>>> saving/restoring more than one style for each layer (via a combo box<br>
>>> for<br>
>>>>> the restore button), which could be great too.<br>
>>>><br>
>>>> This could work quite well. Do you think the "Save style" button could<br>
>>>> be a simple button with the save icon or do we need a labeled button?<br>
>>>><br>
>>>> Best wishes,<br>
>>>> Anita<br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>>><br>
>>>>> Regards,<br>
>>>>> Michael<br>
>>>>><br>
>>>>><br>
>>>>> 2014-03-01 15:01 GMT+01:00 Régis Haubourg <<br>
>>>>> <a href="mailto:regis.haubourg@eau-adour-garonne.fr" target="_blank">regis.haubourg@eau-adour-garonne.fr</a>>:<br>
>>>>><br>
>>>>>> Hi Nathan I agree with your proposal of renaming style by properties.<br>
>>>>>> Users don't understand they also inherit labels, metadata and so on<br>
>>> when<br>
>>>>>> loading a style.<br>
>>>>>><br>
>>>>>> By the way, I think some improvements can be made for reloading style<br>
>>>>>> use<br>
>>>>>> case. Problem occurs (maybe occured, didn't check recently) when user<br>
>>>>>> want<br>
>>>>>> to transfer graduated or single value style classes from one column to<br>
>>>>>> another. Copying style from another table often leads to that<br>
>>> situation,<br>
>>>>>> where field or expression is not in target table. I know this can be<br>
>>>>>> tricky since graduated classes are in autosync with numeric data.<br>
>>>>>> Another issue occurs when geometry type is not the same. Maybe we<br>
>>> could<br>
>>>>>> save<br>
>>>>>> at least color when reapplying style (from point to polygon for<br>
>>>>>> instance).<br>
>>>>>> This was my small thread highjack ;-)<br>
>>>>>> Cheers,<br>
>>>>>><br>
>>>>>> Régis<br>
>>>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>><br>
>>> _______________________________________________<br>
>>> Qgis-developer mailing list<br>
>>> <a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
>>> <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
>>><br>
>><br>
>><br>
><br>
<br>
</div></div></blockquote></div><br></div>
<br>_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br></blockquote></div>
</div></div><br>_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br></blockquote></div><br></div>