Log in

No account? Create an account
first post - S2 Layers — LiveJournal [entries|archive|friends|userinfo]
S2 Layers

[ website | advanced customization ]
[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

[Links:| how to post tags page ]
[affiliated communities| fblayers ]

first post [Sep. 8th, 2004|04:15 pm]
S2 Layers


how to post
post your layer code under a cut after converting all
& to &
< to &lt;
> to &gt;

this can help with the conversion.
if you use the aforementioned tool, change the <code> and </code> to <pre> and </pre> respectively.
if you dont use the aforementioned tool, please wrap your code with <pre> and </pre>.

http://stat.livejournal.com/ should be $*IMGDIR/
http://www.livejournal.com/palimg/ -> $*PALIMGROOT/
http://www.livejournal.com/ -> $*SITEROOT/

the subject line should follow the following format:
[layout name] - [layer type] - [mini description of what your code does] - [page number (if applicable)]
layout name - a sturdy gesture, component, generator, haven, opal, etc.
layer type - layout, user, theme
page number - page #/total pages

if your code is too long to place into a single post:
put a comment in the code saying # part 1 ends here and then in the next post put a comment in the code saying # part 2 starts here ... lather, rinse, repeat.

recommended coloring scheme (not required)
if you have comments in the code, we suggest making it green by doing something like:
<span style="color:green;">comment</span>

variable values: maroon
var string moo = "<span style="color:maroon;">variable</span>";

code that is currently active but can be deactivated by commenting (putting a # in front of it) it out.
active code: blue
"<span style="color:blue;">if($active) { print "make it blue"; }</span>";

code that is currently inactive but can be activated by decommenting (taking # in front of it out) it.
inactive code: pink
"<span style="color:pink;"># if($inactive) { print "make it orange"; }</span>";

screenshot of output
we would also like to have a screenshot available that shows the results of the code.

and finally, select the don't auto-format option. this makes the entry a lot easier to read.

[User Picture]From: miome
2004-09-11 02:35 pm (UTC)
For code that overrides official code (from a existing layout, or from the core), it would be helpful to mark code that's been inserted/modified, and code that was active in the original but has been commented out.

This is a great idea, btw. I've got a bunch of stuff from Variable Flow to post, I'll probably backdate all but the last one, so as not to completely blow away people's friends pages ... is that allowed?
(Reply) (Thread)
[User Picture]From: kunzite1
2004-09-11 02:38 pm (UTC)

i like the idea of commenting out stuffs that is being altered. but only if it makes sense if its like correcting a bug or something.

if its a complete change to how something works, dont bother.

hope that makes sense.

re: backdating... *shrug* ... backdate them so it looks ok in the comm journal if you must.

i enjoy blasting people's friends pages tho... ^_^
(Reply) (Parent) (Thread)
[User Picture]From: sssexygirl
2004-09-13 08:24 pm (UTC)
you can blow them up because your KOOL like that ;)
(Reply) (Parent) (Thread)
[User Picture]From: kunzite1
2004-09-13 08:25 pm (UTC)

oh yes... i roxors... :D
(Reply) (Parent) (Thread)