Date: prev next · Thread: first prev next last
June 2018 Archives by date, by thread · List index


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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |kainz.a@gmail.com
         Resolution|---                         |WONTFIX

--- Comment #2 from andreas_k <kainz.a@gmail.com> ---
Thanks for the bug report to give the possibility to talk about this topic.

As there are a lot of different NB implementations and at the same
implementation there are different behavior I would close this bug with
wantfix.

Example:
Ordinary NB give the users the possibility to use the sidebar. In Impress you
NEED the sidebar for transition and some other stuff. Also draw functions would
be a good example, cause first the sidebars are an big improvement for
transition and draw functions have transition stuff in a horizontal toolbar is
not that intuitive than in the sidebar. So from the designer point of view
(groupedbar and tabbedbar NB) I tend to use the NB as much as possible, BUT if
the sidebar layout is more useful, I would use the existing sidebar instead of
reimplement (and maintain) a NB.

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