Jamie Orchard-Hays <[EMAIL PROTECTED]> wrote... > It's not actually the pure html that bugs me the most. Where I work, > this isn't a limitation either. I've posted my real problems with this > additional syntax in another post, but I'll add here that short-cuts > aren't necessarily a good thing. Not when they make inconsistent, ugly, > messed-up looking code. Having too many ways to do things is as > undesirable as not having a good way to do things.
True. The "there's more than one way to do it" principal has made Perl, for example, rather complex and confusing. We certainly don't want to do that to Tapestry. However, some (including myself) would argue that the "Insert" component is not an ideal way to to display text in a template. It is cumbersome to work with, unless you have a great component-aware GUI development environment. Last I checked, we don't have one of those (and one of the principals of Tapestry is that we shouldn't need one). Plus, the current approach to displaying text relies on extra "dummy" tags (usually <span> tags) that could easily be accidentally removed by an HTML developer or missed while the developer does a cut-and-paste action in a tool like Dreamweaver. Personally, I don't see a great value for using this syntax to automatically replace the "Any" component. However, I do think it has much value for replacing the "Insert" component. -Nathan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
