I noticed the other day that the dijit 1.1 priorities are up. Is there soon to be dojo 1.1 priorities posted? Any release dates for dojo 1.1? We're using 0.4 to do development right now due to portal (it's the only reason) due to the fact we'd need 1.0 and 0.4 to run concurrently without frames/iframes. We've hit a pivotal point in development that we could switch over to 1.0 if and only if the dojo namespace collision is addressed (ticket #4573). I'm just writing to see if there is any movement in that direction so we can plan to include 1.0 or to permanently continue on with 0.4.
Thanks
Martin
what functionality is still
what functionality is still colliding?
dijit 1.1 is the same as dojo 1.1 ... the three projects, currently, are on the same release cycle, and are shipped together for each release.
Right now you can't run 0.4 and 1.0
Right now you can't run 0.4 and 1.0 at the same time ticket #4573 was addressing this issue and it was pushed off to 1.1 (http://trac.dojotoolkit.org/ticket/4573) this ticket was last modified a month ago. Can't find it on http://trac.dojotoolkit.org/report/28 for Dijit 1.1 bugs.
10/28/07 04:37:20 changed by jburke ¶
* milestone changed from 1.0 to 1.1.
Pushing to 1.1. Not comfortable with this level of change so close to the 1.0 release.
I second your request on more information...
Is there a published roadmap or anything that the community can plan around? I opened ticket #4573 and while we are planning on using it for a new framework, I need some form of validation that existing implementations with 0.4 can continue to be supported. It's just too much to expect all code to change used throughout large organizations.
There appears to be a lot of work done to get this working, which is great! Can we expect to see this in the 1.1 release? If so, any high level dates for the release?
The multiversion support is
The multiversion support is expected to be in 1.1. The bug is still open because I want to fix an issue with debugAtAllCosts then document the usage. There are some caveats with the usage, mainly around using djConfig.debugAtAllCosts.
The rough schedule for Dojo 1.1 was to have it come out around the time of Firefox 3 so that we could verify that the release worked with Firefox 3. I think the general plan is to have 1.1 out first part of March.