On 9/14/01 12:13 AM, "Jeff Zhu" <[EMAIL PROTECTED]> wrote:
> Would you please explain the difference between "getScreen" and
> "getScreenTemplate", "setScreen" and "setScreenTemplate" in the RunData?
In almost all cases you should not need to reference the getScreen/setScreen
methods. Screens are modules in Turbine and modules, in the current Turbine
jargon, are responsible for populating contexts. I call them context
builders and generally there is a context builder that corresponds to the
template currently being rendered.
In most cases the context builder, or module, is found for you by the logic
internal to Turbine. Though there is a trend I see where a set of users gets
mapped to use a particular layout, or more generally an arbitrary parmeter
alters the rendering. In Turbine 3.0 this question will be more aptly stated
as "how do I invoke the use of sibling module with a general parameter that
will ultimately affect the rendering?". In Turbine 3.0 there are no such
things as screens, navigations and layouts. There are just modules and they
can be aggregated in an arbitrary fashion to render content.
> Thanks,
>
> Jeff
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
