Date: prev next · Thread: first prev next last
August 2020 Archives by date, by thread · List index


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

andreas_k <kainz.a@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kainz.a@gmail.com

--- Comment #12 from andreas_k <kainz.a@gmail.com> ---
From a muffin dev point of view I can say that if LibO change to a notebookbar
layout by default, than the LibO message has to be also, that LibO is a
community project and not for enterprises.

From a community point of view I would say go for tabbed layout for windows
users by default to find devs how will work on Bugfixes for the notebookbar
component. I was very conservative when users switch to different UIs cause
there is no developer how work on Bugfixes. But after years of waiting that
someone will work on Bugfixes, Nobody come to support my work so I also get
boring to work on notebookbar.

From an enterprise point of view, LibO should remove all different UIs and make
them available as extension.

As LibO is a community project with smart people to do think things, I would
say +1000 to have an UI selector after the installation. LibO have to care on
the project and not on the enterprise end user.

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

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.