RE: [Widex] Updated Widex framework draft

Hi,

In the current draft, there are two ways to attach event listeners to a node in
the DOM tree: at programming level using DOM3's EventTarget interface, and at
document level using XML events and ad-hoc syntax.

By "programming level", I assume what it means is for the application code to
use the DOM3 EventTarget API in the virtual view / DOM at the server side (not
the real view / DOM at the renderer side); and then those API calls get
serialized into WO.Selector messages and delivered to the renderer.

DOM3 uses the term "programming level" because it doesn't have remote events in
mind. "Programming" means using script to attach listeners to nodes on the
client side. For us, I think what's important is WO.Selector messages, and how
the messages are generated is not a big concern. Of course, we could mention
that one possibility is for the server side toolkit to offer DOM3' EventTarget
API to operate on the virtual view.

So I would re-categorize the ways to attach event listeners to a DOM node -
inline (within UI DOM tree) or external (outside of UI DOM tree):

- inline listener specification

This includes ad-hoc syntax from various UI languages, e.g. HTML' onClick
attribute. In addition, one could use the global attributes from XML Events if
the hosting UI language supports them. In this category, WO.Update messages
should be used to maintain the listeners.

- external listener specification

This involves using WO.Selector messages to add / remove / update event
listeners in the renderer. The messages would carry the generic <listener>
element from XML Events. For example:

<addEventListener>
  <listener id="ls1" event="sul:mouse-click" observer="aCircle"/>
</addEventListener>

<removeEventListener>
  ...
</removeEventListener>

The "handler", "phase", and "propagate" attributes of the listener element may
not be relevant to network event delivery, but we can worry about that later in
the Message Formats draft.

The benefit of using external specification is that it's more flexible and
reusable (just like the CSS case).

Regards,

Jin
________________________________________
Jin Yu
OpenXUP.org

> From: Vlad.Stirbu@nokia.com [mailto:Vlad.Stirbu@nokia.com] 
> Sent: Wednesday, May 31, 2006 4:31 AM
> To: widex@ietf.org
> Subject: [Widex] Updated Widex framework draft
>
> Hi, 
> Updated version of the Widex framework draft available at 
> http://www.kolumbus.fi/vlad.stirbu/draft-stirbu-widex-framework-01.txt. 
> It will be available shortly also in the IETF drafts repository.
> 
> Vlad

_______________________________________________
Widex mailing list
Widex@ietf.org
https://www1.ietf.org/mailman/listinfo/widex