on 6/14/01 2:31 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> From my perspective as a very new Turbine experimenter, actions should
> probably only rarely add stuff to the context.
Correct.
> They should mostly modify
> attributes of components that are put in the context via the PullService or
> via the Screen.
Close, but Screen's should exist either. :-) If you have a Screen, then you
have a one-to-one mapping of Java code to a template. That is bad because it
breaks the concepts of the Pull Model.
> When actions add things to the context, your templates
> become dependent upon the actions, which is not a good thing IMHO.
In some cases, this happens anyway because there are few re-usable Actions,
but you are right, having the dependency there is bad.
In summary, the whole idea is to have no dependencies between a template
(Velocity, WM, JSP, etc) and a Turbine Module (Screen, Action, Navigation,
Page, Layout). That is a 100% clean Model 2+1/Pull Model application.
Thanks,
-jon
--
"Open source is not available to commercial companies."
-Steve Ballmer, CEO Microsoft
<http://www.suntimes.com/output/tech/cst-fin-micro01.html>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
