User talk:Smls

From Rosetta Code
Revision as of 07:06, 25 August 2016 by rosettacode>Smls (typos)

use of the   {{out}}   template

Since you're into templates, do you know if the   {{out}}   template can support the adding (or appending/concatenating) of text to the bold   Output   "title"   (and keep the additional text   on the same line) ?

(I have no idea where the template is kept, who can modify it, or if it can be changed.)


I normally use something like   (usually immediately after the   </lang>   HTML tag):

 '''output'''   when using the input of:   <tt> 12   -6 </tt> 

which renders to:

output   when using the input of:    12   -6 

and some people (or person) have been changing the   '''output'''   when using ...   to

 {{out}} when using ... 

which renders to:

Output
 
when using ...

which changes the apparent antecedent of the   when   and modifies my (original) meaning of the phrase.

Also note the additional blank line.


I understand it would be nice to have all the computer programming entries use (more or less) the same (if not a constant) template, but I don't know where the options for (this particular) template(s) are documented (if at all).

At this point, I'm not sure if it is worth the bother, as I certainly don't have the timer or inclination to change over a thousand of my entries.   (I'm not sure of the number, but I think over half of my REXX entries have multiple   output   sections, almost all of them have appended comments.)

-- Gerard Schildberger (talk) 02:39, 25 August 2016 (UTC)

Sure, that kind of template extension is easy. Strangely enough, the {{out}} template already accepted an an undocumented positional parameter to replace the word "Output" with something else, as in {{out|Return value}}. To be safe I left that as it was, and added the new options as named parameters instead. I also put some usage documentation on the Template:Out page. Does it suit your needs now? --Smls (talk) 07:02, 25 August 2016 (UTC)

general feelings about (some) templates

An oversimplification of past experiences in the distant past ··· but my overall feelings of templates (experienced here on Rosetta Code) is that templates have a tendency to be used to pound square pegs into round holes,   or at least, that's my observations with the few that impacted my many numerous entries on Rosetta Code.

Either the templates don't have the flexibility (or the necessary options) to support what I want (or my meaning), or the people don't know that the converting of (header or title) text into a form that they weren't intended for   (or they/it may have changed the original meaning or intent).   I always thought that templates were mostly used (in the templates that I normally used) for general text (for instance, headers, titles and such)   and to supply a shortcut or abbreviated method to (help) express it succinctly.   That is, to be used as tools, not necessary as a method to enforce conformity.   -- Gerard Schildberger (talk) 03:12, 25 August 2016 (UTC)