Re: [Fresco-devel] input::filter

Nick Lewycky wrote:

At the moment, Input::Filter is entirely unimplemented.
Is there any documentation describing how this is supposed to work?

the whole event handling business needs some serious work. Starting from
event types to event interpretation there is a whole lot to discuss, 
have a look in the wiki...

In a nutshell, when dealing with events, there is a series of
mappings/translations to be applied. The first is to map device
specific ('raw') input to fresco's internal event data type(s).
This involves possible emulation of devices, we discussed in the ML
a while ago possible mechanisms to configure the server how to
synthesize these events (hopefully the ML archives are searchable soon,
so we can continue the discussion where it once stopped. I believe the
3dwm project picked up the idea I outlined, i.e. with a specific
functional language express how to generate mouse events with joystick
input (to drop in a simple example).

Once we have fresco events, and we figured out the target controller, we
need to map the event to an action. That is usually the task of the
controller itself, but it may be done elsewhere (with a decorator like
approach) for even more flexibility. This becomes really interesting
when you look not only at single events, but event sequences, aka.
gestures. This is important for 'direct manipulation' behavior, for
example in graphical editors.

This is a very interesting topic, and a real challenge to design in a
flexible and elegant way.

Best regards,
        Stefan