User talk:Inductiveload/Sandbox

It.source and vec.source looking at this...
I've much to study this template! Our it.source header is terribly complex, but it has a different kind of complexity - that one which comes from a much rougher design and from adding and adding and adding again new features. :-(

Nevertheless I added a trick inside, perhaps it could be useful here too: we can add multiple values (i.e: more than one author, and more then one topic) into one parameter. The trick is, to use #titleparts function; this function can be used a "string-splitter" and it's both intuitive for the user, and not so complex to manage. So, introducing "author AAA/author BBB/author CCC" in the unique "author" field, you can pass three authors into the same field, then using them into the template as you like. --Alex brollo (talk) 23:34, 1 January 2011 (UTC)

vec.source current work about header
There are current works about header template into vec.source, introducing the best from en.source, and it.source. I presume that some excellent algoritms from this new header template will be carefully considered, but I like to share here two fresh ideas of Candalua, coming too (and I'm very bold about!) from some ideas tested into it.source: Dante Alighieri then you can retrieve the author of Divina Commedia by normal labeled transclusion; if the section is inside Divina Commedia, by a code such this: Obviuosly you can hide this code into a template, so making it much more "user-friendly". This can be done for anyone from template fields. Presently all header templates are "semantized" into it.source by an asyncronous bot script; Candalua work will allow to semantize them syncronously with any page edit, a great advancement! --Alex brollo (talk) 08:39, 3 January 2011 (UTC)
 * 1) header template runs as a form, just like Index header; the js script manages bott fields of the template, and the section of the page outside the template (this is a great idea of Candalua IMHO!);
 * 2) The template fields are "tokenized" by the js script, so allowing to "semantize" any of them, t.i. they can be transformed into "variables" that can be individually retrieved by a normal template. The idea is very simple: if you introduce somewhere this code into Divina Commedia: