Previous entries link

[mmeg]

Is there a way to add the "previous 5" (or 10 or whatever) link to the navigation bar at the top of my recent entries, reading and network pages? I'm using Mixit, which I believe is a Core1 LJ style.

ETA: Also I figured out how to reverse the order of the entries on my reading page (for values of figured out which equal bugging the Support people), but it didn't reverse the order of my Page Summary. I wonder if there's a way to do that. (I care about this much less than the first question.)

Comments

[matgb]

OK, I think, but can't test. In the function
function Page::lay_print_header_links()

There's a line at the end that says
print """<li$class><a href="$url" title="$text">$text</a></li>""";

After this, but before the } on the next line, copy in the following:
var string skiplinks = ""; var Link forward = $.entry->get_link("nav_next"); var Link backward = $.entry->get_link("nav_prev"); if (defined $forward or defined $backward) { $skiplinks = """<li class="prevnext">"""; if (defined $backward) { $skiplinks = $skiplinks + """<a href="$backward.url">$*text_entry_prev</a>"""; } if (defined $backward and defined $forward) { $skiplinks = $skiplinks + " | "; } if (defined $forward) { $skiplinks = $skiplinks + """<a href="$forward.url">$*text_entry_next</a>"""; } $skiplinks = $skiplinks + """</li>"""; println safe $skiplinks;
I think that works. I'm not 100% sure and can't test it without creating a whole new style.

But, trying to be less cranky in this comment, Mixit is essentially the Vox layout redone for LJ. It's one of the best LJ layouts in terms of functionality, which is why the DW style devs used it as a basis for the core DW layout. Anything doable in Mixit is doable in a Core2 layout, the big advantage of that is you maintain all the built in accessibility goodness that they've spent ages building (ie friends using screenreaders, mobile browers, etc still get a good experience), and if there're new funtions created site wide that benefit everyone, you still get them.

Looking at your layout, I think you can make it Better in TR or similar, wihtout much tweaking. I definitely made a much better layout for DW than I had on LJ.

[mmeg]

I'm getting a compiling error:

Compile error: line 1847, column 10: Unexpected token found. Expecting: [TokenPunct] = (
Got: [TokenIdent] = Page
S2::Node, S2/Node.pm, 144
S2::NodeArguments, S2/NodeArguments.pm, 25
S2::NodeTerm, S2/NodeTerm.pm, 471
S2::NodeIncExpr, S2/NodeIncExpr.pm, 41
S2::NodeTypeCastOp, S2/NodeTypeCastOp.pm, 29
S2::NodeInstanceOf, S2/NodeInstanceOf.pm, 29
S2::NodeUnaryExpr, S2/NodeUnaryExpr.pm, 40
S2::NodeProduct, S2/NodeProduct.pm, 28
S2::NodeSum, S2/NodeSum.pm, 31
S2::NodeRelExpr, S2/NodeRelExpr.pm, 29
S2::NodeEqExpr, S2/NodeEqExpr.pm, 29
S2::NodeLogAndExpr, S2/NodeLogAndExpr.pm, 29
S2::NodeLogOrExpr, S2/NodeLogOrExpr.pm, 29
S2::NodeRange, S2/NodeRange.pm, 29
S2::NodeCondExpr, S2/NodeCondExpr.pm, 29
S2::NodeAssignExpr, S2/NodeAssignExpr.pm, 29
S2::NodeExpr, S2/NodeExpr.pm, 29
S2::NodeExprStmt, S2/NodeExprStmt.pm, 28
S2::NodeStmt, S2/NodeStmt.pm, 67
S2::NodeStmtBlock, S2/NodeStmtBlock.pm, 43
S2::NodeFunction, S2/NodeFunction.pm, 104
S2::Layer, S2/Layer.pm, 59
S2::Compiler, S2/Compiler.pm, 27

Context

1843:
1844: """;
1845: }
1846:
1847: function Page::print_stylesheets() {
1848: # These are the themes that need the header.css file included
1849: var bool{} header_themes = {
1850: "ocean-fish" => true,
1851: "ocean-squid" => true,

I appreciate the work the DW devs have put into accessibility and making things more awesome on the backend and I have spent hours combing style comms looking for something I can use. If you know someone who would like to volunteer to design a core2 layout to my specifications, please let me know. Otherwise, please accept my sincere promise that I will switch the moment I discover a core2 layout that I find both functional and attractive. (I did check to see if people were answering core1 questions in this comm before I posted. I'm sorry core1 kicked your puppy, and I will be happy to pick this back up in the morning when I have regained some emotional perspective.)

[mmeg]

Hey, sorry I got all hysterical. I appreciate the effort you're putting in. I just really want to shift to DW as my primary reading page, and I'm getting a little frustrated with the style options.

[adalger]

I took a look poking around in your layer this morning, and it may need more than just a quick edit. You have duplicates of things, and that may be causing the compiling issues you're having because of ... strange arcane behind-the-curtain hand-wavy stuff. To get this to work the way you want, someone may have to go clean up the code to the point where everything is only in there once.

You mentioned this came "pre-hacked." Can you point a finger at the source and maybe we can lean on the original hacker? :)

[mmeg]

grrliz made the original layout for LJ and posted a tutorial for importing it to DW here. She has been very clear that she won't troubleshoot, so if the original code is screwy, I'll just live with it as is. DW has been really good about adding new styles, so I'm sure eventually I'll find one I like and then I can bug you guys about that instead. (I got so spoiled using Smooth Sailing on LJ. The customization wizard on that one is so very very extensive that I've never had to deal with any of this.)