Since this is supposed to be the "Midterm Evaluation Period" and "Coding Phase II" starts on Tuesday, I've been taking it easy this past week. However, I haven't completely stopped working on my project; there are two new effects. Nothing to spectacular, just a wipe version of the previous "shear" effect ("pinwheel" was the best name I could think of; suggestions are welcome), and an effect where pieces simply fade out. The demo page is here.

Since my last update, I've made the demo page more verbose and created a "shear" effect that, once again, splits the element into rows and/or columns and slides them in alternating directions, with an optional progressive or random delay between each piece's animation.

With the successful completion of the explode effect, I decided to build on the code used to split the node into pieces. I split the code in half and thus created a new generic function, dojox.fx._split that returns an animation object that splits the node into args.rows and args.columns and applies args.pieceAnimation() to each piece. This function takes the piece, its x and y location in the grid of pieces, and the dojo.coords of the original node as arguments and returns either an animation object or an array of animation objects to be combined.

I created a nice animation effect that splits the element into an arbitrary number of rows and columns, then sends them flying away from the element's center. The user can specify whether or not the pieces fade out as they move, and whether or not the distance and duration of each piece's animation should be randomized.

The effect is accomplished by cloning the node once for each piece and combining each piece's animation together. The original node's opacity is set to zero onPlay.

They say imitation is the most sincere form of flattery, and I agree. I had the pleasure of running an experiment writing an identical widget in Dojo, jQuery, and Prototype, and naturally ended up at the script.aculo.us website. Its one of those elegantly simple involving websites, where even if

Hi All,

I have noticed the following behaviour when using the dojo.fx.chain animation and connecting to its onEnd event.

What I would like to do is have a couple of animations run one after the other, then when all have finished, call another function, below is my contrived example;

Hello!

We are currently developing a multiframe dojo mobile windowing desktop (basically, they are iFrames contained inside dojo.dnd and dojo.fx - supporting divs).

When you move the mouse pointer around, the iFrame scrollbars grow and shrink, or scroll up and down freely. Does anyone know how to change this behavior so that they keep static? Thank you in advance.

Red!