![]() | This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 1 | Archive 2 | Archive 3 | → | Archive 5 |
{{
editprotected}}
My goal is to make this 100% compatible with {{ Navigation}} so that this template can replace that one. The major reason is that a bug fix which repaired NavFrame behavior caused {{ Navigation}} to be always initially closed. So we need to implement category:
Please change:
|l1 = {{{body|}}}{{{list1|}}}
to:
|l1 = {{{body|}}}{{{list1|}}}{{{category|}}}
Thank you. ← BenB4 15:51, 19 August 2007 (UTC)
{{
editprotected}}
I have made a template and some CSS code that prevents word wraps inside links and only allows word wraps between the links and in normal text. This is useful for instance for long link lists.
The {{ nowraplinks}} template has now been fully deployed and the CSS code added to common.css. I and other editors have tested it in several ways in several browsers. There for I suggest that the CSS class is used here (in Template:Navbox) to save users of this navigation box from using lots and lots of or {{ nowrap}}. I have tested it with the template's current code in my own testpages/sandboxes.
I suggest that the first line of Template:Navbox/core should be changed to:
<table class="navbox collapsible {{{state|autocollapse}}} nowraplinks"
While I am at it I suggest that the last few lines of Template:Navbox be changed to:
}}<noinclude> {{protected template}} {{template doc}} <!-- Add categories and interwikis to the /doc subpage, not here! --> </noinclude>
The change of the last few lines is to get the documentation look and feel recommended in Wikipedia:Template documentation. (The two empty lines between the "protected template" and the "template doc" is to prevent the green documentation box to come too close to the template, just to make the template page more readable.)
This template seems to have the same purpose and even much of the same logic as Template:Navbox generic. I see that Template:Navigation, which again had the same purpose, was recently merged in to this one... but why did we ever have three to begin with? Offhand I don't see any features or options which couldn't all be included in a single template. -- CBD 11:57, 20 August 2007 (UTC)
{{ editprotected}}
Can the [ hide/show ] be made in small text. To correspond with the " v . d . e ", size text. It also looks ugly with the [ and ] not linked to the hide/show.
It should be more like {{ Navigation}} (which is being depreciated). It looks nicer. SpecialWindler talk 10:06, 21 August 2007 (UTC)
Does anyone know where the "v•d•e" comes from? They aren't in Template:Navbox/core. ← BenB4 14:14, 21 August 2007 (UTC)
I think that the default groupstyle should use "vertical-align:middle;" just like {{ Navbox generic}} does. It just looks better and works even better here at {{ Navbox}} than at {{ Navbox generic}}, since {{ Navbox}} has every second list greyed thus the group heading doesn't need to be aligned with the top of the list to show where the list starts. -- David Göthberg 12:43, 24 August 2007 (UTC)
This is what we have now:
This is what I propose for colors:
The old code is currently:
Navbox:
|bodystyle = {{{style|}}}{{{bodystyle|}}} |titlestyle = {{{titlestyle|}}} |abovestyle = background:#ddddff;{{{abovestyle|}}} |belowstyle = background:#ddddff;{{{belowstyle|}}} |above = {{{above|}}} |below = {{{below|}}} |gs = white-space:nowrap;background:#ddddff;text-align:right;vertical-align:top;{{{groupstyle|}}} |os = width:100%;font-size:95%;{{{liststyle|}}}{{{oddstyle|}}} |es = width:100%;font-size:95%;background:#f7f7f7;{{{liststyle|}}}{{{evenstyle|}}}
Navbox/core
<table class="navbox collapsible {{{state|autocollapse}}} nowraplinks" style="margin:auto; {{#ifeq:{{{nogroups|}}}|true||background:white; }}{{#if:{{{l1|}}}|{{#if:{{{l2|}}}|background:white; }}}}{{{bodystyle|}}}"><!--
The new code would be:
Navbox
|bodystyle = {{{style|}}}{{{bodystyle|}}} |titlestyle = {{{titlestyle|}}} |abovestyle = background:#ddddff;{{{abovestyle|}}} |belowstyle = background:#ddddff;{{{belowstyle|}}} |above = {{{above|}}} |below = {{{below|}}} |gs = white-space:nowrap;background:#ddddff;text-align:right;vertical-align:middle;{{{groupstyle|}}} |os = width:100%;font-size:95%;{{{liststyle|}}}{{{oddstyle|}}} |es = width:100%;font-size:95%;background:#f5f5ff;{{{liststyle|}}}{{{evenstyle|}}}
Navbox/core
<table class="navbox collapsible {{{state|autocollapse}}} nowraplinks" style="margin:auto;background:#fcfcfc{{{bodystyle|}}}"><!--
What do you all think? -- CapitalR 13:39, 24 August 2007 (UTC)
So this is what I (David) propose for colours:
{{ editprotected}}
Could the default font size be changed from 95% to 100% (i.e normal size)? Wikipedia (and any navbox) is for everyone, not just those with perfect vision. Tompw ( talk) ( review) 18:03, 2 September 2007 (UTC)
Is there some particular reason why the group labels aren't centered vertically in their cells? Placing them at the top seems a bit strange. Kirill 21:32, 2 September 2007 (UTC)
Well I guess we can just do this right now so it can take effect before all of the other changes are made.
{{
edit protected}}
Change the "gs" parameter to have the "vertical-align:top" part be changed to "vertical-align:middle". All that needs to be done is to change that one word. Thanks, -
CapitalR 23:03, 2 September 2007 (UTC)
Sorry if this is the wrong place, but is there a specific limitation in the navbox template which means that sub-tables have to be in HTML rather than Wiki markup? Trying to use Wikitables for lists results in a single open curly bracket. I'm asking because I'm trying to make Template:Compression Formats as simple as possible, but keeping the tables for internal layout. Chris Cunningham 14:10, 8 September 2007 (UTC)
{{!}}
to trick MediaWiki into accepting a pipe as parameter. I am not sure that would work in your case.There has been a move (which I approve of) to convert existing templates to use Navbox, which has nicely implemented the collapsible templates on many pages. However, this has broken custom colorization of VDE links in the title bars of many templates. For those templates using dark backgrounds in the title bar (which includes many university athletic teams, which are using school colors), the VDE links can now be nearly impossible to see. (See Template:AuburnBasketballCoach and Template:CaliforniaBasketballCoach for examples.) The title itself and the show/hide links take on the custom color, so it would be great if the VDE links could as well. Is this possible? Thanks. WildCowboy 08:55, 14 September 2007 (UTC)
I have noticed that when a link clicked on in a template, and it no longer appears as a link but as bold text, the nowrap no longer works. See: {{ US Presidents}}, click on Van Buren, my screen resolution setting is 1024px X 768px using FireFox. When Van Buren is the active page, the name wraps to the next line. This is an extremely minor nit-picky point, but if you can fix it go for it. Otherwise, forgetaboutit. Regards.-- Old Hoss 21:17, 21 September 2007 (UTC)
There's a problem with {{ Fourth Balkenende cabinet}}, at least in Firefox. Some of the text appears outside of the box. Anyone know what's going on and how to fix that? JACO PLANE • 2007-09-24 09:23
Say if we find a template that needs to be changed but we don't have the expertize or time to change it, is there a way we can tag it (eg: a category)? Peachey88 07:28, 26 September 2007 (UTC)
Anyone know where I can find a tutorial on how to create a navbox for my own site? Thanks Travb ( talk) 08:49, 27 September 2007 (UTC)
{{ editprotected}}
Firstly, the main page documentation doesn't mention the category
attribute, which can be used to add cats to transcluded pages.
Secondly, these should be <noinclude>d from the category itself. See Template: Games Workshop, which transcludes Category: Games Workshop onto pages which include it but avoids being part of that category itself. I'd rather this were automatic with the attribute, because templates shouldn't be getting tagged with article namespace cats.
Chris Cunningham 12:49, 27 September 2007 (UTC)
{{Navbox |title = Title |list1 = List |category = <includeonly>[[Category:Cat1]]</includeonly><noinclude>[[Category:Cat2]]</noinclude> }}
{{Navbox |title = Title |list1 = List }}<includeonly>[[Category:Cat1]]</includeonly><noinclude>[[Category:Cat2]]</noinclude>
The two above calls do exactly the same thing, so there's really no point in using a category parameter in my opinion. It just makes the template more complicated to understand without adding any use. It's easier to just add the categories at the end after the Navbox call instead of inside of it. Unfortunately, we can't just add the includeonly tags to this main Navbox template, as it would screw up lots of templates that are (unfortunately) using the category parameter. I'm going to remove the editprotected tag for now until more discussion follows. -- CapitalR 08:20, 30 September 2007 (UTC)
Hi — I was wondering if anyone else felt that the gaps between lines that wrap around were a little too wide? When I view the following, for example, the bottom line of list1 looks nearer to the top of line of list2 rather than to the preceding line in list1; note also the line-spacing of the "Quite-a-long group title":
Can the line-spacing in this template be modified to reduce this gap? Thanks, Sardanaphalus 00:59, 28 September 2007 (UTC)
|list1 = <div> blah{{·}} blah{{·}} blah [etc] </div>
In other words, not just using a line-break before the list, but making it a <div> as well. Do you think people would be happy to have this formatting included in the Navbox/core code? Best wishes, Sardanaphalus 13:07, 29 September 2007 (UTC)
The first example is how the code works now. The second example above has the divs for all lists/above/below (which is what was suggested as an edit protected in {{ Navbox/core}}), and you can see how much taller the lists/groups/above/below become, making it look quite weird. I think we should just leave it as is for now until more testing can be done to figure out if we can get around this problem. Also, I'm fairly certain that many templates will get messed up by adding the breaks before/after each list or adding div containers around each list, so we can't make the change yet without more testing. -- CapitalR 08:26, 30 September 2007 (UTC)
<div style="margin:-4px; 0px;"> {{{l1|}}} </div>
I'll do more testing and try to estimate the unintended side effects of adding this to the Navbox/core code. -- CapitalR 09:03, 30 September 2007 (UTC)
![]() | This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 1 | Archive 2 | Archive 3 | → | Archive 5 |
{{
editprotected}}
My goal is to make this 100% compatible with {{ Navigation}} so that this template can replace that one. The major reason is that a bug fix which repaired NavFrame behavior caused {{ Navigation}} to be always initially closed. So we need to implement category:
Please change:
|l1 = {{{body|}}}{{{list1|}}}
to:
|l1 = {{{body|}}}{{{list1|}}}{{{category|}}}
Thank you. ← BenB4 15:51, 19 August 2007 (UTC)
{{
editprotected}}
I have made a template and some CSS code that prevents word wraps inside links and only allows word wraps between the links and in normal text. This is useful for instance for long link lists.
The {{ nowraplinks}} template has now been fully deployed and the CSS code added to common.css. I and other editors have tested it in several ways in several browsers. There for I suggest that the CSS class is used here (in Template:Navbox) to save users of this navigation box from using lots and lots of or {{ nowrap}}. I have tested it with the template's current code in my own testpages/sandboxes.
I suggest that the first line of Template:Navbox/core should be changed to:
<table class="navbox collapsible {{{state|autocollapse}}} nowraplinks"
While I am at it I suggest that the last few lines of Template:Navbox be changed to:
}}<noinclude> {{protected template}} {{template doc}} <!-- Add categories and interwikis to the /doc subpage, not here! --> </noinclude>
The change of the last few lines is to get the documentation look and feel recommended in Wikipedia:Template documentation. (The two empty lines between the "protected template" and the "template doc" is to prevent the green documentation box to come too close to the template, just to make the template page more readable.)
This template seems to have the same purpose and even much of the same logic as Template:Navbox generic. I see that Template:Navigation, which again had the same purpose, was recently merged in to this one... but why did we ever have three to begin with? Offhand I don't see any features or options which couldn't all be included in a single template. -- CBD 11:57, 20 August 2007 (UTC)
{{ editprotected}}
Can the [ hide/show ] be made in small text. To correspond with the " v . d . e ", size text. It also looks ugly with the [ and ] not linked to the hide/show.
It should be more like {{ Navigation}} (which is being depreciated). It looks nicer. SpecialWindler talk 10:06, 21 August 2007 (UTC)
Does anyone know where the "v•d•e" comes from? They aren't in Template:Navbox/core. ← BenB4 14:14, 21 August 2007 (UTC)
I think that the default groupstyle should use "vertical-align:middle;" just like {{ Navbox generic}} does. It just looks better and works even better here at {{ Navbox}} than at {{ Navbox generic}}, since {{ Navbox}} has every second list greyed thus the group heading doesn't need to be aligned with the top of the list to show where the list starts. -- David Göthberg 12:43, 24 August 2007 (UTC)
This is what we have now:
This is what I propose for colors:
The old code is currently:
Navbox:
|bodystyle = {{{style|}}}{{{bodystyle|}}} |titlestyle = {{{titlestyle|}}} |abovestyle = background:#ddddff;{{{abovestyle|}}} |belowstyle = background:#ddddff;{{{belowstyle|}}} |above = {{{above|}}} |below = {{{below|}}} |gs = white-space:nowrap;background:#ddddff;text-align:right;vertical-align:top;{{{groupstyle|}}} |os = width:100%;font-size:95%;{{{liststyle|}}}{{{oddstyle|}}} |es = width:100%;font-size:95%;background:#f7f7f7;{{{liststyle|}}}{{{evenstyle|}}}
Navbox/core
<table class="navbox collapsible {{{state|autocollapse}}} nowraplinks" style="margin:auto; {{#ifeq:{{{nogroups|}}}|true||background:white; }}{{#if:{{{l1|}}}|{{#if:{{{l2|}}}|background:white; }}}}{{{bodystyle|}}}"><!--
The new code would be:
Navbox
|bodystyle = {{{style|}}}{{{bodystyle|}}} |titlestyle = {{{titlestyle|}}} |abovestyle = background:#ddddff;{{{abovestyle|}}} |belowstyle = background:#ddddff;{{{belowstyle|}}} |above = {{{above|}}} |below = {{{below|}}} |gs = white-space:nowrap;background:#ddddff;text-align:right;vertical-align:middle;{{{groupstyle|}}} |os = width:100%;font-size:95%;{{{liststyle|}}}{{{oddstyle|}}} |es = width:100%;font-size:95%;background:#f5f5ff;{{{liststyle|}}}{{{evenstyle|}}}
Navbox/core
<table class="navbox collapsible {{{state|autocollapse}}} nowraplinks" style="margin:auto;background:#fcfcfc{{{bodystyle|}}}"><!--
What do you all think? -- CapitalR 13:39, 24 August 2007 (UTC)
So this is what I (David) propose for colours:
{{ editprotected}}
Could the default font size be changed from 95% to 100% (i.e normal size)? Wikipedia (and any navbox) is for everyone, not just those with perfect vision. Tompw ( talk) ( review) 18:03, 2 September 2007 (UTC)
Is there some particular reason why the group labels aren't centered vertically in their cells? Placing them at the top seems a bit strange. Kirill 21:32, 2 September 2007 (UTC)
Well I guess we can just do this right now so it can take effect before all of the other changes are made.
{{
edit protected}}
Change the "gs" parameter to have the "vertical-align:top" part be changed to "vertical-align:middle". All that needs to be done is to change that one word. Thanks, -
CapitalR 23:03, 2 September 2007 (UTC)
Sorry if this is the wrong place, but is there a specific limitation in the navbox template which means that sub-tables have to be in HTML rather than Wiki markup? Trying to use Wikitables for lists results in a single open curly bracket. I'm asking because I'm trying to make Template:Compression Formats as simple as possible, but keeping the tables for internal layout. Chris Cunningham 14:10, 8 September 2007 (UTC)
{{!}}
to trick MediaWiki into accepting a pipe as parameter. I am not sure that would work in your case.There has been a move (which I approve of) to convert existing templates to use Navbox, which has nicely implemented the collapsible templates on many pages. However, this has broken custom colorization of VDE links in the title bars of many templates. For those templates using dark backgrounds in the title bar (which includes many university athletic teams, which are using school colors), the VDE links can now be nearly impossible to see. (See Template:AuburnBasketballCoach and Template:CaliforniaBasketballCoach for examples.) The title itself and the show/hide links take on the custom color, so it would be great if the VDE links could as well. Is this possible? Thanks. WildCowboy 08:55, 14 September 2007 (UTC)
I have noticed that when a link clicked on in a template, and it no longer appears as a link but as bold text, the nowrap no longer works. See: {{ US Presidents}}, click on Van Buren, my screen resolution setting is 1024px X 768px using FireFox. When Van Buren is the active page, the name wraps to the next line. This is an extremely minor nit-picky point, but if you can fix it go for it. Otherwise, forgetaboutit. Regards.-- Old Hoss 21:17, 21 September 2007 (UTC)
There's a problem with {{ Fourth Balkenende cabinet}}, at least in Firefox. Some of the text appears outside of the box. Anyone know what's going on and how to fix that? JACO PLANE • 2007-09-24 09:23
Say if we find a template that needs to be changed but we don't have the expertize or time to change it, is there a way we can tag it (eg: a category)? Peachey88 07:28, 26 September 2007 (UTC)
Anyone know where I can find a tutorial on how to create a navbox for my own site? Thanks Travb ( talk) 08:49, 27 September 2007 (UTC)
{{ editprotected}}
Firstly, the main page documentation doesn't mention the category
attribute, which can be used to add cats to transcluded pages.
Secondly, these should be <noinclude>d from the category itself. See Template: Games Workshop, which transcludes Category: Games Workshop onto pages which include it but avoids being part of that category itself. I'd rather this were automatic with the attribute, because templates shouldn't be getting tagged with article namespace cats.
Chris Cunningham 12:49, 27 September 2007 (UTC)
{{Navbox |title = Title |list1 = List |category = <includeonly>[[Category:Cat1]]</includeonly><noinclude>[[Category:Cat2]]</noinclude> }}
{{Navbox |title = Title |list1 = List }}<includeonly>[[Category:Cat1]]</includeonly><noinclude>[[Category:Cat2]]</noinclude>
The two above calls do exactly the same thing, so there's really no point in using a category parameter in my opinion. It just makes the template more complicated to understand without adding any use. It's easier to just add the categories at the end after the Navbox call instead of inside of it. Unfortunately, we can't just add the includeonly tags to this main Navbox template, as it would screw up lots of templates that are (unfortunately) using the category parameter. I'm going to remove the editprotected tag for now until more discussion follows. -- CapitalR 08:20, 30 September 2007 (UTC)
Hi — I was wondering if anyone else felt that the gaps between lines that wrap around were a little too wide? When I view the following, for example, the bottom line of list1 looks nearer to the top of line of list2 rather than to the preceding line in list1; note also the line-spacing of the "Quite-a-long group title":
Can the line-spacing in this template be modified to reduce this gap? Thanks, Sardanaphalus 00:59, 28 September 2007 (UTC)
|list1 = <div> blah{{·}} blah{{·}} blah [etc] </div>
In other words, not just using a line-break before the list, but making it a <div> as well. Do you think people would be happy to have this formatting included in the Navbox/core code? Best wishes, Sardanaphalus 13:07, 29 September 2007 (UTC)
The first example is how the code works now. The second example above has the divs for all lists/above/below (which is what was suggested as an edit protected in {{ Navbox/core}}), and you can see how much taller the lists/groups/above/below become, making it look quite weird. I think we should just leave it as is for now until more testing can be done to figure out if we can get around this problem. Also, I'm fairly certain that many templates will get messed up by adding the breaks before/after each list or adding div containers around each list, so we can't make the change yet without more testing. -- CapitalR 08:26, 30 September 2007 (UTC)
<div style="margin:-4px; 0px;"> {{{l1|}}} </div>
I'll do more testing and try to estimate the unintended side effects of adding this to the Navbox/core code. -- CapitalR 09:03, 30 September 2007 (UTC)