#96 open
AlternateTorg

Chapter nav start location

Reported by AlternateTorg | October 5th, 2009 @ 07:34 PM | in emergencyPants 1.3.0 - Col. Bud Manstrong

The previous chapter nav widget was a simple pull-down selector which displayed the current story. When you pulled it down, you saw a navigation list with the current story highlighted. The new widget displays the current chapter and story name, but when you open it, it starts at the megatome/book level instead of the chapter in which the story is located.

I'd suggest that instead of only showing one level at a time, show all three side-by side. This would eliminate the need for a "Back" button, show the user exactly where they are in the context of the strip, and give them much more navigation power.

I've attached a mock-up of what this might look like. Please excuse the crudity of this model; I did not have time to make it to scale.</doc brown>

Comments and changes to this ticket

  • Brendan W. McAdams

    Brendan W. McAdams October 10th, 2009 @ 11:09 AM

    • Milestone set to emergencyPants 1.3.0 - Col. Bud Manstrong

    No crudity, we know this is an issue. We're using a third party component and I've been trying to make it work... but at this point I think i'm rewriting it.

    I believe a "Fix" will be rolled into the new "Adding weekly mode back in" code. I'm behind on everything because I'm a slacker.

    The other issue, I can use feedback on (in the final analysis, performance and usability testing will probably decide this BUT...):

    Right now, partly in order to handle the "If javascript is disabled downgrade gracefully" problem, we render LITERALLY the entire menu contents out in HTML for every possibility of the site.

    I think among other things that it's adding too much parsing to the browser and sucking performance.

    I'm considering a rewrite that will only render out the "Current" view, with just the top level stuff rendered otherwise (books for the omnibus you're in, chapters for the book you're in, sections for the chapter you're in) and use a AJAX/JSON get when you nav into another area.

    Any thoughts?

  • Argelfraster!

    Argelfraster! October 13th, 2009 @ 12:17 AM

    I do like that 'crude' menu design you made, it would work better than what there is (no offense guys, but that thing doesn't like Chrome, and I do...). I think the Current view idea would work out pretty well.
    And since we're on the subject of menus, I think you should add a search box somewhere along the topbar, just check it with the sluggy.info guy/girl, that would rock. On the Community menu, you don't need '(Wiki)' or '(Search Dialog)'. And I hold firm that a search box on the black menu bar, at right, would rock.

  • Argelfraster!

    Argelfraster! October 13th, 2009 @ 12:19 AM

    And another comment - I don't think this is really an error, but I just noticed this - for people where the update is before midnight, the calender looks a bit odd, highlighting the comic's date, but highlighting in a different style the local 'today'. Maybe have it not highlight today's date? (And please don't solve this with something that'll block out the day's comic until our local midnight! I have to get SOME sleep! :) )

  • Brendan W. McAdams

    Brendan W. McAdams October 18th, 2009 @ 02:44 PM

    • State changed from “new” to “open”

    Hmmmmmmmmmmmmmmm.

    I forgot that the calendar is partly driven by JavaScript.

    I'll look into this, as itm ay be a timezone issue.

    I'm in the process of completely chnaging our entire navigation to be "Better..."

    I hate the new nav menu as much as you guys, and we'll be adding in weekly and such.

    I'll try to deal w/ the timezone issue.

  • Argelfraster!

    Argelfraster! November 7th, 2009 @ 07:46 PM

    It's a jQuery default thing, since I'm assuming by the style that you're using jQuery. And I think the best thing to do would be to just disable the 'highlight today's date' thing, if you can. Sorry if I'm asking something impossible, I'm an amateur PHP coder, no JavaScript for me...
    Basic search would be fine, just a text input with a hidden 'go' button or something... We don't need AJAX guessing what we mean or anything, we're tough little sluggites.

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

The new Sluggy site.

Shared Ticket Bins

People watching this ticket

Attachments

Pages