?

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
[Links:| how to post tags page ]
[affiliated communities| fblayers ]

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

s2layers

[kunzite1]
how to post
post your layer code under a cut after converting all
& to &
< to &lt;
and
> 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.
linkReply

Comments:
[User Picture]From: camomiletea
2005-03-14 07:45 pm (UTC)
I can't find your post about the system you came up with for naming variables. I think it was in component_help, but it's not on tutorials page... I want to write a tutorial for this comm. :)
(Reply) (Thread)
[User Picture]From: kunzite1
2005-03-14 07:53 pm (UTC)

and...
for those of us who are making these tutorials, i have come up with a nifty convention for variables.
the first part (k1) is something that abbreviates your username.
the second part (M) is something that abbreviates what the tutorial does.
the third part (title) is the name that you woulda used in the first place.
and you come up with something like k1Mtitle ... yayness. ^_^

link.

so... you can be ct :)
(Reply) (Parent) (Thread)