Politics, Programming and Possibilities
12 May
I’ve just made public the source code to the javascript library I’ve been working on: yootools.
For those in the know, it’s obviously a take-off from mootools, an already great javascript library. As explained on the yootools website, however, we wanted to encourage a more friendly environment for questions and discussion as well as loosen up the requirements for including new code in the library. The result is yootools, or “your object oriented tools”.
We’ll have a forum and mailing list shortly.
14 Responses for "Announcing Yootools"
Is the only goal from your new library is to do drag and drop?
Kid
I think this is a wasted effort. If you aren’t happy with code acceptance or policies of mootools developers, you can just fork it. No need to redo the same thing.
This is the biggest plugin for mootools ever seen.
Wow.. so you’re like the Bill Gates of JavaScript?
Sad…
guys can i have a dollar?
Honestly though… why didn’t you just make a plugin providing your own custom drag and drop class for mootools. You’re using an old version of the mootools core with a crappy drag and drop plugin, just so you could add a custom event to the drag functionality?
dumb things make me sad somtimes… :/
i agree with youreanidiot… this is pretty lame man.
Are you sure that mootools has such an unfriendly community that would result in such a project? I’m sure there are better ways to contribute to mootools or the javascript framework community, but not copying a whole framework just to add your changes. I would be happy to announce and discuss your plugins and changes in the mootools forum … if they are for mootools and not in a ripped of mootools-like framework, that makes me kind-of sad.
I hope you are not serious with this project.
Greetings, A developer
Just found your ticket … if u think u have to start this project because your ticket was not accepted and so you needed to make changes in the mootools code … You can easily add the drag event to the current logic with extending the Drag.Move. I extend mootools every day in my projects, that’s how it works and not creating a new independent library.
I’m sure you understand that the devs and the contributors have to keep the mootools code basic. Mootools provides the coffee, u add sugar and milk … my favorite quote
. We talk about things we add and optimize them, and we also decide against some things. Adding for example your drag event would slow down dragging a lot and not many will use this event.
I’m done here now, please come to one’s senses.
thx man this is great!! mootools peple rnt friently the mootols peple are mean and expect me to know javascript and try to write my own codez be4 they help me n make my sitez for me ur site will be nicer
Holy mother… don’t everybody jump in to tear the guy apart… I might see his point now about “unfriendly” community.
But honestly, I don’t think there’s anything stopping you from forking mootools to roll the changes in that mootools wouldn’t accept. This way you can still contribute without having to rewrite same code and people learning another library.
Yes, this is definitely a code fork.
We’re not against anyone in the mootools community, we just didn’t feel well received. Technically we were very impressed with what we saw, but unfortunately technical merits are not the only part of a library–it has to have a democratic process for change, and preferrably the kind of developers who go out of their way to help when you’re trying to understand, improve upon, or fix the code.
We’ve made some significant changes to the core that we started with, and we’ll be continuing to make changes as we go. It’s past the point of no return for us, so yootools will be around for a while. Feel free to use, learn, and contribute if you are so inclined!
Best regards,
Duane
Update: I changed the little slogan to “friendly” instead of “friendlier”, since it wasn’t really my intention to try to put something else down. Seems like a gesture of good will was certainly due
Leave a reply