Dojo 1.2 will sport a nice API standardization for widgets. Widget.attr() is now the standard interface for setting/getting all widget attributes. For example:
// set title
myTitlePane.attr('title', 'hello world');
// find out if button is disabled
var dis = myButton.attr('disabled');
// set to the current date
myDateTextBox.attr('value', new Date());
It also supports a hash API like dojo.attr(), for setting multiple attributes:
myInput.attr({ tabIndex: 3, disabled: true, value: 'hi'});
Hi dojoers,
I am sure you got question what the heck is Dojo Furniture! Is Dojo changing its profession from javascript framework to furniture wholesaler? Well allow me to explain about it! Since my project proposal, I promised to give many things from code library, documentation and couple tests but *hrmmmm* something missing... then I purposed to have real world example in the list... Then there you go! I called it Dojo Furniture!
In addition to improving the text-splitting process, I created text versions of all but the last two "split" effects. To make up for the two effects I'm leaving out of the text effects, I came up with two new text effects. The first one (which is already pretty much complete) is a simple typewriter effect. It is not as customizable as the others, but is more tailored to achieve expected results. The other will be much more complicated.
Last week I added an unprecedented enhancement to the Dojo Object Harness (DOH) unit test framework, called doh.robot, scheduled to appear in Dojo 1.2. This enhancement adds an API to DOH that enables testers to automate their UI tests using real, cross-platform, system-level input events. In this post, I'm going to explain the enormous value-add of this enhancement in terms of unit and accessibility testing, and how to get started using this new API.
Today, Alex Russell closed the voting on the unanimous selection of a new Dojo Project Lead: me. It is with great pleasure that I write this brief note announcing the change, and look forward to serving the Dojo Toolkit and it's developers, users, and contributors. Both Alex and I have both posted some notes about the change. Thanks to everyone for their vote of confidence, and to Alex, who has dutifully served in this position for the past four years.
Hi dojoers,
In this opportunity, I would like to share my status update for gfx project with Dojo.
What was achieved lately?
- Revised test page.
Yes, a new cool looking page! It cut around 40% loading time from previous version (because of dijit dependancy), which from ~40 seconds become ~20 seconds.
- Camera
After trying unsuccesssfully for about a week to split a block of text into spans of words or letters, I finally followed the KISS rule and made something work. Originally, I was trying to recurse through every non-textNode and split the textNodes inside their parentNodes so any HTML inside the supplied node would remain intact. However, some HTML "features" (and lack of sleep) prevented all my attempts from providing me with what I thought would be a simple, robust, and efficient bit of magic.
I recently had a chance to sit down with Jayant Sai of ESRI to discuss their new Dojo-based GIS JavaScript API.
DS: Let's start at the beginning. What is ESRI?
The Monday portion of Dojo Developer Day Boston is now "sold out" (can free events sell out?) after just a few short weeks since the announcements!
There's a waiting list in case we get more space from the Ajax Experience, so do sign-up if you are interested. And the Committer and Contributor Day on Sunday still has plenty of seats and is also free.
Hi dojoers,
I would like to introduce you a new page for GFX 2.0... Now the new page focuses on the display of the canvas (it is located in the middle of the page and it is very big). How about the other (console and help page)? Dont worry, I made such a way when you need them, all you should do just go to bottom left to click either console or help page... And a draggable panel will be shown! In terms of loading, it cuts the loading time around 50% (from 40 seconds to 20 seconds), it is due to I am using a lot of dijit component... Unfortunately, the only problem of new page is performance downgrade since the canvas size is bigger (take more time to draw)... Please go to this page to see the new look of GFX 2.0 page.
