1 Mar
2009
1 Mar
'09
8:24 p.m.
Hi,
Changing the default blueprint library is not the best way. It's
better to create your own library and load this after the blueprint,
or directly add your definitions to the css in Pier. Like this, you
can update to the latest Pier code without needing to change anything.
Cheers,
Doru
On 1 Mar 2009, at 18:57, John M wrote:
You can always edit blueprint.css in the image. I
changed mine to
1.25em
On Sun, Mar 1, 2009 at 12:39 PM, Keith Hodges <keith_hodges(a)yahoo.co.uk
--
www.tudorgirba.com
"Sometimes the best solution is not the best solution."
wrote:
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;
}
Blueprint is simply trying to set a common baselie between browsers
Keith
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki