Re: Extension Mechanisms in Thot Libraries

> It would appear that to override or augment  default Thot behavior one
> modifies
> or provides an application schema to define before, replacement, and after
> methods
> for specific functions.
> 
> I have two questions about this:
> 
> 1) Can this application schema be modified on the fly on a per-document
> basis?
>      If not, can one do something equivalent on a document-by-document
> basis
>      (that is, modify default function behavior)?

  In Amaya-Java it is possible to add on the fly some specific Java code which
will be triggered upon the occurent of some event. Check for example
  w3c/amaya/applets/DemoContent.java
in the Amaya-Java sources.
 
> 2) Is there a point at which one can capture ALL events, and then decide if
> something
>      should be performed before, in lieu of, or after the default
> functions?

  I guess that the code triggering actions in the Thot library is scattered
in a large number of file, however the central dispatching point is in
  thotlib/dialogue/callback.c
There is no general dispatching of all events to some Java code since it
would probably be too slow (I didn't tried however).

Daniel
-- 
Daniel.Veillard@w3.org | MIT/LCS   Room NE43-344 | Today's Bookmarks :
Tel : +1 617 253 5884  | 545 Technology Square   | Linux, WWW, Java,
Fax : +1 617 258 5999  | Cambridge, MA 02139 USA | badminton, Kaffe,
http://www.w3.org/People/W3Cpeople.html#Veillard | HTTP-NG and Amaya.

Received on Tuesday, 20 January 1998 02:20:34 UTC