E-Books for you

This is
then stored in the onAfterDisplayFoobar attribute of the $foobar object.
We normally do this type of thing in component view classes. A template would
then output the value of the onAfterDisplayFoobar parameter after the Foobar
was displayed.
It is important to understand that this event, although the name contains 'After', is
executed before the Foobar is actually outputted, what this is really identifying is that
the 'After' refers to where strings returned from the event handlers will be displayed.
Our event handlers have all been very simple; there are all sorts of other things
we can achieve using plugins. For example, we can modify referenced parameters,
return important data, alter the page title, send an email, or even make a log entry!
When we think of plugins we must think beyond content and think in terms of
events and listeners. The plugin groups, which we will discuss in a moment, will
demonstrate a number of different things we can achieve, which go far beyond
modifying content.


Pages:
178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202