User talk:Tellos/Template:TestBox

I recommend you remove the splash values for now, since I have a little suprise for it ~小太郎 ^TALK_CONTRIBS 2011:01:17:11:24 (Monday)

I doesn't like et. ): --κєνıи _{(»тαıĸ«)} 11:40, 17 January 2011 (PST)

Which part don't you like? Tellos 11:54, 17 January 2011 (PST)

It might just be me, but it seems a little bit too... crowded..ish.. --κєνıи _{(»тαıĸ«)} 11:56, 17 January 2011 (PST)

You should make use of the space you're given, since most likely, nothing will be put to the right of the template. Also, the image won't always be that large, leaving a giant black spot surrounding the weapon image and leaving the columns too tall. --κєνıи _{(»тαıĸ«)} 11:57, 17 January 2011 (PST)

mabitable class does not allow me to modify the size of table boxes. If you could fix that, then I could change their size but until then its forcefully scaling them. Tellos 12:49, 17 January 2011 (PST)

Since when did mabitable restrict size changing? --κєνıи _{(»тαıĸ«)} 12:52, 17 January 2011 (PST)

It forcefully scales boxes to the size of the text inside them. Its not allowing me to set a fixed width to the boxes. Tellos 12:54, 17 January 2011 (PST)

Seems to work for me... @latest edit to template. --κєνıи _{(»тαıĸ«)} 12:58, 17 January 2011 (PST)

But what I meant was not to stretch it horizontally, but to add more columns and less rows. --κєνıи _{(»тαıĸ«)} 13:00, 17 January 2011 (PST)

I was doing this at 4am. I'm resizing the table to I can allot the rows in a well-organized manner. Gotta know how much space I'm working with. Tellos 13:00, 17 January 2011 (PST)

Alright, the trouble I'm having is row 4 is being forced to the height of the image. Is there any way I can circumvent that without using an embedded table? Tellos 13:37, 17 January 2011 (PST)

You can expand Test2 so that it's under the imagebox. --κєνıи _{(»тαıĸ«)} 14:16, 17 January 2011 (PST)

Or change the "#-hit" and speed back to boxes. --κєνıи _{(»тαıĸ«)} 14:17, 17 January 2011 (PST)

Alright I got it reorganized so that it looks decent and is a proper width. Tellos 15:08, 17 January 2011 (PST)

Now I likey. :) --κєνıи _{(»тαıĸ«)} 15:13, 17 January 2011 (PST)

A quick question...what do you mean by Available Enchant Types? I can guess but just wondering why it requires a show hide? --Khenta 15:33, 17 January 2011 (PST)

What type of enchants can be used on this weapon. Such as... metal equipment... weapons.. helmets... etc --κєνıи _{(»тαıĸ«)} 15:46, 17 January 2011 (PST)

Just making sure, but still wondering why it needs hide box...are you guys thinking of listing every enchant possible that can go on it? --Khenta 15:50, 17 January 2011 (PST)

Doesn't need a hide box. The most parameters you'll see on one weapon is probably 6. Tellos 15:51, 17 January 2011 (PST)

What I meant was what category the equipment will belong to enchant-wise. --κєνıи _{(»тαıĸ«)} 15:56, 17 January 2011 (PST)

Thats what I was thinking along of what Tellos said. You could use a hide box for drops. That way you can detail the +/- stats and enchants comes on it. PS: This talk page is quite indented... --Khenta 16:00, 17 January 2011 (PST)

The hide box makes it look better aesthetically. It serves no real purpose aside from that. Tellos 16:15, 17 January 2011 (PST)

Instead of having to redefine "Stun" value every time you create a template, you can use the switch parserfunction in order to do it automatically, since, according to Stun page, stun times remain static.

Example:

{{#switch: {{Hit}} {{Speed}}
|3 Slow=1.6
|2 Slow=2.3
|2 Very Slow=2.7
|3 Very Slow=1.65
|3 Normal=1.6
|3 Fast=1.4
}}

Alright I'll do that. I didn't know how to put conditional statements in CSS/XHTML.

I also wanted to put a condition for Ego and SpecialUpgrade so that it'd show up in the "other information" box just by defining the parameter.

Such as

{{#if: {{{Egoable|}}}|Egoable weapon}}
{{#if: {{{SpecialUpgrade|}}}|Special upgrade enabled, or whatever.}}

Is there a way to put an else? I want "Unknown" to show up if hit or stun are missing.

Add a line to the end with no conditions.

{{#switch: {{Hit}} {{Speed}}
|3 Slow=1.6
|This text shows up if nothing is matched
}}

Anything else that needs to be changed before it can replace the existing weaponbox?

I'm not sure by just looking at it. We will need to apply some tests on it and see. The splash part of the box will be added when I get my minionship again. It involves javascript :P ~小太郎 ^TALK_CONTRIBS 2011:01:26:09:16 (Wednesday)

What do you plan to do with the box that requires js?

Check this :P ~小太郎 ^TALK_CONTRIBS 2011:01:27:02:39 (Thursday)

I don't like it. It doesn't fit the simplicity of the weaponbox that I am aiming for. Simplicity > "coolness"

Though the function works correctly in chrome, the method of vertical text you're using doesn't seem to be supported. Besides, why use a slidebox when you've already got hiddentext? Seems a tiny bit redundant...

It's not ready yet lawl :P
Also, I'm doing this method since the splash section is rather small, and putting a giant hiddentext thing at the bottom seems to use too much space for comfort. In the weapon template, I'm planning for it to default to a closed state, because I doubt that that information is actually used much ~小太郎 ^TALK_CONTRIBS 2011:01:27:03:13 (Thursday)

I don't see why we don't just include that into the template anyway.. it's not like it's soemthing you really need to hide.

Do you need to modify one of the commons files or something? You can just edit this template if you want.

Instead of creating two conditional statements for each that separate whether it can or cannot, you can use one condition statement.

{{#if:{{{Variable|}}}|True text|False text}}

{{#if:{{{CanEgo|}}}|*Can be made into a spirit weapon.|*Cannot be made into a spirit weapon.}}
{{#if:{{{HasSpecialUpgrade|}}}|*Special Upgrade is available.|*Cannot receive Special Upgrade.}}

If the parameter is null will it default to false?

Yes.