Jason van Zyl wrote:
> Hello,
>
> What are the plans regarding using templates as opposed to ECS?
>
As everybody already said, we have agreed to drop ECS integration in the
core layout engine.
If anybody depends heavily on ECS, they should develop a
ECSTemplatingService, that sets up the ECS object model in the layout,
passes it through using the context, etc., so that the existing objects
can be reused with minor changes.
> I would like to take a stab at setting up Jetspeed to use use
> templates if that is the plan.
>
> I am working with David to get Jetspeed working with the TDK
> and we are off to a good start.
>
> If no one else minds I can probably do the conversion in a couple
> days with David's help.
>
> Are you guys going to support ECS? Or are you planning on
> just using templates. If you are planning on just using templates
> than I think I could help get the Jetspeed code in line with
> Turbine, keep the same functionality and remove some duplicated
> code.
>
>
P.S.) I have been missing lately. A team of Soluziona, including Juan
Carlos and myself, went to the first spanish contest for J2ME MIDP
programming, and actually won it :)))) It was organised by Sun
Microsystems and Telefonica Moviles in Java Expo Spain.
We have delivered (in eight hours) a midlet that takes a XML description
of a user interface and builds it in the mobile phone. Does it sound
familiar to you?
BTW, during a presentation of the Internet Services architecture in Java
Expo Spain I noticed (first time out of here and maybe Cocoon lists) a
concept that we have been using here:
content --> styling --> device rendering
The step of "device rendering" (that we have been calling "rendering")
takes care of adaptation to different devices capabilities and
markup/presentation languages.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
