Date: prev next · Thread: first prev next last
October 2017 Archives by date, by thread · List index


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

V Stuart Foote <vstuart.foote@utsa.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |needsUXEval
             Status|UNCONFIRMED                 |NEW
                 CC|                            |libreoffice-ux-advise@lists
                   |                            |.freedesktop.org,
                   |                            |vstuart.foote@utsa.edu
     Ever confirmed|0                           |1

--- Comment #1 from V Stuart Foote <vstuart.foote@utsa.edu> ---
We already pick up OS DesktopEnvironment theme details cross platform and use
them in the LO user interface(s) implemented as needed for each OS.

Doing more "native" decorations depends on interest of devs (e.g. implementing
separate gtk3 support). But while appealing to some, and getting some dev
attention, overall integration as native OS UI and widgets is not a design or
development goal for the project. 

We use the published IDL and API for the OS DE, but are not well served doing
more to follow the whims of DE for each OS in a cross-platform project.

IMHO => WONTFIX

-- 
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.