Re: Border-Component Problem in Migration to 1.5

2012-02-24 Thread Jürgen Lind
begun to move my application up to 1.5. and I now getting an error in a place that worked just fine in 1.4. The problem seems to lie within creating a border component as it gives me the following error message: org.apache.wicket.WicketRuntimeException: You can not add a component's parent

Border-Component Problem in Migration to 1.5

2012-02-24 Thread Jürgen Lind
Hi, I've just begun to move my application up to 1.5. and I now getting an error in a place that worked just fine in 1.4. The problem seems to lie within creating a border component as it gives me the following error message: org.apache.wicket.WicketRuntimeException: You can not

Re: Border component - naming

2007-11-18 Thread Johan Compagner
> 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 " > > I hope, you understand what I

Re: Border component - naming

2007-11-16 Thread Stefan Simik
n 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Border component - naming

2007-11-16 Thread Igor Vaynberg
igor On Nov 16, 2007 7:51 AM, Stefan Simik <[EMAIL PROTECTED]> 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 component - naming

2007-11-16 Thread Stefan Simik
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 --->>

Re: Border component

2007-11-11 Thread Joshua Jackson
Thanks Martijn I guess I have to get used to this inheritance markup for page composition. The doc is very useful. Thank you so much :) On 11/9/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > For page composition I would suggest using markup inheritance. Borders > are not deprecated, but not re

Re: Border component

2007-11-09 Thread Johan Compagner
really? i always find the border component counter intuitive. Thats why i though of something simpler IComponentBorder That can be used as you would also do it in a swing app (a component has a border instead of a border has components) johan On Nov 9, 2007 2:05 PM, Joshua Jackson <[EM

Re: Border component

2007-11-09 Thread Martijn Dashorst
]> wrote: > Would you recommend using the border component or the markup > inheritance? By nature I like the border component as it as more > natural for templating. Is it deprecated? > > Thanks > > On 11/9/07, Martijn Dashorst <[EMAIL PROTECTED]&g

Re: Border component

2007-11-09 Thread Joshua Jackson
Would you recommend using the border component or the markup inheritance? By nature I like the border component as it as more natural for templating. Is it deprecated? Thanks On 11/9/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > http://wicket.apache.org/examplemarkupinheritance.ht

Re: Border component

2007-11-09 Thread Martijn Dashorst
http://wicket.apache.org/examplemarkupinheritance.html On 11/9/07, Joshua Jackson <[EMAIL PROTECTED]> wrote: > Dear all, > > When I read this document: > > http://cwiki.apache.org/WICKET/consistent-page-layout-using-borders.html > > It is written that the border compo

Border component

2007-11-09 Thread Joshua Jackson
Dear all, When I read this document: http://cwiki.apache.org/WICKET/consistent-page-layout-using-borders.html It is written that the border component is now updated and the document is not valid against the latest wicket distribution. Could anyone please give me a hint on what have changed