LG Navigation - Feature Requests!

Oh and so far the output looks like:

<ul>
    <li class='page_item page-item-1'><a href="#one">one</a></li>
    <li class='page_item page-item-2'><a href="#two">two</a></li>
    <li class='page_item page-item-3 current_page_parent'><a href="#three">three</a>
        <ul>
            <li class='page_item page-item-4'><a href="#three.one">three.one</a>
                <ul>

                    <li class='page_item page-item-6'><a href="#3.1.1">three.one.one</a></li>
                </ul>
            </li>
            <li class='page_item page-item-5 current_page_parent'><a href="#three.two">three.two</a>
                <ul>
                    <li class='page_item page-item-7 current_page_item'><a href="#3.2.1">three.two.one</a></li>
                    <li class='page_item page-item-9'><a href="#3.2.2">three.two.two</a></li>

                </ul>
            </li>
            <li class='page_item page-item-10'><a href="#3.3">three.three</a>
                <ul>
                    <li class='page_item page-item-11'><a href="#3.3.1">three.three.one</a></li>
                </ul>
            </li>
        </ul>

    </li>
    <li class='page_item page-item-8'><a href="#4">four</a></li>
</ul>

Create an alternate url for a navigation item rather than use the page url

Just thought I should clarify this point… Basically this will allow you to create top level nav items that link to a sub-nav item. Unfortunaltely these will just be empty pages with a title so the status will need to be set to closed or something like that 😊

Looks brilliant - as always with your work Leevi, I don’t use Pages much, so unfortunately I don’t have any requests at the moment.

Looks good. You might consider using double quotes instead of single ones.

Looks good. You might consider using double quotes instead of single ones.

Might make that an option… but personally I use single quotes for html and double quotes for php…

Why double quotes? I wasn’t aware of a difference

I believe double quotes in php are always parsed (for variables etc), while single quotes are treated as pure strings and are not parsed.

In html I have no idea, but I always go the other way around; I use single quotes in php and double quotes in html - where applicable.

I use single quotes in php and double quotes in html - where applicable.

Same here and also not sure why. It’s just always the way I learnt from books and the like. I’m sure there must be something about that on http://www.w3.org though.

Looks like a nice new add-on Leevi, congrats!

I probably won’t have any feature requests though either as I don’t like to use the Pages module, sorry.

Good luck with it all though, I’m certain you will be on to another winner again! Do you ever stop to eat that’s what I ask myself? 😉

Best wishes,

Mark

I just realized, the EE dev guidelines mention this; http://expressionengine.com/docs/development/guidelines/general.html#strings

In PHP code, I agree, but for XHTML the W3C recommends double quotes, I seem to remember.

Flip this looks awesome LG!

A tree structure for ordering and editing entries would be a winner in my book!

I just realized, the EE dev guidelines mention this; http://expressionengine.com/docs/development/guidelines/general.html#strings

Ah true…

Correct: ‘My String’

Correct: “”SELECT foo FROM bar WHERE baz = ‘bag’”

I’ll just keep using double quotes rather than a combination of the two to keep it simple 😊

This looks really cool. Wish I would’ve had something like this for a couple of sites that I’m just now wrapping up. 😊

This looks really cool. Wish I would’ve had something like this for a couple of sites that I’m just now wrapping up. 😊

Yeah I finally cracked it during a project I am working on now! I just couldn’t figure out why there was not an easy to use menu building system in EE… THeres plenty of hacks which are ok for developers but clients want it to be easy and infront of them

So no one has any feature requests for this addon? 😉

I do use Pages quite a lot, and this extension looks fantastic. I have no requests either, but it’s hard to know what could be added until we’ve tried it out.

Is this a “when it’s done” project, or do you have a specific date in mind for release/testing?