Why not jquery ?

Quote from: rthrash at Mar 03, 2007, 11:45 AM

I had a long conversation with John yesterday.

sounds great - thanks for replying and not just closing or even deleting my post !

Quote from: rthrash at Mar 02, 2007, 04:52 PM

LOL ... indeed.

another typical conversation at mootools: http://forum.mootools.net/topic.php?id=1922

this is just very sad to say the least.

They have every right to run their project how they choose, and I have tremendous respect for the code they’ve put together. Just because we choose to run our project differently on the forums doesn’t make our way more-right than theirs. They’ve got very clear rules about what the goals of their project are and who they’d like to use it (their intended audience) and you have to respect that ... even if you don’t agree with the way they run it. It’s their project and they’re giving away their code freely, so you get what you pay for.

This is just my opinion so take it easy
I don’t like mootools, jquery is really better.
I studied both frameworks and I must say jqery is the winner for me, although mootools does it’s job also.
But jqery is technicaly better, better documented, more stable (that matters), and more cross-compatible.

I wish modx was using one framework only, to do all these web2 stuff and IE-fixing.
I mean jqery is extensible. WE could write extensions that make it CUSTOM and modx optimized.


--------moooOO---lol
Okay, I think I need to say this, if you don’t.
I used moofx from it’s beginning, then I heard that the dev was about to code a AJAX forum.
I was happy to hear that, but months later when I asked just a simple question (Can I get alpha/beta access, I’ll help you finding bugs.) I got flamed and that was not good. From that on I’d a strange feeling when using their "js".

I’ve to admit that there are some people, who really make very nice products and even for free.
But there are some black sheeps under those programers!
I don’t want to tell names, but I hate people acting arrogant and living like: "I’m admin you’re nothing!"
Be nice people and alle you get is nice! But beeing rude, makes things just worse.

Agree with you, their rudeness has a direct proportion with their reputation.I can’t even think them when mooflex has released.

ps: sorry for my english.

I don’t really mind MODx using mootools except that the documentation is kind of hard to understand (I guess I’m a JS-newbie). The important thing though is, like Xsss4hell says, that MODx uses one framework. It looks kind of messy with all the different libraries and it would also make it easier for plugin and module developers to use the "bundled" library instead of including them...

Another thing (which is JS related but not with jquery vs. mootools) is that the filebrowser used from the RTE (mcpuk) doesn’t play well with Safari – does anyone know how to fix this, or should I try to get the ImageManager to work instead?

Here is some ammo for the jQuery argument. http://ajaxian.com/archives/pquery-php-and-jquery

That does not seem to really have that much to do with Jquery, but with using php (and the sample has short open tags, at that) to generate javascript in the web page, replete with onclicks and other inline javascript. I think we should pay more attention to unobtrusive javascript libraries, if we make such "helper" frameworks. I suppose this is OK for quick-and-dirty AJAX stuff, but it looks to me like it would cause more problems than just learning to use the javascript library properly in the first place.

Well, its easier to update one PHP file when a javascript library has a major update than edit 100s of references IMHO.

Library updates shouldn’t break and change syntax in stable releases without loads of warning in advance. With that said, the pquery concept is very cool and very RoR-ish in the way they integrate with Proto/Script. Nice find.