My GSoC proposition: Raw Input
ewdevel at gmail.com
Thu Apr 5 11:24:34 CDT 2012
In my opinion this implementation does not have to support exotic
devices like tablets. Bear in mind, that all applications affected by
raw input are games (at least for now), so in my opinion this
implementation have to be easy to extend to other devices - it doesn't
have to directly support it. My main focus would be to support mouse
(possibly mice), keyboard and joysticks. Tablets may wait for a time,
when software starts to use them.
Every one of these input devices (possibly except many mice support)
are already implemented.
It'd be hard to complete, but I still think it might be done, because
4 months as a full time job is a lot of time to spend on one subject.
Also, we have "hacky, but working" infamous raw3.patch, which I could
use for reference - of course the end goal will be to get something,
that would be accepted by AJ.
Also Vitaliy, thanks for the hint. I agree, that it's very important
to make good desing and consult it on maillist before writing any
code. That's what I'll do.
W dniu 5 kwietnia 2012 04:10 użytkownik Vitaliy Margolen
<wine-devel at kievinfo.com> napisał:
> On 04/04/2012 12:34 PM, Henri Verbeet wrote:
>> On 4 April 2012 20:21, Eryk Wieliczko<ewdevel at gmail.com> wrote:
>>> I've been thinking about joining GSoC as a student this year. As an
>>> idea I propose Raw Input, and I seek your advise. Is this topic good,
>>> what are possible catches, etc.
>>> I think that it might be possible to finally do a decent
>>> implementation, that would (besides mouse and keyboard) also support
>>> joysticks and possibly some other input devices - tablets and multiple
>>> mice and keyboards.
>>> What do you think about this topic?
>> My impression of Raw Input is that it's the kind of thing that's
>> fairly hard even for someone already familiar with all the areas of
>> Wine involved. That probably makes it unsuitable for GSoC, although I
>> suppose there are no hard rules for what is or isn't suitable.
> It's not really that hard. The hard part is getting design accepted by AJ.
> Raw Input has to heavily interact with wine server. And any changes there
> are hard to get right and eventually accepted.
> So, if you have an idea of how you want to do it. And this idea is good
> enough to go in - that's fine. But be ready to completely redesign & re-code
> some pieces if design won't be accepted.
More information about the wine-devel