[Libreoffice-ux-advise] [Bug 128960] Editing: Add a more direct way to clear character styles
https://bugs.documentfoundation.org/show_bug.cgi?id=128960 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||8973 -- 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
[Libreoffice-ux-advise] [Bug 128960] Editing: Add a more direct way to clear character styles
https://bugs.documentfoundation.org/show_bug.cgi?id=128960
--- Comment #6 from Mike Kaganski ---
Even without the "difficulty" and "distrust" feelings caused by unwanted
large-scale changes editing the Default style, the obvious consequence of this
in user learning is "understanding" that all styles should be "disconnected"
from the Default style (user would need to re-define all the properties in
inheritance tree leafs), thus making the inheritance concept less useful and
more of a hassle ("Why is everything inherited from Default? It makes things so
much harder!"). The very first encounter with the style inheritance concept,
instead of giving a useful and handy tool to user, becomes "meet this useless
and awkward thing that stays on your way" moment.
--
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
[Libreoffice-ux-advise] [Bug 128960] Editing: Add a more direct way to clear character styles
https://bugs.documentfoundation.org/show_bug.cgi?id=128960 --- Comment #5 from Mike Kaganski --- At risk of being off-topic here (since the request was about character styles(!)), I have to describe my PoV. While the imaginary "Default character style" (internally = don't use any character style, and use what is defined in paragraph style) is perfectly reasonable in any sense (and would be most used in ~any stylistically consistent document), Default paragraph style (an actual style, which might - and often should - be modified - consciously) is a *root* of most pre-defined styles, and thus its direct use is wrong from the proper styles use PoV. Of course, using it is not wrong from the programmatic PoV, but its default use in templates is just an unfortunate implementation detail that needs fixing. So making means to directly use it even more prominent than now is a bad thing. Specifically, using "Default paragraph style" in documents, and then starting use styles, would mean that a novice user has main text in that "Default style", and also applies, say, Heading N; also using headers/footers and tables automatically uses relevant styles in those elements. And when user then wants to edit the main style (Default!), this will propagate inherited settings to all the styles right and left - which might be (and often is) not what user needs. The inheritance levels are there for a reason: e.g., if user wants font face to be consistent across all used styles, user sets that in the lowest possible inheritance level; if user needs some paragraphs have indents or spacings, that wouldn't make sense to do at lowest level. Forcing users to start with base-of-everything Default style provokes each style edit to have too widescale (potentially destructive) consequences. We have too much of that Default paragraph style usage in our controls/templates: being the default in the templates; being set when e.g. Alt+Enter'ing out of a table; resetting to it when using the "Clear formatting" item in style list in toolbar... please don't create another prominent way to promote logically inconsistent workflow! It goes against the overall architecture of LibreOffice being built around using styles; and it makes learning using styles much more difficult for beginners (who try simple things like editing the used styles, and suddenly see unwanted results all over the document, which would cause distrust in the tool). -- 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
[Libreoffice-ux-advise] [Bug 128960] Editing: Add a more direct way to clear character styles
https://bugs.documentfoundation.org/show_bug.cgi?id=128960 --- Comment #4 from V Stuart Foote --- (In reply to Mike Kaganski from comment #3) > Please don't extend this to paragraph styles. Doing that would emphasize > usage of Default paragraph style - which is bad. Would it? Not so sure... For most users now--majority of their documents are already going to be in default style(s) as that is what the document type templates open with. While here, goal of having the controls prominent is to get the document content back to a known state--either selecting a word, a text run, a full paragraph, or the full document and resetting its style. Seems the efficient work flow is to first set the selection back to the template defaults for paragraph and character styles (or to the default style(s) as modified in current document). Making it ready to apply new style(s), in a second step if other than defaults is desired. -- 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
[Libreoffice-ux-advise] [Bug 128960] Editing: Add a more direct way to clear character styles
https://bugs.documentfoundation.org/show_bug.cgi?id=128960 --- Comment #3 from Mike Kaganski --- Please don't extend this to paragraph styles. Doing that would emphasize usage of Default paragraph style - which is bad. -- 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
[Libreoffice-ux-advise] [Bug 128960] Editing: Add a more direct way to clear character styles
https://bugs.documentfoundation.org/show_bug.cgi?id=128960 --- Comment #2 from V Stuart Foote --- (In reply to V Stuart Foote from comment #1) > It seems like there should be menu entry (either Style menu or a Format > menu) for the existing UNO controls--".uno:DefaultCharStyle" and > ".uno:DefaultParaStyle" used on the Formatting (Style) toolbar. So, the .uno:DefaultCharStyle is already on the 'Styles' menu--labeled 'Default Character' but uno:DefaultParaStyle is not; regardless addition to Sidebar decks is needed. -- 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
[Libreoffice-ux-advise] [Bug 128960] Editing: Add a more direct way to clear character styles
https://bugs.documentfoundation.org/show_bug.cgi?id=128960 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||7022 Keywords||needsUXEval Summary|Editing: Add a more clear |Editing: Add a more direct |way to clean character |way to clear character |styles |styles Blocks||102946 CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vstuart.fo...@utsa.edu --- Comment #1 from V Stuart Foote --- +1, but maybe more than just for Character styles? It seems like there should be menu entry (either Style menu or a Format menu) for the existing UNO controls--".uno:DefaultCharStyle" and ".uno:DefaultParaStyle" used on the Formatting (Style) toolbar. The menu entry(s) would provide reset to default Character style and/or default Paragraph style--i.e. a "Style" corollary to the 'Clear Direct Formatting' control. And I would suggest this pair of actions also appear on the Sidebar Properties Deck, inside the 'Style' Content Panel or better in its Title bar, as a button action to "Clear (or Reset?) to Default". Likewise the same button actions should be added to the Title bar of the 'Style' deck. Intent of reusing controls--menus, Properties deck, and Style deck--being to provide a consistent and obvious way to remove any assigned styles. It would provide a means to get a text selection or a full paragraph back to known state--i.e. no Direct Formatting, no Style other than document default. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102946 [Bug 102946] [META] Styles bugs and enhancements -- 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
[Libreoffice-ux-advise] [Bug 128712] Is the explanation clear in tip nr. 14 about selection zooming?
https://bugs.documentfoundation.org/show_bug.cgi?id=128712 Heiko Tietze changed: What|Removed |Added CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org Keywords|needsUXEval | --- Comment #7 from Heiko Tietze --- No further input from UX, removing the keyword. -- 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
[Libreoffice-ux-advise] [Bug 124885] Impress is striping whitespace from presentation notes
https://bugs.documentfoundation.org/show_bug.cgi?id=124885 Timur changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org --- Comment #4 from Timur --- To add: I think it's not about stripping whitespaces, but about showing formatted text. That would add some but small and so far not justified value. -- 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
[Libreoffice-ux-advise] [Bug 34355] Option to show track changes in margin is missing
https://bugs.documentfoundation.org/show_bug.cgi?id=34355 --- Comment #85 from Simhadri --- If you use the Track Changes feature of Word, you know how your document looks as you make changes. Added text is shown in some different color, and deleted text is shown with a strikethrough or in balloons to the side of your text. You may want to change how Word shows your changed text. Fortunately, Word allows you great flexibility in this area. To make your configuration changes, follow these steps if you are using Word 2007 or Word 2010: Make sure the Review tab of the ribbon is displayed. Within the Tracking group, click the down arrow under the Track Changes tool. In the resulting submenu, click Change Tracking Options. Word displays the Track Changes Options dialog box. However, If you are using Word 2013 or a later version, the steps are slightly different: https://www.teluguace.com/ -- 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
[Libreoffice-ux-advise] [Bug 126878] Revision Cloud
https://bugs.documentfoundation.org/show_bug.cgi?id=126878 --- Comment #9 from Regina Henschel --- (In reply to Heiko Tietze from comment #8) > The cloud object is a custom shape, and while it's possible to create > similar objects with more or less bumps it won't be as flexible as in > AutoCAD (see also bug 101862). You can also convert the object into a > polygon and modify the points though placing the individual points with a > bezier relation to the neighbors is not possible. We have to stick to the > open document format. Of course it would be possible to add a function that > generates a cloud-like polygon, though the number of users who benefit is > limited. On the other hand, it would be a big step forward if realized as > brush (see bug 90045) - this idea might be too far-fetched. > Any other ideas, Regina? > Such object can be saved in ODF as path object or as custom-shape. What manipulation with the object are done after it is first time generated? If an immediate realization is needed, I would do it via macro. At least the way from the outline of rectangle or ellipse to a sequence of arcs is not hard. Although I would not use real arcs but simple Bézier curve segments. It is not a question of ODF, but a problem of providing a generating tool. Besides a conversion tool also a new kind of freeform line might solve the request. -- 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
[Libreoffice-ux-advise] [Bug 38889] Make macro editing easier
https://bugs.documentfoundation.org/show_bug.cgi?id=38889 LibreOfficiant changed: What|Removed |Added Blocks|107659 |127591 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107659 [Bug 107659] [META] Macro bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=127591 [Bug 127591] [META] User Interface (UI) related Macro bugs -- 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
[Libreoffice-ux-advise] [Bug 126878] Revision Cloud
https://bugs.documentfoundation.org/show_bug.cgi?id=126878 Heiko Tietze changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||michael.me...@collabora.com ||, rb.hensc...@t-online.de, ||t...@libreoffice.org Ever confirmed|0 |1 --- Comment #8 from Heiko Tietze --- The cloud object is a custom shape, and while it's possible to create similar objects with more or less bumps it won't be as flexible as in AutoCAD (see also bug 101862). You can also convert the object into a polygon and modify the points though placing the individual points with a bezier relation to the neighbors is not possible. We have to stick to the open document format. Of course it would be possible to add a function that generates a cloud-like polygon, though the number of users who benefit is limited. On the other hand, it would be a big step forward if realized as brush (see bug 90045) - this idea might be too far-fetched. Any other ideas, Regina? (In reply to Tony Stone from comment #2) > I noticed on Thursday I got an email and it says this report has changed. I > don't know what it means where it says QA:needsComment Your request goes through QA management. We aim to respond quickly and have reminder for tickets that lack on comments. (In reply to Tony Stone from comment #2) > I know some OS projects have options for > "bounties" for features and I would like to know if there is an option some > place for that. We don't have bounties but professional support. Take a look here https://www.libreoffice.org/get-help/professional-support/ -- 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
[Libreoffice-ux-advise] [Bug 128258] Calc feature request: more prominent visual hint for hidden rows or columns
https://bugs.documentfoundation.org/show_bug.cgi?id=128258 --- Comment #8 from chameleonsca...@protonmail.com --- Ok, so a) is my favorite too. Thanks for the mockup. I should have done this from the beginning so it would've been clear right away. -- 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
[Libreoffice-ux-advise] [Bug 128258] Calc feature request: more prominent visual hint for hidden rows or columns
https://bugs.documentfoundation.org/show_bug.cgi?id=128258 --- Comment #7 from Heiko Tietze --- Created attachment 156025 --> https://bugs.documentfoundation.org/attachment.cgi?id=156025&action=edit Mockup for comment 5 (In reply to chameleonscales from comment #6) > I'm not clear whether your fix ideas are additional operations... It's ideas how to solve the problem per code. Solution a) is inspired by the ruler that Writer puts between pages. It would be my favorite. -- 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
