Download it now!
Bug 114943 - UNO command controls to only showing font name and font size
Summary: UNO command controls to only showing font name and font size
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: UNO-Command-New Writer-Toolbar-Formatting-Styles Style-Formatting-Writer-Toolbar
  Show dependency treegraph
 
Reported: 2018-01-10 08:55 UTC by Thomas Lendo
Modified: 2018-06-13 19:43 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:


Attachments
Font name and font size in a styles formatting toolbar (8.20 KB, image/png)
2018-01-10 08:55 UTC, Thomas Lendo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Lendo 2018-01-10 08:55:30 UTC
Created attachment 139010 [details]
Font name and font size in a styles formatting toolbar

When in the toolbars only working with styles instead of direct formatting (like in bug 106781), I'm missing some visual information about the used fonts. Maybe it's because the users are trained to see this information in the toolbars with only direct formatting commands.

I suggest to add commands that only show information without the possibility to edit. Font name and font size are 2 commands that come into my mind. A simple text field that looks like the "normal" command should be enough but without the selection arrows on the right of it.

Why without the possibility to edit? Because when only using styles it shouldn't be possible to change font data in that way.

Sidebar is only a workaround for some users but not for whom they don't use it or they use not the Properties tab but for example Navigator.
Comment 1 Yousuf Philips (jay) (retired) 2018-01-10 20:35:55 UTC
I dont see the benefit of such uno commands, because if the control only displays the font name and font size, users would still want to be able to change them without having to open a dialog and use the 'update style' button to apply it to the given style, similar to using the 'update style' button with font color, which is why font name and font size are available in the toolbar but hidden by default for those who want to utilize them, or any of the other hidden direct formatting options from the formatting toolbar. So this is a WONTFIX for me.
Comment 2 Thomas Lendo 2018-01-10 23:09:16 UTC
I'm aware of the contradictory essence of this request, but the direct formatting buttons (hidden or visible) in the styles formatting toolbar are only a crutch till style equivalents are available. This is also true for font name and font size controls. And for the same reason you added it to the toolbar, I want to have it visible but without the possibility that a colleague can do direct formatting with it.
Comment 3 Yousuf Philips (jay) (retired) 2018-01-14 16:25:33 UTC
(In reply to Thomas Lendo from comment #2)
> I'm aware of the contradictory essence of this request, but the direct
> formatting buttons (hidden or visible) in the styles formatting toolbar are
> only a crutch till style equivalents are available. This is also true for
> font name and font size controls.

Which is why i'm for creating style equivalent version of the font name and font size controls (bug 107865).

> And for the same reason you added it to
> the toolbar, I want to have it visible but without the possibility that a
> colleague can do direct formatting with it.

Well if others agree its a good idea, then the better option would be to have an argument added onto the existing uno commands that just disables user input, something like .uno:CharFontName?Enabled:short=0
Comment 4 Thomas Lendo 2018-01-14 17:29:34 UTC
(In reply to Yousuf Philips (jay) from comment #3)
> (In reply to Thomas Lendo from comment #2)
> > And for the same reason you added it to
> > the toolbar, I want to have it visible but without the possibility that a
> > colleague can do direct formatting with it.
> Well if others agree its a good idea, then the better option would be to
> have an argument added onto the existing uno commands that just disables
> user input, something like .uno:CharFontName?Enabled:short=0
I'm fine with that (it should be as easy implemented as possible) as long as such argument can be added with the Customization dialog.
Comment 5 LibreTraining 2018-04-16 18:28:02 UTC
(In reply to Yousuf Philips (jay) (retired) from comment #3)

> 
> > And for the same reason you added it to
> > the toolbar, I want to have it visible but without the possibility that a
> > colleague can do direct formatting with it.
> 
> Well if others agree its a good idea, then the better option would be to
> have an argument added onto the existing uno commands that just disables
> user input, something like .uno:CharFontName?Enabled:short=0

Word has a feature where you can disable any direct formatting.
Users can only use the template pre-defined styles.

This prevents receiving "style soup" documents from inexperienced users.

This is very useful when multiple users are supplying documents to be combined or imported into a larger publication.

It sounds like these UNO commands could also help achieve that goal.
Comment 6 Heiko Tietze 2018-06-02 07:08:30 UTC
I'm against too many commands. And I agree with Jay that showing font information is not needed. It sounds like a can of worms as name and size are just two parameters that most users are aware of unlike indentation or spacing, for example. Toolbars are means to access frequently used functions and not to show information, strictly speaking. If we show information that has to be in the statusbar.

WF IMHO.
Comment 7 Cor Nouws 2018-06-05 21:55:04 UTC
The request is the UNO-command to be able to show simple information, that makes it easier to recognize a style in the case mentioned, has my sympathy. The proposed way to implement the thing, not. So I would suggest some further thinking.
Comment 8 Heiko Tietze 2018-06-13 19:43:14 UTC
Summarizing the input from UX (primarily my own opinion): Toolbars are controls for frequently used functions, and I'm against abusing it for just information. If we show information it should be at the statusbar or even better at a dedicated styles inspector (bug 112852, bug 115311, bug 88559).

=> WF