No edit summary |
No edit summary |
||
Line 54: | Line 54: | ||
Each set has to be inputted to the template, but the data and formatting will be provided automatically. It will still have the consistency, and still use the best information from the set page, but most importantly, it won't be so buggy, because of the reduced querying. I shall start working on a demo. {{User:UltrasonicNXT/Signature}} |
Each set has to be inputted to the template, but the data and formatting will be provided automatically. It will still have the consistency, and still use the best information from the set page, but most importantly, it won't be so buggy, because of the reduced querying. I shall start working on a demo. {{User:UltrasonicNXT/Signature}} |
||
+ | |||
+ | {{ThemeTable/renovations |
||
+ | |30140 ADU Walker |
||
+ | }} |
Revision as of 23:51, 4 November 2012
- ThemeSet seems to work fine
{{#ask:[[InfoboxTemplate::Set]][[Type::Set]][[Category:Alien Conquest]] |?Released }}
Sorry, - nxt
{{ThemeSet|30140 ADU Walker}} |
||||||
30140 | ADU Walker | 34 | ADU Computer Specialist | 2011 |
- Straight query just for release date works fine
{{#ask:[[InfoboxTemplate::Set]][[Type::Set]][[Category:Alien Conquest]] |?Released |format=template |template=ThemeSet }}
- Is a problem.
... ok, I've gone blank. There was a point to this, ssaving anyway so I might remember sometime :) NightblazeSaber 09:02, November 3, 2012 (UTC)
A proposal
Y'know, I've never actually liked the themetable templates (although I admit they do have some advantages)... The minifigure one is unreliable, and the ones for the sets are constantly glitching in one way or another, with this only really being the latest in a long line... I'd be all for getting rid of them entirely, and going back to manual again. Heck, I can do all the work myself if you want- I've got some free time. :P -Cligra Join the redlink war!
- I also dislike them. I wouldn't want to update them manually myself, but if someone else is willing too. :P --Berrybrick (Talk) 21:09, November 3, 2012 (UTC)
I have had a think about this, and have come up with a solution. ThemeTable was created for 2 reasons: consistency, and because the set page tends to have the best info in the infobox. The problem is the 2D sematic query (a query querying another query). If I could reduce this to a set number of simple queries, it would work fine. And I can. This is what the new code would look like:
{{ThemeTable |1234 Set |2345 Set |3456 Set |4567 Set }}
Each set has to be inputted to the template, but the data and formatting will be provided automatically. It will still have the consistency, and still use the best information from the set page, but most importantly, it won't be so buggy, because of the reduced querying. I shall start working on a demo. - nxt
Image | # | Set | Number of pieces | Minifigures | Price | Release |
---|---|---|---|---|---|---|
30140 | ADU Walker | 34 | ADU Computer Specialist | 2011 |