Module talk:Location map/data/CanadaTerrain

This is an old revision of this page, as edited by Wikid77 (talk | contribs) at 18:41, 10 February 2008 (New parser verified for 80x more template code: new subtopic). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Latest comment: 17 years ago by Wikid77 in topic Split as minimal

This is the discussion/talk page for: Template:Location map CanadaTerrain.

Created

06-Nov-2007: The file "Template:Location map CanadaTerrain" was created November 6, 2007, to allow placing markers over similar terrain maps of Canada. It was created for using the new mapping procedure Template:Location_map_polarx, which can position markers/labels at coordinates skewed to match locations on polar-projection maps. An example using that new template is included to show markers placed on the terrain map of Canada. -Wikid77 20:15, 6 November 2007 (UTC)Reply

Split as minimal

08-Nov-2007: I have split the template description text into a doc file, leaving only a minimal list of settings in the original template. After months of fighting horrific template-resource limits, with templates going wiki-spazoid, I finally discovered the horrific problems of limited templates were formerly caused by the large "nonincluded" text sections of the map-definition templates. Chock up another nightmare to the wikispastic "<noinclude>" tag, another peculiar child of the wikipuke language: well, it seems to INCLUDE the "non-included" text well enough to overwhelm files that include the template multiple times. Okay, it didn't really "include" the non-included text, it just semi-included it enough to cause wikipuking, wikispastic, wikigagging on map templates.

Unlike a sane programming language (which might report, "Language stack full, ignoring nested expressions..."), the MediaWiki-puke language, well, sort of wikipukes more vomitous output of the form "[[image:#if:|180px|180|#if:" (or "Unrecognized ["), with the wikivomit output hiding the true meaning that the "language-processing limits have been reached". After months of trimming templates to run within the limited resources, it's great to discover that "nonincluded" text was clogging the MediaWiki language processing & was causing the exceeded resource limits. Well, imagine that: hundreds of wasted hours, and another reason that people abandon efforts to improve Wikipedia. -Wikid77 07:54, 8 November 2007 (UTC)Reply

10-Feb-2008: In January 2008, new MediaWiki software vastly raised the limits (see below). -Wikid77 (talk) 18:41, 10 February 2008 (UTC)Reply

New parser verified for 80x more template code

10-Feb-2008: In January 2008, the MediaWiki software was quietly revolutionized to use a new parser that bypassed unused template coding (such as in conditional false branches) and skipped template-expansion in the bypassed sections. The new parser could process nested templates over 80 times larger than in November 2007.
Feb.10, 2008, I ran temporary tests with "Template:Location map CanadaTerrain" by repeating the Examples section 14 times as 42 examples using "Location_map_polarx" (28 times) and "Location_map_many_polarx" (14 times). Those 42 examples contained 10,108 uses of "Location_map_CanadaTerrain" as 10,108= 14 * (206+206+310) calls/transclusions. Meanwhile Location_map_CanadaTerrain was stuffed as 4620b with block-text (beyond the former limit of 1.5kb) to verify that noinclude-sections are skipped by the new parser. The gargantuan total result was over 46 MEGABYTES of nested templates, and all 42 examples displayed their Canada maps with no problems: all 46MB+ of template code was processed with no messages reported. Formerly, only 2 mappings of Location_map_polarx were allowed per article; the processing of 42 mappings with block-text in map-specs was over 80 times more capacity. -Wikid77 (talk) 18:41, 10 February 2008 (UTC)Reply

Testing new MediaWiki parser from Jan. 2008

10-Feb-2008: A WP admin informed me days ago that a new MediaWiki parser was installed in January 2008, which will omit noinclude-sections from the template-processing limits. I am testing that new parser now, using the CanadaTerrain template as a known limiting case, which formerly choked when holding over 1.5kb of total text. -Wikid77 (talk) 14:37, 10 February 2008 (UTC)Reply

Other issues

[ Discuss other, unnamed issues here. -Wikid77 ]