mpfserver Manual
 
 
 Token structure | Learn how to use mpf:tokens
Basic token structure
{ mpf: token-name parameters }
there are some facts you must keep in mind:

token- and parameter-names are all case sensitive

whitespaces are not allowed, except if they are part of token- or parameter-values

curly brackets that are not part of a token definition must be escaped with underline: "_}"

parameters may be required (marked by *) or optional

some parameters must be defined at given position (marked by number)

each parameter can be defined once only (there are few exceptions)
Tokens with closing tag
most tokens may be used with closing tag
{ mpf: token-name parameters }
...
{ / mpf: token-name parameters }

closing tag must be equal to opening tag, except that mpf: must be prefixed with slash "/"

behaviour of tokens used with closing tag may vary from use as single tag
Embedded tokens
tokens may be embedded into other (embedded) tokens to assemble their values, parameters or even whole tokens
{ mpf: set = myVar2 || data = { mpf: myVar } }

embedded tokens will be resolved from inside to outside

embedded tokens must not be used with closing tag
Parameters
There a several global parameters you may use.
 
 
2004 by master-p-formance.All rights reserved.
 
This manual is generated on the fly using mpfserver and MPFT (mpf transformation).