Hi guys,
Great work, thanks for cool stuff!
The question is -- when do you plan to release a patch for the module that will work with Dojo 0.9? The reason I'm asking is that we experience some problems with Dojo 0.4 support of Safari 2.
We are in contact with Alex Russel and he says that we need to upgrade to the latest version of Dojo to get it working on older versions of Safari.
If you are not going to have that patch soon, we will start developing it.
Thanks,
Eugene,
TripOvation, Inc.
Dojo Toolkit Module v2.0 is coming very soon
Sorry for the extremely late reply. You bet, v2.0 is nearly complete and is designed specifically for Dojo 0.9. It's very close to completion. You can check out the code from http://svn.cb1inc.com/dojo-module!
v0.9
Any word on the update? Is the dojo-0.9 module code in the trunk directory? Under tags, I just see 1.0 and 1.2.
Latest Dojo Toolkit Module and Dojo 0.9
The latest code in http://svn.cb1inc.com/dojo-module/trunk does work with Dojo 0.9, but there are a couple things left that I'm finishing up. The code in trunk is not production ready, but most of it does work. I hope to wrapping things up very, very soon, so stay tuned!
Dojo module support v0.9
Hi,
I wanted to thank you for starting this project. Using Dojo on Drupal is a great idea.
I downloaded the SVN and tried out the module which worked fine, except some path problems I had (probably due to my install - Should be made clear later). Nevermind these details that took me 5 minutes to fix, now I'm into further developments and hacks.
1 - I was wondering why loading Dojo on every page when we can define a profile to specify the visibility, ie. on which page it should load?
2 - I noticed the theme chosen in the profile is not loaded and only the Tundra theme is loaded by default. That's another thing I'm going to change.
Please let me know what you think of these 2 points. I'm interested in knowing the spirit with which you developed this module and if your ideas in the first place match my current ideas.
Thanks, Dave.
RE: Dojo module support v0.9
I'm curious what path issues you encountered. I tested both with clean URLs and without and resolved those issues. If you are running the server on Windows, then that makes sense.
So, the whole idea behind build profiles was so we could have Dojo 0.4.3 on one page and Dojo 0.9.0 on another. This was before I realized that 0.4.3 and 0.9.0 are very, very different and that I wasn't going to be able to easily support both. Another nice thing from the build profiles was you could have a custom build for authenticated developers or enable debugging.
Originally, Dojo was not loaded on every page, but then it just made sense to load it on every page because A) the Dojo.js gets (hopefully) cached anyways, B) it slow and painful to maintain which pages a build profile should be applied, and C) laziness. With Dojo core loaded on each page, you didn't need to do anything special when using Dojo in a block, theme, module, or content.
The Dijit theme is separate from the Drupal theme. You specify the name of the Dijit theme on the build profile, then when the page loads, some script will set the body's class to Dijit's theme. As of right now, Dijit comes with 3 themes: Tundra, Noir, and Soria. Out of the box, this only affects the rich text editor.
This module was developed A) to make Drupal cooler and B) for the Dojo guys. dojotoolkit.org uses Drupal and this module. Anyways, there are too many issues with Drupal, so I am writing a new CMS that's built on Dojo. This means that eventually, I will stop using Drupal along with the development of the Dojo Toolkit Module.
Post new comment