Hi there. I've recently started using the Quite Lickable layout for a secondary LJ, and I like it a lot. So much so that I'm considering switching to it for my main journal. However, if you look at my layout (I'm currently using Component for this one) you'll see that I have it rather heavily customized, with the components on both sides and
(
Read more... )
Comments 6
function Page::lay_print_paraphernalia() {
$this->lay_print_journalinfo();
$this->lay_print_viewsel();
$this->lay_print_viewspec();
$this->lay_print_userlinks();
$this->lay_print_custom_paraphernalia();
}
(obviously adding whatever layers you've created).
I think they'll alwyas be chained together, though, although I guess there might be a way of modifying the CSS to create some kind of divider, possibly...
Can't help with the two sidebars I'm afraid.
Reply
If you're desperate to mix custom boxes and builtin boxes, one solution would be to make Page::lay_print_paraphernalia only call $this->lay_print_custom_paraphernalia();, and then do the other calls in the custom function. Something like this:
function Page::lay_print_paraphernalia() {
$this->lay_print_custom_paraphernalia();
}
function Page::lay_print_custom_paraphernalia() {
$this->lay_print_journalinfo();
$this->lay_print_viewsel();
$this->lay_print_viewspec();
paraphernalia_box_open("blurb","Blurb");
print "
Blah blah blah!
";
paraphernalia_box_close("blurb","Blurb");
$this->lay_print_userlinks();
}
My usual caveats apply about the possibility that future changes to the layout might break this or misbehave, since this is using the layout functions in a way that wasn't intended.
Reply
Reply
Compile error: line 30, column 20: Unexpected token found. Expecting: [TokenPunct] = ;
Got: [TokenIdent] = http
Is this an impossibility, then?
Reply
Leave a comment