Template talk:Navbox/Archive 9

Archive 5

←

Archive 7

Archive 8

Archive 9

Archive 10

Archive 11

→

Archive 15

Localization problem

Hi! Can some smart Navboxer take look at latvian local template lv:Veidne:Navbox. I've copied all known templates from english wikipedia (except doc templates). All is ok except group titles - they are without bold and background color. (See lv:Veidne:Francijas aizjūras departamenti un teritorijas.) Below line too is without color. Somewhere between navbox title and 1st group default styling is lost. Please help! --Kikos (talk) 14:01, 11 July 2008 (UTC)

I think you need to copy all of the CSS code for navboxes into the MediaWiki:Common.css page. Take a look at MediaWiki:Common.css in English wikipedia and copy all of the lines for navboxes into the lv:MediaWiki:Common.css page (be sure to delete the old navbox CSS lines first; also, note that you need to be an admin to do this). Then clear your cache and it should work. Please let me know if you need assistance with this. --CapitalR (talk) 19:26, 11 July 2008 (UTC)

Thanks! --ScAvenger (talk) 12:29, 12 July 2008 (UTC)

Hide

Hello, I'm making a navbox (albeit much simpler than this one) for another MediaWiki site and the one thing I cant seem to get is the show/hide button and I was wondering if somebody could help me with the code for it. Thanks Highfields (talk) (contribs) 10:34, 16 July 2008 (UTC)

You'll need to copy the contents of Wikipedia:WikiProject Transwiki/MediaWiki:Common.js (basically a copy of Wikipedia's own MediaWiki:Common.js, but with most of the Wikipedia-specific stuff cut out) to that wiki's MediaWiki:Common.js file. It's the one that starts at "/** Collapsible tables *********************************************************", but you should be able to safely copy everything there if you wish (there are a number of other things that will be useful, as well as some bug fixes). -- Ned Scott 12:28, 16 July 2008 (UTC)

Is it possible to construct templates with tabs?

(Originally From Technical Village pump)

Example: The imaginary picture of a final product, a template containing tabs. (Written in Chinese since the original discussion is moved from the Chinese Wikipedia.)

Hello, is it possible to construct templates with tabs (See the figure as an example)? It will be very usful in all wikipedia project, making many articles in different but related aspects more organized, especially for those involving generations of objects (Example: One tab for the related topics of one generation). In the original discussion, some technical problems appeared when the template is constructed. So I moved the discussion here to ask for help. The following two are the embryonic forms of the required templates (Written in Chinese since the topic is brought from the Chinese Wikipedia). Since my English is not good enough to describe the technical situation, please do try to click the tabs of the embryonic forms.

An embryonic forms of method 1(Using <ref>, whose disadvantage is more difficult to arrange typesetting):

| | | |

