Wicket Panel tag

2010-05-21 Thread Brian Mulholland
Our app will be using ExtJS tab controls. So to make that easier I wrapped the ExtJS code up into a Wicket Panel to hide the complexity of working with ExtJS. The idea is that I would tell my class what the wicket:id of the span/div was to draw the thing to, as well as naming the N subtab id's

Re: Wicket Panel tag

2010-05-21 Thread Richard Wilkinson
Hi, 1) To get wicket to output a dom id you must call mycomponent.setOutputMarkupId(true). This will output a generated dom id, which you can access in your java code by calling mycomponent.getMarkupId(). Wicket will overrwrite any dom id in your code, if that element is used for a wicket

Re: Wicket Panel tag

2010-05-21 Thread Brian Mulholland
Cool, those both helped alot. Unfortunately, they have lead me to realize another major flaw in my plan. Of course the wicket panel is destroying the content in the template. In most cases that is a feature, but in this case the point is for the control to act as a wrapper around other content

AW: Wicket Panel tag

2010-05-21 Thread Stefan Lindner
Yes, ist is! Use a WebMarkupcontainer. It will leave your content untouches (except the ID) Stefan Von: Brian Mulholland [mailto:blmulholl...@gmail.com] Gesendet: Fr 21.05.2010 20:10 An: users@wicket.apache.org Betreff: Re: Wicket Panel tag Cool, those both

Re: Wicket Panel tag

2010-05-21 Thread Igor Vaynberg
use a border instead of a panel, thats what borders are for... -igor On Fri, May 21, 2010 at 11:10 AM, Brian Mulholland blmulholl...@gmail.com wrote: Cool, those both helped alot.  Unfortunately, they have lead me to realize another major flaw in my plan.  Of course the wicket panel is