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 4 |
The CSS I propose for asbox (currently hardcoded into the sandbox template
table.asbox {
clear: left;
background: transparent;
}
.asbox th.mbox-text,
.asbox td.mbox-text { /* The message body cell(s) */
font-style: italic; /* Text is italic */
padding: 0em; /* We don't need padding to the left */
width: auto; /* Use normal width */
}
.asbox td.mbox-image { /* The left image cell */
padding: 0em; /* no padding */
}
possibly add also.
table.navbox + table.asbox,
p + table.asbox,
table + table.asbox,
div + table.asbox,
ol + table.asbox,
ul + table.asbox {
margin-top: 1em; /* Margin at top of stack */
}
Your thoughts please ? — TheDJ ( talk • contribs) 14:21, 4 May 2009 (UTC)
p + table.asbox { margin-top: 1em; }
". Or 0.5em. I didn't find it important with the navboxes since paragraphs already have a .5 margin-bottom, but stubs offer a less clear separation from the text, and are much more likely to be placed directly beneath a paragraph.
Amalthea 15:31, 4 May 2009 (UTC)
I believe the recent conversion of the stub templates has left Wikipedia:WikiProject Roads in Maryland/Editing guide broken. Can this be fixed? -- Rschen7754 ( T C) 18:24, 17 August 2009 (UTC)
Per the discussion at Wikipedia talk:WikiProject Stub sorting#/docs I am planning to transclude some common documentation for stub templates on the template page itself (i.e. when {{{name}}}={{FULLPAGENAME}}. I've started a possible version at Template:Stub documentation. It's basically an abridged version of WP:Stub, although it needs further work. Are there any comments or concerns about this? I will of course put the proposed code on the sandbox so that people can look over it before implementing. — Martin ( MSGJ · talk) 22:17, 20 August 2009 (UTC)
In order to keep {{ stub documentation}} free of parser functions and editable by members of WP:WSS without needing any template knowledge I propose to move the template-specific documentation (which is using more and more parameters and parser functions) to /templatepage and keep Template:stub documentation for general (brief) information about stubs. Sound okay? — Martin ( MSGJ · talk) 14:31, 22 August 2009 (UTC)
Using some large clunky template code it is possible to show related templates in the documentation, so for example with {{ England-footy-bio-stub}} we could include:
Related Stubs
The code to do this is
===Related Stubs=== *{{#ifexist:Template:{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-18}}|18}}|{{tl|{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-18}}|18}}}}}} *{{#ifexist:Template:{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-17}}|17}}|{{tl|{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-17}}|17}}}}}} *{{#ifexist:Template:{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-16}}|16}}|{{tl|{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-16}}|16}}}}}} *{{#ifexist:Template:{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-15}}|15}}|{{tl|{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-15}}|15}}}}}} *{{#ifexist:Template:{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-14}}|14}}|{{tl|{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-14}}|14}}}}}} *{{#ifexist:Template:{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-13}}|13}}|{{tl|{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-13}}|13}}}}}} *{{#ifexist:Template:{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-12}}|12}}|{{tl|{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-12}}|12}}}}}} *{{#ifexist:Template:{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-11}}|11}}|{{tl|{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-11}}|11}}}}}} *{{#ifexist:Template:{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-10}}|10}}|{{tl|{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-10}}|10}}}}}} *{{#ifexist:Template:{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-9}}|9}}|{{tl|{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-9}}|9}}}}}} *{{#ifexist:Template:{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-8}}|8}}|{{tl|{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-8}}|8}}}}}} *{{#ifexist:Template:{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-7}}|7}}|{{tl|{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-7}}|7}}}}}}
(although it could be simplified a bit if put into sub-templates)
Is this worth adding? -- WOSlinker ( talk) 22:09, 25 August 2009 (UTC)
{{subtemplate|{{Str index|{{PAGENAME}}|1}} |{{Str index|{{PAGENAME}}|2}} |{{Str index|{{PAGENAME}}|3}} |...etc...}}
I have been thinking about how best to continue with this template. I have the following ideas, and I would like it people would comment.
— TheDJ ( talk • contribs) 18:38, 9 May 2009 (UTC)
{{
image|{{{image}}}|40x30px}}
, which accepts both full image syntax as well as only the name of the image (with namespace or without).<br />
. I give up: what is <s />
? ---—
Gadget850 (Ed)
talk 01:23, 21 May 2009 (UTC)
<s />
an error or a valid? ---—
Gadget850 (Ed)
talk 15:55, 21 May 2009 (UTC)
Is there a way to over-ride the category, e.g. for sample display? – xeno talk 12:48, 27 August 2009 (UTC)
The namespace detection is great, except when templates are being shown as examples on template pages... i.e.
category=History stubs
would need to become
category={{{category|History stubs}}}
On pages such as Template:Coord missing/sample 1, these are a little tricky, but I think we could use something like
{{Arizona-geo-stub<noinclude>|category=no</noinclude>}}
Any better solutions? — Martin ( MSGJ · talk) 16:12, 2 September 2009 (UTC)
|demo=
which can be set to suppress any categories and warnings. Anyone care to check the code for me? — Martin (
MSGJ ·
talk) 15:31, 3 September 2009 (UTC)It's late (for me) and I'd certainly cock things up if I started fiddling. here are things I;ve noticed in the documentation:
icon
and image
, but in Full usage just above, icon
is not listed.pix
, we do not specify the anticipated input format for pix
. We talk about its default value of 40x30, which might lead a user to expect that this format of input is required. Lower down the page in the Using image
an example shows a single input value of 30. Other templates (iirc) user 30px. Specifying the format anticipated by pix
is recommendedthanks -- Tagishsimon (talk) 07:14, 26 August 2009 (UTC)
Yes, I was hoping that eventually icon
would be phased out. As far as the pix
goes there is a default value, and again it would be "best" if all templates used the default value, and the pix parameter could be obsoleted. Certainly updating the docs with strong advice to use 40x30 would be useful. Both these compromises came from my initial plan to cause minimum impact when implementing {Asbox}.
Rich
Farmbrough, 21:18, 31 August 2009 (UTC).
I think it would be useful for the maintainers of stub templates to have a navbar somewhere on it. Obviously this is not needed for the general reader and should be hidden by default. On {{ WPBM}} this was achieved by using style=display:none; and then allowing individual editors to override this in their monobooks. I'm not an expert, but I'll look into it if anyone thinks this is a nice idea. — Martin ( MSGJ · talk) 11:20, 24 July 2009 (UTC)
|name=
to allow building the v·e·d links, like with {{
v|d|e|template={{{name}}}}}
.I did play around with some options for a navbar in the sandbox (but I think TheDJ's latest version has erased it). I think it would be look best and be least intrusive on the far right. Alas I was unable to achieve this. If anyone can help, it would be appreciated. — Martin ( MSGJ · talk) 22:06, 20 August 2009 (UTC)
.stub .navbar {display:inline !important;}
to your monobook.css file. An example template using it is Template:Arizona-geo-stub/sandbox which produces:
Thanks in advance — Martin ( MSGJ · talk) 19:07, 9 September 2009 (UTC)
font-size:smaller;
would be better. Technically the implementation is fine.
Happy‑
melon 22:33, 9 September 2009 (UTC)
It's been pointed out to me that positioning the navbar absolutely on the right side is not always ideal, (for example see Wairoa River, Tasman). Can this be improved at all? — Martin ( MSGJ · talk) 09:25, 11 September 2009 (UTC)
Can we add maintenance categories... split asbox'en into
? – xeno talk 18:11, 9 August 2009 (UTC)
As soon as name has been added to all the templates, we can move all these maintenance categories (apart from "erroneous name" I guess) to /templatepage to keep the code nicer. — Martin ( MSGJ · talk) 13:28, 24 August 2009 (UTC)
Would you care to check Template:Asbox/sandbox for me? — Martin ( MSGJ · talk) 15:22, 25 August 2009 (UTC)
Is it possible with the str len magic that WOSlinker used for the heirarchy? And is it desirable? I know that Xenobot made a couple goofs (forgetting the word "stubs" at the end of the category) which I think I've fixed all, but a maintenance category to make sure would help me to be at ease, and it would also identify asbox that category into non-stub categories, which is and all-around bad idea. – xeno talk 20:06, 4 September 2009 (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 4 |
The CSS I propose for asbox (currently hardcoded into the sandbox template
table.asbox {
clear: left;
background: transparent;
}
.asbox th.mbox-text,
.asbox td.mbox-text { /* The message body cell(s) */
font-style: italic; /* Text is italic */
padding: 0em; /* We don't need padding to the left */
width: auto; /* Use normal width */
}
.asbox td.mbox-image { /* The left image cell */
padding: 0em; /* no padding */
}
possibly add also.
table.navbox + table.asbox,
p + table.asbox,
table + table.asbox,
div + table.asbox,
ol + table.asbox,
ul + table.asbox {
margin-top: 1em; /* Margin at top of stack */
}
Your thoughts please ? — TheDJ ( talk • contribs) 14:21, 4 May 2009 (UTC)
p + table.asbox { margin-top: 1em; }
". Or 0.5em. I didn't find it important with the navboxes since paragraphs already have a .5 margin-bottom, but stubs offer a less clear separation from the text, and are much more likely to be placed directly beneath a paragraph.
Amalthea 15:31, 4 May 2009 (UTC)
I believe the recent conversion of the stub templates has left Wikipedia:WikiProject Roads in Maryland/Editing guide broken. Can this be fixed? -- Rschen7754 ( T C) 18:24, 17 August 2009 (UTC)
Per the discussion at Wikipedia talk:WikiProject Stub sorting#/docs I am planning to transclude some common documentation for stub templates on the template page itself (i.e. when {{{name}}}={{FULLPAGENAME}}. I've started a possible version at Template:Stub documentation. It's basically an abridged version of WP:Stub, although it needs further work. Are there any comments or concerns about this? I will of course put the proposed code on the sandbox so that people can look over it before implementing. — Martin ( MSGJ · talk) 22:17, 20 August 2009 (UTC)
In order to keep {{ stub documentation}} free of parser functions and editable by members of WP:WSS without needing any template knowledge I propose to move the template-specific documentation (which is using more and more parameters and parser functions) to /templatepage and keep Template:stub documentation for general (brief) information about stubs. Sound okay? — Martin ( MSGJ · talk) 14:31, 22 August 2009 (UTC)
Using some large clunky template code it is possible to show related templates in the documentation, so for example with {{ England-footy-bio-stub}} we could include:
Related Stubs
The code to do this is
===Related Stubs=== *{{#ifexist:Template:{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-18}}|18}}|{{tl|{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-18}}|18}}}}}} *{{#ifexist:Template:{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-17}}|17}}|{{tl|{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-17}}|17}}}}}} *{{#ifexist:Template:{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-16}}|16}}|{{tl|{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-16}}|16}}}}}} *{{#ifexist:Template:{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-15}}|15}}|{{tl|{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-15}}|15}}}}}} *{{#ifexist:Template:{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-14}}|14}}|{{tl|{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-14}}|14}}}}}} *{{#ifexist:Template:{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-13}}|13}}|{{tl|{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-13}}|13}}}}}} *{{#ifexist:Template:{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-12}}|12}}|{{tl|{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-12}}|12}}}}}} *{{#ifexist:Template:{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-11}}|11}}|{{tl|{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-11}}|11}}}}}} *{{#ifexist:Template:{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-10}}|10}}|{{tl|{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-10}}|10}}}}}} *{{#ifexist:Template:{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-9}}|9}}|{{tl|{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-9}}|9}}}}}} *{{#ifexist:Template:{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-8}}|8}}|{{tl|{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-8}}|8}}}}}} *{{#ifexist:Template:{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-7}}|7}}|{{tl|{{Str sub|{{PAGENAME}}|{{#expr:{{Str len|{{PAGENAME}}}}-7}}|7}}}}}}
(although it could be simplified a bit if put into sub-templates)
Is this worth adding? -- WOSlinker ( talk) 22:09, 25 August 2009 (UTC)
{{subtemplate|{{Str index|{{PAGENAME}}|1}} |{{Str index|{{PAGENAME}}|2}} |{{Str index|{{PAGENAME}}|3}} |...etc...}}
I have been thinking about how best to continue with this template. I have the following ideas, and I would like it people would comment.
— TheDJ ( talk • contribs) 18:38, 9 May 2009 (UTC)
{{
image|{{{image}}}|40x30px}}
, which accepts both full image syntax as well as only the name of the image (with namespace or without).<br />
. I give up: what is <s />
? ---—
Gadget850 (Ed)
talk 01:23, 21 May 2009 (UTC)
<s />
an error or a valid? ---—
Gadget850 (Ed)
talk 15:55, 21 May 2009 (UTC)
Is there a way to over-ride the category, e.g. for sample display? – xeno talk 12:48, 27 August 2009 (UTC)
The namespace detection is great, except when templates are being shown as examples on template pages... i.e.
category=History stubs
would need to become
category={{{category|History stubs}}}
On pages such as Template:Coord missing/sample 1, these are a little tricky, but I think we could use something like
{{Arizona-geo-stub<noinclude>|category=no</noinclude>}}
Any better solutions? — Martin ( MSGJ · talk) 16:12, 2 September 2009 (UTC)
|demo=
which can be set to suppress any categories and warnings. Anyone care to check the code for me? — Martin (
MSGJ ·
talk) 15:31, 3 September 2009 (UTC)It's late (for me) and I'd certainly cock things up if I started fiddling. here are things I;ve noticed in the documentation:
icon
and image
, but in Full usage just above, icon
is not listed.pix
, we do not specify the anticipated input format for pix
. We talk about its default value of 40x30, which might lead a user to expect that this format of input is required. Lower down the page in the Using image
an example shows a single input value of 30. Other templates (iirc) user 30px. Specifying the format anticipated by pix
is recommendedthanks -- Tagishsimon (talk) 07:14, 26 August 2009 (UTC)
Yes, I was hoping that eventually icon
would be phased out. As far as the pix
goes there is a default value, and again it would be "best" if all templates used the default value, and the pix parameter could be obsoleted. Certainly updating the docs with strong advice to use 40x30 would be useful. Both these compromises came from my initial plan to cause minimum impact when implementing {Asbox}.
Rich
Farmbrough, 21:18, 31 August 2009 (UTC).
I think it would be useful for the maintainers of stub templates to have a navbar somewhere on it. Obviously this is not needed for the general reader and should be hidden by default. On {{ WPBM}} this was achieved by using style=display:none; and then allowing individual editors to override this in their monobooks. I'm not an expert, but I'll look into it if anyone thinks this is a nice idea. — Martin ( MSGJ · talk) 11:20, 24 July 2009 (UTC)
|name=
to allow building the v·e·d links, like with {{
v|d|e|template={{{name}}}}}
.I did play around with some options for a navbar in the sandbox (but I think TheDJ's latest version has erased it). I think it would be look best and be least intrusive on the far right. Alas I was unable to achieve this. If anyone can help, it would be appreciated. — Martin ( MSGJ · talk) 22:06, 20 August 2009 (UTC)
.stub .navbar {display:inline !important;}
to your monobook.css file. An example template using it is Template:Arizona-geo-stub/sandbox which produces:
Thanks in advance — Martin ( MSGJ · talk) 19:07, 9 September 2009 (UTC)
font-size:smaller;
would be better. Technically the implementation is fine.
Happy‑
melon 22:33, 9 September 2009 (UTC)
It's been pointed out to me that positioning the navbar absolutely on the right side is not always ideal, (for example see Wairoa River, Tasman). Can this be improved at all? — Martin ( MSGJ · talk) 09:25, 11 September 2009 (UTC)
Can we add maintenance categories... split asbox'en into
? – xeno talk 18:11, 9 August 2009 (UTC)
As soon as name has been added to all the templates, we can move all these maintenance categories (apart from "erroneous name" I guess) to /templatepage to keep the code nicer. — Martin ( MSGJ · talk) 13:28, 24 August 2009 (UTC)
Would you care to check Template:Asbox/sandbox for me? — Martin ( MSGJ · talk) 15:22, 25 August 2009 (UTC)
Is it possible with the str len magic that WOSlinker used for the heirarchy? And is it desirable? I know that Xenobot made a couple goofs (forgetting the word "stubs" at the end of the category) which I think I've fixed all, but a maintenance category to make sure would help me to be at ease, and it would also identify asbox that category into non-stub categories, which is and all-around bad idea. – xeno talk 20:06, 4 September 2009 (UTC)