PropertyValue
rdfs:label
  • WoWWiki talk:Village pump/Archive18
rdfs:comment
  • Few things have been fixed/added throughout the site, such as the possibility to show/hide tables (see {{Navigation Box}}), or the preferences page. Hope you like them! -- 01:11, 24 July 2007 (UTC) In addition to the extensive CSS work (feedback and suggestions please!), I have altered a few Main Page links slightly, with Reputation and Warcraft Universe now appearing. The latter needs a fair bit of link work, whilst one page it links, Quotes of World of Warcraft, is weird to say the least. It repeats a massive amount of info from flirts and jokes. One other quick thing - how should tables be changed? Atm they appear as:
dcterms:subject
dbkwik:wowwiki/property/wikiPageUsesTemplate
abstract
  • Few things have been fixed/added throughout the site, such as the possibility to show/hide tables (see {{Navigation Box}}), or the preferences page. Hope you like them! -- 01:11, 24 July 2007 (UTC) In addition to the extensive CSS work (feedback and suggestions please!), I have altered a few Main Page links slightly, with Reputation and Warcraft Universe now appearing. The latter needs a fair bit of link work, whilst one page it links, Quotes of World of Warcraft, is weird to say the least. It repeats a massive amount of info from flirts and jokes. One other quick thing - how should tables be changed? Atm they appear as: ... and should probably be altered to fit better with the colour scheme. A darker background perhaps? For comparison pre (large code block) tags use #2c2c2c, whereas darktable (nav tables) uses #202020. 01:59, 24 July 2007 (UTC) Actually, I'm tempted to remove the default bg colour from tables entirely, since it doesn't actually help (and messes with certain other elements, such as categories). 03:48, 24 July 2007 (UTC) More tweaks made! I have yet to do anything with table bgs yet, asi want to see what stuff breaks with the change. The only stuff I have come across so far is some info tables on zones, e.g. Elwynn Forest, which need converting to new-style tables anyway. 18:27, 24 July 2007 (UTC) nav boxes, like stuff derrived from {{Navigation Box}}, don't actually use darktable... they need converted over. 03:34, 24 July 2007 (UTC) As a very minor nugget of info: CSS 2.1 has a color shortcut, where you type #rgb and it's expanded to #rrggbb - that means something like #fc2 will expand to #ffcc22, not #f0c020. So maybe when picking widely used colors, stick to that convention, (meaning change both to #222222). Of course, it's safe to assume most people reading this wiki aren't on ancient 8-bit color displays. But it doesn't hurt to be "accessible" to some degree. Further reading: [1] --Piumosso-Uldum 04:20, 24 July 2007 (UTC) You might want to remove the "google ads" line from above the "Wiki Spotlight" box in the nav column on the left. - 19:53, 25 July 2007 (UTC) Yeah, I have mentioned it to those who can change it. I hate that sidebar anyway, in my own CSS it has no borders or backgrounds. 20:05, 25 July 2007 (UTC) Another quick change - tables now have no background by default, so you may find tables that need a background defined. The only one's I came across in testing were on zone pages (e.g. Westfall), but those tables need redoing anyway. 17:07, 27 July 2007 (UTC) I need a styling opinion on class boxes. Some classes shouldn't have an issue with background coloring. Paladin, mage, rogue, and priest are exceptions, due to their light class color. For the paladin I feel like I got a good color. Further, someone might want to set up alternating background colors for some lists (I'll do my best on the paladin ones. See Paladin and comment on the color choice. Modify at will in mediawiki:common.css. Use your favorite color picker, but the one I found with little searching, which is good enough for me, is ColorPicker 3.1. I've also changed essentially all the templates that call Template:listboxformat so that they're properly classed. Some of the times I invented a new class in the middle of it, so not all similar boxes have the same classing scheme throughout. That's pretty easy to fix, and will come out in the wash I suspect. It is my opinion that many similar templates should be classed similarly (in the relevant way) so that even if their class isn't described in the CSS at the moment, in the future you will be able to describe them all in one swoop, and they'll all match in their own way. It could take a lot of work to manage that now, but for future reference.... Schmidt 16:42, 7 August 2007 (UTC) Great work! 18:07, 7 August 2007 (UTC) I came home and my brother's computer was on NFL.com. He's a Dallas fan, so it was open to the box scores for their preseason game. I found it interesting that their rookie kicker Nick Folk made a 52-yard FG and Grammatica missed a 51-yarder. In any case, I noticed that when you mouseover a stat row on Martin Grammatica's page the entire row takes a different class. I know that it can't be that hard to manage with coding. (onmouseover="this.className='over'" onmouseout="this.className=''") I looked at the source and it's pretty basic, but I was wondering if we could manage to set something up somehow where we could have built-in coding...somehow...yeah. I don't know how it could be pulled off other than the obvious (which would be to code that in for each row), but I wonder if you crazy bot-writing people could jerry-rig something in that regard. Further, is this something that anyone would be interested in implementing for generalized styling? If so, and if no other coding would help, I suppose we could write a template that would allow a row to be formatted with one class normally, and if it was moused over, it would take an alternate class. The main class and the mouseover classes should be user-selectable with the call to the template. Or possibly (not sure about this), maybe we could define some such as: .paladin {...} .paladin:hover {...}, eh? Anyone know? Schmidt 23:42, 19 August 2007 (UTC) And I've added warlock and mage colors to the CSS. See user:D. F. Schmidt/Sandbox for a test version of the nav table. I'll work on more class colors as I find the time and energy. Comments on color formatting are welcome, as well as whether or not these colors (even if otherwise adopted) should be found in the classnav table. Schmidt 06:44, 20 August 2007 (UTC) Ok. I added all the class colors with the obvious exception of Death Knight. Take a look at my sandbox as above. The class colors could use some tweaking, and I don't mind it one bit. I tried to keep all the colors used within the realm of the class color. Obviously rogues and priests are especially tricky on that part. For priests I just made them silverish; rogues are even more tricky than that because yellow doesn't translate well into darker colors. In any case, I would like it if class pages and especially tables that are associated with a given class use these colors (not these specific colors, but class coloring as such), but I don't think I can enforce that to any extent greater than just an expression of wish. Schmidt 13:41, 20 August 2007 (UTC) Yeah, I don't think class coloring to that extent really flows well with the coloring of the wiki. If you hadn't noticed, the wiki is a dark grey background with very dark hues of the other colors. Especially, using bright pink for the paladins won't work. Maybe for accent, but not for the entire table. I think the second dispel example on your sandbox might be best. --Pcj (T•C) 13:07, 23 August 2007 (UTC) As if I hadn't noticed that. I was, after all, designing the colors according to a foreground of white text. I did a pretty good job of selecting colors, I think. I could have done a little better obviously, or--better yet--someone else could have suggested a color or two in response, and even better still, someone else could have come up with a better color right off. In any case, well... whatever. Schmidt 07:26, 25 August 2007 (UTC) Agreed, the last dispel table looks ok, the others are a bit excessive on color. -- 15:07, 23 August 2007 (UTC) Alright, so I guess we can just have one such definition for class box elements, meaning no alternate colors for alternating lines. That works, and it makes it better really, since if the alt colors as they are now are the main colors, it'll match the dark overall scheme better. Alright, when I get to it, I'll change it if no one else has yet. I do agree, but I wanted to check it out anyways. Schmidt 07:17, 25 August 2007 (UTC) Priest alternate row color was badly defined anyway. --Pcj (T•C) 21:27, 27 August 2007 (UTC) I challenge you and anyone else to present a suggestion that someone might have made as to what color these elements should take. (I never said they were the best colors, but the best I could do with my limited design experience.) After all, what is a wiki for, anyways? Schmidt 08:44, 28 August 2007 (UTC) By badly defined I mean it was an invalid number being passed in the CSS entry. You seem to have left off a digit. --Pcj (T•C) 12:04, 28 August 2007 (UTC) You should make the ".paladin a, .paladinalt a" definition white in my opinion, pink on pink looks terrible. --Pcj (T•C) 18:30, 2 September 2007 (UTC) So we have JS... the big question... when are we getting Wowhead-provided hover tooltips for {{loot}}? 07:34, 25 August 2007 (UTC)