or you can just use a factory that lets you create transparent borders :) -igor
On Nov 7, 2007 12:05 PM, Chris Colman <[EMAIL PROTECTED]> wrote: > Presumably the coded work arounds that don't rely on child/extends mean > that the structural markup of each page is used instead of just that of > the base page - and that would spell maintenance issues. Without using > child/extend then ALL the structural markup in each page is used for > each render - NOTHING is pulled from the base page markup (kind of makes > me wonder why we need base page markup if not using child/extend - but > that's another topic!). > > A change of layout structure would mean changing all page markups - yuck > - or do you guys not care about your graphics designers - "arh, that's > their problem if they want to do a site wide change!" > > I think the fundamental thing that most people are missing is that each > component must be well formed XHTML, complete and self contained. If it > starts a <div> (or <table>) then it must also end it. Divs (and tables) > are the basic structural elements of markup. > > One component can't be the start of a structural span of markup, the > next few components content sections for that span and then the last > component ends the structural span - that is not possible because each > component must be well formed and complete. > > So this infers that structural markup typically is stored in page markup > and "wraps" markup that inserts various self contained components. > > Now here's the thing: without using child/extends then that structural > markup must be carefully defined in EVERY page markup because wicket > does not do the funky inheritance merging when you don't use the > child/extends tag. > > So if you want to change a border in between two components you must > change it in EVERY page markup. That would suck. > > Alternatively, if you do use the current child/extend you end up having > to bang multiple components into the overridden section which means that > you also bang in the border that exists between them - so now the border > markup is duplicated many times. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
