Welcome to Template talk:Ent!
This is the start of the
To add a new message, click on "Add Topic/Reply" button below, and set the "Subject".
To add a Reply, do the same as above, but leave the "Subject" blank.
Ent
discussion page.To add a new message, click on "Add Topic/Reply" button below, and set the "Subject".
To add a Reply, do the same as above, but leave the "Subject" blank.
Andreasen 10:21, 23 September 2007 (UTC)
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 12:11, 23 September 2007 (UTC)
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 20:27, 23 September 2007 (UTC) (edited)
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).
One Template, two Purposes
Popcorn 20:52, 23 January 2023 (UTC)
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
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.DaKang233 9:03, 24 January 2023 (UTC+8) (edited)
We originally wanted to move
Before the mode has deprecated by all pages, we can't delete the code for compatibility.
{{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.
Merge with Template:Command
Equalizer 9:07, 22 March 2024 (UTC−7)