Dojo

At Freelock, we're big fans of the Dojo Toolkit. It's a Javascript library for providing data-backed widgets in web applications, on-the-fly graphing, animations, and much more. As we move more of our web applications to the browser, we keep pushing the edge of what's available, and sometimes hit bugs in Dojo itself. So as I mentioned in a previous post, I often find myself teetering between the most recent stable releases and the tip of Dojo development. And I think we have the best way of managing these changes of anyone.

So once more, development on an internal project hit a stumbling block. The latest release of Dojo, 1.3.1, has some bug fixes I'd like to use, and in general I like to keep my main project working with the newest dojo releases. But 1.3.1 introduced a new security constraint that basically escaped all the html that I was showing in a grid control. Suddenly, instead of rich text, I get HTML markup!!!

We're big fans of the Dojo Toolkit, a Javascript framework that allows you to build rich Internet applications right in the browser. We're impressed with the power and flexibility, and have built several big applications on it in addition to solving lots of small tasks.

We've also used other Javascript libraries, including JQuery, Prototype, Scriptaculous, and several others.