ts, such as
>> >> > WebMarkupContainer which
>> >> > > can be used to group components, the use of any component which
>> is
>> >> > not
>> >> > > 'transparent' must have the related wicket:id in some markup
>>
ot
> >> > > 'transparent' must have the related wicket:id in some markup
> >> > somewhere.
> >> > >
> >> > > So, lets take an example where we have a list of item
items which can be
>> > just
>> > > text or a link which has an optional image. It seems that I have to
>> > define
>> > > panels for :-
>> > >
>> > >- wrapper
yes, its not the cleanest way though. cleaner to have a panel that
inside of it has all the variable fragments, and then just adds the
right one
-igor
On Tue, Apr 8, 2008 at 11:09 AM, Eric Rotick <[EMAIL PROTECTED]> wrote:
> One more thing that was suggested in class.
>
> Is it possible to defi
One more thing that was suggested in class.
Is it possible to define a Panel which had all suitable and appropriate sub
components and then to no-op the ones that were not needed?
So in the earlier example there could be a panel
and if the image was not needed it could be no-op'ed out by
Many thanks for the clarification.
As I am about to start teaching the rudiments of Wicket to a project team I
guess the teacher should know what they are talking about.
On Tue, Apr 8, 2008 at 6:50 PM, Igor Vaynberg <[EMAIL PROTECTED]>
wrote:
> you dont need a panel for the repeater itself. as f
you dont need a panel for the repeater itself. as for variable
component hierarchy inside the repeater itself, you are correct: you
have to either use a panel or a fragment.
-igor
On Tue, Apr 8, 2008 at 9:37 AM, Eric Rotick <[EMAIL PROTECTED]> wrote:
> I thought I understood the component hierar
I thought I understood the component hierarchy but then I started to tell
the guys about it and now I'm not so sure.
If the markup defines a hierarchy as A contains B contains C, in effect,
this means that C is added to B which is added to A. If we expand B to be
more complex we can use maybe a Pa
