You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Stefan Simik <st...@gmail.com> on 2007/11/16 16:51:18 UTC
Border component - naming
Hello all,
I have one question about the right naming of the Border component.
I think, that "Border" is a little confusing name, in context of swing-like
border.
In my opinion, border should be used as a decorator, that is transparent for
component,
which has it added --->>> it's like the new IComponentBorder interface
(and MarkupComponentBorder) works.
But the old component - "Border" behaves quite different. It's not border in
swing-context,
but it's like Panel. It has childs, it has own hierarchy ..The only
difference I see, is that Border works with markup inheritance
(with wicket:body) and Panel cannot use it.
So it seems to me, that Border name is a little confusing. It's not "Border"
- it behaves quite
like normal CONTAINER, which has own childs, own hierarchy - quite like
Panel. The only
difference I see, is that Border uses markup inheritance through
<wicket:body>, but panel does not.
I don't know, if I understand this concept correctly... thanks in advance.
--
View this message in context: http://www.nabble.com/Border-component---naming-tf4822088.html#a13795650
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Border component - naming
Posted by Johan Compagner <jc...@gmail.com>.
Thats why we also have IcomponentBorder, because thats like a swing
border, you add that border to a component instead the other way
around
2007/11/16, Stefan Simik <st...@gmail.com>:
>
> thanks for your response igor,
> yes, you are right, i understand, that in the output html border wraps
> its content -> so it's looks like border for nested components.
>
> What we both mean, is the same, difference is only from point of view.
> My point of view is, that generally (in desktop GUI like Swing - that was my
> swing context)
> borders are used for decorating some component (that's the same for wicket)
> but hierarchy
> is reversed towards wicket - for example:
> component.add( new LineBorder() ); //like in
> desktop GUI
> Here: border knows nothing about component, that decorates
>
>
> In Wicket, it's reversed:
> border.add(component); //in
> Wicket
> So it's my point of view, that this border is container component, because
> other
> components are added to it. I know, that it results in decorating added
> component, but in the sense
> of hierarchy, other components are added to the border, so the border is
> container for added components.
>
> In this context I see Border quite like "Panel, that can use markup
> inheritance through <wicket:body/>"
>
> I hope, you understand what I mean..
> thx
>
>
> --
> View this message in context:
> http://www.nabble.com/Border-component---naming-tf4822088.html#a13802790
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Border component - naming
Posted by Stefan Simik <st...@gmail.com>.
thanks for your response igor,
yes, you are right, i understand, that in the output html border wraps
its content -> so it's looks like border for nested components.
What we both mean, is the same, difference is only from point of view.
My point of view is, that generally (in desktop GUI like Swing - that was my
swing context)
borders are used for decorating some component (that's the same for wicket)
but hierarchy
is reversed towards wicket - for example:
component.add( new LineBorder() ); //like in
desktop GUI
Here: border knows nothing about component, that decorates
In Wicket, it's reversed:
border.add(component); //in
Wicket
So it's my point of view, that this border is container component, because
other
components are added to it. I know, that it results in decorating added
component, but in the sense
of hierarchy, other components are added to the border, so the border is
container for added components.
In this context I see Border quite like "Panel, that can use markup
inheritance through <wicket:body/>"
I hope, you understand what I mean..
thx
--
View this message in context: http://www.nabble.com/Border-component---naming-tf4822088.html#a13802790
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Border component - naming
Posted by Igor Vaynberg <ig...@gmail.com>.
we are not working within the context of swing here are we? so to say
something doesnt make sense within the context doesnt make any sense.
anyways, the border is called border because it wraps other components.
eg:
class myborder extends border { myborder() { add(new label("a","a"));
add(new label("b","b")); }}
<wicket:border><div wicket:id="a"/><wicket:body/><div
wicket:id="b"/></wicket:border>
now somewhere else
myborder b=new myborder("mb");
b.add(new label("c","c"));
<div wicket:id="mb"><div wicket:id="c"/></div>
the output from this is:
<div><div>a</div><div>c</div><div>b</div></div>
notice that border is AROUND the component that is inside it, thats
why its called border
-igor
On Nov 16, 2007 7:51 AM, Stefan Simik <st...@gmail.com> wrote:
>
> Hello all,
>
> I have one question about the right naming of the Border component.
>
> I think, that "Border" is a little confusing name, in context of swing-like
> border.
> In my opinion, border should be used as a decorator, that is transparent for
> component,
> which has it added --->>> it's like the new IComponentBorder interface
> (and MarkupComponentBorder) works.
>
> But the old component - "Border" behaves quite different. It's not border in
> swing-context,
> but it's like Panel. It has childs, it has own hierarchy ..The only
> difference I see, is that Border works with markup inheritance
> (with wicket:body) and Panel cannot use it.
>
> So it seems to me, that Border name is a little confusing. It's not "Border"
> - it behaves quite
> like normal CONTAINER, which has own childs, own hierarchy - quite like
> Panel. The only
> difference I see, is that Border uses markup inheritance through
> <wicket:body>, but panel does not.
>
> I don't know, if I understand this concept correctly... thanks in advance.
> --
> View this message in context: http://www.nabble.com/Border-component---naming-tf4822088.html#a13795650
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org