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


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

--- Comment #26 from Heiko Tietze <tietze.heiko@gmail.com> ---
(In reply to Ole Tange from comment #25)
What I refuse (and other people I talked to as well) is the multi-column output.
Can you elaborate on why? 

You focus on the presentation of the list content while dropdowns and list
views usually are there to select an item. When those lists grow the typical
approach for quicker selection is a filter on typing and proper sorting. Your
proposal is not a lightweight standard control anymore and has accessibility
issues. In a one-dimensional list the navigation is done per cursor up/down
while two dimensions multiply the effort (plus all the trouble around impaired
users that have to relay on screen readers). And mentioned before I doubt that
scrolling works nicely as your columns are filled unequally.

I can justify why I prefer the multi-column output: IMHO the goal is to
quickly identify and select one item. 

If you read interface styleguides you will not find the identification aspect
being relevant for lists. 

Your idea is nice for the overview (I would focus on this part ignoring column
types), additional to the selection. And you could realize it yourself as an
extension. How about that?

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