https://bugs.documentfoundation.org/show_bug.cgi?id=149230
--- Comment #10 from Rafael Lima <rafael.palma.l...@gmail.com> --- (In reply to Mike Kaganski from comment #5) > (In reply to Rafael Lima from comment #4) > After a UI is prepared with that mental model, we could *then* think how to > supplement it with convenience tools to repair what needs repair. Hi Mike, I agree with your point of view. My idea while proposing these "repair tools" is that when users are interested in being compliant with styles, they will enable these tools and seek to achieve a document that is free from any warnings concerning the application of styles. Over time this can educate users to a new workflow that avoid these warnings. But again, I get your point that we should rethink the entire workflow so that using Styles become the "natural" way. Your idea reminds me a bit of how Latex works: when you use some markup code, the final document will be rendered based on a template that explains how that markup should be rendered. The main problem with all word processors (Writer, Word, Google Docs, etc) is that when the user enters the main application, he/she has a blank page to type text into and a main Toolbar (or ribbon) with DF commands to choose the font name, size and apply bold, italic and underline. This is the same as telling them that using DF is the way we expect them to use the application. (In reply to Heiko Tietze from comment #9) > In fact, the inbuilt "Formatting (Styles)" toolbar is meant as replacement > for the ordinary Formatting toolbar. We could provide a standard interface where the user is faced with commands in the main toolbar where he/she has to choose headings, emphasis level, etc (all of them style-based). I for one did not know about this "Formatting (Styles)" toolbar, since I use mostly the Tabbed UI. But I think that presenting the user with such a set of tools from the beginning would be a way to let them know how we think Writer should be used. > Since the discussion is going towards Writer only As for other LO applications (Calc, Impress and Draw) styles will have very different roles and their current implementation do now allow for a deeper discussion. For instance, in Impress/Draw we do not have Character, Paragraph and Numbering styles, which would be crucial for us to have a Style-oriented UI. In Calc, styles are only applied at the cell level. We should have at least Chart styles and Table styles (see bug 132780) to start discussing a style-oriented UI for Calc. Let alone that Writer does not support shape styles (which are supported by Impress). -- You are receiving this mail because: You are the assignee for the bug.
