In reverse engineering the Scriptaculous into GWTaculous, I’ve done a bit of spelunking and produced a few artifacts to explain Scriptaculous to myself. I thought I’d share one of them — a sequence diagram for Effects — in the hopes that someone else will find it useful. The diagram below isn’t complete — it doesn’t contain the event calls — and it doesn’t cover the Parallel effects, but it does give a decent overview for anyone trying to understand the Event lifecycle or someone trying to write their own effect.
Technorati Tags: ajax, scriptaculous, gwtaculous
Hi!
I’m always on the lookout for some interesting sequence diagrams, so I was excited to see yours above. I think it’s neat you’re using SD’s in your blog to explain what’s going on.
I’ve created Trace Modeler, a tool to quickly and easily create UML sequence diagrams (see http://www.tracemodeler.com). I’m especially interested in how sequence diagrams are used for web apps, because of their asynchronous nature.
Anyway, about the diagram : I’m a bit confused about the long activation of the Effect instance and don’t understand who calls some of the methods (for example, are ‘initialize’ and ‘cancel’ really self-calls?).
I’d like to help you get the diagram just right (and perhaps even expand it a bit) and in doing so learn a thing or two about SD’s in an AJAX context.
Let me know if you’re interested!
Best regards,
Yanic