found it. WICKET-2238
-igor On Wed, Jun 17, 2009 at 8:55 AM, Igor Vaynberg<[email protected]> wrote: > there was a jira issue, cant find it right now, where we talked about > having a callback that is basically > Component#onMarkupResolved(IMarkupFragment) that would be called as > soon as the markup is known and before render to allow component a > chance to perform markup-specific initialization. > > i think that combined with this would be a very powerful feature. > > -igor > > On Wed, Jun 17, 2009 at 1:33 AM, Juergen > Donnerstag<[email protected]> wrote: >> Just to let know. I have a working copy of IMarkupFragment on my >> computer. Except for IScopeComponent, all junit tests pass, some >> examples still fail. It is based on current 1.4 trunk and allows to >> get access to a components markup as soon as the parent container is >> known. That means it is not available in the Components constructor, >> but can be accessed via parent.getMarkup(child) before you do >> parent.add(child). >> >> Today, a components markup is usually only available during the render >> process. >> >> For Page, Panel etc. it obviously is available in the constructor. >> >> Besides that it allows access to the markup much earlier, it will >> allow us to change the render process from markup driven to component >> driven which in turn will ease ajax development. >> >> Juergen >> >
