Login Register

3D2: Dojo Developer Day #2

Things have been a little quiet around here since 0.4.1 flew the coop, but don't let that fool you. Despite the holiday interruptions the Dojo community has been in the midst of several important discussions on the future of the Toolkit and the future of the Foundation. The time is coming to make the hard cuts and decisions about one-point-oh that can only really happen over beer, so I'm happy to announce the second Dojo Developer Day (aka: 3D2), Jan 12-13th in Mt. View CA. AOL is once again generously donating use of their facility and has promised to keep us from starving. Unlike the previous Developer Day, this one is not aligned with a conference and isn't really an event for users. Instead, project contributors and participants are going to pow-wow for two full days to hash out the future of Dojo and start on the work that's going to make it happen. Event details are in the wiki, and an RSVP to <rsvp at dojotoolkit.org> is greatly appreciated. If you need a place to stay, a ride to the event, or some other sort of help getting to 3D2, let us know when you RSVP. Update: I almost forgot! The day before 3D2 (Jan 11th), the Cometd project is going to be having a similar developer gathering at the 6Apart offices in San Francisco. Send word to the Cometd lists if you're going to be attending that one.

We have details on the

We have details on the Cometd Devleoper Day up on the cometd blog. http://cometd.vox.com/

[...] Work continues on

[...] Work continues on ensuring that 0.4.2 is the highest quality Dojo release to date, but major changes have also been quietly taking place. At last month’s 3D2 significant decisions were made about how to evolve the toolkit. First, Dojo 1.0 will ship this year. Secondly, we will be splitting the project up into 3 separate but coordinated efforts: dojo core, dijit, and dojox. Lastly, it was decided that a major backwards incompatible jump will be made for the next major release of Dojo. To date, we have always attempted to provide at least one full point revision’s warning regarding APIs that were changing or being removed. WHile this has allowed attentive users to easily stay abreast of how to port their applications between Dojo versions, it has contributed to significant amounts of cruft in the core of the toolkit. This cruft is going to be removed wholesale in the next major revisions, Dojo 0.9, and no in-code deprecation warnings will be provided. Instead, a full and complete porting guide for 0.4.x users will be created. The extent of the planned changes make back-compat shims unrealistic. [...]