On Tue, May 22, 2012 at 10:49 AM, Daniel Kinzler daniel.kinzler@wikimedia.de wrote:
For the most part, I tried to keep the normal syntax for template parameters, just introducing structured names (dots and colons). The syntax for selection-by-reference-id is indeed a bit awkward. Perhaps we can just drop it. If this is needed, one can always use the {{#data-value}} function with source=ACME_SURVEY_2010 (perhaps 'ref' is better than 'source').
Whatever the choice is, woudn't it need to be translated to other languages?
form Specifies in what form rendered, that is, in which HTML element the value should be wrapped.
span: wrap in <span> tags, use <span> tags for parts div: wrap in <div> tags, use <span> tags for parts li: wrap in <li> tags, use <span> tags for parts
I don't like this at all, since it limits the number of possibilities, introduces yet another syntax parallel to HTML.
Yet, I don't see anything much better. A half-baked idea is to leave it to the client wikis to create their data display templates that could be used to format data appropriately.
Yes, this is kind of a nasty compromise.
On the one hand, it would be extremely cumbersome to have to re-implement the table (and other) structures for representing property values with various qualifiers, not to speak of the rendering logic for these qualifiers themselves.
On the other hand, we want to allow template authors to integrate property values in different kinds of structures, like tables and lists.
Note that with the help of the show=... parameters, template authors can still implement their own rendering of the value (or rather, statement) with all it's parts, using one {{#data-value}} call for each one.
Here it seems appropriated to ask the same as Jérémie: On Tue, May 22, 2012 at 10:08 AM, Jérémie Roquet arkanosis@gmail.com wrote:
v. What about lua? :)
Best regards, Helder