Howard M. Lewis Ship wrote:

>I'm warming to the concept of "anonymous components" that are specified
>entirely in the HTML template.  This is much more viable now (with the  new
>approach to localization) than before (where localization was always
>multiple HTML templates).  It's a kludge in the way that <span key="..."/>
>is a kludge ... useful enough to outweigh its limitations.
 
If Tapestry (or a user extension there of) were to support another markup besides html, would you not want to keep the component specification separate from the markup.  For example, a application that can render both html and xml would have one .jwc component definition and both a .html and .xml file describing the markup.  The idea being the the component represent the same pull from the MVC, and the markup files represent how to render that information. (Right ?)
 
Craig J. Gregory
Dir. of Information Srevices
Blue Mountain Community College
PO Box 100
2411 NW Carden Av.
Pendleton, OR 97801
(541) 278-5825

Reply via email to