On 9/10/01 2:18 PM, "Jon Stevens" <[EMAIL PROTECTED]> wrote:
> on 9/10/01 8:00 AM, "Jason van Zyl" <[EMAIL PROTECTED]> wrote:
>
>> The template interfaces and classes are particularly confusing because they
>> are adaptered in two places. In Fulcrum itself the TemplateService uses a
>> TemplateContext and each of the Template engines supported has an adapter to
>> make its particular context class appear as a TemplateContext that the
>> TemplateService understands and in Turbine we have our own TemplateContext
>> and it is adapted so that the Fulcrum template service can deal with it.
>>
>> This appears redundant because the projects have just been severed so things
>> definitely appear to be identical in places and they are. But this will not
>> always be the case. I expect Fulcrum, Turbine and Torque to diverge and I
>> hope to protect Turbine from this by defining an independent set of
>> interfaces that Turbine application programmers can use.
>
> I just hope the added confusion and seemingly duplication is worth it to the
> people who have to use this stuff.
>From the perspective of a turbine application developer there will only be a
TemplateContext and that's it. I believe it will be far simpler for turbine
application programmers. I hope the emphasis will shift away from having to
dig into turbine at a low level in order to achieve an end goal and move
toward the use of a clean API that inherently allows easy extension. And I
hope the TemplateContext is a part of that.
> -jon
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
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]
