Difference between revisions of "DPL Extension Testing Ground"

From Project: Gorgon Wiki
Jump to: navigation, search
(Testing table of abilities with DPL pulling from multiple articles.)
(Ability table (work in progress))
Line 54: Line 54:
  
 
==Ability table (work in progress)==
 
==Ability table (work in progress)==
 +
This can be made to look nice, and the same code can be used to output various skill tables. I don't like the complexity though, simple "row templates" like the NPC Shops would be easier to do and easier to understand. However this is the only way I can think of atm in case developer wants to feed all individual abilities/recipes/etc in separate articles.
 +
 +
We don't really need this automation because there is no real need to pull abilities in various formats across various pages. They are mostly going to be listed on the Skills page, and NPCs only feature a subset of abilities that they can train, which can be maintained manually.
 +
 
{{Ability table
 
{{Ability table
 
| category = Fire Magic abilities
 
| category = Fire Magic abilities
 
}}
 
}}

Revision as of 17:07, 26 October 2014

This page is used for testing the DPL extension (it should be an orphan page). See DPL Manual.

DPL Cheatsheet

Invocation

We can use <dpl> or {{ #dpl: ... }} to invoke DPL (Dynamic Page Lists). The latter is more powerful:

  • Magic words like {{PAGENAME}} or {{CURRENTDAY}} can be used.
  • Template calls like {{{some template}}} can be used as parameters.
  • Parser function calls like {{#if:...|...|...}} can be used within arguments.

Special characters and escaping

Wiki characters must be escaped in the DPL arguments:

  • Use {{!}} (ie. Template:!) or the special symbol ¦ to escape the pipe character.
  • or \n must be used to insert a linefeed character where linefeeds are required by the wiki formatting.

Example of using an escape pipe character:

{{#dpl:
  |category = cat1¦cat2
  |linksto  = {{{1}}}
}}

Debugging

 resultsheader=«pre»«nowiki»
 resultsfooter=«/nowiki»«/pre»

Using Titlematch

Pulling all news article for 2014 only. Note! : titlematch can create inefficient queries, and should not be necessary if categories can do it.

dplreplace

This could be useful... (manual)

 {{#dplreplace:abrakadabra|ab|AB}}

ABrakadABra

uses (pulling pages using certain templates)

This is the main way we could handle skills/recipes tables with DPL and templating. WORK IN PROGRESS (trying to figure out the templating of table rows with DPL).

Ability table (work in progress)

This can be made to look nice, and the same code can be used to output various skill tables. I don't like the complexity though, simple "row templates" like the NPC Shops would be easier to do and easier to understand. However this is the only way I can think of atm in case developer wants to feed all individual abilities/recipes/etc in separate articles.

We don't really need this automation because there is no real need to pull abilities in various formats across various pages. They are mostly going to be listed on the Skills page, and NPCs only feature a subset of abilities that they can train, which can be maintained manually.

Extension:DynamicPageList (DPL), version 2.3.0 : Warning: No results.