Dojo Toolkit

The animation framework in Dojo is very flexible, but because of that flexibility, using it is not a trivial task for the common web programmer. The animation system works well for the JavaScript-savvy, but what if a Dojo beginner wants to add a ... [More] simple animated effect to an element on the page? What if he wants to make that animation toggle? Most JavaScript animation systems because of their modularity and flexibility. There are already tickets on this topic, and I intend to solve the problem of "stale values" and any related conflicts between two or more animations acting simultaneously on one object. Right now, I'm still getting familiar with the Dojo framework and community. Since the quarter doesn't end until June 5, I'll be balancing school and this project for awhile, but I look forward to overcoming these challenges, since that's what makes coding so much fun! [Less]

Hi guys, my name is Jon and I'll be working on giving dojo a stronger foothold in the rails community for my summer of code project. The project I'm working on is called d-rails, and its goal is to make it easy for rails guys to quickly get rolling ... [More] with dojo and add rich client-side functionality to their applications with minimal effort. I know there are probably more than a few rails users out there in our community, and I'd LOVE to any and all ideas you have for the project. Shoot me an email, jmoeller (at gmail), and I'll happily take your suggestions with open ears. Anyway, SoC officially kicks off in 1 week, so stay tuned for updates. [Less]

Hi all, I was testing something interesting fact... Maybe you are JS-Expert who likes to use Array a lot! I hope after reading my blog... You changed your coding to use less Array... Why? Because in my comparison test, Array is slower than Object in ... [More] the case if you can substitute Array with Object. First at first, Please go to Test page to see the timing comparison (Careful, this may take 20 seconds to do, it will freeze your browser) between using Array and Object. In my computer, surprisingly it could cut your performance ranged from 30-50%... What a shock! Once again, try to organize such a way so that you dont ever need Array... This test is purposed for my rendering data for GFX 2.0 because I need to have fast writing and reading data for object rendering. Well, I am open type person, if you think what I stated is wrong or just chit chat for improving the speed then feel free to put comments in! [Less]

Hi, my name is Andrey Popelo, I'm form Ukraine. This summer I will work on "Markup previews" project for Dojo. It is for people who use lightweight markup languages (like Markdown, Textile, etc) in their sites. The aim is to create a client-side ... [More] parser which will have an easy way to add different markup languages and an easy way to load them and use with dojo.editor and usual textarea nodes. So it will be handy to quickly preview what you wrote without sending any requests to the server. For example you can take a look at Showdown - a javascript port of Markdown. It is similar to what I intend to do. Also a reverse parser for each markup language will be created and integrated with dijit.Editor, so it would be able to produce data in selected markup language instead of HTML. This will allow to simplify the server side of the projects that will use this feature. My mentors are David Snopek and Robert Coup. It is my first experience in open-source development and is very interesting for me. Doing Google Summer of Code project for Dojo is a great way to start doing open-source! [Less]

The time when I was applying to GoSC for DOJO, of course it is important to do research around the project topics. At that time, my computer was very very old (it is 4 years old), whatever I do multitasking, it always sounds like giving up because of ... [More] too many things to do... LoL poor little box... Unfortunately, I couldnt see couple demo for Canvas3D in Firefox (simple,simple 2.0, kmzview, model view) and Opera (example, snake) since my VGA was so old (all canvas3d needs at least OpenGL1.5) but thanks to this project, I made decision to buy a "killer" box to assist this project! Hehe, I was really excited like a child gets new toys! After spent 5 hours building new computer, I am really amazed with my new computer speed! It is very very fast! Loading photoshop just couple secs, not like before couple minutes... Crazy!!! Now my performance is increased as well! Hahaha! No lag time anymore... [Less]

"Ciao" / "Grüezi" / "Hola" / Hello! I am excited with my first world-wide open source project so trying to greeting in many languages! Firstly, let me introduce myself, I am Robert (Robertus Harmawan Johansyah for full name). About the project, I am ... [More] contributing for GFX library in DOJO Toolkit, 3 dimension graphics in web is getting hot at the moment so we shall not let DOJO be getting behind! In nutshell, this project will enhance GFX 1.1 that already implemented such as adding Canvas3D from Firefox and Opera! Of course API unification will be taken in consideration! If you interested about what i am doing right now, I am studying Computer Science as final year in Macquarie University, Sydney. [Less]

Hello Planet Dojo! I'm Jeff Balogh, and I'm doing doing a Google Summer of Code project for Dojo this summer. I'm an undergrad at the University of Central Florida, with one more semester to go. I'm living in Toronto this summer and ... [More] working with the DrProject folks, so drop me a line if you're in the area. :) For this SoC, I'm creating a drag & drop form editor for Dojo. It's not intended to be a full-featured IDE; I want to make a fun, easy way to interact with Dojo and Dijit in the browser.. I'm planning to use a lot of the great work already available, like dijit.form for the widgets and dojo.dnd for all the fancy moves. This project will provide a way for dojo users to embed dynamic, customizable forms in their apps, and I'm hoping it can also be a nice introduction to using dojo for newcomers. Currently, the plan is to have a drawing area where you drag and style your form elements, an HTML source editor for twiddling with all the little details, and a high-level property editor that exposes the important aspects of each element, like custom validation and callback code. My mentors are Peter Svensson, Liu Cougar, and Greg Wilson. This is my first big javascript project, so tips and suggestions are very welcome! I'm looking forward to a fun and illuminating summer. [Less]

