One page per element on the wiki?

  • jacob1
    8th Oct 2012 Developer 0 Permalink
    I think it would look better like the save above, but if Simon doesn't do it then your way is ok I guess. Also, maybe there should be a section on creating or something, that shows all the different ways hydrogen can be produced.
  • nmd
    9th Oct 2012 Member 0 Permalink

    Is there a way to upload gif files into the wiki page? because I have some that can be useful for specific elements...

  • Vortico
    9th Oct 2012 Member 0 Permalink

    Click on the Special Pages link on the left, and find the Upload File link. Then paste [[File:filename.jpg]] into a page.

  • Box-Poorsoft
    9th Oct 2012 Banned 0 Permalink
    This post is hidden because the user is banned
  • plead-for-destruction
    9th Oct 2012 Member 0 Permalink
    @Vortico (View Post)
    I'm in the mood for writing, I'll chuck a bunch of drafts up when I get home :)

    On my phone right now though. :P
  • Vortico
    9th Oct 2012 Member 0 Permalink

    @Box-Poorsoft (View Post)

    @plead-for-destruction (View Post)

    Great! Hydrogen is the "demo" element page, so if you copy its format, you should be good. Don't spend too much time on the infoboxes though. I'll add those in all at once this evening. Thanks for the help!

  • jacob1
    10th Oct 2012 Developer 0 Permalink
    For the sections on each page, maybe it should be like this:
    Creation
    --how to create the element in reactions
    Reactions
    --what reactions it participates in, includes things like SING destroying stuff and INVS turning neut to blue phot, not just X + Y = Z
    Examples
    --example saves showing off what it can do. (in a table) If there are none, one might need to be created
    Properties
    --All elementdata.c info, maybe I should revert my infobox changes and we can put them here. This should be in a table (and include every property from the source)
    Properties2? Or with above
    --list of what things like tmp, ctype can do and how to customize it with the console

    Other sections can be created too, depending on the element. This way should also give it enough sections to get the header box on top, but also developers like me would have to fill in some information. I like the current pace, because I can slowly add things in when I want.
    I just noticed, there's no place to put things like metal's hot glow, someone put it under reactions, maybe it belongs there? Or anything from the old descriptions that doesn't fit can go into an into at the top
  • Vortico
    10th Oct 2012 Member 1 Permalink

    Here are the infoboxes for all elements, parsed from the TPT C++ element files.

    http://ironspire.net/files/elements.txt

     

    I decided to use C++ property names for the infobox parameters, so the MediaWiki markup and TPT source code would have a closer binding. Since it would be a ridiculous amount of work to change small details of the infobox in such a way that would be reflected across all element pages, the formatting and parsing is entirely controlled by the Infobox_Element template. The individual element infobox markup is therefore more of a raw data container than a declaration for the layout. Currently, about half of the parameters passed to Infobox_Element are actually used, to allow us to add and remove any data we wish in the future.

     

    The intended usage of this file is to be a quick-starter for creating new element pages. The infoboxes should be pasted manually into each element page rather than blindly added with scripts. The astrisks (******) should be replaced with the full name of the element since it usually can't be found in the source code. Also, if the long or short name appears in the description (e.g. "Neutrons. Interact with matter in odd ways."), it would probably be best to remove it to avoid clashing with the infobox header.

     

    When creating a new element page, a quick glance over the data would be helpful to verify any obvious errors. For example, as noted in the HYGN data, a custom function overwrites the Flammability variable, so the obviously correct value "Yes" disagrees with the value "0" in elementdata.c.

     

    For those who are interested in starting some of the element pages, here is an example of a data entry. You can find these in the elements.txt file by searching for the 3-or-4-letter abbreviation. When pasting, you don't need to include the name at the top, just the text inside the curly brackets.

     

    HYGN
    
    {{ infobox Element
    | icon = HYGN.png
    | longname = ******
    | image = [[File:******.png|200px]]
    
    | advection = 2.0
    | airdrag = 0.00
    | airloss = 0.99
    | collision = -0.10
    | colour = 5070FF
    | description = Combines with O2 to make WATR
    | diffusion = 3.00
    | explosive = 0
    | falldown = 0
    | flammable = 0
    | gravity = 0.00
    | hardness = 0
    | heatconduct = 251
    | highpressure = 
    | highpressuretransition = 
    | hightemperature = 
    | hightemperaturetransition = 
    | hotair = 0.000
    | identifier = DEFAULT_PT_H2
    | loss = 0.99
    | lowpressure = 
    | lowpressuretransition = 
    | lowtemperature = 
    | lowtemperaturetransition = 
    | meltable = 0
    | name = HYGN
    | properties = TYPE_GAS
    | state = ST_GAS
    | temperature = 273.15
    | weight = 1
    }}

    TODO:

    • Most temperatures in the list are 22 C less than their actual value because I didn't consider R_TEMP when parsing. Be sure to double check their initial temperatures before pasting.
    • I didn't see electricity conductivity in the source. I'll look into this later.

     

  • plead-for-destruction
    10th Oct 2012 Member 0 Permalink
    @Vortico (View Post)
    I'm adding the pages noa :)
  • Catelite
    10th Oct 2012 Former Staff 0 Permalink

    I'm making GIF animations to use as the infobox graphics for each element.