Personally, I hardly ever use the @Component annotation cause it makes the
source file so messy. And I try to include as little logic as possible in
the .html template. After all, the html vs logic separation is one of
Tapestry's greatest benefits IMO.
If the annotations would be simplified further, perhaps I would start
using @Component. I just can't think of any particular simplification,
what did you have in mind?
On Sun, 15 Jan 2006 18:33:53 +0100, Paul Cantrell <[EMAIL PROTECTED]>
wrote:
The reason you can't do this in the page file is that it would make it
impossible to have a meaningful DTD. Of course, you can do essentially
the same thing in your HTML:
<span jwcid="loop" source="ognl:someCollection>
Ultimately, Gregg is right: annotations are the wave of the future.
(Personally, I view .page and .jwc files as heading for deprecation,
though the Tapestry team might not agree.) And I do think there are many
things about Tapestry's annotation structure that could be simplified --
so that's where simplification efforts should be directed, IMO.
Cheers,
Paul
On Jan 15, 2006, at 8:15 AM, Martin Strand wrote:
How about using <component> attributes instead of the <binding> element?
i.e. we would have
<component id="loop" type="For" source="ognl:someCollection"/>
instead of
<component id="loop" type="For">
<binding name="source" value="ognl:someCollection"/>
</component>
The old way would still work, but there would be a simplified
alternative. What do you think?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_________________________________________________________________
Piano music podcast: http://inthehands.com
Other interesting stuff: http://innig.net
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
