Re: Feature proposal: Alternative input system based on low-cost webcam

[Jan Jokela <janjokela gmail com>]

I think we are missing the important bit here.

Tracking your head with a webcam to drive a mouse results in a bad experience. It doesn't work even remotely well.

Someone will, in the future, figure out how to do this properly and then it won't be called an accessibility feature but something everyone will want to use.

I -think- that for this to work properly we'd need a bunch of things: first, we need to track not only head movement but also your eyes and several facial muscles so that we can have accurate tracking and hints about your intentions. Well, this requires cameras with resolutions much higher than VGA, which is the current standard for these. Then, someone needs to figure out how to track all these elements real-time with little cpu usage. As it is, we can't even maintain a Mexican hat over ones head in Cheese without it lagging 3 seconds behind. And finally for this to work we'de need pretty good AI to be able to understand what you really want so that you don't end up sending a draft-mail just because you glanced at that gorgeous girl that just passed in front of you.

Cheers,

Jan Jokela

On Mon, Oct 24, 2011 at 2:49 PM, Piñeiro <apinheiro igalia com> wrote:

On 10/24/2011 09:16 AM, Vincent Untz wrote:
>> There are other apps included on GNOME moduleset but not at GNOME git
>> (ie: inkscape is also hosted at sourceforge).
> That's the difference between core and non-core. For proper integration
> with GNOME (which includes integration in gnome-shell, g-c-c, etc.),
> this feature would need to be in core, which has additional
> requirements.

I was aware of those difference. But it is true that I missed to do a
analysis in this aspect in relation of both eViacam and Dasher (in a
different thread) (so thanks for the reminder)

>
> Inkscape, on the other hand is not part of GNOME core -- it's a great
> application, but it doesn't need any deep integration with the core of
> the desktop.

In this aspect, and taking into account the know problems with the
integration of eViacam and Dasher, it is clear that we can't ask them to
be accepted as GNOME core, at least for the moment. But both are really
great applications and cover functionality that we feel are we lack
right now. And we feel that it would be easier to improve their
integration with the core if we include them on GNOME ecosystem. Or
explaining this from other POV. If someone ask for that feature and ask
on #a11y channel for an app solving this, we will recommend those.

And in this aspect,  and in relation with what I said about a missing
analysis, after thinking a little on all the accessibility features
proposed, it is clean (IMHO) that there are two different groups:

* Valid as core, so valid as a feature proposal):
  * zoom dialog
  * Brightness and contrast functionality
  * Focus caret/tracking
  * Braille translator
* Work still required to be core, so not valid as a feature proposal but
the moment, just asking them to be include on GNOME apps modulesets:
  * eViacam
  * Dasher

Although in the case of eViacam it is still required to debate if it is
valid also to be included on GNOME moduleset.

BR

--
Alejandro Piñeiro Iglesias

_______________________________________________
desktop-devel-list mailing list
desktop-devel-list gnome org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list