Daniel Eneström

When I first discovered the Spry Ajax framework by Adobe I was jubilant. It gives my HTML applications a similar functionality to the Flex applications I so love. For those who haven’t yet discovered Spry I can tell you it’s a collection of APIs, tools and widgets that make it easier for you to implement ajax functionality on your web site. Many of the widgets are useless (to me) but in general it’s excellent. You can more or less just associate a set of graphics (like rows in a table) with an array (imported externally or built into the page) and the graphics repeat themselves according to the arrays rows. You have to try it to understand its brilliance.

The downside
The documentation is very thorough, but very badly structured. As an example the API documentation does not include the events that can be “listened to” by observers. One has to browse through the Overview document and make much use of the “find” feature of the browser (thank god I’m using Firefox) to find such things.
Another problem is that it sometimes just don’t work. The framework has a really nifty debugging tool built into it, but sometimes errors don’t fire. Simply nothing happens and that makes me furious! I’ve been trying to solve such a problem all day today, but simply can’t find what’s wrong. Firebug (a must-have tool) tells me my dataset has all the data. If I look through the page’s DOM I can find the object there, with all the data in it, but the {labels} I have used in the code are replaced by… nothing…

I’m tired…