Test

PmWiki

pmwiki.org

edit SideBar

PmWiki • WikiTrails

authors (basic) The WikiTrails feature allows wiki authors to create "trails" through sequences of pages in the wiki.

Creating a trail

To create a trail, an author creates a "trail index page" that gives the sequence of page names as either a bullet or numbered list. The page names must be the first item following each bullet.

An example trail index page: a list like

    
    * [[TrailPage1]]
    * Some text.
    * [[TrailPage2]]
    ** [[TrailPage3]]
    ** [[TrailPage4]] some other text [[IrrelevantWikiPage]]
    ** Yet some other text. [[AnotherIrrelevantWikiPage]] 
    ** %center%[[would-beTrailPage]]

creates the following "wikitrail":

TrailPage1 <-> TrailPage2 <-> TrailPage3 <-> TrailPage4

Observations:

  1. In general, indentation levels in the page list don't matter -- trails are a linear sequence of pages.
  2. A page is part of the trail only if the page link immediately follows the list markup.

Using the trail

Creating a trail doesn't do anything on its own -- any page with numbered or bulleted lists implicitly create a trail. What makes a trail "work" is adding trail markup on the pages in the trail (i.e. the pages that are listed in the bullet/numbered list).

To build a trail, add trail markup like <<|[[TrailIndexPage]]|>> to a page, where TrailIndexPage is the page containing the bullet list of pages in the trail. PmWiki will display the trail markup with links to any previous and next pages in the trail. The trail markup can be placed anywhere in a page, and a page can contain multiple trail markups.

PmWiki defines three trail markups:

  • <<|[[TrailIndexPage]]|>> displays as "<< PreviousPage | TrailIndexPage | NextPage >>".

  • <|[[TrailIndexPage]]|> displays as "< PreviousPage | TrailIndexPage | NextPage >", except the appropriate arrow is omitted at the beginning and end of the trail.

  • ^|[[TrailIndexPage]]|^ treats the list levels as a hierarchy and displays the "path" to reach the current page (i.e., a "breadcrumb" trail). In the example trail above, the markup ^|TrailIndexPage|^ on TrailPage4 would display as "TrailIndexPage | TrailPage2 | TrailPage4".

Circular trails

Typically, a trail is a linear list with a first and a last page. However, the trail can be made "circular" by repeating the first page as the last item in the trail index:

    
    * [[TrailPage1]]
    * [[TrailPage2]]
    ...
    * [[TrailPageN]]
    * [[TrailPage1]]

If the trail index page is intended to be read by others, the last item can be made invisible using %item comment%:

    
    * [[TrailPage1]]
    * [[TrailPage2]]
    ...
    * [[TrailPageN]]
    * [[TrailPage1]] %item comment%

Cross Group Trails

Trail pages on both sides of group boundaries must be fully qualified with group names.

Other notes

The %trail% markup used in many of PmWiki's documentation pages is just a WikiStyle that creates a grey background, and is not required for WikiTrails to work. It's defined in the PmWiki.GroupHeader page.

To get it to work, you must create the index page for the trail and the trail pages as stated above. Then you must define the wikistyle you want in the groupheader of the group you want it to appear in. Then you must refer or call to it with the %trail% markup from the trail pages.

Wiki administrators can change the trail separator of the "path" trail ( ^|[[TrailIndexPage]]|^ ) from the default | by setting the variable $TrailPathSep in the config.php file, for instance $TrailPathSep = ' > '; to achieve "TrailIndexPage > TrailPage2 > TrailPage4".

<< Group Headers | DocumentationIndex | Page history >>

July 2014:
Yate 5.4 and YateBTS 4 launched. Added JSON and DNS support in Javascript, Handover support in YateBTS.

March 2014:
YateBTS 2.0 launched. Added authentication and WebGUI. Added USSD support in commercial version.

March 2014:
Yate 5.2 launched. Better JavaScript support and a fixed memory leak.

Jan 2014:
YateBTS 1.0 launched. The first GSM Basestation which works with an IMS/VoLTE core network.

Jan 2014:
Yate 5.1 launched. Better JavaScript support and added libygsm. Elisa chatbot added in RManager

Oct 2013:
OpenHSS is the Yate based HLR/HSS solution for MVNO and LTE carriers.

Oct 2013:
Yate 5 released. Added IPv6 support in SIP for LTE. Improved JavaScript support. Download NOW

Jan 2013:
Yate 4.3 released: Added XML support in Javascript. SCCP - GTT routing between different networks. Stability improvements.
Download NOW

Aug 2012:
Yate 4.2 released: SIP flood protection. Better Jabber/Google Voice support. Usable Javascript. Fixed SIGTRAN links fluctuations.
Download NOW

Apr 2012:
YateClient was accepted in the Mac Store.

Yate 4.1 released: better Gvoice support, iSAC codec, support for new Wanpipe drivers. Fixes T.38 and Mac client issues.

Mar 2012:
SS7Cloud is launched today, 1st March, 2012, by NullTeam, Yate creators. Having all you need to be a US CLEC, it brings SS7 services in a cloud.

Feb 2012:
Yate 4.0 released.
SCCP, TCAP, MAP and CAMEL, TCP and TLS in SIP, Javascript fast prototyping of telephony applications and brand new face for YateClient.

Nov 2011:
Here is a video that, quote "demonstrates the truly awesome power of the YATE engine, as it easily handles 3 simultaneous calls to an audio player application including dtmf (button press) handling "(from PaintedRockComm).

Nov 2011:
Yate will attend ORR - OPENRHEINRUHR (November 12 - 13).

04 May 2011:
sipgate chooses open source project Yate for core infrastructure.

12 Apr 2011:
Yate 3.3.2 released.
Fix for Jingle calls to Google Voice dropping after 5 minutes.
4 Apr 2011:
Yate 3.3 released.
Support for GMail chat conference, fixes for internal microphone in MacOS. Minor fixes in SS7 M2PA and ANSI. Fixes in H.323, SIP and RTP.

9 Mar 2011:
Yate 3.2 released.
Bug fixes in SIGTRAN/MGCP/SS7 and added support for CNAM/LNP lookup by SIP INVITE/3xx.

Feb 2011:
Yate will attend FOSDEM and XMPP summit.

31 Jan 2011:
Yate 3.1 released.
Yate client support for Google Voice. Support for any country tones in tonegen.

20 Dec 2010:
Yate 3.0 released.
SS7 ITU certified. SS7 STP added. Client supports Jabber IM (Google Talk + Facebook).

3 May 2010:
Yate 3.0.0 alpha 3 released. Featuring the new Jabber server and wideband audio.

8 March 2010:
Yate 2.2 released. Mostly bug fixes. Dahdi compatible. Latest 2 release before 3.0.

6-7 February 2010:
Yate booth at FOSDEM 2010. Free CD with Freesentral available.

2 Nov 2009:
Yate 2.1 launched. Can replace a Cisco PGW2200 to control a Cisco AS54xx.

6 Aug 2008:
Yate and OpenSIPS (former OpenSER) join to build IP based clusters.

4 Aug 2008:
Yate 2 launched.


EditHistoryBacklinksRecent ChangesSearch