Template talk:Infobox RF producer

Hey, I'm not sure if you're already aware, but Infobox already has a  parameter you can use for RF producers. 18:11, 23 July 2016 (UTC)
 * Also I'm curious as to what was broken on the pages when you attempted to add RF stuff to engine (which needs to be done, right now the RF pages are pretty bleh because of the lack of RF params). I tested it in my sandbox and it looked fine. --  Satanic Santa 🎅F T B Wiki Admin 19:24, 23 July 2016 (UTC)
 * I was aware and was using that, but that statistic is under the heading "Energy Consumption" in infobox...which doesn't make sense when RF output is the only statistic. In Infobox engine the javaScript collapses rows for which no values were provided after the infobox is first rendered in the browser. On the page where I started using Infobox engine, the JavaScript stopped working, or was very slow to collapse those rows, so I reverted so as not to upset the apple cart. While working on Infobox multiblock I discovered a better technique so that the rows are collapsed by the CSS before the Infobox is ever rendered. I like Infobox engine and will deprecate this in favor of engine and revamp engine in the process. Agreed? This whole thing today has been an iterative process. --  ScottKillen  [ ⌨ ] 03:56, 24 July 2016 (UTC)
 * Perhaps we should rename the "Energy Consumption" heading to "Energy Statistics" so it can cover both producers and consumers. 04:21, 24 July 2016 (UTC)
 * That is kind of stupid, about the Energy Consumption. Perhaps that should be renamed to "Energy", or "Energy Usage", or something. I don't really know about the JS/CSS of infoboxes, so I won't comment on that. I am in favor of Infobox RF producer being merged into engine, and if improving engine means it has better performance, I'm in favor of that. As long as it still works exactly the same, so no pages are broken (or a bot is written to fix it all). --  Satanic Santa 🎅F T B Wiki Admin 04:23, 24 July 2016 (UTC)
 * I will fix it, meaning it will work better and look the same on all pages that use it now. Engine is fairly simple. The JS problem is only noticeable on slow computers like mine... :) -- ScottKillen  [ ⌨ ] 04:29, 24 July 2016 (UTC)
 * Was also thinking today,, that embedding categories in the various infoboxes could help with your project. Maybe? -- ScottKillen  [ ⌨ ] 04:32, 24 July 2016 (UTC)
 * I've been thinking that too lately. Same with navboxes. --  Satanic Santa 🎅F T B Wiki Admin 04:43, 24 July 2016 (UTC)
 * Might be difficult with everyone using the generic catch-all infobox, but for the custom infoboxes would work. -- ScottKillen  [ ⌨ ] 04:46, 24 July 2016 (UTC)
 * Well it would be dependent on the parameters you give it, I'd imagine. Like if you set the rfoutput, it would categorize it as Energy Producer and RF Power or whatever. --  Satanic Santa 🎅F T B Wiki Admin 04:49, 24 July 2016 (UTC)
 * I've been in favor of removing Infobox engine for the regular Infobox... that's why the BuildCraft pages no longer have them... -Xbony2 (talk) 10:18, 24 July 2016 (UTC)
 * Then lets look into changing that "Energy Consumption heading into something more sensible. -- ScottKillen  [ ⌨ ] 11:59, 24 July 2016 (UTC)
 * hmm -Xbony2 (talk) 12:50, 24 July 2016 (UTC)
 * I set it to "Energy". It doesn't feel right, but to be honest I think it's just because I'm used to "Energy Consumption". Oh well. I'm opposed to "Energy Usage" because that's kind of a synonym. -Xbony2 (talk) 12:57, 24 July 2016 (UTC)