[Qgis-developer] Renaming Save Style -> Save Properties (Vector layer dialog)

[Andreas Neumann]

Hi,

How do you envisage to implement this?

Personally I would think it would be useful to have an export dialogue
where the user can choose (with checkboxes or a list widget) which
properties he wants to export:

* General properties (like the filtering, encoding, layer alias, scale
dependent visibility, CRS )
* Style properties
* Labeling properties
* Field properties (incl. display field properties)
* Actions
* Joins and Relations (see the new relations manager that Matthias
recently introduced)
* Diagrams
* Metadata

As a shortcut one should be able to export all at once without having to
press all checkboxes.

---------------

When importing, the importer of the layer properties should list what is
available in the .qml file and offer just the available bits of the
layer properties. Again - a short cut to import all layer properties
would be useful.

Thanks,
Andreas

Am 01.03.2014 15:42, schrieb Anita Graser:
> Hi Michael,
> 
> Am 01.03.2014, 15:55 Uhr, schrieb kimaidou <kimaidou at gmail.com>:
>> I also think it could be great to have a button
>> "save style". But the latest should not lie in the bottom of the layer
>> dialog, but instead in the Style tab only, to avoid confusion.
> 
> +1
> 
>> By the way, having a "save style" button could also lead to the
>> ability of
>> saving/restoring more than one style for each layer (via a combo box for
>> the restore button), which could be great too.
> 
> This could work quite well. Do you think the "Save style" button could
> be a simple button with the save icon or do we need a labeled button?
> 
> Best wishes,
> Anita
> 
> 
> 
> 
>>
>> Regards,
>> Michael
>>
>>
>> 2014-03-01 15:01 GMT+01:00 Régis Haubourg <
>> regis.haubourg at eau-adour-garonne.fr>:
>>
>>> Hi Nathan I agree with your proposal of renaming style by properties.
>>> Users don't understand they also inherit labels, metadata and so on when
>>> loading a style.
>>>
>>> By the way, I think some improvements can be made for reloading style
>>> use
>>> case. Problem occurs (maybe occured, didn't check recently) when user
>>> want
>>> to transfer graduated or single value style classes from one column to
>>> another. Copying style from another table often leads to that situation,
>>> where field or expression is not in target table.   I know this can be
>>> tricky since graduated classes are in autosync with numeric data.
>>> Another issue occurs when geometry type is not the same. Maybe we could
>>> save
>>> at least color when reapplying style (from point to polygon for
>>> instance).
>>> This was my small thread highjack ;-)
>>> Cheers,
>>>
>>> Régis
>>>
> 
> 
>