2014-04-15 17:11 GMT+02:00 PCMan <email@example.com>:Maybe a good idea is to merge them first and wait for user feedback?On Tue, Apr 15, 2014 at 6:30 PM, Jerome Leclanche <firstname.lastname@example.org> wrote:
> On Tue, Apr 15, 2014 at 11:07 AM, email@example.com
> <firstname.lastname@example.org> wrote:
>> 2014-04-15 11:40 GMT+02:00 PCMan <email@example.com>:
>>> I'd like to raise this issue again.
>>> Previously lxinput-qt provides configuration tools for keyboard and mouse.
>>> It handles things like delay, repeat interval, acceleration of mouse
>>> pointer, ...etc.
>>> The original lxqt-config-mouse only handles mouse cursor theme. It
>>> does not manage other mouse configurations. It's obvious that it might
>>> be better to merge them.
>>> I already have working code in my own branch, but I noticed a problem.
>>> Now lxqt-config-input (the merged program) has three config pages.
>>> One is for keyboard settings, and the other two are for mouse settings
>>> and cursor theme settings.
>>> If later we support keyboard layout settings, there will be four pages.
>>> The config dialog will become crowded.
>>> I hence want to propose splitting it into two programs,
>>> lxqt-config-keyboard for keyboard related settings and
>>> lxqt-config-mouse for mouse settings + cursor theme.
>>> Configure all input devices in one place sounds good, but having
>>> smaller and simpler separate tools is an appealing option, too.
>>> Any comments?
>>> Guys I'd like to ask for your comments before I continue hacking on this.
>>> If you guys don't like the idea of splitting keyboard and mouse
>>> setting tools, I can merge them into lxqt-config-inut, a single config
>>> program for all input devices.
>> I think one way of reasoning about modules is to ask: Would it make sense
>> for a user to replace it with something else?
>> I mean: You could imagine a user - say a gamer - buying some ultra-advanced
>> gaming-mouse with a gazillion buttons and extra functionality. Then he/she
>> might want to use a special-purpose application to configure that mouse, but
>> still use lxqt-config-keyboard. In that case separation of config-mouse and
>> config-keyboard would seem ok. So I'd say yes, split in 2 :-).
> I agree it's a good way to reason about it but as someone who has used
> gaming mice, you're unlikely to replace the app that provides the core
> functionality (acceleration, double click interval, wheel settings).
> You would rather use a separate config tool for the extra buttons.
> This is commonplace on both Windows and OSX, I don't see why we should
> make it different for the sake of ideology really - we shouldn't force
> people who do config dialogs for extra mouse buttons to deal with
> these types of settings which are virtually always handled by the DE
> (and even if they do, we should keep our module anyway).
> I would rather not overwhelm users with too many config dialogs.
> Putting keyboard and mouse settings in the same place is very
> J. Leclanche
>> I'm not sure about the cursor-theme, though. I feel it would be more
>> naturally placed in lxqt-config-appearance. But maybe tradition from other
>> desktops is to place it where one configures the mouse?
>> br. Chr.
>>> Thank you.
We can get some more feedback after the first alpha release.
Let's merge them first. If needed, we can split it later anytime since
it's not difficult.
That's fine by me. Although I found it more natural to split, it's not terribly important for me if we go one way or the other :-)br. Chr.Just my two cents
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
Lxde-list mailing list