NOTE: This post is very out of date. For more up to date information about RESTful JSON in Dojo applications there are a number of more recent tutorials are available, such as the Dojo Store introduction, as well as tutorials demonstrating store-driven grids and trees, among others.

Since Dojo 1.1 was released a week ago, several outlets have published articles: Dojo 1.1 Refines Ajax Development – Features SitePen’s Peter Higgins and Alex Russell with their thoughts on Dojo 1.1, and a comprehensive summary of what’s new with the 1.1 release Dojo Stabilizes Open Source Ajax Toolkit – Mentions Dojo backing from IBM, Sun, AOL and Nexaweb, and gives a summary of IBM and Nexaweb’s opinions of Dojo 1.1 Dojo Encourages Ajax Innovation – The facts aren’t particularly solid in this one, but it’s still nice to see Dojo get mentioned Adobe AIR for Linux – Mentions Dojo working on AIR What’s new with Google Gears – Includes a short section about Dojo Storage and the Gears Dojo data provider. .

Mobile application development has many challenges. The announcement of Google Gears on Mobile Devices will help solve the problems of network connectivity, network latency, and limited bandwidth.

This is it folks! This is the last week of dev for Dojo Offline until we pop the Dojo Offline beta out the door, either later this week or on Monday, April 16th. Last week we finished the Windows installer for Dojo Offline.

We finished a bunch of big tasks last week, mostly having to do with fit and finish and our installers: * The Moxie demo for Dojo Offline used to take too long to load — it was loading about 27 resources on page load — we optimized this to about 3 resources on page load drastically improving page load time.* We created about 80% of a Windows installer using an open source toolkit from Microsoft called WiX. Unfortunately, WiXturns out to make easy things hard and hard things close to impossible, trying to turn XML into a programming language.

We’re almost there! Here’s a laundry list of some of the code checkins from the last week: * We now provide a way to give a ‘magic’ domain name that will resolve to the localhost to help in testing in scenarios where the developer is running both the client and the server on the same machine. Polipo, our local proxy, doesn’t read and parse your hosts.conf file for local domain names or use the platform’s standard gethostbyname function; instead, it rolls its own DNS communication for various reliability and performance reasons, which means that it bypasses the hosts.conf file.

Last week we did lots and lots of coding on the local proxy for Dojo Offline. Here’s a laundry list of some of the code checkins and QA fixes: * Moxie had an encoding bug related to new lines being incorrectly serialized during the Dojo Offline syncing process — fixed * Polipo, our local proxy, was modified so that if it is online and a network error occurs, either from DNS, talking to a server, etc., we automatically ‘fault’, move offline, and attempt to replay the request against our local cache.

Development was a bit slow last week since I was at Microsoft for a few days at their research laboraties and TechFest, and I gave a keynote at Yahoo on Thursday titled “Inventing the Future”. The video of the keynote should be available online this week.

Someone managed to upload a document that broke Moxie — I’ve removed this document from the Moxie database and cleaned up most of the test docs people added to Moxie, leaving just a few. Go ahead and give Moxie + Dojo Offline a try if you haven’t before..

Sorry about getting this up a little late in the day; I’m actually in Redmond, Washington right now to attend a Microsoft research event at their R&D labs. I just got situated at my hotel and found a WiFi network to work from to start hacking on code and post this status report.

Instead of doing a status report this week I have created a screencast and blog post: Screencast of Dojo Offline + Demo + Release Download. .

The JavaScript layer for Dojo Offline, including the Moxie demo, were brought to functional completion. This means we have syncing working, including local data storage — Moxie now illustrates and shows both.

Every week we will be sending out a status report on the Dojo Offline Toolkit project to keep folks abreast of what we have accomplished the last week and what is planned for the week ahead. Last week the focus was on syncing and local data storage.

Every week we will be sending out a status report on the Dojo Offline Toolkit project to keep folks abreast of what we have accomplished the last week and what is planned for the week ahead. We finished the UI portion of the Dojo Offline Widget, blogged it, and put a demo release up.

Every week we will be sending out a status report on the Dojo Offline Toolkit project to keep folks abreast of what we have accomplished the last week and what is planned for the week ahead. After a bunch of thought to ensure an easy-to-use and powerful API, we blogged what the Dojo Offline API will look like.

Every week we will be sending out a status report on the Dojo Offline Toolkit project to keep folks abreast of what we have accomplished the last week and what is planned for the week ahead. The big task last week was finishing the Dojo Offline API.

Every week we will be sending out a status report on the Dojo Offline Toolkit project to keep folks abreast of what we have accomplished the last week and what is planned for the week ahead. The big task last week was finishing mockups of what potential offline-enabled web applications might look like.