Hi,
I have read the the following document:
Widgets 1.0: Packaging and Configuration
W3C Candidate Recommendation 14 July 2009
http://dev.w3.org/2006/waf/widgets/
Please find below my suggestions.
Best regards,
Oguz Kupusoglu
Suggestion 1
Using a separate XML file named
Hi Dom,
It's fairly straightforward to extract the WebIDLs from W3C specs (e.g.
using XSLT), and I can also imagining annotating these with doxygen
comments by more auto-extracting work.
My checkers also tries to verify that the Web IDL and documentation match
semantically.
For this we need a
On Jul 17, 2009, at 15:04 , Marcin Hanclik wrote:
Is it possible that BONDI specs, together with widl format
specification are taken as basis in DAP?
Who, when and how takes this decision?
That would be a decision for the DAP WG to take, once there are enough
participants signed up (it
On Thursday, July 16, 2009 4:46 PM, Nikunj R. Mehta wrote:
On Jul 16, 2009, at 3:31 PM, Adrian Bateman wrote:
I agree with Jonas and I'd like to understand the expected use cases
better too. I think I get the point that making the network access
seamless regardless of whether there is
Hi everyone,
Wookie - which I demonstrated at the Paris F2F - has just been
accepted into the Apache Incubator.
Wookie implements the W3C Widgets draft specifications as a web
service supporting web applications, in a manner similar to (and
compatible with) Apache Shindig for OpenSocial
On Thu, Jul 16, 2009 at 4:17 PM, Nikunj R. Mehtanikunj.me...@oracle.com wrote:
On Jul 16, 2009, at 3:54 PM, Jonas Sicking wrote:
I do understand how Interceptor/DataCache works. And understand that
it's seamless and can (based on a decision made by the browser)
seamlessly intercept both XHR
On Friday, July 17, 2009, Scott Wilson scott.bradley.wil...@gmail.com wrote:
Hi everyone,
Wookie - which I demonstrated at the Paris F2F - has just been accepted into
the Apache Incubator.
congratulations!
Wookie implements the W3C Widgets draft specifications as a web service
