Putting previous and next links with the other navigation links.

[ex_awakened208]

Would it be possible to merge the "previous" and "next" links with the main navigation that has the "recent entries"/"read page"/"tags", etc links in it?

The end result I am looking for is a header navigation that goes in this order:

previous | recent entries | archive | read | tags | info | next

I would prefer if the previous/next links only show up if there are actually entries before/afterward.

I hope that was clear enough! Thanks in advance.

Comments

[foxfirefey]

Beneath RecentPage is just FriendsPage--you can see the hierarchy of the objects here. There's a page that explains more about the language here.

For the code that I gave you, I only need to check if the page we're on is a RecentPage, whether it's actually a RecentPage or a FriendsPage, because the variables I need from it all end up being the same. Sometimes that might not work! Sometimes you might need to know whether it is a specific view, or a specific object and not one that includes the children.

If it's about the specific object, there's a different type operator to use called "instanceof". For that one, if I did $p instanceof RecentPage, it wouldn't return true if $p was a FriendsPage.

If it's about the specific view, Page objects have a variable called "view" that can be used to check--I think that's what I was using previously when I was only doing the entries, something like $p.view == "entry". In that case, view would be different from recent page, or the readig page, or the network page.

[ex_awakened208]

Ah, gotcha! Thank you again for taking time to not only write a code for me but to explain some of it to me as well! I appreciate it.

[foxfirefey]

Thank YOU for working with native DW layouts!

Head-scratcher

[marahmarie]

If that hierarchy is literal it's rather strange (which is not a critique so much as a statement of complete befuddlement at it).

I always thought the hierarchy should flow more like this:

Page >
equal in hierarchy to
FriendsPage >
which would both own
RecentPage >
with the following descendants
TagsPage
YearPage
MonthPage
DayPage
EntryPage
EntryPreviewPage

To my mind, that makes more sense. The way it is now, FriendsPage is a descendant of Page when they should be more or less equal in value because they hold and do the same thing! But maybe I'm just not able to wrap my mind around why FriendsPage should be a descendant of Recent...

Re: Head-scratcher

[foxfirefey]

For the most part, object inheritance goes from the more general, all-encompassing class down to the more specific ones. So, Page is the umbrella over them all, because it is the most generic. A RecentPage is a page that lists recent entries, it's next. A FriendsPage is pretty much on the level of a recent page, really, but it has the tweak of displaying entries from others instead of recent entries in a journal, and reading and network pages use it. It inherits a lot of the code from the RecentPage, so that's its ancestor. Other pages are a lot more different from each other, so for the most part they inherit directly from the main Page (which is controlling basic layout stuff, layout out module areas and headers, etc). The exception is EntryPreviewPage, which is ALMOST like an EntryPage but with a preview, so that's what it inherits from.

Re: Head-scratcher

[marahmarie]

OK, I had to really wrap my mind around that for a minute, but of course that's exactly right. Page (as in Page) can control anything so Friends page can't inherit directly from it since Page gives it no specific structure to work with (it needs RecentPage to build off of for that).

I think the other thing that threw me off is I always thought Recent was literally the first direct descendant of Page (in other words, in the hierarchy, DayPage, EntryPage, EntryPreviewPage, IconsPage, MessagePage and MonthPage would never precede it). But this was probably more a bias of mine based on how I work through the code when I'm editing an entire layout (it goes like this: Recent/Friends-Network, Entry, Tags, Archive-Month-Day - I'm kind of OCD in that I have to edit each view in exactly that order) than a rational way to order the hierarchy.

Thanks for the further explanation, the specific code I needed and all your help. :)