cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonio Gallardo" <>
Subject Re: Dynamic woody templates?
Date Sun, 02 Nov 2003 13:35:03 GMT
Sylvain Wallez dijo:
>>>But I'm also wondering, as woody usage increases, if we will not need
>>> to write form templates involving more and more conditional parts. And
>>> for this, JXTemplate shines. But mixing jx-like access to the form
>>> model with wt: templates elements is likely to quickly become
>>> unnatural. A solution could be to augment the JXTemplate syntax with
>>> new Woody-related instructions. Taglibs for JXTemplate?
>>>What do you think (again)?
>>Don't know I am not sure if is a good idea to mantain a copy of
>> JXTemplate lib just for woody in another namespace. It will cause
>> overhead.
> That's not what I meant: I was suggesting to turn JXTemplate to an
> expandable language to which tag libraries can be added. Just like XSP,
> JSP or... the taglib transformer. I have to look deeper at this last
> one, as it may be close to what I need (but I'd like to have a
> generator)

I don't think it is a good idea, but let time decides if this is OK.

>>I understand the idea of using just one taglib for "wt" namespace. But
>> I think not is a good choice for every case. I think the user that need
>> or want to use JXTemplate, let then use it by defining the namespace
>> and on the same time who does not want it, then don't add then
>> overprocessing by checking for non existent tags.
> Sorry, I don't understand clearly. Do you mean that using JXTemplate
> should not be mandatory to use Woody? I agree with this, and was more or
>  less thinking to having the woody taglib to define the exact same tags
> than the transformer does, _plus_ some additional tags.

Nope. I mean about the taglibs you suggested above.

Best Regards,

Antonio Gallardo

View raw message