W3C home > Mailing lists > Public > www-svg@w3.org > July 2004

RE: The 'hanlder' element

From: James Bentley <James.Bentley@guideworkstv.com>
Date: Tue, 20 Jul 2004 11:33:12 -0600
Message-ID: <687B7858C99ED711B87B00B0D0D1C922C0FB41@LAMBIC>
To: 'Dean Jackson' <dean@w3.org>
Cc: 'Cameron McCormack' <cam-www-svg@aka.mcc.id.au>, "'www-svg@w3.org'" <www-svg@w3.org>

That's great but it doesn't cover non-character key presses, and it
doesn't address the issue of not using script. It would be nice if the
handler could encapsulate SVG, or the SMIL provided by Cameron.
If it encapsulated the SMIL, we could set the 'display' attribute, of
some group, when the event occurs. If it encapsulated SVG, we could
interpret the SVG when the event occurs. In the example below, I
may be able to write '<set begin="r.text" ...>', or something 
similar, but that would, I assume, capture all character input events.
It would be nice to bind the handler to a specific key event - even
non-character key events.

Essentially, I'm working in a serverly constrained environment where
scripting should be minimized, if not eliminated. If necessary, perhaps
we can support extended 'handler' types for SVG Tiny, only. Also, I don't
have a 'standard' input device, so key codes are not necessarily character,
don't always have the same meaning as on the QWERTY keyboard.

Ultimately, I believe the W3 will need to consider another profile to meet
the needs of my environment - a television profile. While Tiny is, for the
most part, implementable, it is too constrained. However, Basic is not
constrained enough for some low-end platforms (a conversation for another
time, I suppose).

-----Original Message-----
From: Dean Jackson [mailto:dean@w3.org]
Sent: Tuesday, July 20, 2004 11:06 AM
To: James Bentley
Cc: 'Cameron McCormack'; 'www-svg@w3.org'
Subject: Re: The 'hanlder' element

On Tue 20 Jul 2004, James Bentley wrote:

> That's a wonderful example, but, how would
> I bind it to a key event? Key events were
> introduced with XML Events.

You should really see the DOM 3 Events spec for

<handler ev:event="textInput">

>  I assumed the
> 'handler' element was created to integrate with
> XML Events.  If there is another way, I'd love
> to use it.
> Thanks.
> -----Original Message-----
> From: Cameron McCormack [mailto:cam-www-svg@aka.mcc.id.au]
> Sent: Friday, July 16, 2004 8:32 PM
> To: 'www-svg@w3.org'
> Subject: Re: The 'hanlder' element
> Hi James.
> James Bentley:
> > Would it be possible for a 'handler' to contain
> > and/or reference SVG content? The 'handler'
> > can specify a type of 'image/svg'. The contents
> > of the 'handler' would not be rendered until
> > the event, to which it is bound, occurs.
> I think that this could be done without changing the handler element,
> just by using SMIL to set the display property of a g element on the
> event you are interested in, for example:
>   <g display="none">
>     <!-- stuff to display on rect click -->
>     <set begin="r.click" attributeName="display" to="inline"/>
>   </g>
>   <rect id="r" width="10" height="10"/>
> Cameron
> -- 
> Cameron McCormack
> |  Web: http://mcc.id.au/
> |  ICQ: 26955922
Received on Tuesday, 20 July 2004 13:44:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:54:02 UTC