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.


Gili wrote:

        Correct me if I'm wrong: we really don't know anything about
the rendered state a a component until it is already rendered; the
current API does not make this explicit.

        So why don't we just tell users: if you want to get at
information that is only available post-rendering, you have to force
rendering and *then* do your query. So users can invoke doRender(),
query the resulting model and then when the real rendering occurs it
notices that the Component has already been rendered and it just uses
the cached value.

Gili

On Wed, 2 Feb 2005 19:35:19 +0100, Juergen Donnerstag wrote:



While playing a bit with this idea. A container's constructor does not
know the current locale (required to find the markup). Though you
might use getSession(), it is actually the wrong session/locale you
are using, as it is the session/locale of the current page which
requested to load the new one. At the time the new page gets rendered,
the locale might have been changed.

Juergen


------------------------------------------------------- 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







-------------------------------------------------------
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





-------------------------------------------------------
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

Reply via email to