Talk:Item display transition to CSS


 * I am not opposed. Sounds like you know what are you doing. --Cru121 (Contributions • Message) 02:33, January 17, 2014 (EST)


 * I'm a tad late, but for the record, I'm certainly in favor of separating content from presentation. Aldyron (Contributions • Message) 09:39, January 28, 2014 (EST)


 * That's not exactly accurate Joe. We employ &lt;css&gt;&lt;/css&gt; on DDOwiki which allows you to define the classes once at the top of the page (or anywhere really) for the whole page or template. (See [ this example of how it is used] if you are interested. ShoeMaker (Contributions • Message) 17:58, January 28, 2014 (EST)


 * Very neat, indeed. I wasnt aware that that extension existed, much less was installed here. I'll do some testing in my test environment to find out order of precedence for attributes defined in various locations.
 * I definitely am a fan of having a clean / lightweight Common.css, but at the end of the day, I believe giving the user more options to be able to customize is important as well. Joenuts (Contributions • Message) 19:07, January 28, 2014 (EST)


 * I agree with you wholly with having lightweight external stylesheets. Makes for good webdev&apos;ing.  :)  At the end of the day, the order of precedence is exactly how it is handled by all browsers -&gt; (1) Browser Default, (2) External Stylesheets (the link&apos;s in the &lt;head&gt;), (3) Internal Stylesheets (CSS classes and definitions placed in the &lt;head&gt;, (4) Inline Styles.  Style definitions farthest to the right will essentially overwrite those declared to the left on the list.  User defined common.css gets appended to the MW common.css so user defined styles will also overwrite those in the MW file. Ague (Contributions • Message) 19:27, January 28, 2014 (EST)


 * For the record, once I have some free time and everything in RL is more stable and I have internet at home and whatnot, I intend to finish my T:Named Item project. The template actually isn't the only part of that project, but the template part is very similar to what you've started working on Joe. And there is a reason I want to merge all of the various Named foo templates in to one.  The other part of it is every page that uses T:Named Item in the Item: namespace will not use the default edit window.  I've been mentally developing an interactive form ui to be able to edit item properties which should make it a ton easier for standard non-wiki-code-minded people to edit (and give them less options for making messes out of pages.  But, that part of it is still a bit down the road and I have not decided if I want to do it as an on-by-default JavaScript gadget that registered users can turn off (although there will still be a "raw edit" type option on the page) or as an extension which I would need to get  to install which would give me more backend power to manipulate things.  Once I've had more time to think about it, and work things out, I'll give some more details and see if the majority like the idea.  ShoeMaker (Contributions • Message) 20:02, January 28, 2014 (EST)