Agile Ajax

Why Does Scriptaculous Need Prototype?

I've been going through the Scriptaculous effects library in some detail. After grokking all there is to know about effects queues, I was left with one question: why does the effects library have a dependency on Prototype? The dependency could be removed with maybe two dozen lines of Javascript. So, why the dependency?

After having several other frameworks arm wrestle me for the $ identifier, I'd like to drop Prototype at the nearest corner.

Anyhow, I'm working on something involving Scriptaculous now that will likely make me the but of both jokes and death threats. Stay tuned.

Comments: 3 so far

  1. I’d be interested in knowing more!!

    Comment by Rey Bango, Tuesday, May 29, 2007 @ 9:50 am

  2. I’m not sure how much dependency there really is. If in fact there isn’t a lot of dependency it might be that since they were sort of written in tandem, they thought prototype might help a lot more than it needed to.

    Though I’m sure since the creators are also Rubyists, they’d probably say why don’t you just remove the dependencies yourself ;)

    Comment by Ben, Wednesday, May 30, 2007 @ 10:16 am

  3. Why did you choose scriptaculous over moofx? I’ve found moofx to be smaller and stabler (and not dependent on prototype).

    Comment by Matt Snider, Monday, June 4, 2007 @ 12:31 pm

Leave a comment

Powered by WP Hashcash

About Pathfinder

  • We design and build extraordinary applications for companies looking to make the next great idea a reality.
  • learn more

Topics

WordPress

Comments about this site: info@pathf.com