User talk:Lord Farin/Long-Term Projects/Extension

From ProofWiki
Jump to navigation Jump to search

By:

"I strive for the possibility to adjust the heading level of all stuff inside the transcluded tag at once, avoiding the struggle now often encountered."

... presumably you mean:

"I strive for the possibility to adjust the heading level of all stuff inside the transcluded tag automatically, avoiding the struggle now often encountered."

In which case I'd say that would probably be the main aim of the entire exercise, which is an excellent aim.

One point: the suggestion is to add (ht/x)ml-style tags, which would work for computer-literate people, but may be confusing for some; would the curly-bracket "template" model work instead? This point needs further discussion. I'm not too worried either way, just thought I'd mention it as a point to consider.

Apart from that, a brilliant proposal. --prime mover 01:27, 1 March 2012 (EST)

Your assessment of my intentions was correct. Considering the tags, I think it is best to use the HTML/XML tags, because otherwise we would restrict ourselves to:
  1. Losing the possibility for the useful expressions {{ and }} throughout the site.
  2. Having to enclose huge portions of text inside these brackets, which is prone for errors and less 'clean' so to speak, than the XML tags.
So I have thought about the issues that using tags would give, but they are outweighed by the fact that the alternatives have bigger downsides; at least for the structuring tags. I think it isn't possible to overload the {{:Pagename}} construct to be parsed by a handwritten function. However, it is possible to, instead of a <transclude> tag, create a template-resembling, so-called parser function {{#transclude:Pagename|option=option}}. Mentioning it, this might be a better technique. --Lord_Farin 03:36, 1 March 2012 (EST)
XML/HTML: Okay, no worries. You know what you're about. --prime mover 16:20, 1 March 2012 (EST)