Point well taken.
So we're back to your idea of moving the logic into add(). Can
we do this?
Gili
On Wed, 02 Feb 2005 12:04:47 -0800, Jonathan Locke wrote:
>
>i may not understand the problem you are trying to solve, but i think
>this is a pretty horrible idea.
>users should not be involved in the rendering process at all. this is
>exactly the kind of "control"
>that makes tapestry so hard to use. we need straightforward components
>that you just place and
>which take care of themselves. component authors may have to be aware,
>but that's another matter.
>
>i think the problem with locales does not exist because components and
>pages have no notion
>of their locale. if the session switches locales, they will render
>differently because getAssociatedMarkup()
>will return different markup on rendering.
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
