Talk:Incarnate Thread Component

Missing Section

The "Used In" section is missing recipes for Commons (20 threads each, yes?). It appears to be a problem with the templates, but I don't like to fiddle with templates, so I'm leaving it alone and hoping someone will read this and fix it.Haecceity 18:34, 15 January 2012 (UTC)

Turns out those particular templates required a lot of fiddling... but it's fixed now! -- Sekoia 09:44, 16 January 2012 (UTC)

How to Get

Is there anyway that we can make the various "How to Get" sections look cleaner? Something like this, maybe:

Threads	From Item:
5	10 Incarnate Shards
10	10 Incarnate Shards and 1,000,000 inf (usable only once every 20 hours)
4	1 Astral Merit
20	1 Empyrean Merit
40	1 Notice of the Well
100	1 Favor of the Well

—Thirty7 14:18, 26 January 2012 (UTC)

Oh, I think we could probably put something together pretty easily to do that. I'm thinking along the lines of the tables in the articles for each power set. Maybe something like:

{{ThreadGet_Start}}

{{ThreadGet_Row|threads=5|component={{IComponent|Incarnate Shard|10}}}}

{{ThreadGet_Row|threads=10|component={{IComponent|Incarnate Shard|10}} and 1,000,000 [[inf]]<br />(usable only once every 20 hours)}}

{{ThreadGet_Row|threads=4|component={{IComponent|Astral Merit|1}}}}

{{ThreadGet_Row|threads=20|component={{IComponent|Empyrean Merit|1}}}}

{{ThreadGet_Row|threads=40|component={{IComponent|Notice of the Well|1}}}}

{{ThreadGet_Row|threads=100|component={{IComponent|Favor of the Well|1}}}}

{{ThreadGet_End}}

Alternately, we could define the template to just accept the arguments without identifiers if that's not potentially too confusing:

{{ThreadGet_Start}}

{{ThreadGet_Row|5|{{IComponent|Incarnate Shard|10}}}}

{{ThreadGet_Row|10|{{IComponent|Incarnate Shard|10}} and 1,000,000 [[inf]]<br />(usable only once every 20 hours)}}

{{ThreadGet_Row|4|{{IComponent|Astral Merit|1}}}}

{{ThreadGet_Row|20|{{IComponent|Empyrean Merit|1}}}}

{{ThreadGet_Row|40|{{IComponent|Notice of the Well|1}}}}

{{ThreadGet_Row|100|{{IComponent|Favor of the Well|1}}}}

{{ThreadGet_End}}

And the names of the templates are, of course, subject to change if anyone has any better suggestions. :)

Note that I intentionally did not assume that we would want the IComponent template calls to be assumed due to the info in that second row. --Eabrace 15:59, 26 January 2012 (UTC)

After some further thought, we could name the templates IComponentGet_ instead of ThreadGet_ and add a parameter to the _Start to specify what you're converting to (e.g. Threads, Arcane Cantrips, Favor of the Well) if we want something that could be used for more than just threads.

{{IComponentGet_Start|Threads}}

{{IComponentGet_Row|5|{{IComponent|Incarnate Shard|10}}}}

{{IComponentGet_Row|10|{{IComponent|Incarnate Shard|10}} and 1,000,000 [[inf]]<br />(usable only once every 20 hours)}}

{{IComponentGet_Row|4|{{IComponent|Astral Merit|1}}}}

{{IComponentGet_Row|20|{{IComponent|Empyrean Merit|1}}}}

{{IComponentGet_Row|40|{{IComponent|Notice of the Well|1}}}}

{{IComponentGet_Row|100|{{IComponent|Favor of the Well|1}}}}

{{IComponentGet_End}}

--Eabrace 16:36, 26 January 2012 (UTC)

If we are gonna make a template to do this, then I think that last option is the way to go... adaptability and multitasking Templates are a good thing. Also makes it easier to promote consistency among articles. : Approved! —Thirty7 21:50, 26 January 2012 (UTC)

Also, I have been meaning to ask this... when we are creating templates that make tables, why is it that we define a template to end the table when "|}" could work just as well... and be shorter? —Thirty7 21:53, 26 January 2012 (UTC)

>.> you want to template it.. we have 2 merits that can be converted into threads right now, with 2 more on the way.. --Sleepykitty 00:17, 27 January 2012 (UTC)

Has it been confirmed that those Merits are actually gonna be used? —Thirty7 01:24, 27 January 2012 (UTC)

<.< will be used? yes, break down into anything in the current incarnate bits... err... >.> --Sleepykitty 02:05, 27 January 2012 (UTC)

I can think of two possible reasons behind using a template to end a table. The first is that it might be clearer to someone unfamiliar with wiki syntax; nothing else in the series of template calls uses table syntax, and then suddenly there's this weird "|}" at the end... "what is that for?". As opposed to something like "{{IComponentGet_End}} which semantically states what it's doing instead of using a cryptic symbol. The second reason is that if we ever change the implementation of the set of templates, "|}" may no longer be a suitable closing for it. Perhaps we'll decide someday to do it with divs. Or perhaps we'll decide to add a table footer to all of the tables. Using a template allows us to more easily make such changes should we decide to later. That all said... I don't find either reasoning all that compelling most of the time and we're far from consistent on the matter. -- Sekoia 09:05, 27 January 2012 (UTC)

It's somewhat moot since it's already addressed by reasoning of the second row of the table as Eabrace said, but... We wouldn't be able to do away with the calls to IComponent without some serious reworking of the DPL-based stuff that depends on them. Those calls expect that the IComponent template call be on the article page. DPL doesn't transclude all the templates to see where it might encounter things through various iterations of transclusion; they have to be in the article directly for it to make use of them. -- Sekoia 09:12, 27 January 2012 (UTC)

On further reflection... Where else would we use these templates? Looking at Ancient Texts Component for example, the table above doesn't suit. The first column would all be ones, and the column heading would be really really long given that everything else in that column would be ones. I think that the Incarnate Threads are a special case. Many of the other articles wouldn't benefit from a two-column layout. (Unless I'm missing something, of course.) It would be excessive to create a system of templates for just one or two articles, I think. Especially when the corresponding wikicode is just a basic table styled with the standard wikitable styling. -- Sekoia 09:21, 27 January 2012 (UTC)