Template talk:Ent: Difference between revisions
1416006136 (talk | contribs) No edit summary |
1416006136 (talk | contribs) (style updated) |
||
| Line 1: | Line 1: | ||
I think that if Jeff would know [http://www.w3schools.com/xml/default.asp XML], he could simply create a new tag in the CSS itself, called <nowiki><ent></nowiki>. That would leave the question, what is easier to write - "<nowiki>{{ent|path_track}}</nowiki>" or "<nowiki><ent path_track/></nowiki>"? | {{Discussion page}} | ||
{{Message|I think that if Jeff would know [http://www.w3schools.com/xml/default.asp XML], he could simply create a new tag in the CSS itself, called <nowiki><ent></nowiki>. That would leave the question, what is easier to write - "<nowiki>{{ent|path_track}}</nowiki>" or "<nowiki><ent path_track/></nowiki>"?|user=Andreasen|time=10:21, 23 Sep 2007}} | |||
{{Message|Not much of a difference really...|user=Ts2do|time=12:06, 23 Sep 2007}} | |||
{{Message|The big difference would be if Valve allowed us to set the CSS on our user settings page. In that way Jeff would get his highlighting, while I could just read the ents as plain text, at the same time. |user=Andreasen|time=12:11, 23 Sep 2007}} | |||
Actually, as this template means that entities will ''always'' be linked to, Jeff is against it, as this is considered excess use of linking. Unless you can write <nowiki>[[{{ent|func_wholly}}]]</nowiki>, XML tags seems like the only possibility (and don't consider writing a "<nowiki>{{nolinkent| }}</nowiki>", please). | {{Message|Actually, as this template means that entities will ''always'' be linked to, Jeff is against it, as this is considered excess use of linking. Unless you can write <nowiki>[[{{ent|func_wholly}}]]</nowiki>, XML tags seems like the only possibility (and don't consider writing a "<nowiki>{{nolinkent| }}</nowiki>", please).|user=Andreasen|edited=1|time=20:27, 23 Sep 2007}} | ||
== One Template, two Purposes == | == One Template, two Purposes == | ||
If I may ask, why use this template for two completely different purposes? (1. a code-style link, 2. the first sentence for an entity page)<br> | {{Message|If I may ask, why use this template for two completely different purposes? (1. a code-style link, 2. the first sentence for an entity page)<br> | ||
If we want to revolutionize {{tl2|point ent}}, then I'd suggest doing the first step with a new template, and not with this simple template that is being used on nearly every page. Extending {{tlc|ent}} for two distinct purposes makes it unnecessarily hard to find the pages that use {{tlc|ent}} for just one of the two purposes. And honestly, isn't it annoying to write {{tlc|ent|mode{{=}}entity|...}} every time? Why not make a new template? [[Template:Entity]] is still open. | If we want to revolutionize {{tl2|point ent}}, then I'd suggest doing the first step with a new template, and not with this simple template that is being used on nearly every page. Extending {{tlc|ent}} for two distinct purposes makes it unnecessarily hard to find the pages that use {{tlc|ent}} for just one of the two purposes. And honestly, isn't it annoying to write {{tlc|ent|mode{{=}}entity|...}} every time? Why not make a new template? [[Template:Entity]] is still open.|user=Popcorn|time=20:52, 23 January 2023}} | ||
{{Message|We originally wanted to move {{tl|point ent}} to {{tl|ent}} when it was finished improvement. I think it's a good idea that making a new template on a new page. I will move the template later.<br>Before the mode has deprecated by all pages, we can't delete the code for compatibility.|user=1416006136|time=01:03, 24 January 2023|edited=1}} | |||
Revision as of 11:44, 1 February 2023
Comments on talk pages should be signed with "~~~~", which will be converted into your signature and a timestamp.
(using Template:Message) I think that if Jeff would know XML, he could simply create a new tag in the CSS itself, called <ent>. That would leave the question, what is easier to write - "{{ent|path_track}}" or "<ent path_track/>"? --Andreasen (talk) 10:21, 23 Sep 2007 (UTC)
(using Template:Message) Not much of a difference really... --Ts2do (talk) 12:06, 23 Sep 2007 (UTC)
(using Template:Message) The big difference would be if Valve allowed us to set the CSS on our user settings page. In that way Jeff would get his highlighting, while I could just read the ents as plain text, at the same time. --Andreasen (talk) 12:11, 23 Sep 2007 (UTC)
(using Template:Message) Actually, as this template means that entities will always be linked to, Jeff is against it, as this is considered excess use of linking. Unless you can write [[{{ent|func_wholly}}]], XML tags seems like the only possibility (and don't consider writing a "{{nolinkent| }}", please). --Andreasen (talk) 20:27, 23 Sep 2007 (UTC)
One Template, two Purposes
(using Template:Message) If I may ask, why use this template for two completely different purposes? (1. a code-style link, 2. the first sentence for an entity page)
If we want to revolutionize {{point ent}}, then I'd suggest doing the first step with a new template, and not with this simple template that is being used on nearly every page. Extending {{ent}} for two distinct purposes makes it unnecessarily hard to find the pages that use {{ent}} for just one of the two purposes. And honestly, isn't it annoying to write {{ent|mode=entity|...}} every time? Why not make a new template? Template:Entity is still open. --Popcorn (talk) 20:52, 23 January 2023 (UTC)
(using Template:Message) We originally wanted to move {{point ent}} to {{ent}} when it was finished improvement. I think it's a good idea that making a new template on a new page. I will move the template later.
Before the mode has deprecated by all pages, we can't delete the code for compatibility. --1416006136 (talk) 01:03, 24 January 2023 (UTC)