How to use Wide Lines on your journal (version 0.9.31) - Wide Lines






[cmshaw]
widelines
12:18 pm on Wednesday, May 18th, 2005
How to use Wide Lines on your journal (version 0.9.31)
Previous Entry Next Entry


Consider this method of remaining always on the latest version of Wide Lines.

To upgrade your "Wide Lines" layout to the latest version:

1. Log in and go to your layers page.
2. In the table under "Child of layer 1: LiveJournal S2 Core, v1" there is a row with a name of "Wide Lines"; click on "Edit...".
3. Delete all of the text in the large text box shown.
4. Cut and paste all of the text from the current code link below into the large text box and click "Compile".
If this page reloads and says "No error", continue. If it gives an error, repeat steps 3 and 4 just in case a character was lost in the cut and paste, then contact me with a comment here if it continues to fail.

Code for current version

To save the "Wide Lines" layout for later use if you have never used it before:

1. Log in and go to your layers page.
2. At the bottom of the page under "Create top-level layer" select "Type: Layout" and click "Create".
3. In the table under "Child of layer 1: LiveJournal S2 Core, v1" there is now a row with a name of (None); click on "Edit...".
4. Cut and paste all of the text from the current code link above into the large text box and click "Compile".
If this page reloads and says "No error", continue. If it gives an error, repeat step 4 just in case a character was lost in the cut and paste, then contact me with a comment here if it continues to fail.

New features:
* Font size defaults display properly in all browsers.
* The DOCTYPE specification now allows quirks mode, which displays scrollbar colors in Internet Explorer.
* See the notes for version 0.9.3 for more information.

All themes created for version 0.9 or 0.9.2 will continue to work in this version.
If you are uploading "Wide Lines" for the first time, follow this link for instructions on how to upload themes for Wide Lines.

To use "Wide Lines" on your livejournal:

1. After having uploaded the layout and any themes, log in and go to your customize journal page.
2. Under "Choose style system" select "New System (S2)" and click "Change".
3. Under "Step 1: Layout" select "Wide Lines" (it will be at the bottom of the drop-down box) and click "Change".
4. Under "Step 2: Customize Layout" select any theme from the "Themes" drop-down box and click "Change" (previews are not available).
5. Click "Add customizations" to tweak settings further, if desired.

For the historical record: Code for version 0.9.31 (18 May 2005). The code at this link will not change.

The following functions have changed:
* lay_print_cssbody
* Page::print
The following properties have been added:
* doctype_quirks


Tags: ,

Previous Entry Next Entry




Post a comment
View all comments chronologically



Not sheepish, but individ-ewe-al: likeness
From:livredor
Date:May 20th, 2005 - 01:07 pm
(Link)
Is there some reason why you are versioning your style this way? I appreciate you're being very rigorous about keeping the code for deprecated versions available, which is great.

But S2 has a built in way of using someone else's style so that it automatically updates when the creator changes something. Admittedly, the implementation of this is a little buggy, so maybe that's why you don't want to rely on it? But take some random user who just wants to use your style and have it work, and isn't necessarily interested in following the details of the development. They're probably not going to want to watch widelines and go through the process of deleting all the code from their layout layer and then pasting your new code in, every time there's a minor tweak.

In your position, I would be tempted to instruct casual users to go to http://www.livejournal.com/customize/advanced/styles.bml, create a style called 'Widelines', and input 4162751 into the form when it asks for the layout number. Then make sure that layout layer always has the latest version of your style and all the people who have set up their style in that way will be automatically have the latest version. Of course, there's no reason why you shouldn't carry on creating new styles so you can provide permalinks to code for old versions, but you could do that as well as having one layout layer which is always going to be the latest version.
(Reply to this comment) (Thread on this comment)
cmshaw
From:cmshaw
Date:May 20th, 2005 - 02:07 pm
(Link)
But S2 has a built in way of using someone else's style so that it automatically updates when the creator changes something.

Apparently I missed this feature entirely. I didn't know you could do that -- which would be why I wasn't including it in my directions, yes. I'll add that now, and thank you!

(Layer 4162751 has always had the latest version -- I'm creating new layers and updating the permanent one each time with a new version.)
(Reply to this comment) (Jump to parent comment) (Thread on parent comment) (Thread on this comment)
(no subject) - nis_ (5/24/05 07:32 am)
cmshaw
From:cmshaw
Date:May 24th, 2005 - 02:48 pm
(Link)
Oh, thank you for pointing that out! I clearly forgot to revalidate the friends page after putting in the colored lines. I'll fix that now.

I'm glad you found the style interesting!
(Reply to this comment) (Jump to parent comment) (Thread on parent comment) (Thread on this comment)
cmshaw
From:cmshaw
Date:May 24th, 2005 - 02:50 pm
(Link)
(Also, the IE-specific scrollbar colors will not validate, but they will also not be present if you uncheck the "use quirks" option in the wizard (under Layout).)
(Reply to this comment) (Jump to parent comment) (Thread on parent comment) (Thread on this comment)
(no subject) - nis_ (5/24/05 06:50 pm)
cmshaw: L33t Girl
From:cmshaw
Date:May 25th, 2005 - 09:36 pm
(Link)
Torrington, eh? It is a same world -- I'm from Canton, or at least I went to high school there once upon a time!

You spent a lot of time formatting your code to present well

Thank you! Maintainability of shared code is a big priority of mine. I'm glad it's proving so useful. Have you looked through this writeup I did of the comment sorting? I'm crossing my fingers that the new styles, at least, incorporate some of that....

As for the DOCTYPE, I did add one in eventually; it might have been just after you grabbed the code for your own style. I had to sort out a couple of invalid things I was doing (mostly mixing inline and block elements poorly) before it validated, and then I apparently got my development wires crossed and broke the validation I thought I had on the friends page (by tossing per-entry CSS styling into the body of the page instead of reading it during the creation of the <header> -- that was silly linear thinking on my part, not to mention that the mistakes in the CSS itself were not my finest moment).

Sadly -- and not to malign good old vi in any way, of course -- there's very little in the way of S2 development tools available. There is supposed to be a web interface on the compiler, so a client tool could be built that could get compile-time syntax checking that way, but I didn't understand the authentication needed in order to write my own (perhaps the new authentication protocols in the works right now could change that?); I wrote a little client tool that's basically a glorified text editor in VB.NET, since that's what I have at work, and I like to think that I'm savoring the irony of doing open-source work on a closed-source platform because otherwise Micro$oft makes me sad but it doesn't really have the sorts of features that make it worth sharing, I don't think -- its only syntax checking is on the function level, so vim's is probably better!

Why any of us would bother to learn S2 is the greater mystery, since even when a style is complete, it cannot filter out other people's ill-formed HTML in the friends view.

Well, aside from its being fun (no, really!), you could do a little text parsing on $e.text if you wanted to.
(Reply to this comment) (Jump to parent comment) (Thread on parent comment) (Thread on this comment)



Post a comment
View all comments chronologically