1 Mar
2009
1 Mar
'09
6:31 p.m.
On Sun, 2009-03-01 at 16:37 +0100, Tudor Girba wrote:
Hi Norbert,
My answers are inlined below.
Hmm, then it seems I do not understand your situation. Let's try to
clarify it a bit.
When you say broken, what exactly do you mean? Of course that the
layout and colors are not going to be the same, but the forms will
still have proper dimensions, which is what seemed to have spawned the
first problem.
Hi Tudor,
I think I found the cause of the problem. It has to do with the
precedence of css selectors. We had some styles like
* {
margin: 0px;
}
which is really not a good idea. Any other that does the same a little
more precise will win out. So we are the root cause of the problem.
But then I also do not understand why blueprint is defining globals,
e.g.
body {
line-height: 1.5;
}
I find this too general.
But thanks for your help,
Norbert
The
default look and feel is based on the blueprint css framework.
This is provided via the PRBlueprintLibrary library. This framework
is
a generic one and it mostly provides css classes for laying out the
pages into columns. It also provides some default styles for basic
html tags like textarea or input which is what gets eventually used
for editing pier. See the project page for more details:
http://code.google.com/p/blueprintcss/
The CSS that is specific to the look and feel of the default webpage
is available to you via the Edit Design command. This is
where .footer
and .header is defined. So, you have complete control over the look
and feel without removing the libraries. The provided css features
some commented to point out where the large parts out. So, all you
have to replace the Pier css (or part of it) with your css in the
provided area and to modify the template accordingly.
Is this helpful?
Not really. I have to investigate this somewhat deeper. I understand
what you are trying to say. But in my case it is different. If I
have the libraries loaded and in "edit design" the css removed
completely the design of my page is broken. So there are things that
conflict. I'm not that good in css but I hope I'll be able to figure
it out. I even did a dummy component inside the page that does
updateRoot: to be sure mine is the last loaded.