https://bugs.documentfoundation.org/show_bug.cgi?id=135373
--- Comment #17 from Cougar Brenneman <couga...@gmail.com> --- (In reply to Mike Kaganski from comment #14) > (In reply to Heiko Tietze from comment #12) > > Not a fan of a special outline mode as this hinders the use case of hiding > > text in edit mode > > But what is "the use case of hiding text in edit mode"? First, what is "edit > mode" in this context? Normal view (with pages) mode? or something? because > the outline mode is also "edit mode", with different emphasis and different > workflow. > > And then, what is the need of hiding text in that "edit mode" other than > outline mode? By definition, the "Normal View" is designed to show you the > document as close to the resulting printed state as possible. Its emphasis > is WYSIWYG. It has own "hiding text" means, that are related to actually > hiding contents from the end printout (like "hidden" character attribute, or > "hidden text"/"hidden paragraph" fields, or "hidden" property of sections). > Collapsing text in "Normal" view is exactly "hindering the intended > workflow", while in specialized Outline view it is in its place. Thanks, Mike. You're translating what I'm trying to say into a more technical presentation. I haven't been able to do that. >From the beginning of my conversation with this community, way back before 2011 fork, back in 2001 with OpenOffice, I described the specialized Outline view and the workflow it enabled as my "Superpower," because everywhere I went, it provided me with a new way of thinking, a new paradigm of how to write well. I only recently read in "The Object-Oriented Thought Process" book by Matt A. Weisfeld how different paradigms of thinking lead to different results, and until recently, I didn't have enough technical understanding to say that in a way that might appeal to developers. Now I know that this is as radical a change of thinking paradigm as moving from procedural programming to OOP is a radical change in the thinking paradigm. In my earlier comment 2, I described how my notes from a meeting became part of the Agile process of the department. In most programming houses, the technical writer is not an active member of the Agile team, but using this process enabled me to be an active contributor to the Agile process. In many coding houses, technical writing is aligned with post-production and advertising, rather than part of the production process. Using this one superpower, which requires a powerful outline mode, can change everything, from top to bottom, left to right, front to back. This so changed my role in the production process that if you go to chapter 4 in the Developers Guide, you'll find a tutorial that tells developers how to write an adapter for the i-Flow engine using JavaScript. I wrote that entire script, though I had no expertise in programming in JavaScript before getting that job. The outliner mode and the way it changes your thinking process as a writer is so powerful that I continue to think of it as a superpower. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
