Presently object formatting is scattered around in various dialogs like Line, Area, Position and Size, Text, etc. and it would be good to merge all of these into a single dialog so users have access to modify all of these settings in one dialog and for it to take up less space in the context menu. It would exclude the Colors, Gradients, Hatching, and Bitmap tabs from the Area dialog, as these tabs are for creation and modification of colors and not for their selection on an object.
Did you take a look at the Styles and Formatting window, when an object is selected ;) ? IMO this is simply WorksForMe
Yes the styles dialog would be the suitable dialog to duplicate, with the removal of some of the unnecessary tabs like organizer, font, font effects, indent & spacing, alignment, tabs, etc. Many users do not use styles, which is why context menu entries for Line..., Area..., Text...
(In reply to Jay Philips from comment #2) > Many users do not use styles, which is why context menu entries for Line..., > Area..., Text... So we already offer direct formatting via toolbar, context menu, the side bar and now you want to make it even more confusing with an extra dialog, similar to that of the applied style bit with some tabs removed.. To facilitate dump use even more.. IMO it's time that you come on your bare knees to my desk to ask for forgiveness :)
(In reply to Cor Nouws from comment #3) > So we already offer direct formatting via toolbar, context menu, the side > bar and now you want to make it even more confusing with an extra dialog, > similar to that of the applied style bit with some tabs removed.. > To facilitate dump use even more.. Well the point was to consolidate all the currently available dialogs for Line, Area, Text, etc. into a single dialog, so a user who wants to modify the line transparency (only available in the sidebar) and add a shadow to the area (only available in the toolbar) doesnt have to jump into two different dialogs to do so. > IMO it's time that you come on your bare knees to my desk to ask for > forgiveness :) Yes my lord. :D
(In reply to Jay Philips from comment #4) > Well the point was to consolidate all the currently available dialogs for > Line, Area, Text, etc. into a single dialog, so a user who wants to modify > the line transparency (only available in the sidebar) and add a shadow to > the area (only available in the toolbar) doesnt have to jump into two > different dialogs to do so. the dialog for Styles has 14 tabs.. So I guess that when you follow your path in the end you will have 13 tabs? At least not adding to oversight ;\ > Yes my lord. :D Ah well: the go ... and sin no more ;)
(In reply to Jay Philips from comment #4) > Well the point was to consolidate all the currently available dialogs for > Line, Area, Text, etc. into a single dialog, so a user who wants to modify > the line transparency (only available in the sidebar) and add a shadow to > the area (only available in the toolbar) doesnt have to jump into two > different dialogs to do so. the dialog for Styles has 14 tabs.. So I guess that when you follow your path in the end you will have 13 tabs? At least not adding to oversight ;\ > Yes my lord. :D Ah well: then go ... and sin no more ;)
@Cor: Well i see where the argument of object styles fails and that is within Writer and Calc which doesnt have object styles, so a object formatting dialog would be very useful there. :D This is no different from the character and paragraph dialogs which work across all apps, though impress/draw dont have character or paragraph styles.
(In reply to Yousuf (Jay) Philips from comment #7) > @Cor: Well i see where the argument of object styles fails and that is > within Writer and Calc which doesnt have object styles, so a object > formatting dialog would be very useful there. :D There are styles for some objects. And I'd rather see energy spent to improve that. After all, the ability to edit the properties is not missing at the moment. Let's say wontFix ;) ?
Migrating Whiteboard tags to Keywords: (needsDevEval, topicUI) [NinjaEdit]
We're replacing our use of the 'ux-advise' component with a keyword: Component -> LibreOffice Add Keyword: needsUXEval [NinjaEdit]
We talked about the idea in the design meeting and agreed on it. Before implementation starts it makes sense to check whether or not all tabs can be integrated into the new dialog or if we need an additional level in the hierarchy. Meaning a mockup is required now.
(Just removing needsUX as we made the decision)