Furnace page actions
Furnace framework ยป Furnace actions
Furnace framework ยป Furnace actions
| Prev: | Furnace action lifecycle |
| Next: | Furnace actions implementation |
Page actions implement the common case of an action that simply serves a Chloe template in response to a GET request.
When using a page action, instead of setting the display slot, the template slot is set instead. The init, authorize, validate and submit slots can still be set as usual.
The template slot of a page-action contains a pair with shape { responder name }, where responder is a responder class, usually a subclass of dispatcher, and name is the name of a template file, without the .xml extension, relative to the directory containing the responder's vocabulary source file.
Furnace page action example
page-action
<page-action> ( -- page )
When using a page action, instead of setting the display slot, the template slot is set instead. The init, authorize, validate and submit slots can still be set as usual.
The template slot of a page-action contains a pair with shape { responder name }, where responder is a responder class, usually a subclass of dispatcher, and name is the name of a template file, without the .xml extension, relative to the directory containing the responder's vocabulary source file.
Furnace page action example