Mouse related accessibility settings (was: [Kde-accessibility] kcontrol)

[Pupeno]

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 18 December 2002 05:58, Olaf Jan Schmidt wrote:
> Pupeno wrote on kde-accessibility:
> > Currently (HEAD), there's a group Regional and Accessibility and inside
> > that there's only one item related to Accessibility called,
> > Accessibility. That item contains two tabs to configure bell and
> > keyboard.
>
> Is there no mouse tab?
> That's really bad, because that means there are accessibility settings
> that are not in "Regional and Accessibility".
Yes, there's no mouse tab, the mouse related settings are in=20
peripherasl/mouse.

> In KDE 3.0.5, Accessibility is under personal settings, and also contains
> settings of the keyboard mouse (now moved to devices/mouse).
>
> The KDE Usability Project did a rework of the kcontrol modules for KDE
> 3.1. The keyboard related accessibility settings are duplicated now:
>
> http://lists.kde.org/?l=3Dkde-usability&m=3D103479301115699&w=3D2
>
> Is it possible to do something similar for mouse related accessibility
> settings? Otherwise we seriously need another rework of kcontrol.
I don't see why not. Having a mouse tab in the (future) Accessibility group=
=20
with the mouse accessibility related options is a good idea not so hard to=
=20
implement.

> Is it possible to do that for KDE 3.1? Otherwise we will ship a very
> confusing kcontrol.
I don't think so, KDE 3.1 is almost out, they're doing the security audit, =
but=20
it is totally frozen (well, it has been froze, as usual, for three months o=
r=20
more), that measn , no features and that includes changes like that. Anyway=
,=20
I can't do it (I can just work on HEAD). Unfortunatly, we'll have to wait f=
or=20
3.2 (3.2 will be like 'The Accessibility resurrection' ;)

> > Break up the group into Regional as one group and Accessibility as
> > another group.
>
> "Regional and Accessibility" is more or less a container for everything
> that did not fit into any of the other groups. It also contains
> keyboard-related settings that are neither regional settings nor
> accessibility settings, but close to some of them.

Yes, I know, I don't know why keyboard layout isn't in Peripherals/Keyboard=
=20
but that's not up to me (I've been seen the reestructuring kcontrol thread =
in=20
kde-core-devel for a lot of times and I think nobody will be happy with mor=
e=20
kcontrol oddities, anyway, I think the accessibility group should be done, =
by=20
us)

> > The Accessbility group will contain: Bell and Keyboard (break that tabs
> > into two at least there are more things) and in a close feature Text To
> > Speech (a.k.a.: Proklam).
>
> Yes, in an "Accessibility" group we should have four items: keyboard,
> mouse, bell, and the new text-to-speech module.
Agree

> There are some items that could fit into several of the three groups
> "Regional", "Accessibility" and "Devices", and shortcut configuration
> does not really belong into any of them. That's what makes it so
> difficult.
I didn't understand, what do you mean by 'and shortcut configuration
> does not really belong into any of them'

> > I would like to clean up that too.
>
> I definately think cleaning this up is a good idea, but expect heavy
> discussions with some kde-usability people...
I mean, clean up of source code.
But it seems we'll have to go a bit deeper.
=2D --=20
Pupeno: pupeno@kde.org
KDE Accessibility co-maintainer
http://accessibility.kde.org
=2D ---
Help the hungry children of Argentina,
please go to (and make it your homepage):
http://www.porloschicos.com/servlet/PorLosChicos?comando=3Ddonar
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+AHdCLr8z5XzmSDQRAic0AKCwuuQrA8pSu4lnLBuH/x+IdgwMRACdF1Bx
fpcp+IL1EpkW6Ot1vHydjbE=3D
=3Dtruo
=2D----END PGP SIGNATURE-----