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


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

--- Comment #19 from V Stuart Foote <vstuart.foote@utsa.edu> ---
(In reply to Bastián Díaz from comment #18)
So what is the solution?

To me, a min/max for the sidebar is not a way of "personalization" is a way
to add consistency to the contents of the sidebar -as a whole-.

How strange it would be that each tab on the sidebar, had its own width
min/max.
Actually, at some point he proposed the existence of a minimum and maximum
width for the sidebar (not all users have a wide screen), but really the
best solution is the existence of a single width for side, consistent bar
and It would save time showing and hiding the content (not adjust the width
to view the content of some tabs!).

Sure, if the Sidebar were a static UI element we could make a case for fixed
static structure. However, we quickly migrated it from .src to GTK .UI based
widgets making it dynamic by nature.  Building on that we have "enhancements"
in queue to do some neat things like splitting out content panels into
independent decks--detaching them as .UI based analogs to legacy dialogs--ref
bug 85905

The limitation at the moment is that we implement the Sidebar with its Tabbar
and just one Deck holding Content Panels, displayed docked or undocked. From a
UI design and development perspective that is constraining--and leads to wrong
headed ideas that static and fixed is better UI and improve the user
experience.

Fortunately once over that development hurdle the Sidebar gains tremendous
flexibility. For example ability to undock a custom content panel and drag your
favorite UNO widgets into it--closing the rest of the Sidebar, or shifting to
"Single" mode of bug 92220 and bug 92218

We support those longer range features now by ensuring the ability of the user
to fully customize their content panels and to retain those customizations
within a session and within their profile, with an ability to recover or
transfer their customizations to a new profile. That all comes from supporting
a design that nurtures dynamic layout and customization.

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