W3C home > Mailing lists > Public > public-script-coord@w3.org > January to March 2010

RE: Java bindings generated from Web IDL

From: Travis Leithead <travil@microsoft.com>
Date: Wed, 27 Jan 2010 04:06:40 +0000
To: Shiki Okasaka <shiki@google.com>
CC: "public-script-coord@w3.org" <public-script-coord@w3.org>
Message-ID: <49142F02149340458FDD20841AD0AD564B32E903@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
Just curious because I also wrote a prototype parser/validator for the ECMAScript binding of WebIDL; written in JavaScript :-)

However, my tool builds a JavaScript OM taking into account ES5 bindings and has quite a few custom extended attributes. I hope it will be of interest when we start looking to updating WebIDL to use ES5 bindings...


From: Shiki Okasaka [shiki@google.com]
Sent: Tuesday, January 26, 2010 4:47 PM
To: Travis Leithead
Cc: public-script-coord@w3.org
Subject: Re: Java bindings generated from Web IDL

Hi Travis,

Yes, but it also generates the interface metadata in a string encoded
format in the generated C++ header file. This metadata can be used
with a language reflection runtime to invoke native methods from
ECMAScript, etc. (esjs ES3 interpreter does this.)

Please let me know if there is anything that could be generated from
Web IDL for ECMAScript binding. I'm happy to add it to the generators.

 - Shiki

On Tue, Jan 26, 2010 at 9:32 AM, Travis Leithead <travil@microsoft.com> wrote:
> Shiki, your tool just generates the Java/C++ bindings, not the ECMA bindings, correct?
> -----Original Message-----
> From: public-script-coord-request@w3.org [mailto:public-script-coord-request@w3.org] On Behalf Of Shiki Okasaka
> Sent: Tuesday, December 08, 2009 10:17 PM
> To: public-script-coord@w3.org
> Subject: Java bindings generated from Web IDL
> FYI, I've updated esidl Web IDL compiler to support Java in addition to C++.
> The Java files generated from Web IDL files are available at,
>  http://es-operating-system.googlecode.com/files/java-binding.zip
> The Web IDL files used for this are based on the following files and drafts:
> * Cameron's Web IDL-ized DOM Core, Events, etc.
>  http://lists.w3.org/Archives/Public/public-script-coord/2009OctDec/0022.html
> * HTML5
>  http://www.w3.org/TR/2009/WD-html5-20090825/Overview.html
> * CSSOM View
>  http://www.w3.org/TR/2009/WD-cssom-view-20090804/
> * File API
>  http://www.w3.org/TR/2009/WD-FileAPI-20091117/
> * XMLHttpRequest Level 2
>  http://www.w3.org/TR/2009/WD-XMLHttpRequest2-20090820/
> To make generated Java files mostly compatible with existing Java DOM bindings, I've manually added module names like 'html' to the IDL files for now. It's likely to be unnecessary in the future, though [0].
> To use esidl, please install bison, yacc, and ant, then follow the steps below:
> $ mkdir esidl
> $ svn checkout http://es-operating-system.googlecode.com/svn/trunk/esidl src $ mkdir obj $ cd obj $ ../src/configure $ make $ cd java $ ant
> This leaves .java and .class files under esidl/obj/java/org/w3c/.
> Hopefully this will also help spec editors to check their Web IDL definitions and keep them usable from Java. I'd appreciate any feedback.
> [0] http://lists.w3.org/Archives/Public/public-webapps/2009JulSep/0081.html
> Best,
>  - Shiki
Received on Wednesday, 27 January 2010 04:07:16 UTC

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