NONE OF THIS MAKES SENSE!

Look, I am a proper develop - I am used to things like includes for menus, etc. Everything works when I program it myself in vim, Dreamweaver, Notepad whatever.

I want to use this so I can just let managers edit their own pages - but this plug-in is causing me great frustration... none of the documentation I have come across actually helps me at all... I understand non of it.

I want to have just a simple menu - using a UL class called navlist which seems impossible - the only way I could seemingly do it was to put the default "basic snippet" code inside a div and have a div with the formatting I wanted for the UL on that div... but that just doesn’t work...
all this "chunk" stuff is like another language it doesn’t make sense, so just telling me to put a chunk in is stupid - I know what a chunk is, but just putting it won’t work - putting the snippet before and after doesn’t make a difference, I always end up with a sick looking menu.

I really need someone to help me on this, prefereably one on one. - I don’t want to abandon ModX on the ground of I can’t have a menu on my pages.

TIA

Matt. :’(

if all you want is the class navlist on the outer ul

just set the parameter &outerClass=`navlist`

I totally get your frustration. I’ve been creating bespoke, css styled, dynamically generated unordered list menus for ages now. However, I’ve just started using MODx and whilst I love it, also hit a brick wall when it came to using Wayfinder. It seemed infinitely configurable, but damned if I could work it out. The long list of parameters didn’t explain how to use it, they only served to confuse me more. What I needed was a simple tutorial and as luck would have it, there is one:

http://wiki.modxcms.com/index.php/Accordion_menu_with_Wayfinder

It goes through, step by step, how to create a nice accordion menu. It’s basic, but suddenly it started to make sense for me. I’m not suddenly an expert, but at least I can have a go now. I hope that helps and let us know how you get on

if all you want is the class navlist on the outer ul

just set the parameter &outerClass=`navlist`

That worked but didn’t get that from the documentation... I think the vast amount of features it has makes the documentation to hard to understand if all one wants is something simple.

Thanks.

glad you got it working. I will see if there is a better way to organize it ot make it easier.

Quote from: kylej at Jan 28, 2007, 07:49 AM

glad you got it working. I will see if there is a better way to organize it not make it easier.

I’m also having big difficulties with it, and it really need to works on it for days before having a general view of the stuff... now things are coming, but ..

May I suggest to
simply think, not in terms of high tech specialist, but exactly as you should be forced to explain WF to an audience of people that almost never read anything about MODX ? And do not know about Dropmenu neither.

This alway supposes to introduce WHAT is WF. and how it works - Cause the concept is missing.

WHERE it could be use (with a couple of good example -simple one -)
Tell a word about limitations.
Add paragraphs with many examples from the simplest to the hardest.

And then, and only then, flash out this whole bunch of tag/parameter that of course are a must, but that could not be enough in themselves.

Keep going

I think that the people who can code, should mostly code, and try to write at least some documentation for the parameters, but that’s it. Then the people, who has gone through the learning process and knows what should be documented better can do it in the Wiki easily. Why bring it all to the developer who is busy anyways..

Quote from: doze at Jan 29, 2007, 04:56 PM

I think that the people who can code, should mostly code, and try to write at least some documentation for the parameters, but that’s it. Then the people, who has gone through the learning process and knows what should be documented better can do it in the Wiki easily. Why bring it all to the developer who is busy anyways..

Huh, it’s a point of view, and I understand,
but this, may be, supposes an extra reliable organization, closer to a private company, where each one has a specific role, than a diluted community. Of course the main coder could consider it’s task consists into firing and "forgetting" a cool application, and expecting that someone who think it’s cool will do the remaining 50% : writing cool doc and training.

Personally, I would consider the best person to explain something is the creator himself. He is the only one who REALLY knows what is what and won’t write bullsheets.
May be it’s also a question of culture (US Anglo-Saxons vs Europeans ?).

So when ’Doze’ says

I will see if there is a better way to organize it not make it easier.

We can suppose he agrees with this.

But, sure, we are talking about open source, and it’s free, so every body is free to choose something else.. could be just a pity to miss new ’adepts’ for an only documentations question.

Sadly, this is still very much a donated time effort. Documentation time for the dev team and project leaders sometimes has to take a back seat to activities that put food on the table.

I just put my first Wayfinder menu together this morning, after dissecting the MODxHost template’s wf menu and chunks to figure out how they work. I’m still missing a lot of the big picture, but I know how to convince Wayfinder to generate a bunch of <li>s now.

I think one thing that might help the documentation would be a number of simple, well-documented examples, to the tune of "these wayfinder options generate this kind of code." If I have any inspiration left after I finish putting together the demo my client next week, I’ll try to come up with something like that and throw it on the wiki.

I love how powerful ModX is, and I’d like to give a bit back because its certainly making my life a lot easier than it could be lately.