MooTools Tabs

http://dev.digitarald.de/tabs.html

Maybe we can use something like this (not sure if its released or under what licence) to replace the tabs in MODx so they all work under MooTools.

should be based on GPL/MIT I guess since it’s based on my code originally written for prototype and scriptaculous

What about http://webhost.bridgew.edu/etribou/layouts/rMenu/index.html?
It’s very crossbrowser friendly and isn’t that an important point on the next-gen MODx?
Javascript+AJAX etc. can be added and modifiying this menu is easy.
So a JSoff/CSSoff version is available for the IE/NS browser conservatives.

I don’t see any tabs on that page. Am I missing something?

scroll down , but it ain’t tabs. it’s just a better dropdown menu.

The dropdown menus are nice...but to be honest, I would like to see them written to utilize a javascript library like MooTools, jQuery, or the like. Reason is that it doesn’t make any sense to have to load yet another isolated javascript file. The idea behind javascript libraries like MooTools is that you can load just one simple, small library file that allows you to write and extend your own custom classes and functions to do what you want to do with much less code. Plus, with something like MooTools you can combine and chain together different functions to produce different effects and results. Imagine the same dropdown menus in MooTools. If you wanted to you could add a fade effect or even a slideout effect to the submenus. That’s not something you could easily do with a stand-alone script.

Jeff

In c|net’s mootorial they have a "layout widget" called tabswapper.js. The tabs created have fade transition etc. and look quite good (even if the demo’s orange color isn’t that great).
http://clientside.cnet.com/wiki/cnet-libraries/04-layoutwidgets (scroll to the bottom)

I’m a fan of effects, but you should keep on mind that the dropdownmenu I sent to you is the most accessible known to me at time. And accessibililty and standards compatibility with fallback if js or css is off is very important to me.

So maybe someone has the time to convert the HTML + JS code in the dropdownexample into a HTML+MooTools (or JQuery) version.

That would be great, and it’s really no big effort to do so.

Personally I wouldn’t want to use any menus that require a browser detection script to work (and for my money, the CSS Play menus are nicer and at least as accessible if not more so).

I don’t think that "Stu’s" menus are more crossbrowser friendly than the modified menu of "son of suckerfish" in the above link. A little unobstruvice JS would make that menu animate and fade like what ever..
You should know that Stu is experimenting and playing with css. And crossbrowser friendlyness is not his aim.

But that’s my opinion. If you’re more confortable in using TabsMenu (animated tabs menu), then use it, why not? hehe