Treeview extension

This demonstrates the use of the Treeview extension

Treeview can produce clickable tree lists. The interesting thing is that the input for Treeview can either be defined statically or can be derived from a DPL query.

The following images are used in Treeview:   plus   minus.gif   arrow-Closed.png   arrow-Open.png   Folder   Folder-Open   Document   Spacer

Example (static definition of items)

Treeview recognizes lines which start with one or more asterisks just like the mediawiki parser does when it is looking for bullet point lists:

{{#tree:
*A
**A1
**A2
***A21
***A22
**A3
*B
}}

As a result you will get a clickable tree: {{#tree:

• A
  • A1
  • A2
    • A21
    • A22
  • A3
• B

}}

Generating Simple Tree Views with DPL

Treeviews can be generated by DPL, as in the following example. We define a Template called Template:Links 1 which expects

• the direction of the links (outgoing="from" or incoming = "to")
• the source page
• an optional name for the source page

Now we can write something like:

 {{#tree:{{Links 1|from|Wgraph}}}}
               or
 {{#tree:{{Links 1|to|Wgraph|references to the ''Wgraph homepage''}}}}

which will give us two menu trees, one for each direction: {{#tree:

• Wgraph
  • Ahnen
  • Architecture
  • Bug Reports
  • Command Reference
  • Commandline arguments
  • Discussion
  • Example 1
  • Example 2
  • Example 3
  • Example 4
  • Example Timebar
  • Fundamentals
  • Installation
  • Known Bugs
  • Requests for new features
  • Sample Genealogy
  • Tutorial
  • Version History
  • Websites using Wgraph
  • Wgraph Manual

}}

---

{{#tree:

• references to the Wgraph homepage
  • Aa
  • Add "minimum-number-of-revisions" like Criteria for page selection
  • Links 1
  • Main Page
  • NavTree
  • Old Homepage
  • Schwallex
  • TourBusStop

}}

Generating Advanced Tree Views with DPL

Using nested DPL statements we can even produce a menu which shows more than one level of linkage references. Although this can be solved generally with a recursive template we prefer to have an explicitly named template for two levels.

 {{#tree:{{Links 2|from|Wgraph}}}}
           and
 {{#tree:{{Links 2|to|Wgraph}}}}

This will produce the following tree menus: {{#tree:

• Wgraph
  • Ahnen
  • Architecture
    • Structure.wgl
  • Bug Reports
    • Bug Reports Archive
  • Command Reference
    • Commands a
    • Commands b
    • Commands c
    • Commands d
    • Commands e
    • Commands f
    • Commands g
    • Commands h
    • Commands i
    • Commands k
    • Commands l
    • Commands m
    • Commands n
    • Commands o
    • Commands p
    • Commands r
    • Commands s
    • Commands t
    • Commands u
    • Commands v
    • Commands w
    • Commands x
    • Commands y
  • Commandline arguments
  • Discussion
    • Bug Reports
    • Requests for new features
  • Example 1
    • Example 2
    • Example Holiday Planner
    • Example Timebar
    • Sample 1.wgl
  • Example 2
    • Example 1
    • Example 3
  • Example 3
    • Catgraph
    • Cezanne
    • Example 2
    • Example 4
    • Manet
    • Painter
    • Renoir
    • Sample Genealogy
    • Signac
    • Van Gogh
  • Example 4
    • Cezanne
    • Example 3
    • Expressionism
    • Impressionism
    • Manet
    • Painter
    • Renoir
    • Sample Genealogy
    • Signac
    • Van Gogh
  • Example Timebar
  • Fundamentals
    • Architecture
    • Catgraph
  • Installation
    • DavidWhitten/Wgraph Install Notes
    • Download
  • Known Bugs
    • Schwallex
  • Requests for new features
    • Example Timebar
    • Gero
    • Known Bugs
    • Roc michael
    • Sample Genealogy 6
  • Sample Genealogy
    • Sample Genealogy 2
  • Tutorial
    • Tutorial edge layout
    • Tutorial graph layout
    • Tutorial identifiers
    • Tutorial node layout
    • Tutorial shapes
    • Tutorial size
    • Tutorial strings
    • Tutorial types
  • Version History
  • Websites using Wgraph
  • Wgraph Manual

}}

---

{{#tree:

• Wgraph
  • Aa
  • Add "minimum-number-of-revisions" like Criteria for page selection
    • Mode=category loses letter headings when ordermethod=titlewithoutnamespace
  • Links 1
  • Main Page
    • Add "minimum-number-of-revisions" like Criteria for page selection
    • Extension DPL
    • Included Template Name Matching
    • Links 1
    • Manual
    • Modifiedby can return crap result
    • Requests for new features
    • Specific enhancements for 'table from template' DPL
    • StringFunctions extension
    • StripMarkup extension
    • Subfader
    • Test linksfrom 2
    • TourBusStop
  • NavTree
    • Links 1
    • Manual - DPL parameters: Controlling output format
  • Old Homepage
    • Aa
    • Add "minimum-number-of-revisions" like Criteria for page selection
    • Links 1
    • Main Page
  • Schwallex
    • AiSee crash due to several near edges
    • Dirty edge option crashes program
    • Fisheye problem
    • Known Bugs
    • Line styles look different in png and svg
    • Links 1
    • Minor changes in border affect forcedir layout strongly
    • Question regarding fstraight phase
  • TourBusStop
    • Links 1
    • Old Homepage
    • Peu
    • Wikibus.png

}}

Note that Template:Links 2 uses a special notation to represent double curly braces and a special pipe symbol to separate template arguments:

²{subQuery¦parameter¦..}²

This is needed because we must defer the evaluation of subQuery to a moment in time where the DPL result of the first (outer) query has already been calculated. This is necessary because we want to use %PAGE% and %TITLE% as part of the argument list for subQuery.

DPL has a built-in replacement mechanism which will convert the special characters ²{,}² and ¦ to their normal counterpart at the appropriate moment. This is a very powerful feature as is allows recursive calls between DPL statements. See the DPL:Manual - General Usage and Invocation Syntax.