I moved to another IT company as a web developers in Spring in 2010, and the people here (including me) are using JQuery too.

Kitty

動物基地貓貓

I haven’t used any framework other than Mootools, but constantly evaluate the options that are available. Mootools is the fastest, most innovative, and technically superior to all the others. But it may not be for long; it has indeed grown stagnant and the recent 1.2 release may not be able to save it. As is, Mootools requires too much dependence upon OOP Javascript fundamentals for it be easily ingested by javascript neophytes (i.e. the vast majority of front-end developers).

The community is substandard. The developers of the framework itself are elitist by association to their egotistical, presumptuous, and prodigal young javascript leader, Valerio Proietti. Collectively, they spend too much time parrying with their own community over their lack of knowledge. I was banned from the forums for bringing up their lack of friendly acceptance, and suggesting an alternate approach to communicating with the public. I suppose you could reason I am disgruntled, but this assertion would not explain why I use MooTools exclusively.

Unfortunately, the project leaders’ insolence and terse contributions to documentation force you to piece together an education on Javascript over a period of months. The framework will flounder unless they take a corporate approach in presenting the framework to the public, build the MooTools brand, and build exhaustive documentation and resources for its potential users, regardless of their skill level.

Take the heretofore unheard-of Sproutcore as an example. Apple adopted it, and put it on the map. Yet still, it has professional appeal out of the gate. It isn’t logical for newcomers, but expect it to do right by its adopters after time is spent in the documentation.

There aint any trolls.

If you can post a few lines of code you wrote yourself, the feedback is good and helpful.

They are focused and clean – without any of that fluff that crowds others forums.
I think they do a fantastic job – and as a moo resource, i don’t think you could ask for much better.

When this Noob signed up – I sure wasn’t scared away.

peace.

Cholerics aside, mootools is clean and elegant and very well thought out. I do have some personal issues with it, though, for instance, it seems very DOM element centric (especially with the new DOM storage), thus we had to come up with a different solutuion to the same problem. However, the Moo way is certainly valid.

We have solved the UI library problem by writing our own comprehensive UI on top of Mootools, so we are going to stick with it for some time to come.

The release cycle is too slow. We are waiting for 1.2 since like, forever, and have even implemented a lot of stuff that is promised for the new version on our own, since we want to work with stable versions. It does not help that the blog is updated only every other month or so, and it is hard to get a sense of progress even when monitoring the Trac.

The most serious problem for me is the lack of tools, though. We are using Aptana, and NaturalDocs is not parsed for code completion. Also, Mootools’ class system does not go well with the outline view.
If the moo people could get one of their ranks to write tools, then this would be a major reason to stay on board.

You should check out the new iframe and Swiff classes in Mootools. Iframe tunneling and manipulation rocks and the Swiff class makes JS to flash translation a snap!

I looked at jQuery and it appears that Moo has all the same selectors except Moo compounds them into one method while jQuery singles them out like this:

Mootools ‘.inject’ has 4 options myElement.inject(el[, where]); you would put top, bottom, after, before in the ‘where’ place and that same method would do all 4.

with jQuery you have to memorize a bunch of individual methods like this:

$(“p”).insertAfter(“#foo”);

$(“p”).insertBefore(“#foo”);

$(“span”).appendTo(“#foo”);

$(“p”).prepend(“Hello “)

Why is it more clear to have 40 million little selectors separated and callable through a slew of different method arrangements when you could use simple text strings to indicate all of them in the same format and method. That seems counter intuitive and quite long-handed in my view.

An improvement would be a reassessment, a simple first time notice that “please look in the docs/google it before asking” – a lot of people don’t do it. A lot of people don’t know what they’re searching for, or even quite what the “real” question is. I understand that you don’t want to hold someone’s hand, but just because the main devs are on the site, doesn’t mean that other fans can’t assist the “dumb users” or “noobs” on the site.

I’m trying to branch back into jQuery – while still using mootools for the majority of my implementations, I recognize the need to be proficient in more than one framework when you work with clients who may all ready be utilizing existing frameworks, creating a barrier for those who focus on their “framework of choice.”

the site btw is
http://demos.mootools.net/Fx.Elements

Thanks in advance.