At 21:31 2000-12-03, Raphael Luta wrote:
Hello,
It's been about one month since we started clean-up the Jetspeed source
code and implement new features. In this one month, a lot of work has
been done and many new ideas were proposed and the project now counts
3 new committers.
I think this is a
Raphael, I somewhere read following statement about the jars
in turbine's
lib directory: "vleocity-0.4.jar: Atemplating engine that
will soon replace
Webmacro." This was a posting of Cristopher Elkins on 17th,
October - I'm
not sure if this is agreed upon by all turbine members, but
"Diethelm Guallar, Gonzalo" wrote:
Raphael, I somewhere read following statement about the jars
in turbine's
lib directory: "vleocity-0.4.jar: Atemplating engine that
will soon replace
Webmacro." This was a posting of Cristopher Elkins on 17th,
October - I'm
not sure if this is
on 12/6/2000 6:52 AM, "Raphael Luta" [EMAIL PROTECTED]
wrote:
Yes, but currently there's still some support classes missing for
Velocity and most important: the templates are the same so switching
for Webmacro to Velocity will just be an issue of changing the default
configuration in TR.p.
[EMAIL PROTECTED] wrote:
Raphael,
thanks for the info.
Would the template support in portlets/controls/controllers
use nested invocation of templates like in the example below
to avoid use of ECS for page generation ?
Yes
template1 (e.g. controller template)
calls template11
Something like that yes, although I was also playing with the
idea of changing the portal OM, the control would become the
display peer of a portlet thus completely hiding the portlet API
from the rendering engine. This will allos to evolve the
rendering/layout engine independently of
Raphael,
it may be that some of your work impacts our work in the areas
of WAP support and JSP template support. Can you provide a brief
overview on these items ?
- reworking the screens/layouts/navigations to use Webmacro
- implementation of template support in portlets/portletcontrols/
Im working on the profiler service. Starting today and for the remainder of
December, I hope to be a lot more active. I am looking at doing this in two
phases: first without Turbine security and then the second phase to add the
security. I hope to commit the first part of the work by the end of
Raphael,
thanks for the info.
Would the template support in portlets/controls/controllers
use nested invocation of templates like in the example below
to avoid use of ECS for page generation ?
template1 (e.g. controller template)
calls template11 (e.g. control template )
calls
