Re: Input devices capplets
On Tue, 2007-11-06 at 17:02 +, Sergey Udaltsov wrote: About the many tabs: at least the Layouts tab could move to the i18n capplet when we have finished it. Oh really? But what about the Layout Options popup? It does not really belong to i18n... how so? it belong to the layout part, which is in the localization capplet mockup Denis sent a while ago, and which I should be getting to life soon (sorry, quite busy, and I've got just a very little code done, but will try to have a first version before the end of the week) -- Rodrigo Moya [EMAIL PROTECTED] ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
how so? it belong to the layout part, which is in the localization capplet mockup Denis sent a while ago, and which I should be getting to life soon (sorry, quite busy, and I've got just a very little code done, but will try to have a first version before the end of the week) Well, if you think so... I am just not sure people find things like numpad-related options or CapsLock behaviour belonging to i18n. Anyway, since now this is just a popup - it would be quite trivial to move it into any capplet we'll find suitable. Actually I was more thinking along the lines of the latest mockups: http://ultimum-projekt.de/mockups/keyboard.html. Sergey ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
On Wed, 2007-10-31 at 16:27 -0400, Matthias Clasen wrote: On 10/31/07, Jürg Billeter [EMAIL PROTECTED] wrote: On Wed, 2007-10-31 at 18:59 +0100, Denis Washington wrote: I created two mockups for possible keyboard and mouse capplets in GNOME 2.20. Their aim is to incorporate accessibility features in both; the existing keyboard a11y features into Keyboard and the already discussed Mousetweaks settings into Mouse. The mockups can be found here: Keyboard: http://ultimum-projekt.de/mockups/keyboard.html Mouse:http://ultimum-projekt.de/mockups/mouse.html What do you think? Shouldn't we also incorporate the Keyboard Shortcuts capplet into the Keyboard capplet at the same time? Otherwise good work, as far as I can tell from a quick look. I don't think there was sufficient agreement that shortcuts have much if anything to do with the other keyboard settings. right, and it would make the keyboard capplet too crowded. Since there is the mousetweaks discussion going on, what about having shortcuts and mousetweaks into an 'input devices actions' (find a better name) capplet? -- Rodrigo Moya [EMAIL PROTECTED] ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
In the keyboard capplet it would be good to add on the Layouts tab the option to configure the keyboard shortcut used to switch between layouts. Currently this option is located in the Layout Options tab, inside Group Shift/Lock behaviour, towards the end of the list. This options group is one of the groups provided in base.xml. The only way to distinguish it is hardcode its id. Which does not sound great to me... But the visible strings in this group - they are provided as is, and I totaly against extracting the key names from them (BTW they are localized). Sergey ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
Le jeudi 01 novembre 2007, à 22:48 +0100, Luca Ferretti a écrit : Il giorno gio, 01/11/2007 alle 15.09 +0100, Vincent Untz ha scritto: Matthew hacked this up to work with DEVICE_RESOLUTION, so SHMConfig isn't needed. Only three settings work, though (tap to click, horizontal scrolling, vertical scrolling). I don't know where to find a patch (the source package doesn't have any patch), but I believe it's only a minor change. But it's only a short term hack, I guess :-) (I looked at all this to see how easy it'd be to add support for my disable touchpad key) mmmhhh.. Isn't Ignore touchpad while typing option a better solution for laptop guys? Don't know how other people work, but when I plug an USB mouse, I don't want my touchpad to work. That's the main use case for me. But your proposal can also make sense. Anyway, in this case, it's not about making it automagically work, but about using the key on my laptop which is designed for this :-) Vincent -- Les gens heureux ne sont pas pressés. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
On Thu, 2007-11-01 at 11:38 +0100, Denis Washington wrote: Especially if we have plans to add other kinds of shortcuts, like e.g. mouse gestures, having them in the keyboard capplet is quite counter-intuitive. I think part of the problem is that it looks a little ugly/confusing having both Keyboard and Keyboard Shortcuts items in the Preferences menu/shell, so it would certainly be good if we're generalising it to the extent that we can change the name to just Shortcuts instead. That said, I can certainly see an argument for having Keyboard Shortcuts in the Keyboard prefs, and Mouse Getsures in the Mouse Prefs-- I'm pretty sure that's where I'd look first. Cheeri, Calum. -- CALUM BENSON, Usability Engineer Sun Microsystems Ireland mailto:[EMAIL PROTECTED]GNOME Desktop Team http://blogs.sun.com/calum +353 1 819 9771 Any opinions are personal and not necessarily those of Sun Microsystems ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
On Mon, 2007-11-05 at 19:29 +0100, Denis Washington wrote: The main problem that Jens and I still have is the organization of the a11y options. I put the beep options in an extra Notifications window to save space, but this is highly suboptimal. Having another way to organize these settings sanely without having a too long tab would be great. I guess one option would be to move the notifications to the Sound capplet, although it's probably not really a very good idea to fracture the AccessX settings like that if we can avoid it. (On the other hand, the visual bell setting already lives in the Sound capplet, and it's arguably sort-of related, in an okay-maybe-that's-stretching-it-a-bit kind of way...) Cheeri, Calum. -- CALUM BENSON, Usability Engineer Sun Microsystems Ireland mailto:[EMAIL PROTECTED]GNOME Desktop Team http://blogs.sun.com/calum +353 1 819 9771 Any opinions are personal and not necessarily those of Sun Microsystems ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
Hi Denis, I created two mockups for possible keyboard and mouse capplets in GNOME 2.20. Their aim is to incorporate accessibility features in both; the existing keyboard a11y features into Keyboard and the already discussed Mousetweaks settings into Mouse. The mockups can be found here: Keyboard: http://ultimum-projekt.de/mockups/keyboard.html Mouse:http://ultimum-projekt.de/mockups/mouse.html What do you think? I guess I know why you cross-posted this message to d-d-l and cc-list (increase visibility). However, cross-posting is not really apropriate for topics that will most likely generate long threads like this one and will end up on too specific discussions for a wider-scope mailing list such as d-d-l. --lucasr ps: maybe that's just me? ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
About the many tabs: at least the Layouts tab could move to the i18n capplet when we have finished it. Oh really? But what about the Layout Options popup? It does not really belong to i18n... Sergey ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
Il giorno gio, 01/11/2007 alle 15.09 +0100, Vincent Untz ha scritto: Matthew hacked this up to work with DEVICE_RESOLUTION, so SHMConfig isn't needed. Only three settings work, though (tap to click, horizontal scrolling, vertical scrolling). I don't know where to find a patch (the source package doesn't have any patch), but I believe it's only a minor change. But it's only a short term hack, I guess :-) (I looked at all this to see how easy it'd be to add support for my disable touchpad key) mmmhhh.. Isn't Ignore touchpad while typing option a better solution for laptop guys? ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
On Wed, 2007-10-31 at 18:59 +0100, Denis Washington wrote: Hi, I created two mockups for possible keyboard and mouse capplets in GNOME 2.20. Their aim is to incorporate accessibility features in both; the existing keyboard a11y features into Keyboard and the already discussed Mousetweaks settings into Mouse. The mockups can be found here: Keyboard: http://ultimum-projekt.de/mockups/keyboard.html Mouse:http://ultimum-projekt.de/mockups/mouse.html What do you think? I think they look good, given we can't really merge them on a single capplet. The keyboard capplet has many tabs, but this is much better than having separate a11y capplets, so, unless something better is proposed, you've got my vote :) -- Rodrigo Moya [EMAIL PROTECTED] ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
On Mon, 2007-11-05 at 17:57 +0100, Rodrigo Moya wrote: On Wed, 2007-10-31 at 18:59 +0100, Denis Washington wrote: Hi, I created two mockups for possible keyboard and mouse capplets in GNOME 2.20. Their aim is to incorporate accessibility features in both; the existing keyboard a11y features into Keyboard and the already discussed Mousetweaks settings into Mouse. The mockups can be found here: Keyboard: http://ultimum-projekt.de/mockups/keyboard.html Mouse:http://ultimum-projekt.de/mockups/mouse.html What do you think? I think they look good, given we can't really merge them on a single capplet. The keyboard capplet has many tabs, but this is much better than having separate a11y capplets, so, unless something better is proposed, you've got my vote :) Thanks for the positive feedback. :) About the many tabs: at least the Layouts tab could move to the i18n capplet when we have finished it. The main problem that Jens and I still have is the organization of the a11y options. I put the beep options in an extra Notifications window to save space, but this is highly suboptimal. Having another way to organize these settings sanely without having a too long tab would be great. Regards, Denis ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
On 11/1/07, Matthew Garrett [EMAIL PROTECTED] wrote: On Thu, Nov 01, 2007 at 09:12:59AM -0400, Matthias Clasen wrote: On 11/1/07, Scott James Remnant [EMAIL PROTECTED] wrote: This needs infrastructure fixes in the lower layers first. SHMConfig is really not something we want to turn on by default, the touchpad driver should use the existing Xinput configuration mechanism. Exactly. Our patches may not be that useful right now. Unfortunately, I don't expect much interest from the Ubuntu side in doing this kind of infrastructure work. Or do you have plans to do the right thing here in the long term, Scott ? The Ubuntu patches use XInput, not SHMConfig. However, right now they're overloading DEVICE_RESOLUTION rather than using a well-specified device control. I'm working with X upstream to define a suitable mechanism for doing this. Thats great to hear, thanks. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
On Wed, 2007-10-31 at 16:27 -0400, Matthias Clasen wrote: On 10/31/07, Jürg Billeter [EMAIL PROTECTED] wrote: On Wed, 2007-10-31 at 18:59 +0100, Denis Washington wrote: I created two mockups for possible keyboard and mouse capplets in GNOME 2.20. Their aim is to incorporate accessibility features in both; the existing keyboard a11y features into Keyboard and the already discussed Mousetweaks settings into Mouse. The mockups can be found here: Keyboard: http://ultimum-projekt.de/mockups/keyboard.html Mouse:http://ultimum-projekt.de/mockups/mouse.html What do you think? Shouldn't we also incorporate the Keyboard Shortcuts capplet into the Keyboard capplet at the same time? Otherwise good work, as far as I can tell from a quick look. I don't think there was sufficient agreement that shortcuts have much if anything to do with the other keyboard settings. Especially if we have plans to add other kinds of shortcuts, like e.g. mouse gestures, having them in the keyboard capplet is quite counter-intuitive. Denis ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
Hi, There is no touchpad tab in mouse capplet. Is this planned ? Étienne. -- E Ultreïa ! ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
Em Qui, 2007-11-01 às 11:47 +0100, Étienne Bersac escreveu: Hi, There is no touchpad tab in mouse capplet. Is this planned ? http://bugzilla.gnome.org/show_bug.cgi?id=154029 -- Jonh Wendell www.bani.com.br ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
Hi, Running Gutsy, the mouse-properties capplet does have a touchpad tab. But the mockup drops it. Unless this is planned, this is a regression. Otherwise the touchpad tab is ubuntu specific. Regards, Étienne. -- E Ultreïa ! ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
On Thu, 2007-11-01 at 12:24 +0100, Étienne Bersac wrote: Running Gutsy, the mouse-properties capplet does have a touchpad tab. But the mockup drops it. Unless this is planned, this is a regression. Otherwise the touchpad tab is ubuntu specific. It was a last minute hack-up by Matthew Garrett; he may not have sent the patch upstream yet, and it may result on some other Ubuntu hacks to work. If there's immediate interest, I can dig it out if I know the right person to give it to. Scott -- Scott James Remnant [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
On 11/1/07, Scott James Remnant [EMAIL PROTECTED] wrote: On Thu, 2007-11-01 at 12:24 +0100, Étienne Bersac wrote: Running Gutsy, the mouse-properties capplet does have a touchpad tab. But the mockup drops it. Unless this is planned, this is a regression. Otherwise the touchpad tab is ubuntu specific. It was a last minute hack-up by Matthew Garrett; he may not have sent the patch upstream yet, and it may result on some other Ubuntu hacks to If there's immediate interest, I can dig it out if I know the right person to give it to. This needs infrastructure fixes in the lower layers first. SHMConfig is really not something we want to turn on by default, the touchpad driver should use the existing Xinput configuration mechanism. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
On Thu, 2007-11-01 at 08:58 -0400, Matthias Clasen wrote: On 11/1/07, Scott James Remnant [EMAIL PROTECTED] wrote: On Thu, 2007-11-01 at 12:24 +0100, Étienne Bersac wrote: Running Gutsy, the mouse-properties capplet does have a touchpad tab. But the mockup drops it. Unless this is planned, this is a regression. Otherwise the touchpad tab is ubuntu specific. It was a last minute hack-up by Matthew Garrett; he may not have sent the patch upstream yet, and it may result on some other Ubuntu hacks to If there's immediate interest, I can dig it out if I know the right person to give it to. This needs infrastructure fixes in the lower layers first. SHMConfig is really not something we want to turn on by default, the touchpad driver should use the existing Xinput configuration mechanism. Exactly. Our patches may not be that useful right now. Scott -- Scott James Remnant [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
On 11/1/07, Scott James Remnant [EMAIL PROTECTED] wrote: This needs infrastructure fixes in the lower layers first. SHMConfig is really not something we want to turn on by default, the touchpad driver should use the existing Xinput configuration mechanism. Exactly. Our patches may not be that useful right now. Unfortunately, I don't expect much interest from the Ubuntu side in doing this kind of infrastructure work. Or do you have plans to do the right thing here in the long term, Scott ? ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
On Thu, 2007-11-01 at 09:12 -0400, Matthias Clasen wrote: On 11/1/07, Scott James Remnant [EMAIL PROTECTED] wrote: This needs infrastructure fixes in the lower layers first. SHMConfig is really not something we want to turn on by default, the touchpad driver should use the existing Xinput configuration mechanism. Exactly. Our patches may not be that useful right now. Unfortunately, I don't expect much interest from the Ubuntu side in doing this kind of infrastructure work. Or do you have plans to do the right thing here in the long term, Scott ? We have open positions for people to do this kind of work; it isn't necessarily something our existing team has time/skills for. Scott -- Scott James Remnant [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
Le jeudi 01 novembre 2007, à 08:58 -0400, Matthias Clasen a écrit : On 11/1/07, Scott James Remnant [EMAIL PROTECTED] wrote: On Thu, 2007-11-01 at 12:24 +0100, Étienne Bersac wrote: Running Gutsy, the mouse-properties capplet does have a touchpad tab. But the mockup drops it. Unless this is planned, this is a regression. Otherwise the touchpad tab is ubuntu specific. It was a last minute hack-up by Matthew Garrett; he may not have sent the patch upstream yet, and it may result on some other Ubuntu hacks to If there's immediate interest, I can dig it out if I know the right person to give it to. This needs infrastructure fixes in the lower layers first. SHMConfig is really not something we want to turn on by default, the touchpad driver should use the existing Xinput configuration mechanism. Matthew hacked this up to work with DEVICE_RESOLUTION, so SHMConfig isn't needed. Only three settings work, though (tap to click, horizontal scrolling, vertical scrolling). I don't know where to find a patch (the source package doesn't have any patch), but I believe it's only a minor change. But it's only a short term hack, I guess :-) (I looked at all this to see how easy it'd be to add support for my disable touchpad key) Vincent -- Les gens heureux ne sont pas pressés. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
On Thu, 2007-11-01 at 15:09 +0100, Vincent Untz wrote: Le jeudi 01 novembre 2007, à 08:58 -0400, Matthias Clasen a écrit : On 11/1/07, Scott James Remnant [EMAIL PROTECTED] wrote: On Thu, 2007-11-01 at 12:24 +0100, Étienne Bersac wrote: Running Gutsy, the mouse-properties capplet does have a touchpad tab. But the mockup drops it. Unless this is planned, this is a regression. Otherwise the touchpad tab is ubuntu specific. It was a last minute hack-up by Matthew Garrett; he may not have sent the patch upstream yet, and it may result on some other Ubuntu hacks to If there's immediate interest, I can dig it out if I know the right person to give it to. This needs infrastructure fixes in the lower layers first. SHMConfig is really not something we want to turn on by default, the touchpad driver should use the existing Xinput configuration mechanism. Matthew hacked this up to work with DEVICE_RESOLUTION, so SHMConfig isn't needed. Only three settings work, though (tap to click, horizontal scrolling, vertical scrolling). I don't know where to find a patch (the source package doesn't have any patch), but I believe it's only a minor change. But it's only a short term hack, I guess :-) In debian/patches: 26_add_touchpad_to_mouse_settings.patch 27_add_touchpad_to_settings_daemon.patch 28_fixup_touchpad_config.patch 30_extra_touchpad_config_paranoia.patch (http://people.ubuntu.com/~scott/gnome-control-center-patches) Scott -- Scott James Remnant [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
On Wed, 2007-10-31 at 18:59 +0100, Denis Washington wrote: Keyboard: http://ultimum-projekt.de/mockups/keyboard.html The layout options dialog should really be re-worked in order to make it understandable and usable... ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
On Thu, Nov 01, 2007 at 09:12:59AM -0400, Matthias Clasen wrote: On 11/1/07, Scott James Remnant [EMAIL PROTECTED] wrote: This needs infrastructure fixes in the lower layers first. SHMConfig is really not something we want to turn on by default, the touchpad driver should use the existing Xinput configuration mechanism. Exactly. Our patches may not be that useful right now. Unfortunately, I don't expect much interest from the Ubuntu side in doing this kind of infrastructure work. Or do you have plans to do the right thing here in the long term, Scott ? The Ubuntu patches use XInput, not SHMConfig. However, right now they're overloading DEVICE_RESOLUTION rather than using a well-specified device control. I'm working with X upstream to define a suitable mechanism for doing this. -- Matthew Garrett | [EMAIL PROTECTED] ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
On Wed, 2007-10-31 at 18:59 +0100, Denis Washington wrote: Hi, I created two mockups for possible keyboard and mouse capplets in GNOME 2.20. Their aim is to incorporate accessibility features in both; the existing keyboard a11y features into Keyboard and the already discussed Mousetweaks settings into Mouse. The mockups can be found here: Keyboard: http://ultimum-projekt.de/mockups/keyboard.html Mouse:http://ultimum-projekt.de/mockups/mouse.html What do you think? I would be tickled pink if somebody made the mouse preferences tool capable of setting certain things on a per-mouse basis. Some use cases: *) My laptop has a touchpad, but I far prefer using an actual mouse. I use the touchpad when I have to, but plug in a mouse when I have desk space. My preferred speed settings for the touchpad are much different than for the mouse. *) To offset wrist pain, I've tried to teach myself to mouse left-handed. I'm reasonably OKish at it, but I still prefer using the right for things where I need to be fast and precise (like games). It would be nice to have two mice, one set to left-handed, the other to right-handed. I blogged about this not long ago and got some comments. In particular, Anders Olsson says I myself am using a total of six different pointing devices in different combinations. So I'm at least not the only person weird enough to want this functionality. (I suspect my first use case is probably the most common use of this proposed feature. Lots of people prefer mice, but will use their laptop's built-in pointing device when they have to.) -- Shaun ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
In Ubuntu, the touchpad tab is only shown if you have a touchpad. Regards, Denis On Thu, 2007-11-01 at 12:24 +0100, Étienne Bersac wrote: Hi, Running Gutsy, the mouse-properties capplet does have a touchpad tab. But the mockup drops it. Unless this is planned, this is a regression. Otherwise the touchpad tab is ubuntu specific. Regards, Étienne. -- E Ultreïa ! ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Input devices capplets
Hi, I created two mockups for possible keyboard and mouse capplets in GNOME 2.20. Their aim is to incorporate accessibility features in both; the existing keyboard a11y features into Keyboard and the already discussed Mousetweaks settings into Mouse. The mockups can be found here: Keyboard: http://ultimum-projekt.de/mockups/keyboard.html Mouse:http://ultimum-projekt.de/mockups/mouse.html What do you think? Regards, Denis ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
On Wed, 2007-10-31 at 18:59 +0100, Denis Washington wrote: I created two mockups for possible keyboard and mouse capplets in GNOME 2.20. Their aim is to incorporate accessibility features in both; the existing keyboard a11y features into Keyboard and the already discussed Mousetweaks settings into Mouse. The mockups can be found here: Keyboard: http://ultimum-projekt.de/mockups/keyboard.html Mouse:http://ultimum-projekt.de/mockups/mouse.html What do you think? Shouldn't we also incorporate the Keyboard Shortcuts capplet into the Keyboard capplet at the same time? Otherwise good work, as far as I can tell from a quick look. Jürg ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Input devices capplets
On 10/31/07, Jürg Billeter [EMAIL PROTECTED] wrote: On Wed, 2007-10-31 at 18:59 +0100, Denis Washington wrote: I created two mockups for possible keyboard and mouse capplets in GNOME 2.20. Their aim is to incorporate accessibility features in both; the existing keyboard a11y features into Keyboard and the already discussed Mousetweaks settings into Mouse. The mockups can be found here: Keyboard: http://ultimum-projekt.de/mockups/keyboard.html Mouse:http://ultimum-projekt.de/mockups/mouse.html What do you think? Shouldn't we also incorporate the Keyboard Shortcuts capplet into the Keyboard capplet at the same time? Otherwise good work, as far as I can tell from a quick look. I don't think there was sufficient agreement that shortcuts have much if anything to do with the other keyboard settings. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
