https://bugs.documentfoundation.org/show_bug.cgi?id=106781
--- Comment #3 from Yousuf Philips (jay) <[email protected]> ---
Created attachment 132160
--> https://bugs.documentfoundation.org/attachment.cgi?id=132160&action=edit
preliminary toolbar xml
(In reply to Thomas Lendo from comment #1)
> One question to the New style command: Will it create a child style of the
> style where the caret actually is or a complete new style, independent from
> caret position and/or currently activated style in the drop-down?
Yes it would behave similar to its current behaviour in the sidebar, of
creating a child style either based on the selection (if all the text is styled
the same) or based on the caret position. Its creation is being handled in bug
106782.
(In reply to V Stuart Foote from comment #2)
> Not opposed as I think current standard and formatting toolbars over
> emphasize Direct formatting rather than applying Styles, but wouldn't this
> be more in line with MUFFIN customizations of the Sidebar or the Notebookbar?
MUFFIN doesnt customize the sidebar or notebookbar, it simply provides preset
arrangements of toolbars, sidebar and notebookbar. Wheels turn slowly with the
sidebar and notebookbar, but much faster with toolbars, and if the concept
works fine with the toolbars, it could possibly be adopted into the
notebookbar, but highly unlikely with the sidebar.
> The mockup is fine, but as I note on bug 106681#c2 the drop list widget for
> Character styles is more concise and can actually hold all the available
> styles--rather than trying to decide on a specific set of buttons to provide
> on the toolbar.
With 27 default character styles available in Writer, that doesnt reduce the
number clicks and mouse movements needed to select a different style, which
could take alot less mouse movement and a single click to activate from a
toolbar button.
> And of course, question becomes how these additional toolbar controls are
> made available. Are they core .src provided like other "legacy" toolbars,
> exposed from the View -> Toolbar menu--or would they be packaged as .oxt
> extensions to skin the UI with the tools and layout a user prefers to work
> with?
It will be a standard toolbar .xml file, which a user can easily active from
View > Toolbars. I've included in the attachment if you'd like to try it out,
though some of the character style controls are just placeholders for when the
real uno commands are implemented.
> Working out details to do the latter for all the MUFFIN resources would
> provide a lot more flexibility.
The various MUFFIN toolbar/sidebar/notebookbar layouts are currently configured
in code, which means that a dev would need to code the creation of new layouts.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
