1 Mar
2009
1 Mar
'09
2:23 p.m.
On Sat, 2009-02-28 at 20:25 +0100, Tudor Girba wrote:
Hi 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.
Btw. some trivial things to note:
If you try to remove the css in "edit design" completely you get an
MessageNotUnderstood: UndefinedObject>>asByteArray
And you have to make sure that SULibrary is added before
PRJavascriptSupport.
Norbert
On 28 Feb 2009, at 17:59, 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
--
www.tudorgirba.com
"Being happy is a matter of choice."
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki