GreenPepper Filter - GreenPepper Seeds

	GreenPepper Seeds	Log In
	GreenPepper Filter

Browse Space

View
Info

Added by Christian Lapointe, last edited by Christian Lapointe on Jun 21, 2007

GreenPepperAnonymous access is denied. You must log in to use GreenPepper.

Note for developpers
This filter is not available on Confluence

The greenpepper filter is used to specify that one or a group of tables have to be interpreted by GreenPepper.
The filter works with the execution mode : "Lazy" or "Eager".
-In Eager mode this filter does not change the behaviour : all table are interpreted.
-In Lazy mode the document tables are never interpreted until you specify a greenpepper filter.

In Lazy mode, only tables between tags [begin example] and [end example] are interpreted

rule for	greenpepper filter
Document content	execution mode	interpreted elements?
[a first table] ** [begin example] [a second table] [begin example] [a third table] [end example] [end example] [a fourth table] [begin example] [begin example] [end example] [a fifth table] [a sixth table] [end example] ** [a seventh table]	lazy	[a second table][a third table][a fifth table][a sixth table]
[a first table] **** [a second table]	lazy	none

In Eager mode, only tables between tags [begin example] and [end example] are interpreted

rule for	greenpepper filter
Document content	execution mode	interpreted elements?
[a first table] ** [begin example] [a second table] [begin example] [a third table] [end example] [end example] ** [a fourth table]	eager	[a first table][a second table][a third table][a fourth table]
[a first table] **** [a second table]	eager	[a first table][a second table]

The greenpepper filter does not override other filters behaviour like Section

rule for	greenpepper filter
Document content	section	execution mode	interpreted elements?
[section] [unix] ** [a first table] ** [a second table]	unix	lazy	none
[begin example] ** [a first table] [section] [unix] [a second table] ** [end example]	mac	lazy	[a first table]

The greenpepper filter does not override other filters behaviour like Begin Info

rule for	greenpepper filter
Document content	execution mode	interpreted elements?
[begin info] ** [a first table] [a second table] ** [end info]	lazy	none
[begin example] ** [a first table] [begin info] [a second table] [end info] ** [end example]	lazy	[a first table]

The scope of greenpepper filter is all the tables after [begin example] tag to the first next [end example] tag :
-if the [begin example] tag is not found but there is a [end example] tag then the filter will working from the top of the document to the [end example] tag.
-if the [end example] tag is not found then the filter will not working.

rule for	greenpepper filter
Document content	execution mode	interpreted elements?
[a first table] ** [begin example] [a second table] [a third table] [end example] ** [a fourth table]	lazy	[a second table][a third table]
[a first table] ** [begin example] [a second table] [a third table] ** [a fourth table]	lazy	none
[a first table] ** [a second table] [a third table] [end example] [a fourth table] [end example] ** [a fifth table]	lazy	[a first table][a second table][a third table][a fourth table]