User talk:Deltaneos

Code review
Now that I've finally finished my initial cleanup of the main table's code on Template:CardTable2/sandbox, I'd appreciate another pair of eyes (or more, if you know of any other MediaWiki code jockeys who may be interested) looking over the code to hopefully spot any bugs or errors I may have overlooked, as well as to provide suggestions for further improvements - I already have some ideas myself, but I'm only one person, and other perspectives would be quite welcome. Thanks in advance! =) 「 ダイノ ガイ 千？！ 」? · Talk⇒Dinoguy1000 21:51, November 7, 2010 (UTC)


 * I'll have a look at finding possible bugs soon. Is this going to rely on the same input as the current CardTable2? Or would it be okay if we did stuff like change  to something like   or how the sets should be entered so we can apply SMW to them? Or is that a later step? -- Deltaneos (talk) 01:12, November 8, 2010 (UTC)


 * I haven't actually changed any parameters yet, though in some cases I have changed how they behave somewhat (hopefully nothing causing breakage though). I'm thinking that would be a later step; first I would like to finish up the initial cleanup (there are a few more things I'd like to do with the main table code, and I've really just glazed over the statuses table and SMW block), have it spot-tested, and get it deployed in place of the current code to check for any more bugs. After that I'll be working on splitting the template into a frontend wrapper and a /core (which will probably itself eventually become a wrapper for per-game subtemplates, once I see how the code falls from the /core separation), which will enable us to make much more drastic changes to the parameter landscape with much less overall work on the template than it would take with a single unified template design (i.e. what we have now). This will be accompanied by lots of exploring how, where, and when current parameters are used to see how the code can be further refined.
 * As for the sets, I had been intending for Card table set to take the role of SMW handling; it feels cleaner to me to have the template called directly rather than having CardTable2 call it for the editor, but there are some benefits to that approach as well (not least of which, Card table set could default to not outputting SMW info unless supplied with an extra parameter, which CardTable2 could provide). I really still don't understand how SMW works yet, though, so there could be more benefits I'm just not seeing. =)
 * And yeah, I realize all this sounds like a lot of work (it is, or at least I'm really good at saying way more than necessary), but the /core separation should be fairly straightforward, and once it's done, everything else can be done gradually. 「 ダイノ ガイ 千？！ 」? · Talk⇒Dinoguy1000 04:01, November 8, 2010 (UTC)


 * *nudge* 「 ダイノ ガイ 千？！ 」? · Talk⇒Dinoguy1000 18:30, November 26, 2010 (UTC)


 * Nothing too major, except where inherited from the original CardTable2.
 * Images are being aligned to the centre of the column and the titles on each sets collapsible are being aligned to the centre of their row. I'm not sure if they were deliberate or not, but I think it looks better when all the flags are lined up.
 * The format status: "OCG Status", "TCG Advanced Format Status" and "TCG Traditional Format Status" aren't supposed to be given values when not applicable. The current CardTable2, I think, is kinda sloppy about that though, so it easy to get them mixed-up. If I recall correctly, in CardTable2, there's a parser that sets them to "Not Present" if they don't exist in the OCG or TCG, but that's contained within another parser that causes that property to not be added at all when not applicable. That's a result of it being done one way, then changed without entirely removing the old way.
 * A lot of the stuff in the black box under the table is supposed to disappear when not applicable. Same as above though, the current CardTable2 just handles it very messily.
 * The width being forced to 400, unless a is specified, is temporary, I take it?
 * Bug with the original table... WC10 isn't appearing in the "Medium" property.
 * Also a bug with the original table, but needs fixing for the new one too. For Property:S/T Class, we need to change it to S/T Class:: Spell Cards and S/T Class:: Trap Cards rather than S/T Class::, since it uses Type:Page (I hate that type being used just for the sake of adding a link) and the Normal and Continuous titles aren't being used for the Spell or Trap Cards specifically. We may need to fix a few pages like this; List of Continuous Spell Cards, but that shouldn't be too difficult.
 * P.S. I had forgotten I had this enabled, but that showed me some more reason not to use max-height/width. It can throw off proportions for pages that exceed one of the limits, but isn't a regular card. e.g. Joey (MW). -- Deltaneos (talk) 00:35, November 28, 2010 (UTC)


 * Looks mostly like ambiguities in the original code I didn't know how to handle (and I've moved most of the styles to external CSS, to make the ultimate addition to MediaWiki:Common.css that much easier; to preview the new styles, add  to your monobook.js or common.js page).
 * In the current table, the card image gets aligned via . I've been trying to figure out how to get the image centered using only CSS, but I haven't been able to get it yet. As for the flags, that's a side effect of using the same template for all the collapsible boxes now. I personally like all the headers being centered, since that makes the whole table look more unified IMO; I could easily add a left-aligned parameter for flagicons though.
 * Yes, the original code in CardTable2 was quite ambiguous about what the default behavior should be. Am I understanding you correctly, that *all* of the statuses information should default to not being shown at all?
 * This is basically the same as the last point. One thing that's always bothered me about the statuses table, though, is that it doesn't disappear when it's empty - the new version will (visually, at least; it would take another layer of template abstraction to cleanly prevent any HTML from being output, either).
 * Yes, until we decide for sure on what the width should be (I believe current consensus is favoring 300px).
 * Is this bug still present in the new table? The SMW code under the table is still a massive mess, even with what cleanup I've done on it, and there're almost certainly gaps that need to be filled.
 * Sounds easy enough.
 * If only one of max-width/height is set, will the other scale appropriately?
 * Now a couple of CSS issues I haven't been able to resolve:
 * No matter what I've tried, I haven't been able to get the card image cell's borders to "stick" to the image in all cases. I could probably hack it by adding  to one of the rows, but there's no telling how screwed up that'd look in some browsers.
 * The styles I've written for cardtable are interfering with the navbox styles for the collapsible info. I've tried "resetting" the navbox styles from within the cardtable CSS, but haven't managed to get anywhere significant.
 * After I've resolved these issues and done a bit more work on the template (and the styles have been tested across more browsers and in the Wikia skin, and moved to Common.css), I'm planning on starting a discussion in the forum and posting a sitenotice to get more people to test the box prior to deployment. Any further comments or help with the issues I'm trying to fix? 「 ダイノ ガイ 千？！ 」? · Talk⇒Dinoguy1000 01:02, November 28, 2010 (UTC)


 * It was more that the image is in the vertical centre than the horizontal centre. Just set valign to "top", I guess. The current template is messy about the alignment of the collapsibles' titles; lores are centred, while everything else is to the left. The flags (and video game icons), should at least be aligned, In my opinion. The text part is fine centred or left aligned, as long as it's consistent.
 * Cards that appear in neither the OCG nor the TCG, shouldn't have the status section.
 * Meh, it's not very important. I don't particularly like that box. I don't think it's going to look to pretty regardless of whether some cells are left empty or not. If you plans to make it disappear when empty, that's great.
 * Okay.
 * No, it's corrected in the new table.
 * Okay.
 * No, it will only scale one. An 800x600 image facing a max-width of 300 will turn into a 300x600 image.
 * Really? One of the things that really stuck out for me was that the borders did stick to the image. Maybe browser differences? I'm using Chrome at the moment. I agree it does look better with the borders sticking to the image.
 * Oh, I totally didn't see you already had the css written. I was only checking for problems with the template itself. I'll take a look tomorrow. I have to go soon.
 * Have you heard of browsershots.org? It might be helpful for seeing stuff in other browsers. Although you'll need a saved page using the template and the CSS applied sitewide. Sitenotice is dead in the new skin, so don't forget to update MediaWiki:Community-corner too when you get that far. Other than that, I can't think of anything more moment, but I'll see if there's anything else after I check test it with the CSS. -- Deltaneos (talk) 02:00, November 28, 2010 (UTC)


 * I've made some updates per the discussion here. In the case of S/T Class, I just changed it to, so further tweaking may be needed there.
 * I also use Chrome (I've been using the dev channel for some time now), so some of the styling issues must be related to the specific CSS I have set up. I've heard of BrowserShots; I'll be sure to use that once the CSS has been set up. 「 ダイノ ガイ 千？！ 」? · Talk⇒Dinoguy1000 03:51, November 28, 2010 (UTC)


 * I've imported the CSS. Curiously, why is to be imported into a JS page, when it's CSS?
 * So yeah, I see you already have the image valigned to the top and now the side borders aren't sticking to it. Is the problem with the navbox styles that there is an extra border around the heading and content and that the heading is thicker? -- Deltaneos (talk) 14:47, November 28, 2010 (UTC)


 * Because Im more comfortable with  than I am with  . ;)
 * Yep (though, after looking at it for a while, I think the thicker header looks nicer). Any ideas? 「 ダイノ ガイ 千？！ 」? · Talk⇒Dinoguy1000 21:33, November 28, 2010 (UTC)


 * Actually, I don't think the borders sticking and not sticking to the image is because of a difference in CSS. At least not directly. When I didn't have the CSS applied, I didn't have the forced 98% width, so the table was only minimally wide, which is why it didn't have the extra space next to the image. -- Deltaneos (talk) 23:24, November 29, 2010 (UTC)

