On Dec 2, 2004, at 4:47 PM, Stefano Mazzocchi wrote:
Sure, that's a better syntax, but the fundamental problem remains: template designers don't know nothing about SQL, nor care, nor know anything about request parameters, not know anything about dynamic tags nor know how to debug something in case somebody screws up with the order of those tags!
taglibs are *very* useful for applications. a programmer (that may or may not have knowledge of how to use tags) can construct a form using a tag library.
the constructed document can then be rendered to multiple mediums.. rich browser UI, static PDF, tables to XLS, simple HTML for handhelds.
the "template designer" just creates one master template for each output medium. a programmer actually writes the implementation of that template.
With that said, a usable taglib-driven system already exists. Jelly. If you need taglibs, go with that. No need to re-invent something different in cocoon.
Both I and Carsten have tried to use Jelly in Cocoon but the fit isn't that good. See our posts in http://marc.theaimsgroup.com/?t=109932680200001&r=1&w=2.
/Daniel
