28 Feb
2009
28 Feb
'09
8:14 p.m.
I agree that it would be helpful if pier css were more constrained.
For example, I wanted to apply my own css to a wiki-generated table.
But doing so messed with all the tables that pier uses (like for edit
forms). I went ahead with my css ('cause it was end-user facing) but
I'd rather that the css didn't clash.
David
----
1 Squeak/Seaside/Pier site deployed
On Feb 28, 2009, at 9:59 AM, Norbert Hartl wrote:
While testing how hard it will be to bring my site
into pier I discovered some css class clashes. For
people it is quite normal to assign classes like
header, footer and the like.
In my opinion a cms like pier should try to step
out of the way of any usage conflict. Therefor I
would propose to namespace the css classes. A
pr_header, pr_footer will do I think.
Or do I missunderstand something completely? For me
it was not possible to reconstruct our layout without
haveing to remove all librares for the application. But
then it is tedious to work with pier as the edit boxes
and stuff are too small.
What is the best approach to bring in the own developed
design and having pier still functioning?
thanks,
Norbert
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki