Enough with all the widget specifications already!!

After what feels like a cascade of widget specifications (iWidget, Google Gadget, Wookie) the World Wide Web Consortium (W3C) is working on a widget specification to unite them all. If you’re interested in stuff like this I recommend this developerWorks article (W3C widget configuration and packaging (Learn about the candidate specification for W3C widgets)).

Good thing is that we’re still talking JavaScript, CSS and HTML so existing widgets should be pretty easy to port if need be.

2 thoughts on “Enough with all the widget specifications already!!”

  1. As long as we keep Microsoft the hell away from it!

    I had heard that Notes widgets and Google Gadgets are very transferrable — is that true?


  2. Don’t know of a "Notes widget"-specification per say but you might mean iWidgets?! iWidgets is what’s used in Lotus Connections and other IBM products. As to being transferable I think so. As a widget developer you normally write the code in JavaScript and get a handle to a HTML DIV-element that’s the center of your world and you manipulate using DOM methods. Whether it’s specification A, B or C they all work the same way – the difference is in the plumbing and naming.


Comments are closed.