https://github.com/jdonnerstag/wicket/commit/e5150ecb58fb9617120911b3b984767009f9f9d6
-Juergen
On Fri, Jul 22, 2011 at 9:09 AM, Martin Grigorov mgrigo...@apache.org wrote:
I don't see any commit message related to autoadd at
https://github.com/jdonnerstag/wicket/commits/autoadd
Can you give
I gave the idea to resolve components after onInitalize() a try by
re-using ComponentResolvers to resolve the auto-components. They are
added (not queued) at the right place in the hierarchy. Component's
queued will be added to the auto-components as well, so that the
hierarchies (markup and
Hi,
I don't have much experience with component/transparent resolvers but
here is how I see it.
On Fri, Jul 15, 2011 at 7:03 AM, Igor Vaynberg igor.vaynb...@gmail.com wrote:
working with this wicket:for stuff makes me really hate all the
autoresolver and autocomponent stuff. if only add() did
working with this wicket:for stuff makes me really hate all the
autoresolver and autocomponent stuff. if only add() did what queue()
from the component queueing discussions does we would be able to get
rid of auto components and make them full fledged components instead.
look at this:
div
