From a technological perspective, the grid is quite robust, offering a number of features, including support for large datasets, column manipulation, data independence, and editing of cell data.
- Developers begin using, and adopting, the libraries as their development platform of choice.
- Commercial widgets are built on top of the platform.
- A commercial widget is freed, and becomes Open Source.
Now, obviously, the assumed effect on Open Web development that this particular widget has will vary greatly depending on whose asked. In the opinions of the Dojo Foundation (and the sponsors), it’s very important. Asking users of another library, however, and you’ll get a significantly different story. That’s the one piece of this equation that particularly grates with me, especially coming from a vendor-neutral organization like Mozilla. The support of this widget is actually saying three things: 1) This is a high quality piece of code 2) Having this code open for all to use will better the web and 3) That you should be using the Dojo Toolkit for your development (since it’s required in order for the widget to work).
I think an optimal approach would’ve been one with an extra stipulation: The widget would be freed both ownership-wise and dependency-wise. It’s definitely possible, and the recent work that the Ext library has done proves that it can happen.
Side discussion: Apparently dojo 1.0 has dropped support for Safari 2? Bwahh? How is it even possible to drop support for a browser release that is still its current version? Trust me, once Safari 3 goes gold, I’m dropping Safari 2 support from jQuery like there’s no tomorrow, I hate that browser with the fury of a thousand angry web developers, but until that time – too soon?
Update: I was asked to clarify a couple things: I’m not expecting Dojo to go out of their way to port the widget to other platforms (or even to free it from their own), I’d just think that Mozilla should make a strong attempt to generate codebase-neutral code. Granted, that may not be always possible – in the case of the Dojo Grid there’s a significant amount of functionality tying it back to Dojo core.
Also, as far as the dropping of Safari 2 support goes, it was clarified to me that the Dojo 1.0 release will be at about the same time as OS X Leopard, thus, Safari 2 will already be by the wayside at that point. Noted – and approved of!