On Aug 12, 2005, at 12:55 PM, Robert Zeigler wrote:
A possible workaround for custom types would be something like:
<binding name="foo" custom="prefix:value"/>
But then, really, we're back where we started, right? :)
This what I had suggested with my type attribute. So generally,
you'd have:
<binding name="hey" type="literal" value="Some text"/>
for custom bindings, it would be something like:
<binding name="hey" type="custom" value="custom_prefix:value"/>
That would allow the DTD to work fine with the built-in types. As
for the custom ones, I'm not really sure the framework could offer
you much help anyway. I am with you though, I don't think there's a
terrible need to provide your own binding. I think Tapestry should
certainly support it, but not at the clear majority use case's expense.
--
Kevin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
