NEWS
28 Nov. 2011
LNCS proceedings is available online
25 August 2011
Pictures from the conference are now on the web.
15 August 2011
Online Registration is closed, but OnSite registration is possible.
26 July 2011
Updated info about venue, etc.
18 June 2011
Program published
13 June 2011
EXTENSION: Doctoral Symposium has the submission site open for 12 more hours (i.e., until midnight, Oslo time).
7 June 2011
Registration page for the main conference is open.
6 June 2011
Author notification: list of accepted papers available
03 June 2011
Submission site opened for the Doctoral Symposium.
04 Apr. 2011
Deadline Extension: submission deadline has been extended to 14 April (midnight Hawaii time)
29 Mar. 2011
Sponsorships are available for participants. See Registration page for details on eligibility criteria.
16 Feb. 2011
FCT 2011 is honored by the invited speakers:
11 Feb. 2011
One can use the FCT11 Posters for display with the purpose of advertising the FCT 2011 symposium.
31 Jan. 2011
A Doctoral Symposium event will be associated with the FCT 2011. See the specific CFP.
10 Jan. 2011
First call for workshops is out
15 Dec. 2010
First call for papers is out
14 Dec. 2010
Web Page is up
Page text variables are string variables created in the wiki text of a page, and can be automatically made available for inclusion in other pages.
Defining Page Text Variables
There are three ways to define automated Page Text Variables:
- use a definition list - the normal pmwiki markup for a definition list will create a page text variable
:Name: Crisses
"{$:Name}"
|
"Crisses" |
{$:Name} (becomes: "Crisses") in the page.
- use a simple colon delimiter in normal text
Address: 1313 Mockingbird Lane
"{$:Address}"
| Address: 1313 Mockingbird Lane "1313 Mockingbird Lane" |
{$:Address} variable (variable markup becomes: "1313 Mockingbird Lane") in the page.
- hidden directive form - PmWiki markup that doesn't render on the page, but defines the variable
(:Country: Transylvania :)
"{$:Country}"
| "Transylvania " |
{$:Country} variable (variable markup becomes: "Transylvania ") in the page.
Usage
Usage on the same page
On the same page you can resolve page text variables through the {$:Var} format (shown above).
Usage in headers and footers: special references
If you want a GroupHeader, GroupFooter, SideBar, etc to call on page text variable in the main page, you need to include special reference information.
To explicitly reference the page text variable from the page being displayed add an asterisk to the page text variable's markup: {*$:Address} on the GroupFooter or GroupHeader page.
{*$:City}
|
To include a page text variable from a header or footer see usage from other pages below.
Usage from other pages
If you want to pull the data from another page, use the {Group/PageName$:Var} format.
Suburb: Khandallah
(:Lake:Taupo:)
:Mountain:Mt Ruapehu
->"{PmWiki/PageTextVariables$:Suburb}"
->"{{$FullName}$:Lake}"
->"{PmWiki/PageTextVariables$:Mountain}"
| Suburb: Khandallah
"Khandallah"
"Taupo"
"Mt Ruapehu"
|
Usage from included pages
Page text variables are never included from their source page. See Usage from other pages above to refer to a page text variable on another page.
Usage with pagelists
Page lists can also access the page text variables:
(:pagelist group=PmWiki order=$:Summary count=6 fmt=#singleline:) |
And to create pagelist formats (such as those documented at Site.Page List Templates, Page Lists, Page List Templates, Page Variables. Store custom pagelists at Site.Local Templates?).
Page lists can also use page text variables to select pages :
(:pagelist group=PmWiki $:City=Paris count=8 fmt=#singleline order=-name:) |
(:pagelist group=PmWiki $:City="Addis Ababa,Paris" order=-$:Version count=8 fmt=#singleline:) |
- When using page text variables for selection or ordering, don't put the curly braces around the variable name. The curly forms do a replacement before the pagelist command is evaluated.
Testing if set or not set
| =- | PTV is set (is not empty), eg (:pagelist $:Var=- :) |
| =-?* | PTV is not set (is empty), ie not one character followed by 0 or more characters, eg. (:pagelist $:Var=-?* :) |
| =* | display all pages, regardless of the page text variable (slow) |
| =-* | display no pages, regardless of the page text variable (slow) |
Tip : (:if ! equal "{$:PTV}" "":) will test if PTV is empty/unset or not.
(:pagelist group=PmWiki $:Summary=-?* count=6 fmt=#singleline:) |
Use page text variable in a template
Display pages by Audience page text variable.
>>comment<<
[[#byaudience]]
(:if ! equal '{=$:Audience}'
'{<$:Audience}':)
-<'''{=$:Audience}''':
(:ifend:)
[[{=$Name}]]
[[#byaudienceend]]
>><<
(:pagelist group=PmWiki count=10
fmt=#byaudience order=-$:Audience:)
|
visitors (intermediate) :
authors, admins (intermediate) :
authors, admins (advanced) :
authors (intermediate) :
PageVariables IncludeOtherPages Categories TableDirectives GroupHeaders Uploads |
Use page text variables in conditional markup
Page text variables will be assigned/evaluated before any conditional markup is evaluated. This effectively means that you cannot declare a PTV within an if...else condition; and also that a PTV will have a value even if it is set within a (:if false:)....(:if:) condition.
Usage - from within code (developers only)
The standard PageVar($pagename,$varname) function can return page text variables, but remember to include the dollar and colon like this:
$var=PageVar($pagename,'$:City')
It works by caching all page (text) variables it finds in a page (in $PCache) and returns the one requested.
This page may have a more recent version on pmwiki.org: PmWiki:PageTextVariables, and a talk page: PmWiki:PageTextVariables-Talk.
