[Libreoffice-ux-advise] [Bug 135501] Change the default UI

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=135501

--- Comment #14 from Telesto <telesto at surfxs.nl> ---
(In reply to andreas_k from comment #12)
> From an enterprise point of view, LibO should remove all different UIs and
> make them available as extension.

What's the reasoning behind this? I only see different audiences. Not taking in
editions. University's who use LibreOffice should use an Enterprise Edition.
Which maybe opt for the tabbed menu, as the enduser (students) like them etc.
I don't think the dichotomy between community <-> enterprise being fruitful. 
Company's might have to drop toolbars because every employee being used to
tabbed stuff.  

About the extension part; LibreOffice has outdone itself on the variants of the
user interface, IMHO. This shows the flexibility. However, it's confusing to
choose (from user perspective) and hard to maintain quality of those. There are
specific tabbed related issues.

So if there are toolbar & a tabbed bar default and the rest as extension (if
technical possible), also fine

>From a community point of view I would say go for tabbed layout for windows users by default

Hard to tell why people are choosing LibreOffice, maybe because of the toolbar
:-). I'm surely not to interested in they tabbed stuff. However I do read a lot
of complains about LibreOffice looking old & outdated. 
Mostly because of lacking tabbed toolbar, but maybe (also) partly because of
theming. Somehow I find they tabbed mode one big gray area. Not nice to look
at. For example the tabs are still gray even with theming. And sidebar having
different shade of gray. It's aesthetically not 'polished' somehow; can't put
my finger on it exactly. It must be possible to make it little more attractive
for they eye, without being distracting. [And I have this problem of course
only with tabbed interface, not with they regular toolbar]

-- 
You are receiving this mail because:
You are on the CC list for the bug.