<div dir="ltr">Andreas,<div><br></div><div>Something like this is what I was thinking. (With a better UI of course)</div><div><br></div><div><a href="http://i.imgur.com/2XbNqlp.png">http://i.imgur.com/2XbNqlp.png</a><br></div>
<div><br></div><div>- Nathan</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Mar 2, 2014 at 9:45 PM, Nathan Woodrow <span dir="ltr"><<a href="mailto:madmanwoo@gmail.com" target="_blank">madmanwoo@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hey <span style="font-size:13px;font-family:arial,sans-serif">Andreas,</span><div><span style="font-size:13px;font-family:arial,sans-serif"><br>
</span></div><div><span style="font-size:13px;font-family:arial,sans-serif">I'm not 100% yet. I'm not sure what it is but I really hate the Load Style../Save Style buttons at the bottom of the dialog. I was thinking a new page in the properties dialog would be better with the title Import/Export. For me this would mean not having a open another dialog, which I really don't like the idea of, and we have more room to play with.</span></div>
<div><span style="font-size:13px;font-family:arial,sans-serif"><br></span></div><div><span style="font-size:13px;font-family:arial,sans-serif">One of my goals is to be able to export just the style part in order to expand the Style Manager to handle prebuilt styles. I was planning on adding some Save and Load buttons on the style tab that would just load the style information from the .qml file.</span></div>
<span class="HOEnZb"><font color="#888888">
<div><span style="font-size:13px;font-family:arial,sans-serif"><br></span></div><div><span style="font-size:13px;font-family:arial,sans-serif">- Nathan</span></div></font></span></div><div class="HOEnZb"><div class="h5">
<div class="gmail_extra">
<br><br><div class="gmail_quote">On Sun, Mar 2, 2014 at 9:39 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,<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>
<div><div>> 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 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 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 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 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>
</div></div><div><div>_______________________________________________<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></div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>