The latest Dojo release includes critical but low-risk patches to version 1.1.0, plus localizations to bring the list of languages supported by Dojo to 22. Dojo 1.1.1 is a drop-in replacement for Dojo 1.1. Because this is the release where the ... [More] localizations landed, and because of the critical bug fixes, it is recommended that all 1.1.0 users upgrade to 1.1.1 immediately. Here are the highlights: New localizations donated by IBM -- now 24 in total, including English and two variants each of Chinese and Portuguese -- to accompany cultural support of hundreds of locales by dojo.cldr. Dojo mini, a new packaging of Dojo source weighing in at just over 1M. The same Dojo, with no tests, no utilities, no demos, just the unoptimized source code, making it easier than ever to download and explore Dojo. Bug fixes -- 26 tickets fixed ranging from look and feel tweaks to loader and cross domain (xd) loader bug fixes to severe bugs like one in dojox.cometd [Less]

I had the chance to talk about Dojo at JavaOne last week, and one of the attendees, Kenn Thisted, was nice enough to create OpenSearch plugins for dojotoolkit.org and api.dojotoolkit.org: http://mycroft.mozdev.org/download.html?name=dojo If you are ... [More] using Firefox 2 or 3, or Internet Explorer 7, you can easily add Dojo search to your browser's search bar. [Less]

This is important, so please read on ... A long time ago, I proposed a patch to Dojo, adding in a little gem of JavaScript to each and every test case in Dijit: _testCommon.js ... it was magic. It loaded whichever theme we chose safely, and set a ... [More] class name on the body tag, just as dijit themeing requires. It also allowed us to test pseudo-a11y mode, and genuine right-to-left mode for each of the widgets at our whim. This kind of testing is important to Dijit, and as seen by the "matrix", is extensive. We have to test at a _minimum_ each of the "tundra" tests in all of dijit's supported browsers: Internet Explorer 6 7, FireFox 2 (and FF3 coming), Safari 3 (ideally both MacOS and Windows variants, as they differ some), as well as fun testing on "technically unsupported" browsers like the WebKit in the iPhone, Opera 9 (which Dijit mostly works with, just not guaranteed) ... It's a huge matrix. _testCommon.js helped with that some, but did something entirely anti-Dojo: magic. This is my plea: grep your html. If you are inadvertently loading in _testCommon.js via a script tag, remove it. It is 2k of JavaScript entirely unnecessary in any production environment, or any website whatsoever. We use it as a test mechanism, though it introduces magic that causes a lot of confusion, especially among new users of Dojo. So go. grep your html. If you have a reference to _testCommon.js, remove it. I'll wait. If something broke, you've come back. Taking the "magic" away from our test-matrix exposes the downside of me having introduced testCommon in the first place. Again with the "there is no Dojo magic here", _testCommon.js breaks two (or more) fundamental Dijit paradigms: you need a class="themeName" somewhere! The default Dijit theme is called "tundra" ... It is done entirely based on CSS, and uses a selector ".tundra" to prefix all the class definitions. _testCommon.js was adding the appropriate class name to the body tag, the most top level node available. You can technically utilize CSS inheritance / cascading, and simply put a class="themeName" around your widget dom, but some things that are direct descendant of body (Dialog, Tooltip, Popups) need the class on the body. the safest way: <body class="tundra"><!-- my page --></body> you need to load the theme.css! each theme available has a folder in dijit/themes/ based on the theme name. To load the "tundra" theme, you need the file dijit/themes/tundra/tundra.css ... There is an opportunity for optimization there, but currently the only supported theme mechanism is to pull in the theme "rollup" of all the available components. _testCommon.js was using document.write (of all things) to include the link tags necessary to load the theme files. This is "magic", and also left our test cases without any useful CSS being loaded. This "magic" also probably introduced a race condition in several widgets who relied on the CSS being loaded in order to size properly. It is our recommendation you load theme theme css file before loading dojo.js to limit risk of hitting this race condition. the recommended way: <head>         <link rel="stylesheet" href="js/dijit/themes/tundra/tundra.css" />         <script src="js/dojo/dojo.js" type="text/javascript"></script> </head> <body class="tundra"><!-- your markup --></body> People use our tests to learn, to copy, to start. Most of our tests are copies of previous tests, modified for some new widget. Having this "magic" _testCommon.js in each and every page propagated throughout all of dijit, some of dojox, and into user pages (I'm no exception to this copy/pasting) ... The Above "skeleton" page is all that is needed to use Dijit. Add another script tag for all your dojo.requires(), and flood the body with markup -- you are on your way. All this said, _testCommon.js is _still_ in every test file! Ignore it, don't use it, remove it from your pages still ... We still use it to test Nihilo and Soria themes, as well as do the automated magic to set Right-to-Left mode and pseudo-a11y mode. It is still very important for us to test all these modes, and we like having the helper. Though now _testCommon.js does nothing magic until you force it, and the default theme and configuration is reflected throughout all the dijit and dojox tests. I hope this clarifies some stuff for everyone. [Less]