[Libreoffice-ux-advise] [Bug 53847] Bring a tool bar to work with styles only ( is a sort of ability to 'forbid' the use of direct formatting)
https://bugs.documentfoundation.org/show_bug.cgi?id=53847 Commit Notification changed: What|Removed |Added Whiteboard|BSA |BSA target:6.4.0 -- 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 53847] Bring a tool bar to work with styles only ( is a sort of ability to 'forbid' the use of direct formatting)
https://bugs.documentfoundation.org/show_bug.cgi?id=53847 --- Comment #7 from Commit Notification --- Heiko Tietze committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/55291868dd1b73d2ba4ec2aa75889e10377d5bef%5E%21 tdf#53847 - Styles focused toolbar It will be available in 6.4.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- 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 126277] Writer Character Styles are not intuitive to read
https://bugs.documentfoundation.org/show_bug.cgi?id=126277 Heiko Tietze changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #10 from Heiko Tietze --- No further opinions so closing now as WF. -- 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 53847] Bring a tool bar to work with styles only ( is a sort of ability to 'forbid' the use of direct formatting)
https://bugs.documentfoundation.org/show_bug.cgi?id=53847 Heiko Tietze changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #6 from Heiko Tietze --- We discussed the topic in the design meeting. With the introduction of a styles focused toolbar (bug 106781) the request is done. You have to manually disable the Formatting toolbar and enable Formatting (Styles). As an addition I'll hide the few direct formatting commands. -- 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 62926] Add option to show 'Apply Style' menu in plain text
https://bugs.documentfoundation.org/show_bug.cgi?id=62926 --- Comment #11 from Heiko Tietze --- We discussed the topic in the design meeting and decided to involve the community. So here is a poll including the abstract of our discussion https://design.blog.documentfoundation.org/2019/08/15/poll-about-design-preview-for-dropdown-controls/ -- 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 126752] Find & Replace should optionally also make use of AutoCorrect single or double quote substitutions for easier keyboard search entry
https://bugs.documentfoundation.org/show_bug.cgi?id=126752 Heiko Tietze changed: What|Removed |Added CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org Keywords|needsUXEval | --- Comment #8 from Heiko Tietze --- We discussed this topic in the design meeting. The implementation requires a general approach, ie. all autocorrection terms have to handled similarly. Technically it might be challenging to run the search twice if some string might have been replaced (for example ' by " where users can undo the autocorrection so consequently we have to search first for ' and subsequently for "). So we suggest to simply show a message that this input might have been autocorrected. It could be something like "No results found but might have been replaced by ." as an enhancement to the current information. -- 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 126857] Alignment of images
https://bugs.documentfoundation.org/show_bug.cgi?id=126857 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 --- We discussed this topic in the design meeting. Too many options, as suggested in c5 and c6, might be an overkill and bloat the menus (and the UNO API). But the idea of one additional command using Stuart's suggestion from c3 is very welcome. -- 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
