Forum:Simplifying all infoboxes

From the RuneScape Wiki, the wiki for all things RuneScape
Jump to: navigation, search
Forums: Yew Grove > Simplifying all infoboxes
This page or section is an archive.
Please do not edit the contents of this page.
This thread was archived on 1 January 2011 by Cook Me Plox.

I developed a small change for infoboxes, which makes filling it in a little easier. This is because it doesn't require to fill in a release date anymore. For example, when we replace the current code in Template:Infobox Item:

| {{#if:{{{release|}}}|{{{release}}} {{#ifeq:{{{release}}}|Not released||{{#ifeq:{{{release}}}|RuneScape Classic||{{#if:{{{update|}}}|{{#ifexist:Update:{{{update}}}|([[Update:{{{update}}}|Update]])|(Update unknown) <small>[{{fullurl:{{FULLPAGENAME}}|action=edit}} edit]</small><includeonly>{{Mainonly|[[Category:Needs update added]]}}</includeonly>}}|(Update unknown) <small>[{{fullurl:{{FULLPAGENAME}}|action=edit}} edit]</small><includeonly>[[Category:Needs update added]]</includeonly>}}}}}}|Unknown <small>[{{fullurl:{{FULLPAGENAME}}|action=edit}} edit]</small>}}

with this code i developed:

| {{#ifeq:{{{release}}}|Not released|Not released|{{#ifeq:{{{release}}}|RuneScape Classic|[[RuneScape Classic]]|{{#if:{{{release|}}}|{{{release}}}|{{#if:{{{update|}}}|{{rmv|'''|{{#explode:{{#explode:{{Update:{{{update}}}}}|on |1}}|.|0}}}}|Unknown <small>[{{fullurl:{{FULLPAGENAME}}|action=edit}} edit]</small>}}}} {{#if:{{{release|}}}|{{#if:{{{update|}}}||(Update unknown) <small>[{{fullurl:{{FULLPAGENAME}}|action=edit}} edit]</small><includeonly>{{Mainonly|[[Category:Needs update added]]}}</includeonly>}}|}}{{#if:{{{update|}}}|{{#ifexist:Update:{{{update}}}|([[Update:{{{update}}}|Update]])|(Update unknown) <small>[{{fullurl:{{FULLPAGENAME}}|action=edit}} edit]</small><includeonly>{{Mainonly|[[Category:Needs update added]]}}</includeonly>|}}}}}}}}

It won't need a release parameter filled in, but still has the option to do so (for cases like Christmas cracker) and all other options of the current code are preserved. The code given above could be added to all infoboxes, which automates them all.

The code that detects the date in the update page is
{{rmv|'''|{{#explode:{{#explode:{{Update:{{{update}}}}}|on |1}}|.|0}}}}
For example, for the Update:Dungeoneering Skill! the result with the above code is: {{rmv|'''|{{#explode:{{#explode:{{Update:Dungeoneering Skill!}}|on |1}}|.|0}}}}

I don't see why this, which only reduces work, should not be used, and the only reason i wasn't bold is because of the thing at the top of some infoboxes. (not so an admin has to change it, i'll do it if needed)

Examples could be found [[User:Joeytje50/Autodate#Examples|here]]


Support - As nom JOEYTJE50TALKpull my finger 19:40, December 28, 2010 (UTC)

Changed to Oppose per below. JOEYTJE50TALKpull my finger 00:25, January 1, 2011 (UTC)

Question - As far as I can tell, this fetches the release date if it sees the name in update text. Am I right? If no, please explain how this works. If yes, what is it going to do if something is mentioned in two different update texts? bad_fetustalk 19:44, December 28, 2010 (UTC)

Nevermind, I really need to read carefully before commenting. bad_fetustalk 19:45, December 28, 2010 (UTC)
Although you understand it now, i'll explain it for the people who don't: #explode gives the thing after the xth specified character in the input text. So in this case, it searches for the text after the first "on " and, as it also had another #explode around it which searched for the text before the first . (as 0 is before the first, duhLol) in the already fetched text(which would be the date and everything after that until another "on ") so the first . would be directly after the date. Therefore, it only fetches the date. As it already has a link around it, that doesn't need to be added, and as it is bolded, it only needs {{rmv|'''|fetched date}} around it to remove the bold and you have the date.  —The preceding unsigned comment was added by Joeytje50 (talk).

Support - Don't see why not. bad_fetustalk 19:45, December 28, 2010 (UTC)

Supprot - I hate those dates... User_talk:Fswe1 Fswe1 Brassica Prime symbol.png 13:30, December 29, 2010 (UTC)

Why? This proposal is not to remove the dates. ʞooɔ 01:44, December 30, 2010 (UTC)
I know, but if I don't know the (up)date (almost always), I can leave it blank and it would look neater. User_talk:Fswe1 Fswe1 Brassica Prime symbol.png 07:41, December 31, 2010 (UTC)
But if you do not fill in the release date (which someone nearly always does), it will say "Not released", which is not true at all. ʞooɔ 09:23, December 31, 2010 (UTC)

Support - Well, this saves quite a bit of work, so I'm all for it. --LiquidTalk 17:31, December 29, 2010 (UTC)

Support Oppose - Um yea. The current system works fine and apparantly "it's all wrong" (Cook) 222 talk 00:05, December 30, 2010 (UTC)

Comment - Why would we want it to say "eering update players"? I'm confused. Anyway, I don't see the need to fix what isn't broken, as I think we already have them all filled in that we know. Seems overly complicated, and the current system we have doesn't seem to be causing any problems. I guess I just don't really see the point. ʞooɔ 00:25, December 30, 2010 (UTC)

"Why would we want it to say "eering update players"? I'm confused." thats because it used to work, but someone broke the template. And it is not causing any problems, but is can be made simpler. Its not broken, but... w8 example here: A bronze dagger is not broken. It works perfectly fine. But you can make it easier to kill monsters if you got a whip/gs or something. It is not broken, but it is possible to make it easier.
Also, I don't like just saying "RuneScape Classic" as a release date. It's not precise and we can do better (and often have; nearly all of the RSC items have release dates from their actual release.) ʞooɔ 01:45, December 30, 2010 (UTC)
The current infobox also has this. I just moved over what is currently there. We could as well remove it ok? Its not my fault someone else added it, and i just kept it available. If i would not have moved it over you would probably have said "but some functions of the old templates will be inavailable" so i just moved it over. But this is not about rsc as release date, but about automating it. JOEYTJE50TALKpull my finger 14:00, December 30, 2010 (UTC)

Oppose - Unless I'm missing something major, I think this will be more work. The three main points:

  • Not released - Just because we don't have the release parameter filled in that doesn't mean that it's not released. Look at Category:Needs release date.
  • RuneScape Classic - What I said above. We can do better than just saying that. It's like saying that Dragon defenders are from RuneScape 2.
  • Explode-y stuff - Seems useless to me. More work, in addition to other things. We don't need to make everything automated, and if we do this we will need to remove update from nearly all of the infoboxes. We already have the Release + Update for (I think) over 6000 things, and there are none of them that I know of that have the update parameter but not the release parameter. If there are ones that do, it would be so much easier to just add it to those. Yes, it would make things more automated in the future, but it's not worth the hassle now. ʞooɔ 02:00, December 30, 2010 (UTC)
Apparently you are indeed missing something major, as I just imported the current system, and it doesn't cost any work removing any parameters, as all parameters will keep working.
  • Not released - This is the same as the above: it has been imported from the current use. Also, things that are not released yet should have "not released" in the infobox. But again, this is not what we are discussing.
  • RuneScape Classic - What I said above. I just imported it, and this is not what we are discussing about. Its about automating it.
  • Explode-y stuff - Its absolutely 0.0 hassle as the release parameter will still be available. It won't need to be removed, but just in the future it doesn't need to be added. It works perfect with either of the methods, as seen in [[User:Joeytje50/Autodate#Examples|the examples]] i gave. JOEYTJE50TALKpull my finger 14:00, December 30, 2010 (UTC)

Strong oppose - per Cook, we've done most of the work. LordDarkPhantom 09:50, December 30, 2010 (UTC)

And it just reduces any future work. JOEYTJE50TALKpull my finger 14:00, December 30, 2010 (UTC)
By an incredibly minute amount, at the cost of transcluding an extra page. ʞooɔ 09:23, December 31, 2010 (UTC)

Oppose - While I don't doubt the technical ability to work, I don't think we really need it. Practically every date is added where the update is, and where its not its but a mouseclick away (that includes future releases). In addition, it would involve transcluding a page onto every use of the infoboxes - which is most of the pages on the wiki. Frankly I'd rather not put that much extra burden on Wikia's already pathetic servers unnecessarily. Quest.png Gaz Lloyd 7:^]Events!99s 15:10, December 30, 2010 (UTC)

Doesn't it just get the date off the page? JOEYTJE50TALKpull my finger 16:03, December 30, 2010 (UTC)
You're still transcluding the entire page to do that. Quest.png Gaz Lloyd 7:^]Events!99s
So in fact it loads 2 pages for the one page then? JOEYTJE50TALKpull my finger 07:29, December 31, 2010 (UTC)

Oppose - Per Cook. After looking over the code, it has some hard-coding and does not find the data in an efficient manner. Farming cape (t).png Lil cloud 9 Talk 15:31, December 30, 2010 (UTC)

Oppose - The work its meant to save has already been done, and it adds a lot of extra loading time to pages as it needs to also load all the data stored in the update pages to automatically find the date. kitty.pngPsycho Robot talkSilver bar.png`

Comment - I withdraw my nomination, because I thought it would not have to load 2 pages for the price of 1. I don't know if it can be closed now, even if there is support other than the nominator, but I now Oppose too. This does indeed cost too much loading time then. JOEYTJE50TALKpull my finger 00:25, January 1, 2011 (UTC)

Closed - Nominator withdrawal. ʞooɔ 01:41, January 1, 2011 (UTC)