On 7/2/01 2:30 PM, "Berin Loritsch" <[EMAIL PROTECTED]> wrote:
> Jason van Zyl wrote:
>>
>> Some have told us that the Turbine documentation is a little on the slim
>> side too!
>
> There is a bit more than on Cocoon though.
>
>>> I am intimately familiar with
>>> the architecture of Cocoon and Avalon, so I would be able to offer
>>> suggestions
>>> that will provide a smooth migration path to something that is embeddable.
>>
>> You mean embedding Cocoon in Turbine?
>
> Or the other way around. In the beginning, I will persue the path of least
> resistance. If it is easier to embed Turbine, I will go that route. If it
> is easier to embed Cocoon, then you get the idea. I need to wrap my head
> around the way Turbine works, so that will take me a few days.
What aspect of Turbine did you want to use with cocoon? The view
portion? I assume cocoon already has it's own db connection code
that comes from avalon.
I would look at HEAD. It will be changing over the next few days,
but it's a glimpse of what's to come.
--
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]
