W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2012

[WebIDL] Representing functions that user code can call

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Fri, 07 Dec 2012 21:56:14 -0500
Message-ID: <50C2AC4E.10002@mit.edu>
To: public-webapps <public-webapps@w3.org>
We have a way to represent user functions that platform objects can 
call: callbacks.

But I don't think there's really a good way to represent functions that 
are not hanging off any particular object that user code can call.  Or 
can callbacks be used for that too?

Note that right now the web components spec is using callbacks for this, 
but they're not a great fit given how callback conversions between 
WebIDL and ES are defined...

What's really wanted for this sort of use case is something closer to 
how Constructors are defined: basically a standalone WebIDL operation, 
not hanging off any object.

Thoughts?

-Boris
Received on Saturday, 8 December 2012 02:56:43 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:56 GMT