On Tue, Oct 26, 2010 at 5:37 PM, Kevin Hunter <hunteke@earlham.edu> wrote:
At 6:18pm -0400 Tue, 26 Oct 2010, Christian Lohmaier wrote:
I personally disagree that an alphabetically sortet list is best.
e.g. now the font inclusion options wrt dejavu and liberation fonts
are spread apart, build tool options are interspread the
feature/code switches, extension-switches are mixed with core ones,
etc.
I personally don't like that part of the patch.
And butting in to the conversation, may I offer a middle of the road
suggestion? I find alphabetizing very helpful, both as an end user and as a
developer. However, you do make an excellent point that related options
need to still be together. Solution: argument groups.
I don't actually know this environment, but if I may point you to Python's
Argument Parsing module for a moment, I claim that it has an intuitive API
for just this purpose:
http://docs.python.org/library/argparse.html
Take note as well of argument groups (Section 15.4.5.3).
fwiw: I like functional grouping too.
pure alphabetical is useful when you know the name of the option you
are looking for. most of the time, I find myself fishing for something
that may be related for the issue I have... without knowing the name
of the option in advance....
Norbert
A thought,
Kevin
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
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.