Template talk:Navbox/Archive 11

Archive 5

←

Archive 9

Archive 10

Archive 11

Archive 12

Archive 13

→

Archive 15

Parent/child

I would like to clarify something for myself: if I build nested navboxes, is there a way to have all style parameters inherit from the parent? (groupstyle, titlestyle, etc etc). I'm working on something that is far more elegant when using nested boxes, but I'm not sure how to make styles inherit. is foostyle = inherit the parameter? Thanks! Prince of Canada ^{t | c} 06:09, 22 September 2008 (UTC)

I've often felt it would be nice, but as far as I know there isn't. I think you have to do it manually.--Kotniski (talk) 07:17, 22 September 2008 (UTC)

That really sucks. Oh well... Prince of Canada ^{t | c} 07:18, 22 September 2008 (UTC)

AFAIK, there is no universal "inherit" feature for CSS... at best, you would have to list a whole bumch of possible CSS properties, setting them all to inherit, but then that starts presenting issues for browser support (I believe IE has some trouble with the inherit attribute for certain properties/elements, but I really don't know much about it). Alternatively, you could just leave the nested elements unstyled and hope they properly inherit their parent's styles (but, again, the whole browser support thing)... —Dinoguy1000 19:43, 25 September 2008 (UTC)

Rendering (in Firefox?)

Using Firefox, at Recovered Territories I'm seeing the {{Borders of Poland}} Navbox in the middle of the screen, with the table of contents bunched up to the left. In IE I see the Navbox as it should be, at the right of the screen. Is this a known issue? Anything that can be done?--Kotniski (talk) 08:46, 29 September 2008 (UTC)

It floats right for me in Firefox, Chrome and IE — chandler — 09:33, 29 September 2008 (UTC)

Weird, maybe my Firefox didn't load the CSS right or something. Hopefully it will solve itself over time.--Kotniski (talk) 10:05, 29 September 2008 (UTC)

Very likely a CSS issue — I've had it happen to me before. Usually when someone screws something up on the back end. Silly devs! :D --Izno (talk) 12:58, 29 September 2008 (UTC)

Well, it seems to have sorted itself out now. (I'm having problems with the positioning of the [edit] buttons, but that's another story.)--Kotniski (talk) 14:21, 29 September 2008 (UTC)

Optional "namespace" param in Template:Tnavbar

Please respond at this thread. עוד מישהו Od Mishehu 16:25, 26 October 2008 (UTC)

State parameter

The state parameter seems to be quite useful in navboxes when you desire the template to display differently on one article than on others. However, for it to work, you must have "|state = " in the template that is transcluded (e.g. {{Current Iowa Senators}}). Is there any way to adjust the Navbox template such that this functionality will still work in articles even where this parameter hasn't been included in the transcluded template? --Philosopher ^{Let us reason together.} 20:02, 30 October 2008 (UTC)

No. All parameters must be passed explicitely. If one link in the template chain doesn't pass a parameter, navbox will not receive it and use the default value instead. — Edokter • Talk • 21:25, 30 October 2008 (UTC)

Group colours

Is there any way to get the group headings to come up in different colours? I was hoping to be able to mark which parties on this template are members of the governing coalition. Cheers, пﮟოьεԻ 57 17:14, 31 October 2008 (UTC)

Yes. I'll head over there... can you let me know what exactly you're aiming for? [ roux ] [x] 17:32, 31 October 2008 (UTC)

Need help...

Hello! Can anyone tell me why there are large lines between navboxes like on this article? How can I fix them? It is very annoying. Thank You! Richmond96 (talk) 03:11, 6 November 2008 (UTC)

Fixed. When someone transcludes a template by using {{whatever}}, the software pulls everything on the page (apart from stuff wrapped by <noinclude> tags), which includes hard returns. If you look at the last diffs of the navboxes, you'll see I removed a hard return after each navbox template. Cheers. [ roux ] [x] 03:51, 6 November 2008 (UTC)

Collapsing

Did the possibility to collapse navboxes disappear? Cant see it on my favourite navboxes :(.--Kozuch (talk) 16:16, 25 November 2008 (UTC)

I don't think so, I still see the show/hide links on navboxes... have you tried clearing your cache? —Dinoguy1000 19:07, 25 November 2008 (UTC)

Seems like autocollapsing does not work. Look here: http://en.wikipedia.org/w/index.php?title=Zimbra&oldid=253555555 --Kozuch (talk) 00:18, 2 December 2008 (UTC)

I still have no problem with it, those navboxes all expand and collapse just fine for me... perhaps you have Javascript disabled in your browser? Does the show/hide link appear at all for you? —Dinoguy1000 20:54, 2 December 2008 (UTC)

This is really silly - today, suddenly, the "show/hide" links appeared for me again. I use some JavaScript gadgets like Friendly, wikiEd etc. Maybe some of them updating their code could broke/repair autocollapsing for me? I am curious.--Kozuch (talk) 23:06, 18 January 2009 (UTC)

Solved. This comes from Wikipedia:Friendly. When turned on, collapsing dissapears. Will report there...--Kozuch (talk) 13:38, 26 January 2009 (UTC)

Expansion needed

I am working on Category:United States House of Representatives delegations navigational boxes. Specifically, I am doing {{ILRepresentatives}} and {{NYRepresentatives}}. It looks like {{Navbox}} will only handle 20 list/group combinations. This needs to be expanded to about 60 to handle states like New York and California.--TonyTheTiger (t/c/bio/WP:CHICAGO/WP:LOTM) 14:33, 28 November 2008 (UTC)

You should be able to increase it beyond 20 without negative effects by using child navboxes. --Izno (talk) 14:39, 28 November 2008 (UTC)

Do you have any formatting suggestions so that its (I have started the IL one) flag and seal placement are more harmonious with the states with less than 21 districts.--TonyTheTiger (t/c/bio/WP:CHICAGO/WP:LOTM) 17:06, 28 November 2008 (UTC)

• Woah. This isn't an appropriate use for the navbox template. It isn't a directory - it's meant to be used to quickly navigate to related articles. Including a thousand links on one navbox is insanity. I'd advise you to rethink your approach entirely. Chris Cunningham (not at work) - talk 14:08, 2 December 2008 (UTC)

Clarification request Can you point us to a place where there is consensus for creating this type of template and/or explain its purpose? I can see a template like this for a congressional district individually or for a small group (or state in the case of a small state), but for the entirety of a large state, what's wrong with using {{CA-FedRep}}? If used on a representative's page, it could always be supplemented by individual template(s) for that district/set of districts. And it doesn't have a problem with this template. --Philosopher ^{Let us reason together.} 22:24, 2 December 2008 (UTC)

Colors

What are the default colors for the template, like the top and group cells? I can't seem to figure it out. Baltro [ talk ] 03:21, 24 December 2008 (UTC)

Title is #CCCCFF, groupname is #DDDDFF. // roux   03:26, 24 December 2008 (UTC)

Greatly appreciated. Baltro [ talk ] 03:37, 24 December 2008 (UTC)

By the way, when I try using the template on the wikia I'm trying to add it to, the entire table's width is only about 50% of the page width. Do you know what I'm doing wrong/code I haven't added? Baltro [ talk ] 03:41, 24 December 2008 (UTC)

Check MediaWiki:Common.css; it contains all CSS classes for navbox. — Edokter • Talk • 12:38, 24 December 2008 (UTC)

White Line

I'm trying to convert Template:Interludes to use the Navbox template and I've got it mostly ready apart from a white line between the groups and lists. Is there another style I need to set to get it to match the rest?

-- WOSlinker (talk) 10:14, 25 December 2008 (UTC)

There was an inherited border-left attribute, now overridden in the code above, see diff. For added effect, try swapping the background colors in the groupstyle. — Edokter • Talk • 13:32, 25 December 2008 (UTC)

Thanks for the help. -- WOSlinker (talk) 15:36, 27 December 2008 (UTC)

Fix for navbox

As this case reveals, there is some hardcoded border left in the template. These borders should prefereably be replaced with empty cells (the same way the rows are spaced) within Navbox itself. However, I need to do some more research before imlementing (as I didn't write the original code). — Edokter • Talk • 04:06, 26 December 2008 (UTC)

Erm? Got the first bit (up to "in the template"), but not the second bit... --Izno (talk) 08:19, 26 December 2008 (UTC)

I clarified it a bit; Basically I was saying that Navbox itself needs a fix. — Edokter • Talk • 16:13, 26 December 2008 (UTC)

I suspect you're talking about this change that I had to make to ensure that the borders turned out correct on a not-white-skinned wiki? I also had to change the skinning in Common.css on the wiki, which should be directly translatable to mediawiki:common.css with this edit. It's not necessary that all the css be placed in Common, but I figured that would clean up the coding nicely. --Izno (talk) 18:58, 28 December 2008 (UTC)

No, that's not it. Each list cell has a hard-"styled" border to provide the horizontal spacing, which is near-white, no matter the background. I've been trying replacing htose with empty (and skinnable) cells, but that introduces other problems. However, I'm investigating another method to replace the hardcoded colors with a CSS id. — Edokter • Talk • 20:15, 28 December 2008 (UTC)

Fixed WP:TRAN Navbox

I fixed WP:TRAN Navbox so that it doesn't put a </div> at the end. This also involved combining an extra #if block so that fix might be portable to the master Navbox

Roadrunner (talk) 20:30, 27 December 2008 (UTC)

What was the problem (and the fix) exactly? I don't see any box at WP:TRAN. Never mind, I see it. Though I can see no fault in the original code, the extra #if seems redundant indeed. — Edokter • Talk • 22:13, 27 December 2008 (UTC)

Navbox Width

Please, can you fix the width of this navbox template, so it must be 100% of the page, not more. To understand what I am saying, please see this and especially this: I used the instruction (<div style="overflow: auto; overflow-x: scroll; width: 100%;">) to force the family tree inside the navbox to be at 100% of the navbox, but the navbox itself expands! So please, fix the navbox so it doesn't expand more than 100% of the page. Thank you very much. --DrFO.Jr.Tn (talk) 18:18, 28 December 2008 (UTC)

Get rid of purple

I'd like to suggest switching to the same colors used in infoboxes. I.e. light gray and white. I don't think the purple looks that hot, and colors should maybe be reserved for special notices/banners and so forth. SharkD (talk) 06:53, 10 February 2009 (UTC)

You're using IE? --Izno (talk) 12:43, 10 February 2009 (UTC)

I don't see that it would make a different if SharkD were using IE - the lavender colour is the same across other browsers. I'd happily ditch the colouring if a suitable alternative were found - might have a poke about in the sandbox later. Chris Cunningham (not at work) - talk 13:05, 10 February 2009 (UTC)

Purple though? It's almost blue on my display... besides, I don't see a reason to change the color — I.e., his argument boils down to ILIKEIT and mine boils to IDONT. That said, I'd say it keeps with the color of the links well, offsetting the point about special notices in my opinion. --Izno (talk) 18:05, 10 February 2009 (UTC)

The point is that the colour is completely arbitrary, and we've been progressively doing away with that over the last few years on project-wide templates (once upon a time this wouldn't have looked too out of place). I'm not convinced that this template will work without field shadings right now, but it's definitely worth considering. Chris Cunningham (not at work) - talk 18:20, 10 February 2009 (UTC)

I've fiddled with navboxes with zero shading; they're much more difficult to read. Some sort of neutral fill is a really good thing in terms of readability. I hate the purple too. Would it be possible and/or desirable to make the field colours dependent on what theme you're using? E.g. use shades of very washed-out blue for people using Monobook. //roux   18:30, 10 February 2009 (UTC)

Yes, that just needs a line of CSS added to the site's skin. I believe in general we're only really meant to worry about monobook - users of other skins have their own projects to tweak template appearances. Chris Cunningham (not at work) - talk 18:53, 10 February 2009 (UTC)

Note that you are also able to customize the appearance of navboxes in your monobook.css file. 「ダイノガイ千？！」^{(Dinoguy1000)} 19:38, 10 February 2009 (UTC)

Of course; however, the main point of discussion is the changing of the default appearance of the template for the majority of our readers (almost all of whom aren't even logged in, never mind using another skin). Chris Cunningham (not at work) - talk 21:49, 10 February 2009 (UTC)

I know that, but the question ultimately is whether the color really bothers a majority of people, or just a select few individuals. Personally, I quite like the current color scheme, but am perfectly willing to have a look at proposed alternatives. 「ダイノガイ千？！」^{(Dinoguy1000)} 22:18, 10 February 2009 (UTC)

Seconded. We shouldn't change it based on a single of few editors' personal preference. No reader ever complained, and no matter what color is chosen, someone is always going to dislike it. — Edokter • Talk • 15:37, 11 February 2009 (UTC)

How about this? SharkD (talk) 08:04, 11 February 2009 (UTC)

That could certainly work. Chris Cunningham (not at work) - talk 08:54, 11 February 2009 (UTC)

1: The current colours in the navbox template are not at all purple. If you check the actual colour values it uses, or make a screen dump and load the image into an image editing program and use the colour inspection tool of that program, you can see that the colours are exactly blue, that is light blue. Anyone seeing anything else either have a bad monitor (which is all too common today with the LCD screens) or have bad colour vision. So SharkD, you could start by adjusting your monitor since you are seeing purple...

2: I have been making diagrams and templates for Wikipedia for several years now. I have often made examples with different colour intensities and almost always the majority of Wikipedia editors have preferred the more colourful versions. (Often to my surprise since most people seem to want more colours than I want.) I have gotten the same results when I have tested it on friends who are not Wikipedia editors. Usually they prefer versions much more colourful than the current version of the navbox. And as you can see if you look around, almost always when people and projects set other colours for the navboxes they use stronger colours, not less colours.

3: I myself would find it very boring if the navboxes were only grey. I find the current light blue colours to be subdued and slightly boring, thus "official looking", which perhaps is fitting for an encyclopaedia. Although I know most people I know think that Wikipedia doesn't have too look strict and official.

4: And to avoid misunderstandings: I did not code this template and did not choose its colours, but I think it is pretty good as it is.

--David Göthberg (talk) 17:05, 11 February 2009 (UTC)

Whatever. It looks like lavender to me, and lavender's color code is #e6e6fa--not far off from the template's color of #ccccff. SharkD (talk) 17:37, 11 February 2009 (UTC)

It probably looks like something different than blue due to some of the background being slightly tinted towards the light blue side and the text in the navbox being more purple. The color scheme may not seem that great until you look at some alternate color schemes and actually use them live, not just a test in a sandbox. This particular color scheme was chosen because it was the least disliked, if I remember correctly. The links show up well in this scheme, as do already followed links, and bold and italic text are easy to detect with this color scheme, and the alternating background striping melds well. It doesn't stick out and it doesn't blend in, which is the purpose it is supposed to serve. Don't change just to change. This scheme is just fine, unless you have results from a controlled experiment showing otherwise. ;) Rgrds. --Tombstone (talk) 18:52, 11 February 2009 (UTC)

FYI: the pale blue colours in the template are #ccf and #ddf (hexadecimal RGB colour triplets). Both are pure light blues (it's not purple, or violet, unless there's more red than green). If it looks purple to you, then maybe your monitor settings are maladjusted. —Michael Z. 2009-02-14 06:25 z

For the record, my userpages, which use #EAF0FF, have more green than red, but still appear vaguely purple on some monitors I've used (not my own, of course). When we consider what colour we're talking about, it's useful to note that the proposed grey configuration will probably look more-or-less the same on most monitors regardless of a certain amount of calibration error. While I personally prefer the status quo, there may be good reasons for switching to a duller appearance. {{Nihiltres|talk|log}} 15:55, 14 February 2009 (UTC)

The colour used as default is called periwinkle, and is defined as being somewhere between blue and violet. It's not pure blue, it's more like a light indigo. -- Jsdo1980 (talk) 20:52, 19 March 2009 (UTC)

HTML Tidy requirement

It seems pretty unfortunate that I had to turn HTML Tidy on to be able to use this template on another MediaWiki install. I'm a template noob, and it all looks very complicated... is it just too much work to fix this? JoshDuffMan (talk) 02:03, 16 February 2009 (UTC)

Did you take a look at WP:TRAN? Templates there (including Navbox) don't need Tidy to be turned on. kazu (talk) 15:50, 17 February 2009 (UTC)

Is this noted in the documentation here? It would be good to prominently announce "if you're looking to transwiki this for personal use, go here". 「ダイノガイ千？！」^{(Dinoguy1000)} 21:34, 17 February 2009 (UTC)

That's amazingly useful, thanks kazu. And I like Dinoguy1000's point - it would be nice if there was a note on the templates so that Wiki n00bs like me would know what was up. It took a lot of searching just to find out that I needed to turn on Tidy to get some of the Wikipedia templates to work. JoshDuffMan (talk) 22:11, 19 February 2009 (UTC)

I've added a note to the documentation intro about transwikiing the template. Feel free to move or adjust it if necessary. (and a thought just occurred to me... WP:TRANS could develop a template expressly for transcluding onto templates they have a version of to add a note or something to that effect, to save local editors this trouble) 「ダイノガイ千？！」^{(Dinoguy1000)} 18:31, 20 February 2009 (UTC)

New navbox design

I've been working on a navbox design based on the "Today's featured article", "In the news", etc. boxes on the main page. I thought I'd share it to see what you think. The first version uses the green color scheme. SharkD (talk) 03:30, 22 February 2009 (UTC)

I dunno, the NavFrame class has been deprecated in favor of collapsible tables for some time now. Is there some specific problem you're trying to address by proposing a switch back to NavFrame (or are you proposing a design for an alternate Navbox template)? 「ダイノガイ千？！」^{(Dinoguy1000)} 18:44, 23 February 2009 (UTC)

I didn't know that NavFrame had been deprecated. Anyway, it's the visual design that I'd like people to comment on, not the code itself. SharkD (talk) 01:40, 24 February 2009 (UTC)

I don't really like it. It's too big, the colours are pale and washed-out. The current design is fine, IMHO. //roux   05:42, 24 February 2009 (UTC)

Ditto. Not everything should look the same. — Edokter • Talk • 15:28, 24 February 2009 (UTC)

I'd have to agree - I originally thought about commenting on the appearance, but changed my mind for some reason that I subsequently forgot (huh? =) ). 「ダイノガイ千？！」^{(Dinoguy1000)} 18:51, 24 February 2009 (UTC)

Edit protect

{{editprotect}} Can someone revert the last edit backto the last one, the new edit does not remove redundant code, it affects the {{Navbox with columns}}. See difference down below on the coloumns which gets padded in instead lining up with the groups and title — CHANDLER#10 — 02:13, 1 March 2009 (UTC)

Old code

Topplistan: Prizm (835p) Pierre (658p) mjolk (622p) chandler (379p) superalbin (216p) adrenaline (192p) ReactoR (151p) Ace (128p) Bollinger (119p) Bunghole (104p) kayl (102p) fuck (102p) Ekvation (98p) nolve (93p) nat (89p) topic (89p) lulle (88p) SessCa (76p) danell (75p) conel (72p) rich (67p) Azze (66p) KloN (40p) yoch (33p) Wisso (32p) TTl (30p) geekosaurus (30p) rejvar (28p) byggarn (28p) PHYZ (18p) Scar (18p) pik (17p) snyft (15p) agent_R (11p) jaite (11p) chubby (10p) luddeluff (9p) Dibbe (6p) patroN (4p) LorDo (3p) fungahh (3p) Kvantum (3p) speedfister (3p) Cilsh (2p) OggC (0p) Trassel (0p) oakis (-1p) netropa (-3p) Bella (-5p) Memphis (-9p) IQ fiskmås (-13p) rexas (-18p) meth (-25p)

Topplistan: Prizm (907p) mjolk (896p) Pierre (725p) chandler (419p) adrenaline (291p) superalbin (222p) conel (222p) ReactoR (218p) fuck (191p) topic (167p) kayl (156p) Ace (154p) Bollinger (139p) Bunghole (138p) danell (134p) lulle (131p) Ekvation (115p) SessCa (110p) rich (101p) nat (99p) Wisso (76p) byggarn (70p) nolve (68p) Azze (65p) agent_R (57p) yoch (50p) TTl (39p) rejvar (37p) geekosaurus (30p) KloN (26p) pik (26p) PHYZ (23p) Scar (18p) snyft (15p) jaite (12p) chubby (10p) luddeluff (9p) fungahh (8p) Dibbe (6p) patroN (4p) Kvantum (3p) LorDo (3p) Cilsh (2p) OggC (2p) JohanE (1p) Trassel (0p) speedfister (0p) oakis (-1p) harma (-1p) netropa (-3p) Bella (-4p) aikonstyle (-5p) Memphis (-9p) IQ fiskmås (-12p) rexas (-18p) meth (-42p) New code

•  Done Yes, you are correct that the edit did mess up the Navbox with columns templates. I've reverted the edit and all should be back to normal now. The strange code gives the option to remove the padding altogether from wrapping the lists, which prevents odd html quirks from adding extra pixels of spacing to the left and right in certain cases (such as the Navbox with columns case). --CapitalR (talk) 11:14, 1 March 2009 (UTC)

I can see no difference at all at the examples given above, possibly due to the revert. Excatly what code caused the problem? Then that code should be commented as required. Not all changes could possibly be responsible for the adverse effects. — Edokter • Talk • 19:24, 1 March 2009 (UTC)

OK, stripping the list1padding was the mistake. All other changes had nothing to do with this issue. So I would like to reinstate the other fixes (and comment the list1padding parameter) if there are no objections. — Edokter • Talk • 20:33, 1 March 2009 (UTC)

Yeah, I took a look through other templates dependent on Navbox and think that list1padding is the only required one. Removing the other ones should be perfectly fine. --CapitalR (talk) 22:40, 1 March 2009 (UTC)

Autocollapse modification

Now there are so many template that each article will have 2 template. But due to autocollapse both are collapsed, and novice wiki users(not editors) dont see template at all. Also this hampers navigation by search engines too.

So when multiple templates are there in an article, autocollapse should expand first of the multiple templates included in that page. Which template appears first is determined by editors of the article. This modification will not call for large scale modification of many articles, instead just the modification of wiki rendering software. Cited third page (talk) 07:01, 2 March 2009 (UTC)

This request should be made on MediaWiki talk:Common.js, since {{Navbox}} itself doesn't and can't automatically control collapsing on articles with multiple navboxes. And IIRC, the autocollapse is not triggered unless there are more than two collapsible elements on the same page (which is why navboxes on most anime and manga series articles are collapsed by default, even if they only transclude one navbox), and trying to keep track of exactly what is being made collapsible (is it navboxes, or some part of the infobox, or something else, and how many instances of each) would unnecessarily complicate an already complicated piece of Javascript. A far simpler solution for your problem would be to define |state={{{state|}}} in the individual navbox in question, which can then be expanded by default on articles simply by calling {{Name of navbox|state=expanded}}. 「ダイノガイ千？！」^{(Dinoguy1000)} 19:42, 2 March 2009 (UTC)

Why two tables?

Is there any particular reason for using a table embedded in another table to display the box? --Tgr (talk) 14:17, 4 March 2009 (UTC)

Mostly styling issues, but I think collapsability is also one reason. — Edokter • Talk • 16:46, 4 March 2009 (UTC)

Something like that, I'm sure. CapitalR did a lot of testing to get to the current code, and if there was any satisfactory layout that only required one table, he would've found and used it. 「ダイノガイ千？！」^{(Dinoguy1000)} 20:20, 4 March 2009 (UTC)

Does it have anything to do with the "child" function which I guess is 1 table, but when it's outside the navbox like below, the title moves when you click on show/hide? (at least in my Firefox, Safari, Chrome and Opera, but stays in the middle with IE7) ch¹⁰ · 21:19, 4 March 2009 (UTC)

{{Navbox|child
|style = width:25%;
|state = collapsed
|title   = title
|list1   = list
}}

That is due to the float conatining the "hide"/"show" text changing size. I'm not sure why it doesn't happen in the double table version (probably some CSS rule that is normally inherited from the outer table is missing), but you can fix it easily by giving .collapseButton a fixed width. --Tgr (talk) 11:45, 5 March 2009 (UTC)

Hmn, the code I added for .collapseButton in MediaWiki:Common.css does give it a fixed width inside the "navbox" class, which was supposed to prevent precisely this issue (and balance the vde links on the other side). Is that class not given in the single table version? Happy‑melon 18:44, 9 March 2009 (UTC)

Collapsibility works perfectly well with only one table (though I didn't test it in all browsers). I'll ask CapitalR then. --Tgr (talk) 11:45, 5 March 2009 (UTC)

It's been a few years since I wrote the Navbox code, but I do recall that doing it with two tables was the only way to get proper display for nested Navboxes in all browsers (I think IE6/7 were the offenders that made that necessary). Without nested Navboxes, it wouldn't be necessary for the two table system, but with them (i.e. {{Navbox subgroup}}, {{Navbox with columns}}, and {{Navbox with collapsible groups}}), the two table solution was needed. In order to keep the code the same in all of these templates (and to allow nesting directly into {{Navbox}} lists), I had to use the two table solution for Navbox. If I recall correctly, it will be possible for me to do a major code rewrite and go to the one table method once mw:Extension:StringFunctions are implemented (see bugzilla:6455). Also, with StringFunctions, I would be able to fix the odd way the spaces are drawn between the table cells (again, necessary due to browser support). However, I've been waiting on that bug for years now, so don't count on the code rewrite any time soon (unfortunately). Also, it may be possible to eliminate the two table solution in favor of one table if support for IE6 is dropped (though don't hold me to that, as IE7 has much of the same weirdness/bugs as IE6). Perhaps someone else can try to do it with one table, but I will say that I tried very hard and couldn't do it successfully (and I spent in excess of 200 hours developing the Navbox code). --CapitalR (talk) 12:40, 5 March 2009 (UTC)

I would also love to see StringFunctions implemented, but none of us are devs, and none of the devs seem to want to spend time on it (something about "more important things to work on" =) ), so I'll have to be content with voting for it for now. 「ダイノガイ千？！」^{(Dinoguy1000)} 20:34, 5 March 2009 (UTC)

Wrapping text around an image

Is it possible to wrap the text around an image, such as in this template. --Geronimo20 (talk) 03:26, 12 March 2009 (UTC)

I don't think it's possible, unless you were to float the image inside one of the lists off to the right side (which would probably look funny unless the image was small). --CapitalR (talk) 04:11, 12 March 2009 (UTC)

More than 20 groups

{{editprotected}} Could we get more than 20 groups? Needed for {{Street newspapers}}, for all the countries in Europe. --Apoc2400 (talk) 12:10, 21 March 2009 (UTC)

 Not done You can nest Navboxes to get as many groups as you wish. I'll take a look at the template in question for you. --CapitalR (talk) 13:00, 21 March 2009 (UTC)

There you go, should be all fixed now; you can keep adding more groups to the new child navbox I added. --CapitalR (talk) 13:03, 21 March 2009 (UTC)

Thank you. Is there any reason for the 20-group limit? Also, would it be possible to have the template display a warning message if there are too many groups? --Apoc2400 (talk) 13:40, 21 March 2009 (UTC)

Basically, the more groups there are the longer it takes the servers to render pages with Navboxes. I did some testing when I wrote the Navbox code and found that each additional group's code does add non-trivial render time, so capping the groups at 20 keeps it at a reasonable level (my original plan was 16 groups, but I bumped it to 20 at the last minute). Also, of the 55,000 or so templates using Navbox, only about 25 require more than 20 groups, so it's really not worth adding more do to the increased render cost on all other pages. --CapitalR (talk) 21:20, 21 March 2009 (UTC)

I have ported this template to my own wiki and am using it for a textbook. Unfortunately the textbook has 22 chapters. I tried to go in and extend the template to 24 groups to no avail. Is there something I'm missing? Is there a better way of navigation? This seems to be the perfect navigation between subchapters, so I would think extending this template would be the way to go. Any comments would be appreciated (http://wiki.chemprime.chemeddl.org - an online living chemistry textbook). Jshorb (talk) 16:42, 10 April 2009 (UTC)

Taking a quick look, it seems you have group19/list19 twice in the template code and forgot group21/list21. Also, you need to make sure that all of the even/odd code is correct. To fix this, I recommend starting over and copying and pasting rows 17-20 again to convert them into 21-24. This will ensure proper even/odd-ness. Then convert all the 17s to 21s, all the 18s, to 22s, etc. --CapitalR (talk) 20:43, 10 April 2009 (UTC)

Excellent. I hadn't noticed the even/odd requirement. That fixed everything. Thanks for the help. Jshorb (talk) 18:16, 5 May 2009 (UTC)

How about creating a Template:Navbox-long with many more groups that can be used when needed? --Apoc2400 (talk) 21:39, 10 April 2009 (UTC)

I just created {{Navbox long}} which supports up to 38 groups/lists. It performs the nesting automatically making it easy to get that many groups. Note that it is unable to determine the group width properly between the first 18 groups and the subsequent groups (due to technical reasons that are not possible to overcome). Thus, you must manually specify the group width for this to work. This can be done by adding the parameters groupstyle = width:XXXem; and liststyle = width:auto; which should make it work (where XXX is the desired group width). Let me know if it works for you; if it seems to do the trick and my further testing does well, I'll add it to the {{Navbox suite}} list. --CapitalR (talk) 01:06, 12 April 2009 (UTC)

Nice! Is it because of the nesting that you have to set the group width? --Apoc2400 (talk) 08:45, 12 April 2009 (UTC)

Yup, that's the reason. We could, of course, make a version without the nesting in it by copying the Navbox code and adding more groups, but then we run into maintenance problems because any change on {{Navbox}} needs to be copied into {{Navbox long}} (which is likely to be overlooked occasionally). Considering how few templates need more than 20 groups (it's about 35 out of 55,000), I don't think it's too much to ask to specify the group width on those to avoid the duplicate code problem. --CapitalR (talk) 10:08, 12 April 2009 (UTC)

Question???

What is the code for the view • discussion • edit in the title space? I can't seem to figure it out. (Tigerghost (talk) 13:32, 23 March 2009 (UTC))

{{tnavbar}}. 「ダイノガイ千？！」^{(Dinoguy1000)} 19:35, 23 March 2009 (UTC)

I was wondering about this. I there any way we can make those links show up only to logged in users? For readers they are just a distraction. --Apoc2400 (talk) 10:18, 12 April 2009 (UTC)

IPs can edit and discuss templates too. They're no different then the section edit links. — Edokter • Talk • 17:54, 12 April 2009 (UTC)

And section edit links aren't visible to IPs. They are much less likely to want to edit templates, and it distracts from reading. --Apoc2400 (talk) 18:12, 12 April 2009 (UTC)

They are very visible to everyone, including IPs. Why would we want to hide them from the templates and keep up the notion of an encyclopedia that anyone can edit? — Edokter • Talk • 21:10, 12 April 2009 (UTC)

You are right. I must have confused it. --Apoc2400 (talk) 19:43, 13 April 2009 (UTC)

I frequently edit while logged out; section edit links are definitely visible to me, and hiding those links (and the v-d-e links) from anonymous users would be a huge disservice to myself and others (it's annoying enough when I'm looking at talk page archives and don't see the section edit links, even while logged in). 「ダイノガイ千？！」^{(Dinoguy1000)} 19:23, 13 April 2009 (UTC)

←Section edit links aren't available to IPs on semi-protected articles (which is quite a few), but are still available to registered users. Maybe that was the confusion, Apoc...? --64.85.222.57 (talk) 12:07, 29 April 2009 (UTC)

True. But then again, it is the article that is protected, not the navbox. For protected navboxes, navbar has a noedit=1 option. There is (currently) no way to automatically hide the edit link for protected navbox templates. — Edokter • Talk • 12:37, 29 April 2009 (UTC)

Transcluding Issue

Hi, I'm attempting to transclude this template to a personal wiki. However, even after installing MediaWiki:Common.css and MediaWiki:Common.js, I'm still getting strings of code like "+1}}{{#if:|+1}}{{#if:|-1}}}} class="navbox-title" | {{#if:{{#switch:|plain|off=1}} {{#if:" when I view the template. I'm using this version of Navbox, and this version of Tnavbar. Somebody mind helping me out? Here's an image, if it helps. Thanks,  Aaron  ►  04:07, 9 April 2009 (UTC)

It looks like you need to install the ParserFunctions extension. 「ダイノガイ千？！」^{(Dinoguy1000)} 17:45, 11 April 2009 (UTC)

You are now my own personal Jesus Christ. But now it looks like I have to update my installation of MediaWiki; I'm still on 1.9.. Thanks!  Aaron  ►  23:58, 11 April 2009 (UTC)

Navbox rendering problem

Does Wikipedia have a limitation that you can't 2 of {{Navbox with collapsible groups. If so please remove it.

Because Template:Computer Science (this version) is having the problem and I don't know how to fix it. --75.154.186.241 (talk) 22:58, 17 April 2009 (UTC)

No, you simply forgot a 'group1 =' and 'list1 ='. — Edokter • Talk • 00:05, 18 April 2009 (UTC)

Oh thanks. Was too distracted by the "spacing" = Quotation rather than seeing the overall errors. --75.154.186.241 (talk) 05:08, 18 April 2009 (UTC)

Tnavbar --> Navbar

The next time an admin edits this template, could you please also change Tnavbar to Navbar? {{Tnavbar}} has been moved to {{Navbar}} since its functionality was expanded to work in all namespaces, and {{Navbox}} is by far the cause of most of its usages. 「ダイノガイ千？！」^{(Dinoguy1000)} 02:04, 22 April 2009 (UTC)

Aah, never mind, it seems Happy-melon already took care of it. 「ダイノガイ千？！」^{(Dinoguy1000)} 02:32, 22 April 2009 (UTC)

Top margin

Just in case anyone's curious, an adjustment was just made to MediaWiki:Common.css to improve the margin on navbox stacks – discussion was here. —Werson (talk) 18:44, 26 April 2009 (UTC)

wikiclass

I think the Template:Navbox with columns should be transformed to class=" ". They are used more commonly as tables.

• Can you make the colfooter expandable

(not expandable as a collapsible group, rather just have a "show / hide" button.)

I would imagine a lot of footer are used for extra information (relevant topics) instead of below=, which provided additional information (meaning one product having 2 properties).

“ e.g. Template:ATI, theoretically should be categorized by colheadings the series of the product and the current colheading title 2D rendering, Direct3D 3-6, Direct3D 7, Direct3D 8, Direct3D 9, Direct3D 10 and Direct3D 11 should be used as colfooter, because they are somewhat technical for a template. ”

• class="wikitable sortable" able to be sortable.

Template:Deadliest_tornadoes_by_state can be transformed to a Navbox for easier maintainance. Also they really should have class="wikitable sortable" feature added.

• when making the colheader expandable, make it as the following

groupcol1-12header = {{class="";style=""; padding="" line-height:0em; width:0em; text-align:center;font-weight:normal;}}

• I think {{Navbox Year}} should also be also be changed into a class also.

--75.154.186.241 (talk) 23:04, 8 May 2009 (UTC)

I really have no idea what you're asking. Other editors: please note that this IP was blocked for being a probable sock puppet. --CapitalR (talk) 23:41, 13 May 2009 (UTC)

Missing Template:FULLPAGENAME: Error

Greetings! I am importing this template into my person wiki and keep getting a missing template error. I used the Special:Export feature to export Navbox and all associated templates. It appears as though all is well with the exception of a few templates which look to be associated with the "v • d • e" functions. The templates missing are as follows:

Template:FULLPAGENAME: Former French colonies in Africa and the Indian Ocean
Template:FULLPAGENAME: Former French colonies in Asia and Oceania
Template:FULLPAGENAME: Former French colonies in the Americas
Template:FULLPAGENAME: Navbox/doc
Template:FULLPAGENAME: Navigation templates
Template:NAMESPACE: Former French colonies in Africa and the Indian Ocean
Template:NAMESPACE: Former French colonies in Asia and Oceania
Template:NAMESPACE: Former French colonies in the Americas
Template:NAMESPACE: Navbox/doc
Template:NAMESPACE: Navigation templates

The rendering of "v • d • e" on my wiki looks like this:

[[Template:FULLPAGENAME: Navigation templates|view]] • [[{{TALKPAGENAME:Template:FULLPAGENAME: Navigation templates}}|talk]] •  [{{fullurl:Template:FULLPAGENAME: Navigation templates|action=edit}}edit]

While the output lists a few specific templates I'm not concerned about (such as Former French colonies), I am interested in getting the Template:FULLPAGENAME and Template:NAMESPACE. These templates appear not to exist. Can someone tell me where to find these templates or what I should change in Template:Navbox or Template:Navbox/doc to solve the "v • d • e" rendering errors. I appologize if I have misdirected or miscategorized this question. Thanks! aszymanik speak! 01:59, 20 March 2009 (UTC)

{{FULLPAGENAME}} and {{NAMESPACE}} are magic words (manual) that produce The full page name and the name space ("Template talk:Navbox/Archive 11" and "Template talk") Personally I don't know how one would do to copy them... You can perhaps ask on MediaWiki's help page, Wikipedia's help page or something (unless someone here knows) chandler · 02:07, 20 March 2009 (UTC)

there is no need to copy the magic words, they exist in every MediaWiki installation. In any case, it sounds like something got accidentally substituted when you transwikid the templates, aszymanik. Could you provide a link to them on your wiki, please? 「ダイノガイ千？！」^{(Dinoguy1000)} 17:20, 20 March 2009 (UTC)

Did anyone figure out this problem? This happened to my wiki as well and all the templates are freaking out. Kristinpedia (talk) 18:53, 6 May 2009 (UTC)

Once again, please provide a link to one of the problem pages on your wiki so we can see exactly what's going on. 「ダイノガイ千？！」^{(Dinoguy1000)} 04:55, 7 May 2009 (UTC)

Only from MetaWiki version 1.15 onwards,the FULLPAGENAME magicword can be used to refer a namespace —Preceding unsigned comment added by 203.200.20.98 (talk) 12:28, 19 May 2009 (UTC)

Sure. http://sunshinereview.org/index.php/Template:State_sunshine_laws. Kristinpedia —Preceding unsigned comment added by 98.223.170.149 (talk) 19:22, 8 July 2009 (UTC)

Whatever the problem was, it seems to have been fixed. If you encounter any pages where the problem remains, you should be able to fix it simply by purging the server cache of the page. 「ダイノガイ千？！」^{? · Talk⇒Dinoguy1000} 20:54, 8 July 2009 (UTC)

Line break headache

My template seems to be acting up. When I place each entry to a list on a separate line (As opposed to having every entry on the same line separated by a space, as they are now), the result is for the most part satisfactory... Except that the first and last entries are on individual separate lines! What am I doing wrong? -- ʄɭoʏɗiaɲ ^τ _¢ 09:11, 14 July 2009 (UTC)

I think I can fix it for you, but I don't see why you are using {{!}} to insert pipes; bullets are used in many more navboxes and are much easier to read. Also I don't really understand why you used {{nowrap}} over and over; {{nowrap begin}} and {{nowrap end}} are superior in this case. → ROUX ₪ 09:17, 14 July 2009 (UTC)

 Done I have less than no idea as to why it was doing that, had to try several different things before it would actually work. → ROUX ₪ 09:46, 14 July 2009 (UTC)

I'll be honest. I stole it from Jefferson County, Ohio. Thank you! :) ʄɭoʏɗiaɲ ^τ _¢ 15:32, 14 July 2009 (UTC)

Heh. Off to fix that one now.. → ROUX ₪ 17:47, 14 July 2009 (UTC)

Actually, there's no point in using any of the {{nowrap}} family with navboxes unless you are trying to keep something other than links from wrapping; all navboxes which use {{Navbox}} already have class="nowraplinks" which prevents links from wrapping. 「ダイノガイ」^{? · Talk⇒Dinoguy1000} 18:52, 14 July 2009 (UTC)

Transferring this to Wikia

Hi! I'm a Wikia user, and currently, our Navboxs are too big. Text is too big. I noticed the text on this Navbox template is small, and more compact, and I was wondering if it's possible to transfer this code to Wikia, while not losing any functionality? If it is, please, leave a message on my talk page at the Castle Crashers Wikia. Thanks! 24.226.33.10 (talk) 03:11, 21 April 2009 (UTC)

Err, I figured out that we have a "style1", "style2", etc feature, and I've figured out, using "font-size:90%;" how to make the gtitle stuff smaller, but I can't figure out how to make the group area's bluish background width smaller, or how to make the group text smaller either. Again, if anyone can help, a link to my wikia talk page is above, leave me a message and we can talk. 24.226.33.10 (talk) 03:20, 21 April 2009 (UTC)

It sounds like you may not have the correct styles copied to your wiki. Compare your styles in your local Common.css file with those here (you should be looking for the various .navbox rules). 「ダイノガイ千？！」^{(Dinoguy1000)} 02:09, 22 April 2009 (UTC)

I have different question about transferring this template to Wikia: How do you turn on HTML Tidy? It seems to me that this software is a simple I/O program that runs on a computer, rather than a Wiki - not to mention that it has no easily accessible option to be turned on. Hue03 (talk) 19:16, 21 July 2009 (UTC)

If Tidy isn't already running on the Wikia you're trying to copy this to, you'll need to get in touch with a Wikia staffer to see about enabling it. In the meantime, there is a version of Navbox that doesn't require Tidy; see the box at the top of the page for a link. 「ダイノガイ千？！」^{? · Talk⇒Dinoguy1000} 21:27, 21 July 2009 (UTC)

Collapse in NAVBOX

I would like see if my idea is possible first of all, and then if anyone thinks it would be worthwhile. I find that many users mis-understand the collapsing and most just ignore it all together, so that very few use the state variable in order to make one navbox uncollapsed and just let the rest autocollapse (collapsed if there is more than one).

So this brings me to my point, could you make it work such that, if anyone sets the state variable to a certain "reserved word", that it would make the state be the code below? The code below is useful also, because it makes the state of the navbox uncollapsed when you view it directly (go to the template page itself).

My reasoning is that, then, a user can take any navbox transclusion and define the state (i.e. {{NASA navbox|state=uncollapsed}} won't work unless Template:NASA navbox defines state.) So, at least to make my life easier and I'm sure others, maybe the below could either be:

1. the default for state if it is not defined in a transclusion of navbox
2. if you set state to be 1, then it becomes the code below

|state = {{{state|<includeonly>autocollapse</includeonly><noinclude>uncollapsed</noinclude>}}}

I know this may seem unclear, but I am trying to describe it the best I know how. Please comment.

  Jonverve  ^{Talk  Contrib}  22:59, 29 July 2009 (UTC)

So you're asking for something like

{{navbox
| name  = Foo
| title = Foo
| state = 1
| ...
}}

where "state=1" is automatically expanded into state={{{state|<includeonly>autocollapse</includeonly><noinclude>uncollapsed</noinclude>}}}? Unfortunately, that isn't possible (except maybe with some subst coding that would be so convoluted as to not be worth the trouble). The only thing you can do is to manually add the specified code to each navbox as the need arises. 「ダイノガイ千？！」^{? · Talk⇒Dinoguy1000} 05:33, 30 July 2009 (UTC)

Please add "class" parameters

{{editprotected}} In order to facilitate the addition of microformats, please will someone with the necessary skill and knowledge add "titleclass" and "bodyclass" parameters, like those on {{Infobox}}? That will remove the need for this workaround I made after forgetting that the parameters are not already available. Thank you. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 20:39, 23 July 2009 (UTC)

Sandbox updated with what should work, if you'd care to test. Chris Cunningham (not at work) - talk 21:32, 28 July 2009 (UTC)

Thank you. I had to make one tweak, and it's now working. Please see if you're happy with that, or wish to make further changes, or implement it. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 21:54, 28 July 2009 (UTC)

Looks okay to me, though obviously it would be good to wait for further input before this is rolled out. Chris Cunningham (not at work) - talk 22:00, 28 July 2009 (UTC)

Ok. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 22:06, 28 July 2009 (UTC)

No comments, so I think we should go ahead, now. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 08:30, 30 July 2009 (UTC)

 Done. Would one of you update the documentation please? — Martin (MSGJ · talk) 09:52, 30 July 2009 (UTC)

Thank you. Documentation updated. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 18:52, 30 July 2009 (UTC)

Semantic markup

I suggest to correct the semantic markup of the navbox tables. The groups should be marked up with th and the scrope attribute scope="row" as they function as heading for the lists. Also the empty rows which are only there for display reasons should be removed. Instead use the correct css styling (border-spacing). —Preceding unsigned comment added by 77.186.117.84 (talk) 22:54, 29 July 2009 (UTC)

Oh we stopped caring about semantic markup around the time we transitioned from div based navboxes back to tables (tables were easier to use). — Dispenser 23:02, 29 July 2009 (UTC)

I can't decide if this is supposed to be sarcastic or not. =/ At any rate, User:CapitalR is probably the go-to guy for modifications as drastic as what is proposed, as he developed the current navbox. More than likely, though, the proposed changes would require an extensive rewrite to avoid breaking anything and to maintain current functionality, and IIRC CapitalR has previously stated that he's not up to such work again. 「ダイノガイ千？！」^{? · Talk⇒Dinoguy1000} 05:29, 30 July 2009 (UTC)

Using css-border spacing would be ideal, except that it doesn't work properly in all browsers (i.e. IE). I think there is now a way to get special css for just IE browsers for Wiki pages, but I don't have the time to go through and redesign the Navbox template to make use of this feature (though I'd be interested to see if anyone else can make it work). As for the th/td for groups, does it really matter? That could be fixed (with some corresponding changes to the default group css) if you want to do it. --CapitalR (talk) 18:33, 10 August 2009 (UTC)

Color usage

Has there ever been a color scheme for Navbox that isn't the ugly purple-blue that everyone uses? Or is that the only one people have bothered with? —harej (talk) 01:54, 10 August 2009 (UTC)

Template:Canada topics doesn't use it, largely because the default is so insipidly hideous. → ROUX ₪ 03:42, 10 August 2009 (UTC)

Canada topics looks terrible. /bashmore. Suggest less ugly coloration; I would personally like to see the greys of wikitables and the blues of Vector skin used. --Izno (talk) 03:51, 10 August 2009 (UTC)

Template:Canada topics indeed has egregious inconsistency (and poor color matching in general). I personally don't like gray. —harej (talk) 04:13, 10 August 2009 (UTC)

Egregious inconsistency? What on earth are you talking about? There are a total of two colours in the template--red and grey. The colour scheme was hammered out at WT:CANADA, so you can take the discussion there if you want it changed. → ROUX ₪ 14:49, 10 August 2009 (UTC)

Also white. Oh, it just looked inconsistent because of the alternating levels of indentation used. —harej (talk) 16:48, 10 August 2009 (UTC)

And those custom colours also lead to brilliant palettes such as at Interior Plateau#Further reading. But maybe we should choose a new colour scheme when move to the new Vector skin. I like the simple lines on white used by the Canada navbox, just replace the red with a more neutral dark grey. —Ruud 18:40, 10 August 2009 (UTC)

White doesn't provide enough contrast against the rest of the page, which is perhaps the (largest) problem with Canada topics (note that I do realize why [duh] those colors are used). --Izno (talk) 19:05, 10 August 2009 (UTC)

But should they contrast with the rest of the article? I'd say navigational boxes are secondary to the real article content. —Ruud 19:13, 10 August 2009 (UTC)

All that matters is that they're different from the article's intent. It's a matter of emphasis; we want to emphasize that the navbox is different from article content. This is why there's that subtle blue on non-mainspace pages and why the navigation is in grey... so on and so forth. --Izno (talk) 19:18, 10 August 2009 (UTC)

All this being said, are there other examples of the navbox not using the standard color scheme? —harej (talk) 19:33, 10 August 2009 (UTC)

I've seen quite a lot of them, usually when they are related to a country, television show, sports team or university. —Ruud 19:46, 10 August 2009 (UTC)

I am migrating some of my Wikipedia:Coordination listings over to Navbox, and I would like to know what good examples there are. —harej (talk) 20:05, 10 August 2009 (UTC)

(remains silent) —Ruud 20:19, 10 August 2009 (UTC)

Milhist has nice coloring to me, which is standard within the Milhist project. --Izno (talk) 23:46, 10 August 2009 (UTC)

Please don't migrate navbox templates en masse to custom colour schemes. if the move to the Vector theme means a rethink of our default colours then that would be excellent - they should not, however, be arbitrarily overridden because someone thinks the defaults are ugly. Chris Cunningham (not at work) - talk 11:51, 11 August 2009 (UTC)

To be sure, I want to be clear that that was not my intent at all. —harej (talk) 13:05, 11 August 2009 (UTC)

This drives straight to the main issue here: different people have different views on aesthetics. Personally, I quite like the current navbox color scheme, even though I do find it a tad dry/bland. I also find that most alternate schemes I see on individual navboxes are quite horrible, though I do spend a lot of time around anime/manga articles, where such color schemes tend to be eye-bleedingly bad anyways. I wouldn't be opposed to the development of a new, Vector-esque scheme, though, once Vector goes default. 「ダイノガイ千？！」^{? · Talk⇒Dinoguy1000} 18:59, 11 August 2009 (UTC)

OMG, You idiot! They're not purple, they're blue! j/k See Template talk:Navbox/Archive 11#Get rid of purple. Also, I was working on a couple of test versions that have a different style: 1, 2, 3. Never got around to finishing them. SharkD (talk) 04:15, 12 August 2009 (UTC)