May guess is, it is a lot of work. Currently it is one step: Get the markup for a Page, iterate over the markup elements, if component tag than assign the markup and render the tag. You request requires to separate it into two phase. That sounds like a lot of work for me, but I guess we have to do it, right?
Juergen On 8/27/05, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > Hi list, Juergen, > > I'm struggeling with getting DatePicker right. To solve things > properly, I really need to be able to get the basic (immutable) tag > information before rendering. In this case, I need to know what the > attributes of the associated tag are. But for other cases - mostly > ajax - information such as with which tag a component is associated, > and it's position in the markup (so that we can render a component on > it's own) would be very helpfull too. > > Is there any way we can efficiently 'pre-parse' this info (e.g. at > creation time?), and have it avaible for clients? > > Eelco > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Wicket-develop mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-develop > ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
