https://bugs.documentfoundation.org/show_bug.cgi?id=154492
--- Comment #16 from Eyal Rozenberg <[email protected]> --- (In reply to Regina Henschel from comment #15) > So you should read "Presentation Styles" as "Styles which > are used in presentations for objects which are specific for presentations". Regina, come on. That's not a serious suggestion. Think again of the style categories we have in our modules: Writer: Paragraph Styles, Character Styles, Page Styles, List Styles. Calc: Cell Styles, Drawing (Object) Styles, Page Styles. Impress: Drawing (Object) Styles, Presentation Styles. For all of these categories, except "Presentation Styles", the semantic is very clear: When you have an XYZ, you can choose the XYZ Styles category on the styles tab, and apply any one of those styles to your XYZ. And that's because "XYZ Styles" are "Styles of XYZ entities", "Styles applicable any XYZ entity": Page styles are styles of pages, paragraph styles are styles of paragraphs etc. No LO user looks at, say, "List styles" and thinks that these are "styles which a re used in lists for objects which are specific for lists". Those are styles for lists - plain and simple. > When you examine these objects with the Development Tools and look at their > ShapeType, you will see, that they are of kind com.sun.star.presentation, > whereas other objects are of kind com.sun.star.drawing. But LO users don't examine anything with developer tools. We see what's in front of us and expect clear and consistent information from the UI. Which we mostly do get, except for "Presentation Styles". That's simply a misuse of the styles sidebar. Items in master slides can be accessed via master slide view. and if it's really important for some reason to have a list of these items on the sidebar - developers can introduce a different sidebar, not 'Styles', for master-slide elements or presentation elements or what-not. -- You are receiving this mail because: You are the assignee for the bug.
