What about ptwikibooks' usage of https://pt.wikibooks.org/wiki/Template:Lista_de_cap%C3%ADtulos/Posterior?act... https://pt.wikibooks.org/wiki/Template:Lista_de_cap%C3%ADtulos/Anterior?acti... https://pt.wikibooks.org/wiki/Template:Lista_de_cap%C3%ADtulos/Imprimir?acti... https://pt.wikibooks.org/wiki/Template:Lista_de_cap%C3%ADtulos/Cole%C3%A7%C3... etc...? Is that acceptable? Those templates were created as a workaround for features which are (still) missing on non-Wikipedia projects, such as these: https://bugzilla.wikimedia.org/showdependencytree.cgi?id=15071&hide_reso...
It would be really great if on this GSoC 2012, https://www.mediawiki.org/wiki/Summer_of_Code_2012 , some of the projects were focused on improving Wikibooks/Wikisources... I hope someone gets interested.
On Mon, Jan 30, 2012 at 15:24, Roan Kattouw roan.kattouw@gmail.com wrote:
On Mon, Jan 30, 2012 at 3:11 PM, Alex Brollo alex.brollo@gmail.com wrote:
I'm using more and more #switch into templates, it's surprising how many issues it can solve, and how much large arrays it can manage. My
questions
are:
- Is there a reasonable upper limit for the number of #switch options?
- Is there a difference in server load between a long list of #switch
options and a "tree" of options t.i. something as a nested #switch? 3. Is there any drawback into a large use of #swtch-based templates?
I can at least tell you that the answer to #1 is probably no, and the answer to #3 is yes. There were some server issues last week that were blamed on ocwiki's use of templates with #switch statements with thousands of options. For instance, https://oc.wikipedia.org/w/index.php?title=Mod%C3%A8l:Altmejcom&action=e... has 36,611 cases, because it's essentially used as a database. That's the kind of thing that takes forever to parse.
Roan
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l