Some very annoing designers is messing things up :) 

Here's the thing. I'm designing the wicket pages and a  common thing is to
add a css attribute to a ListView.
Something like listItem.add( AttributeModifier( "myClass" , ...... to make a
row red, something bold etc.

My problem is that if there a several css  designers ( non java ), then
every now and then they deside to throw away the css class and are not aware
of that it's needed in wicket to markup the list.

They only see the html markup and the css in there and do a css clean not
realizing that the css class is needed.

Sometimes we're not in the same office so it's a little frustrating to
always tell them. What is the proper way of doing this? How can I get rid of
this gap between css designers and wicket designers?

Sometimes I try to add css as a header contribution in the wicket page but
then the designer wondering why their css don't work. 

Pointers?

-- 
View this message in context: 
http://www.nabble.com/Question-on-markup-and-wicket-page-tp19542131p19542131.html
Sent from the Wicket - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to