MooFxDropMenu

I know that someone has already wrote a snippet that use MooFx javascript library, but I didn’t know that so i wrote my own.
After a time of testing and bug fixing I think it’s ready to be released, so here it is.
MooFxDropMenu ver 0.7 is a snippet to create menu with the accordion fx by MooFx javascript library.
You can download it here and some feedback will also be appreciated.
It’s possibile to see the snippet in action here www.aurora-onlus.it.
Bye

I have also done an accordian menu example using Wayfinder and scriptaculous + prototype. But I had forgot about it and have not put the instructions on anywhere yet.. but It uses just Wayfinder and it’s templating abilies. You can view it here (select Wayfinder from the menu).

I’ll put the info available soon.

I never used wayfinder. I don’t know how difficoult it could be to integrate MooFx with wayfinder. I’ll take a look as soon as possible.
Or maybe it will not be necessary if you release a snippet (or a full documentation) to let the people create accordion menu in a easy way with wayfinder without MooFx, only with scriptaculous+prototype.
By the way MooFx is just a 3kb library that extend scriptaculous+prototype creeating some effects.
Bye

It shouldn’t be any harder to do it with MooFX than what it was with scriptaculous+prototype. I just used those because they are shipped with modx. But 0.9.5 has MooTool too, so we should probably take a look at that. You will see info on how to set that scriptaculous menu up tomorrow.

Look here.

Nice tutorial. When I have time I take a look deeper in it and in wayfinder.
Maybe it should be better to create a multi graphic fx menu snippet the next time. Include this one.

Bye

what a nice tutorial but though I have a problem.

all installed correctly but then this:
"document.getElementById("visible") has no properties" --- init

the line:
var avis = document.getElementById(’visible’).parentNode.id+’-body’;

What happend? "the menu opens only if clicked the next item (i.e. you have first to click one item then the click on the next item opens the resp. item). All is quite slow

could you please help for I find this accordeon stuff quit usefull in some cases

Did you do every chunk etc exactly like it was in the tutorial?

What do you mean by:
Quote from: nos at Jan 02, 2007, 05:09 AM

"the menu opens only if clicked the next item (i.e. you have first to click one item then the click on the next item opens the resp. item).

In the accordian menu, it should work the way that you click the "headings" to see the links and when clicking the links under one section, it remains open.. I have it running on this page what I did when I wrote that tutorial. Only that page and the "Test child" has that template to see the accordian menu and Google maps + Main pages don’t have any childs.. But there you can see how it should work if you have done everything like it was in the tuto.. If that menu fails too, then it’s an browser issue and I don’t probably have enough energy to check into it..

Thanx for the answer. All that I found on the diffrent pages. I also have done similar menus with rico.js.

I don’t think it’s an issue of a browser (sorry). It looks more than that there is no item with the ID "visible" when opening the page the first time. Opening your exampl. there is one item "open" while with my page all items are closed and there is the error message (see above). So it seems it lacks one item to be defined as open ("visible"). (Certainly it would be finer all items could be closed too).

In the tutorial, the wfParentRowHere chunk has that id "visible" in the H3 tag. When you access your page, Wayfinder should then set the id then to current active parent item.. so there should be that id if you did everything like it’s put in the wiki page and the document you access is under some folder or a folder itself.. but if the document is just a single document and there are no pages under it, it won’t have that id.. but this menu is only designed to a folder/file(s) structure and 1 level deep.