On Fri, Nov 5, 2010 at 10:31 AM, Martin Makundi <
martin.maku...@koodaripalvelut.com> wrote:

> To be more precise: namespace would always be per each markupcontainer
> which has its own markup.
>
So the "hell" is still here. It is just moved one level up.
It seems you didn't think of all cases.

>
> **
> Martin
>
> > Please give a concrete example of such situation. If names are panel
> > or page scope I cannot immagine many worthwile items that can be
> > imported onto panels and pages that cannot be refactored.
> >
> > **
> > Martin
> >
> >>
> >>>
> >>> **
> >>> Martin
> >>>
> >>> >
> >>> >>
> >>> >> **
> >>> >> Martin
> >>> >>
> >>> >> >
> >>> >> >> I think if you find component hierarchies to be "hell", you
> probably
> >>> >> >> aren't
> >>> >> >> using Wicket right. Break things down into small reusable chunks
> >>> using
> >>> >> >> Panels and you will find everything gets much, much easier.
> >>> >> >
> >>> >> >
> ---------------------------------------------------------------------
> >>> >> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> >>> >> > For additional commands, e-mail: users-h...@wicket.apache.org
> >>> >> >
> >>> >> >
> >>> >>
> >>> >>
> ---------------------------------------------------------------------
> >>> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> >>> >> For additional commands, e-mail: users-h...@wicket.apache.org
> >>> >>
> >>> >>
> >>> >
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> >>> For additional commands, e-mail: users-h...@wicket.apache.org
> >>>
> >>>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Reply via email to