kunzite (kunzite1) wrote in s2styles,
kunzite
kunzite1
s2styles

s1 & s2 terms

  • s1
    style:
    an s1 style is one of the basic looks provided by the system. they can be found here.
    variables:
    little snippets of code that alter how an s1 style is displayed.
    overrides:
    one or more variables that are placed into s1 styles.
    custom styles (aka "layout"):
    an s1 custom style is a complete collection of overrides that can be saved and selected when you want it to be active on your journal.



  • s2
    classes:
    structures that define objects in s2. a lot like an encyclopedia article for each object that you can play with. it contains the basic parts of each object and the abilities that each object has.
    variables:
    containers that hold specific types of data.
    properties:
    items that act a lot like the settings-style s1 variables, such as s1's "LASTN_OPT_ITEMS" variable. it is equivalent to s2's page_recent_items property.
    functions:
    blocks of code that are a lot like the other type of s1 variables. such as s1's "GLOBAL_HEAD" variable. it is equivalent to s2's Page::print_custom_head() function.
    override:
    to redefine the value of a property or redefine the output of a function.
    layers:
    text files in which classes, properties and functions can reside.
    • core:
      this is the skeleton of s2. all of your basic needs can be found here.
      • core internationalization:
        there are many text properties and functions in the core layer. this layer holds the definitions for these properties and functions that dictate how they should look in a language other than english.
    • layout:
      this adds muscles and other living tissues to the core layer. it can even invent new things that don't exist in the core layer and introduce mutations that make this layout unique.
      • layout internationalization:
        the text properties and functions that are present in the layout layer but not the core layer get altered here for languages other than english.
      • user:
        these layers are automatically attached to your style when you use the customization wizard. when using the wizard, it will override the values of properties that are, defined and/or declared as used, in the layout layer. when not using the wizard, one can manually override values of properties or redefine functions. this second method is considered to be an advanced customization as you run the risk of losing some of the custom code if you use the wizard to make any changes.
      • theme:
        one set of these layers are supplied by LiveJournal's servers and override properties and may redefine functions to give you examples of what the layout can do. they most oftenly have different color schemes that you can choose from. when not using a server-supplied theme layer, you can create your own and use it to override values of properties that are defined in the core layer or defined and/or declared as used in the layout layer as well as redefining functions. you will need to use a theme layer to keep the custom values of properties that are defined in the core layer but not declared as used in the layout layer.
    styles:
    an s2 style is a specific collection of layers that can be saved and selected when you want it to be active on your journal.

questions/comments/concerns/krispy kremes?
Tags: ljuser:k1
Subscribe

  • yo

    i'm going out of the country for a week. uniquewonders is in charge for that time. i expect you all to be on your best behavior. ;)

  • s2 refried paper

    s1's refried paper is now available in the public layers system. if you come up with any color themes that look neat, please submit them here. i…

  • s2 disjointed

    s1's disjointed is now available in the public layers system with a handful of color themes. here's component_help in s1's…

  • Post a new comment

    Error

    default userpic

    Your IP address will be recorded 

    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.
  • 8 comments