Jump to page in URL

[ahankinson]

It would be nice to be able to link to a specific page via URL, e.g.,

http://example.com/diva/32#p=499

[alastair]

it'd be cool if the addressbar updated as you scrolled pages, using one of the frameworks that fixes the back button (so that back/forward will switch pages as well)

[ahankinson]

Also, we will need to specify the zoom level for each page link. Suggestions are welcome on how to incorporate this while still providing "clean" URLs.

/diva/32/${Z}/${PGNO}?

[dellsystem]

I like the second idea. I'll see if I can get that set up.

[alastair]

I'm not a fan of things that look like urls but then use js magic. Can we use the #! standard instead? or even just a #
e.g.
/diva#!pg/zoom
or
/diva#pg/zoom

I think it makes sense to have pg first because then you're getting more specific as you add more url.

[alastair]

Note also that the hashbang urls are a spec: http://code.google.com/web/ajaxcrawling/docs/getting-started.html
Maybe we don't need to make pages crawlable in this sense, so a plain # makes more sense.

[ahankinson]

There isn't really universal consensus on this issue:

http://dannythorpe.com/2011/02/09/side-effects-of-hash-bang-urls/
http://isolani.co.uk/blog/javascript/BreakingTheWebWithHashBangs

On 2011-06-07, at 1:03 PM, alastair wrote:

Note also that the hashbang urls are a spec: http://code.google.com/web/ajaxcrawling/docs/getting-started.html
Maybe we don't need to make pages crawlable in this sense, so a plain # makes more sense.

Reply to this email directly or view it on GitHub:
#31 (comment)

[dellsystem]

How about this? #p=149&z=3 or #p=149 or #z=3 so that one can be specified without the other.

[dellsystem]

There's a bit of a problem in that it's not able to validate the requested zoom level to make sure that it's a valid one until after the first ajax request, because that's when the script receives the max zoom level. I'll see if I can find a workaround but it looks like I'll have to do 2 ajax requests, one after the other, if hash fragments are specified. Not that terrible but not the best solution, either.

[alastair]

Yeah, I agree with those posts, however I think what we're doing is slightly
different to how lifehacker et al. do theirs. We load a page and then scroll
to a position, rather than load a blank page, find the fragment, then
replace the entire page contents. Thinking about it, this fact makes me
wonder if hashbangs are the correct solution or not, and maybe just a #
makes more sense - like Wendy's solution.

On Tue, Jun 7, 2011 at 1:47 PM, ahankinson <
reply@reply.github.com>wrote:

There isn't really universal consensus on this issue:

http://dannythorpe.com/2011/02/09/side-effects-of-hash-bang-urls/
http://isolani.co.uk/blog/javascript/BreakingTheWebWithHashBangs

On 2011-06-07, at 1:03 PM, alastair wrote:

Note also that the hashbang urls are a spec:
http://code.google.com/web/ajaxcrawling/docs/getting-started.html
Maybe we don't need to make pages crawlable in this sense, so a plain #
makes more sense.

Reply to this email directly or view it on GitHub:
#31 (comment)

Reply to this email directly or view it on GitHub:
#31 (comment)

[dellsystem]

Added to the develop branch. See http://petrucci.musiclibs.net:9002/#z=0&p=100 for an example. If an invalid zoom level is entered, then we default to a zoom level of 0; if an invalid page number if entered, then we just stay on the first page. There is a problem with the amount of horizontal scroll being calculated inaccurately, but that's another issue.

[dellsystem]

Forgot about the request to update the address bar as well. I'll add that in.

[dellsystem]

It now updates the address bar as of these commits, but the back/forward buttons don't behave as expected yet. This jQuery plugin looks promising for fixing that. The only problem I can foresee is that if a user follows a link to a document viewer, scrolls for a while (and thus hits many pages) then tries to go back to the previous URL, the user will have to first wade through the all pages of the document that were accessed. Which could be annoying. Perhaps it would be better to just keep the back button pointing to the previous URL.