1) Why do you use immediate-child selectors (involving > ) instead of just child selectors (without the >)? The selector ".custom-component-class header" will work. 2) wicket namespace tags are removed in deployment mode (or if you tell markup settings to strip them), so wicket:child will disappear the same way wicket:panel does. 3) Look into approaches that involve less subclassing, the real problem is that design-time you will not see the entire HTML template as long as fractions are spread around due to child class markup. Even using wicket:fragment elements within the replaced element will make it easier to see the design.
mvh - Tor Iver Wilhelmsen, Arrive AS -----Original Message----- From: kamiseq [mailto:kami...@gmail.com] Sent: 28. april 2011 11:14 To: users@wicket.apache.org Subject: wicket tags hi, this is more about how you guys working with wicket rather then a bug or something. and as Im relativelly new to wicket maybe you can help me out. I created panels that can be extended ie. <wicket:panel> <header>my header</header> <form> <wicket:child></wicket:child> <input type="text" /> </form> </wicket:panel> usually I style the component in "offline" mode (without running the server) so I need to add some additional markup to mock it, plus I set wicket to strip wicket tags and override onComponentTag to set name of the tag (let say section) so it look like. <section class="custom-component-class"> <wicket:panel><!-- this will go away --> <header>my header</header> <form> <wicket:child></wicket:child> <input type="text" /> </form> </wicket:panel> </section> so now the problem is that 1. I cannot use css selector like section.custom-component-class > header or I need to comment the wicket:panel tag on time I style component 2. wicket:child is not recognized as valid html tag so I cannot add style to it ie. display:none 3. surrounding wicket:child element with some html tag makes no sens why wicket tags couldnt be attributes so any valid html could have attribute like wicket:behavior="panel" or type="child" or something like that I know that this is not a big issue. probably designer should create html + css styles first and then developer turn it into the working code but with time things like that are annoying, so how do you work with such problems? pozdrawiam Paweł Kamiński kami...@gmail.com pkaminski....@gmail.com ______________________