Video game parameters
I just (mostly) finished a massive space-delimited table at the top of the code listing every single video game-related parameter I could find after a cursory amount of searching through the code (this also showed me a handful of bugs that are now fixed ^_^ ); are these all the video gmes CardTable2 needs to worry about right now, or are there more? Are there any parameter gaps that need to be filled (I already know there are several output/SMW gaps to be filled)?

I am probably going to do much the same thing for languages next; any comments on that one before I start, or suggestions on any other stuff to document in a like manner? 「 ダイノ ガイ 千？！ 」? · Talk⇒Dinoguy1000 20:23, November 29, 2010 (UTC)


 * I added some more after browsing the list of video games. I didn't know if I should included "abilitydesc" and "jpabilitydesc" or not. They are kinda generic, but still only apply to monsters from the video game Yu-Gi-Oh! Monster Capsule Breed & Battle (MCBB). e.g. "Hapippy".
 * I take it you've already done a text search for each of the abbreviations for the video games you've added? So I don't need to check if any of them are missing, unless I think there're any parameter names that don't use the abbreviation?
 * I suppose we could have something to list the parameters for all the non-standard games, Bandai, Dungeon Dice Monsters, Monster World, Capsule Monster Chess etc. A couple of the parameters used for them are obsolete and can be removed from the template once they've been removed from articles. "dmlevel", "ddmlevel", "ddmatk", ddmdef", "banlevel", "manlevel" and "anilevel" are all no longer necessary. I've started removing them. We can also get rid of the need for "altlevel", "altatk" and "altdef", as you suggested for non-numeric width values earlier, using #iferror. -- Deltaneos (talk) 22:37, November 29, 2010 (UTC)


 * If they apply to only a single game, I see no reason not to add them. I'm going to be using this info to look for bugs and gaps, and ultimately we'll be writing documentation based on it (one thing I've *never* liked about CardTable2 is how woefully under-documented it is), so the more we do now, the easier our future work will be.
 * What was the original purpose for altlevel, altatk, and altdef?
 * Are these the only parameters which are deprecated at this time? Are there any parameters which used to be used, but were deprecated in the past? 「 ダイノ ガイ 千？！ 」? · Talk⇒Dinoguy1000 23:38, November 29, 2010 (UTC)


 * I'll see if I can organise the documentation better.
 * Property:ATK, Property:DEF and Property:Level use numeric values. Anything else gives an error message. The "alt" stuff is for the values ? (printed on some cards whose effect determines their ATK), ??? (used if we don't know the value), ???? ("The Winged Dragon of Ra"), X000 ("Slifer the Sky Dragon") and ∞ ("Divine Serpent").
 * (with a lowercase "c") is also deprecated. It doesn't need to be removed from the few, if any, articles using it before removing it from the template, nor should we need to rewrite any alternative code before removing it from the template. It used to be used to determine if a card was a Capsule Monster, a DDM, anime only, video game only, anime and video game only, video game DDM only etc. It was possible to get that info using other existing parameters. -- Deltaneos (talk) 00:14, November 30, 2010 (UTC)


 * Currently, then, altatk et al. add pages to Property:?ATK, Property:?DEF, and Property:?Level, right (that's what it looks like from the code, at least)? So we should be able to do e.g., right?
 * Could you explain exactly what different cases CardTable2 needs to worry about, and exactly what parameters/values to look for to determine which cases a given page fits, on Template talk:CardTable2? When I do the /core separation, I'm going to do all this checking a single time in the outer wrapper and just pass the results into /core (this may be across several parameters, depending on the granularity required), so the more accurate and comprehensive my knowledge of the check is, the better. 「 ダイノ ガイ 千？！ 」? · Talk⇒Dinoguy1000 01:32, November 30, 2010 (UTC)


 * Yeah, that should do.
 * I just started on reorganising CardTable2's documentation. See Template:CardTable2/doc/Bandai and Template:CardTable2/doc/Capsule Monster Chess for examples. They also cover what's necessary to detect what type of card something is and example pages.
 * I also found a bug while doing the Bandai one.  is used to add an SMW property that identifies something as a Monster Card. But Bandai monsters don't have Attributes, so they're not being picked-up. I think we should change it to   (Maybe throw in the DEF parameters too to be safe.) -- Deltaneos (talk) 01:45, November 30, 2010 (UTC)


 * I'll have a look in a minute, sounds promising.
 * That sounds good. Hearing that, I'm definitely going to be using more than one parameter for identifying a card's categories: so far, I'm thinking one for the overall card game (OCG-TCG/Bandai/DDM/CM/VG/etc.), whether the card is exclusive to that category, and some general card characteristics (at the very least whether a card is a monster/spell/trap/tip-strategy/token/*other division any other card game may use on this level*). I think there's a lot of simplification that could be done if these parameters are handled correctly, with the added bonus of being able to perform a good amount of error checking with minimal effort.
 * For the specific example of Card Category::Monster Cards, don't forget the handful of vg-specific atk and def parameters. We probably don't have to worry about them if we combine the checks, though: . I'll go ahead and add this and the above tweaks for alt* (so that you can immediately start replacing instances of alt* with their regular variants, so we can drop support for them in the sandbox) to CardTable2 and the sandbox. 「 ダイノ ガイ  千？！ 」? · Talk⇒Dinoguy1000 02:45, November 30, 2010 (UTC)

Templates
I don't know if this is the right place to put this, but maybe you can help me. I was trying to make this "http://mfbeyblade.wikia.com/wiki/Metal_Fight_Beyblade_-_Episode_001" look like this ""http://yugioh.wikia.com/wiki/Yu-Gi-Oh!_5D%27s_-_Episode_001" Whoever did those templates on the Yugioh wikia here, could you please help me fix that on mine so it'll display correctly?

Also, how is it that the Yugioh wikia has a "Special:Browse" but my mfbeyblade wikia don't? Shouldn't that be on all wikia's? the Special:Browse thing? DranzerX13 (talk • contribs) 12:41, November 30, 2010 (UTC).

Thank you. Now I understand, hehehe. DranzerX13 (talk • contribs) 13:07, November 30, 2010 (UTC).

That SMW thing is installed, but... can you please fix this:?
 * http://mfbeyblade.wikia.com/wiki/Template:Infobox/Metal_Fight_Beyblade/Episode
 * http://mfbeyblade.wikia.com/wiki/Metal_Fight_Beyblade_-_Episode_001

it still messed up some. DranzerX13 (talk • contribs) 18:21, November 30, 2010 (UTC).

Oh, I forgot something: http://mfbeyblade.wikia.com/wiki/Template:Metal_Fight_Beyblade_episodes/season_1

no matter what I do, it still says  on it. DranzerX13 (talk • contribs) 21:38, November 30, 2010 (UTC).

Any reason why "http://mfbeyblade.wikia.com/wiki/Metal_Fight_Beyblade_Original_Arc" is still like this?

When it should be like this "http://yugioh.wikia.com/wiki/Fortune_Cup" DranzerX13 (talk • contribs) 00:57, December 1, 2010 (UTC).

I don't see how episode 2 and its picture is showing up on original Arc 2. DranzerX13 (talk • contribs) 01:06, December 1, 2010 (UTC).

I added in the has type thing on "http://mfbeyblade.wikia.com/wiki/Property%3AEpisode_number" and "http://mfbeyblade.wikia.com/wiki/Type:Number" I created. Now look at the "http://mfbeyblade.wikia.com/wiki/Metal_Fight_Beyblade_Original_Arc" no pictures. DranzerX13 (talk • contribs) 01:22, December 1, 2010 (UTC).

Re: Featured Cards
I've commented. And I see the problem - some of these new featured card pages really do suck. Runer5h (talk • contribs) 02:51, December 1, 2010 (UTC)Runer5h

Template:Ruby and SMW
Any idea why this is breaking SMW so horribly, and how we might fix it? Ruby would be a vast improvement over ..., from a code readability standpoint, so SMW not liking it is a problem. 「 ダイノ ガイ 千？！ 」? · Talk⇒Dinoguy1000 04:21, December 1, 2010 (UTC)


 * In the factbox at the bottom of the page, the value for "Ruby Text" is has the middle replaced with "..." because it's so long. This results in a closing  without a corresponding opening   messing the page up. -- Deltaneos (talk) 12:53, December 1, 2010 (UTC)


 * Regarding fixing, maybe we should report it as a bug. The new skin doesn't have the factbox and doesn't break when HTML tags are missing like that, so it's not a problem there. Newer versions of SMW allow you to remove the factbox, which is probably a good idea. It's not something readers need to see. Plus the link to Special:Browse in the sidebar (something the new skin lacks) can be used instead. Although, I don't know if that breaks too with missing HTML tags. -- Deltaneos (talk) 13:07, December 1, 2010 (UTC)


 * I've been trying to come up with some way we could accept a plain-text value for the ruby text and format it for display, while passing the plain-text value to SMW, but without some really interesting StringFunctions (and to a certain extent, even *with* them), I can't really see how it could be done. If we had an actual programming language at our disposal, it would be pretty easy, though.
 * As for a bug report, that would probably be a good idea, though it's hard to say when it would be fixed. I have a Bugzilla account, so I could post the bug I just need to know your thoughts on the best title and description. 「 ダイノ ガイ 千？！ 」? · Talk⇒Dinoguy1000 16:06, December 1, 2010 (UTC)


 * Since you've them applied those font styles to the "rt" tag, isn't the proceeding "span" tag doing the same thing to the same portion of text? So can't the span be removed, avoiding the problem, or can't those styles be applied to rt all tags by editing the Common.css page?
 * By plain text do you mean using something like "(闇)[やみ]より(出)[い]でし(絶)[ぜつ](望)[ぼう]" as the input and what's stored as the SMW value? Then CardTable2 and any page which asks for this value will have to use something to format it as " 闇(やみ) より 出(い) でし 絶</rb>(</rp>ぜつ</rt>)</rp>望</rb>(</rp>ぼう</rt>)</rp> "? I don't really like the idea of needing to apply the formatting to every page that asks for the value. It will mean we'd have to use  in every   that that uses , which will stop us being able to use the tabular format.
 * You might also be interested in this suggestion for ruby text. You might remember it from a few years back.
 * I guess the title of the bug report could be "Factbox creating broken HTML". The description could be Since the middle of long values visible in the factbox are replaced with an ellipsis (...), this can result in broken HTML. For example a value containing "span" tags can have the opening  cut out by the ellipsis and the closing   left visible. This can cause some skins, such as Monobook to break. I think it's also important that you mention which version of SMW you see the problem on. Maybe the internet browser and site too. -- Deltaneos (talk) 19:30, December 1, 2010 (UTC)


 * After doing some research (mostly reading the original and HTML5 specs; there's a shocking paucity of information elsewhere on the internet, compounded by the fact that the annotation shares its name with a popular programming language (which, even more unfortunately, is widely used for web development, making search results that much harder to correctly distinguish without actually reading them)), I was able to simplify Ruby to a certain extent, and it doesn't even break SMW now (check the diff I originally linked). I am currently playing with some styles that might let Ruby render in more browsers than just IE/FF-with-extension, based on http://web.nickshanks.com/stylesheets/ruby.css; do you have any idea what stylesheet Dantman was talking about in the linked discussion (in the meantime, the template should be deployable as-is; I just have to see if has the same problems with Ruby output from the template that they were having with raw Ruby code in the page source)? 「 ダイノ ガイ  千？！ 」? · Talk⇒Dinoguy1000 02:56, December 2, 2010 (UTC)


 * I think Dantman was planning on writing it himself.
 * Is Template:Ruby intended to fix the problem Aeris Ventaile is seeing or to simplify the code for adding ruby text? -- Deltaneos (talk) 20:10, December 2, 2010 (UTC)


 * Its original purpose was to simplify the code, but I'm going to see if I can fix the output of HTML Ruby as well (though, if its output doesn't respond to CSS styling, we'll either have to recommend people not use HTML Ruby in Firefox on this wiki (at least until the pertinent bug is fixed), or change how Template:Ruby works somewhat). 「 ダイノ ガイ 千？！ 」? · Talk⇒Dinoguy1000 23:38, December 2, 2010 (UTC)

Awesome
Hi, I'm sorta new here but I am familiar with Wikia and I am not an idiot XD. I just wanted to say that you are really good at this editing thing and you're sort of a legend on here. Ooh, I want to be legndary too! XD Ok, that's all, bye. YamiYusei1 (talk • contribs) 02:25, December 2, 2010 (UTC)YamiYusei1

Request
Could you please say a few words to the IP contributor 76.89.243.144? For some reason he has been removing the Unofficial name template from a few card articles lately. A case in point is Naturia Leodrake. -- ΜοｎtΕ cｈrísＴο ９5 15:18, December 4, 2010 (UTC)

RE:Ironoid
「アイアン」 "aian" is a common way of translating "iron". Most people (over here in Canada, at least) pronounce "iron" as "ai-ern", which becomes "aiān", which becomes "aian" because people are lazy.

So yeah, "Aianoid" should be "Ironoid". --Deus Ex Machina (Talk) 21:23, December 8, 2010 (UTC)

User page
Hi, Could you please delete my User Page? Thanks. <font face="TimokU Italic" color="#330033">2X☆∞ | <font face="Viner Hand ITC" color="#00ccff">GUESS WHO?!  <font face="Onyx" color="#46 82 B4">IT'S T.S.!  11:37, December 9, 2010 (UTC)


 * Done. 「 ダイノ ガイ 千？！ 」? · Talk⇒Dinoguy1000 16:15, December 9, 2010 (UTC)

Problem with Machine Emperor
That new user seemed to be an idiot for changing the fourth Emperor into more religious insult name. Why not fixing that page back to normal? -- F  red  C  at  Ta.P. • F.P. • J.R. • W.S. • Th.P. • S.C. 04:19, December 10, 2010 (UTC)