And this one, an embryonic forms of method 2 (I don't know whether it had used the Anchor function):

一劃 | 二劃 | 三劃 | 四劃 | 五劃

一部 | 丨部 | 丶部| 丿部 | 乙部 | 亅部

二部|亠部|人部|-{儿部}-|入部|八部|冂部|冖部|冫部|-{几部}-|凵部|刀部|力部|勹部|匕部|匚部|匸部|十部|-{卜部}-|卩部|-{厂部}-|厶部|又部

-{口部}-|-{囗部}-|-{土部}-|-{士部}-|-{夂部}-|-{夊部}-|-{夕部}-|-{大部}-|-{女部}-|-{子部}-|-{宀部}-|-{寸部}-|-{小部}-|-{尢部}-|-{尸部}-|-{屮部}-|-{山部}-|-{巛部}-|-{工部}-|-{己部}-|-{巾部}-|-{干部}-|-{幺部}-|-{广部}-|-{廴部}-|-{廾部}-|-{弋部}-|-{弓部}-|-{彐部}-|-{彡部}-|-{彳部}-

-{心部}-|-{戈部}-|-{戶部}-|-{手部}-|-{支部}-|-{攴部}-|-{文部}-|-{斗部}-|-{斤部}-|-{方部}-|-{无部}-|-{日部}-|-{曰部}-|-{月部}-|-{木部}-|-{欠部}-|-{止部}-|-{歹部}-|-{殳部}-|-{毋部}-|-{比部}-|-{毛部}-|-{氏部}-|-{气部}-|-{水部}-|-{火部}-|-{爪部}-|-{父部}-|-{爻部}-|-{爿部}-|-{片部}-|-{牙部}-|-{牛部}-|-{犬部}-

-{玄部}-|-{玉部}-|-{瓜部}-|-{瓦部}-|-{甘部}-|-{生部}-|-{用部}-|-{田部}-|-{疋部}-|-{疒部}-|-{癶部}-|-{白部}-|-{皮部}-|-{皿部}-|-{目部}-|-{矛部}-|-{矢部}-|-{石部}-|-{示部}-|-{禸部}-|-{禾部}-|-{穴部}-|-{立部}-

The original discussion is from the Chinese Wikipedia, as a reference if you can read Chinese.

Angelalive (talk) 13:24, 15 July 2008 (UTC)

Template:PageTabs, perhaps? -- John Broughton (♫♫) 16:33, 15 July 2008 (UTC)

Another imaginary example in English. Hope it helps explain.

I have tried using Template:PageTabs, but seems not work. Template:PageTabs really gives an outlook with tabs, but involving the changes of different pages when clicking another tab (i.e. In Wikipedia:WikiProject Missing encyclopedic articles/biographies/M, the page changes to Wikipedia:WikiProject Missing encyclopedic articles/biographies/S after clicking the tab-S). So it's not suitable for the required template.Angelalive (talk) 17:20, 15 July 2008 (UTC)

See also: zh:Wikipedia:互助客栈/技术#有可能編寫出有分頁的模板嗎？.--PhiLiP (talk) 17:29, 15 July 2008 (UTC)

I think the only really elegant solution for this would be to use Javascript (otherwise, you're relying on really ugly hacks like the two you have above). If you can get the necessary support and find someone to write the script, this would be a really nice addition to {{Navbox}} and company. —Dinoguy1000 17:56, 15 July 2008 (UTC)

I've written a few JS tabbers for mediawiki, the latest was on wikiality.com. Perhaps it could be adapted as a starting point. Several things to keep in mind: it should show all by default if there is no JS enabled (and you could have all but the first hidden by default even before page load, using appendCSS before addOnloadHook, preventing annoying page-flash when the document loads), and all sections should display when printing, unless the whole object is meant to be hidden. --Splarka (rant) 07:25, 16 July 2008 (UTC)

If anyone is interested in trying to write a script for this (I'm not experienced enough in JavaScript to be able to do it), I'm sure we could find all sorts of good uses to put this to. —Dinoguy1000 20:45, 21 July 2008 (UTC)

I love the idea. It would make some of the larger templates much easier to organise. If tabs that don't automatically scroll the page down every time they are clicked can be implemented, then I'm all for it! --.:Alex:. 19:29, 24 July 2008 (UTC)

As I said above, before the discussion was moved here, it would be pretty straightforward with Javascript. In more detail, the script could likely be based off of the collapsible tables script - on page load, the tabber script would look for an appropriate container class and, if present, collapse all but the first occurence of a second class within the container class (while at the same time generating tabs). When a different tab is clicked on, the script then just hides the currently shown content, reveals the hidden content tied to the clicked tab, and updates the tab styles. If a user's browser doesn't support JS (or they have scripting turned off or the tabbing script otherwise disabled), the content remains visible, possibly similar in appearance to a navbox. That's the general idea, anyways, and unfortunately there still doesn't seem to be any scripter around interested in doing anything like this. —Dinoguy1000 20:55, 24 July 2008 (UTC)

I would just like to comment that the Chinese characters take up less space and are therefore better suited to this sort of tabularization. Without them you run the risk of tabs running out of space and possibly breaking onto a new line, and depending heavily on a reader's screen resolution. How do you hope to resolve these types of issues? SharkD (talk) 01:34, 3 August 2008 (UTC)

There's no reason to have to handle such issues. These problems should be checked for by whomever is creating or editing the tabbox, and is beyond the capabilities of MediaWiki to check for anyways. If a given template has inordinately long tab text, it's an issue of poor design in that specific template, not one involving the metatemplate. For comparison, group_n text can offer the exact same problems if it's poorly thought out/written; it's then the responsibility of the editor who made the template - or anyone who feels like changing it - to update the text and reduce its length, not the maintainers of {{Navbox}} to try and add a check and correction into the metatemplate (which, as I stated above, is impossible with MediaWiki anyways). —Dinoguy1000 19:37, 5 August 2008 (UTC)

Add history link proposal

I find that with many Navbox templates, I usually need to look at the history to check or revert edits, except that this process is a little bit more time consuming than editing or viewing the template as you need to click on one of those links first and then click the history, which can be frustrating when the internet is acting slow (or in my case svchost chews up the cpu -__-). I notice a few other templates have recently started including history, or "changes" links alongside the standard "v/d/e" links. Is it possible to implement a new link to the history page alongside the existing ones? --.:Alex:. 19:26, 24 July 2008 (UTC)

{{Navbox}} makes use of {{tnavbar}} to generate the VDE links, you may want to propose a change there and cross-post to the major templates that use it. In the meantime, could you link to a specific template that implements an additional history link? I'm curious to see how it's being done for now. —Dinoguy1000 20:57, 24 July 2008 (UTC)

Up group count to 26

I'd like to up the allowable group count from 20 to 26, to allow the use of a group for each letter of the alphabet. I've done the coding and testing in the sandbox [1], but I don't want to edit this very important template without getting approval here first. Comments? - Trevor MacInnis (Contribs) 05:31, 2 August 2008 (UTC)

• This isn't necessary. Just use two child Navboxes inside of the parent one:

The 20 groups that it has already is already a lot and can cause a few seconds of delay whenever the servers have to re-render pages with multiple navboxes. I'm not worried about over-working the servers, but it annoying to users to have to wait for pages to reload, which is why I'd prefer to keep the group/list count down. When I wrote the template initially I did tests for the amount of time it took to render a navbox based on the total allowable number of groups/lists, and there was a linear relationship. Besides, there are very, very few cases where more than 20 are needed (a handful out of the 35,000 uses of this template), so I think those extra cases can just use some nested child navboxes to get the job done (that's what nested boxes were designed for). --CapitalR (talk) 12:41, 2 August 2008 (UTC)

Ah, I had no idea it could be used that way. I'll use it at Template:List of airlines. - Trevor MacInnis (Contribs) 14:12, 2 August 2008 (UTC)

Personally, I'd like to see the group/list stuff moved to a seperate subtemplate (along the lines of Template:Navbox/row), but - if it's even possible - coding it would likely be prohibitively difficult and complex, considering the very advanced functionality present in this template. —Dinoguy1000 16:23, 2 August 2008 (UTC)

From a design point of view I completely agree with you. Unfortunately, I did tests on that, and having to call the separate group/list templates caused significant performance degradation. So until they rewrite the Mediawiki parser (which is painfully inefficient in my view), I think it's probably better to keep it all in one template. --CapitalR (talk) 22:17, 2 August 2008 (UTC)

I don't have a link handy, but aren't there pre-existing alphabetized templates that'd be a better fit anyway? MrZaius^talk 06:04, 5 August 2008 (UTC)

Mishandled Template Name field

Sandboxed and user-space templates that transclude Template:Navbox and Template:Navbox generic have their names misinterpreted when generating the v-d-e links in the upper left-hand corner. See example: User:Mrzaius/TravelTemplate, where they all wind up aimed at Template:User:Mrzaius/TravelTemplate.

• Simple solution - Don't prepend the word "Template:" on template names that explicitly provide their namespace names. This may also prevent typos when new users attempt to specify "template" as part of the article name.
• Complicated Solution, but the more elegant and quick one - Force the user to explicitly specify the namespace after going through with a bot and prepending "Template:" to all existing navboxes, while implementing the Simple Solution in the interim.

MrZaius^talk 06:04, 5 August 2008 (UTC)

Far, far simpler solution: instead of {{Navbox}} requiring the editor to tell the template what namespace it's in, always assume the template is in the Template: namespace unless it's being transcluded on on a User: page (since templates in userspace shouldn't be getting transcluded into articles and what-have-you anyways). Of course, this leads to the issue of when navboxes are transcluded from Template: to a userpage, but this shouldn't happen in general except for discussions, where it should be properly linked to anyways using {{tl}} and company. —Dinoguy1000 19:31, 5 August 2008 (UTC)

Is there any way to remove the autocollapsible feature in templates based on this one?

Please respond on my talk page if you know.`Savidan 17:18, 9 August 2008 (UTC)

Well, you could set |state = uncollapsed, but that won't prevent people from manually collapsing the navbox... Why do you need this functionality disabled, anyways? —Dinoguy1000 17:20, 9 August 2008 (UTC)

|state = plain will not collapse the navbox and hide the show/hide link. — Edokter • Talk • 22:03, 9 August 2008 (UTC)

Help with helpbox

May I ask someone here who is template-savvy to add the [hide] button to template:helpbox? I tried it, but it broke the centering of the header text, especially when it wrapped onto a second line. Much obliged.--Father Goose (talk) 02:53, 11 August 2008 (UTC)

I need help

Can you tell me how to add collapsibility to a template. That would be really helpful because I'm the template designer on a wikia and I need to know how to make my templates colloapsible. Thank You. Please reply on my Talk Page. Zero (talk) 06:32, 15 August 2008 (UTC)

Force template shown in 1 article?

How do I force a template to be shown in an article, eventho it should by default be hidden in other articles? E.g.

• bio1: hidden
• bio2: hidden
• cabinet article: shown
• bio4: hidden -- Jeandré, 2008-08-15t21:42z

Make your template have a state parameter like this:

{{Navbox
|name = templatename
|state = {{{state|}}}
|title = The title
...
}}

Then, when you go to use the template in the page where you want it to be uncollapsed, include this code: {{templatename|state=uncollapsed}}. For pages where you want it to just automaticlly decide whether to collapse itself or not, just use {{templatename}}. You can also force it to be collapsed by using {{templatename|state=collapsed}}. Hope that helps, --CapitalR (talk) 18:51, 16 August 2008 (UTC)

Perfect, thanks. -- Jeandré, 2008-08-24t15:29z