> > The only thing I am missing in this mockup is the ability to > check/uncheck all checkboxes. It is kind of boring having to uncheck a > lot of checkboxes if just want the styling or labeling.
Just an implementation detail. That is something I would add. - Nathan On Sun, Mar 2, 2014 at 10:06 PM, Andreas Neumann <[email protected]>wrote: > Hi Nathan, > > Yes - I like the idea of a separate tab for import/export of layer > properties. > > I guess the "Save style" would then be renamed to "Save Property"? > > The only thing I am missing in this mockup is the ability to > check/uncheck all checkboxes. It is kind of boring having to uncheck a > lot of checkboxes if just want the styling or labeling. > > Cool - looking forward to these improvements! > > Andreas > > Am 02.03.2014 11:58, schrieb Nathan Woodrow: > > Andreas, > > > > Something like this is what I was thinking. (With a better UI of course) > > > > http://i.imgur.com/2XbNqlp.png > > > > - Nathan > > > > > > On Sun, Mar 2, 2014 at 9:45 PM, Nathan Woodrow <[email protected]> > wrote: > > > >> Hey Andreas, > >> > >> 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. > >> > >> 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. > >> > >> - Nathan > >> > >> > >> On Sun, Mar 2, 2014 at 9:39 PM, Andreas Neumann <[email protected] > >wrote: > >> > >>> 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 <[email protected]>: > >>>>> 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 < > >>>>> [email protected]>: > >>>>> > >>>>>> 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 > >>>>>> > >>>> > >>>> > >>>> > >>> > >>> _______________________________________________ > >>> Qgis-developer mailing list > >>> [email protected] > >>> http://lists.osgeo.org/mailman/listinfo/qgis-developer > >>> > >> > >> > > > >
_______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
