like i said in the previous thread, your idea looks good on paper.
lets suppose the interface i specified is real, could you show us an
example implementation?
-igor
On Fri, Mar 7, 2008 at 3:26 AM, JP Saraceno
<[EMAIL PROTECTED]> wrote:
>
> What I was proposing was pretty much in the line of this interface you
> described. For a valid use case, this is triggered by the issue on the
> thread I referenced above.
>
> So I would be able to develop different implementations of
> IMarkupIdGenerator (for different kinds of Components) to do stuff that can
> be more meaningful to my application than just a generic counter all across
> the page. E.g.
> * For simple stuff than can't be repeated, maybe just copy over the
> wicket-id without any counter
> * For panels, add a counter on the number of instances of that specific
> panel on the page
> * For repeaters, use a the iteration index + the container Id.
> * etc, etc.
>
>
>
>
> igor.vaynberg wrote:
> >
> > something simple like automatic markupid generation can be moved out
> > of component into some factory interface, but then you would have to
> > provide a valid usecase for us to add that additional complexity. eg
> > suppose we have
> >
> > IMarkupIdGenerator { String getMarkupForComponent(Component c); }
> >
>
> --
> View this message in context:
> http://www.nabble.com/Start-delegating-stuff-out-of-Component--tp15884385p15891161.html
>
>
> Sent from the Wicket - Dev mailing list archive at Nabble.com.
>
>
