autonav in general

Permalink
The autonav block is nice if you don't care much about the layout of your navigation.

But whenever there's an exact layout you try to adapt, it's horrible. It takes a lot of time to build.

For example - I'm trying to build that page in c5:http://www.nutriconsult.net/nutri/index.ort?kategorie=Abnehmen&...

Whenever there's a link at the top level selected, it should be surrounded by a little shadow.

Since there's not even a real recursion (why not?), I don't even know when an element has children. Well, I do know, after the parent has be written..

There are a few other problems with that navigation too..


Am I the only person who thinks the autonav makes things very complicated??
I'm even considering to build my own autonav block. Probably a bit more complicated to use but a lot more powerful. Real recursion, classes for all elements...

Remo
 
Styves replied on at Permalink Reply
Styves
I think you're right. It is not evident and can surely be more sophisticated than it is now. Too limited. I agree 100%.
rapidsnow replied on at Permalink Reply
It is already a nice tool to have, but it is very limited. I tried for a long time to edit my css to make it look nice, but I eventually gave up on it and changed <li> and <a> throughout the whole site.

A lot of it for me is that the theme my site has is the original theme I built, and isn't very robust or... good. Still autonav should have an option to change the look of it. Also, the way the recursion is set up, as you say, is not quite right. Let me know if you do build your own block, I'd love to take a look.
Styves replied on at Permalink Reply
Styves
We definitively need something more. I agree 100% too.
andrew replied on at Permalink Reply
andrew
Would someone mind posting a feature request for this in the feature requests section, and then adding in all the things you'd like to see?

I'm not saying that everything written there will be addressed, or that we'll be able to worry about it any time soon, but people do seem to have concerns/questions about the autonav, and we want to try and be responsive (and most importantly, solve the problems that are really affecting people.)
Remo replied on at Permalink Reply
Remo
I already tried but completely failed ;-)

I had a few ideas about a new concept but it's a bit complicated. Well too complicated.

I'll try to make a list of problems I had with the autonav block as soon as possible!
Remo replied on at Permalink Reply
Remo
I tried to make a list with all the autonav problems I had during the last few days. There might be other problems.. Will add them to this thread if I remember them.




CSS CLASSES

every level should have a unique class. That should be fairly easy to implement but gives you more control over the layout



RELATIVE PATH

Imagine a structure like this:
/en/about
/en/contact
/en/products
/en/products/product_1
/en/products/product_1/spec
/en/products/product_2
/en/products/product_2/spec
/de/about
/de/contact
/de/products
/de/products/product_1
/en/products/product_1/spec
/de/products/product_2
/en/products/product_2/spec

the autonav in the footer should print the link to about and contact.
there's another autonav that lists all the products.

the autonav block in the footer should display the second level, but only those underneath the currently selected language.
I'm not aware that it is possible to do this at the moment, without customizing a template (which I did and works).



PICTURES

In a lot of situations you might want to use pictures instead of text. The page attribute you've added makes this already a lot easier but I still think this is quite complicated for a lot of c5 website builders outhere.


SHOWING FIRST CHILD ELEMENT

I'm not sure if this is something only needed by one person (the one called Remo) but this really bothers me:
http://www.concrete5.org/community/forums/usage/pages_underneath_ex...

Using an external link doesn't seem to be a good solution because it doesn't generate a nice page structure and the autonav block doesn't like it.


RECURSION

A real recursion instead of a flat list would be much more powerful imho. I could do a lot of using within the template. Mostly using php code which isn't the easiest thing for everyone but at least I could easily do whatever I want using php.

For example: The problem with "showing the first child element". Add a new page attribute "show_first_child_element". Check if it is set to "true" and if so, echo something like this: "$currentAutoNavElement->children[0]->link" in case there's a child available..

The default code to display the ul-li structure would also be easier to read I think. A recursion is nothing complicated, is it?
Stoob replied on at Permalink Reply
Stoob
Hi. Autonav is limited. I would like to see a way to have an AutoNav with thumbnails. Let's say I was creating a series of pages and I wanted an icon or thumbnail to represent each page, NOT a text link. It would be nice to have that option and that style of navigation.