8 Mar
2008
8 Mar
'08
10:29 a.m.
Hi,
I'm trying to customize a number of XWiki installations to be able to
show its potentialities minimizing the effort invested in modifying its
apparency. Using 1.3-SNAPSHOT.8231.
At the moment is out of my capacities to understand how Toucan has been
developed and is evolving, but I saw that copying a number of templates
and CSS files to the folder of a new skin helps a lot.
If I copy colorsblack.css to the new skin folder, it is quite easy to
modify margins, font sizes and other properties. But I would like to
understand how does the url in the background-image property work. For
instance here:
#globallinks {
background-image:url(headerperso-bg.jpg);
background-position:left bottom;
}
It seems that headerperso-bg.jpg is picked up from Albatross skin, the
base one, and not from the new skin folder where colorsblack.css is
stored. By using Firebug I can see that it is that new CSS the one the
site is using.
I can use any absolute URL there and it works fine.
Please, is this the expected behavior or must the browser pick up the
new background stored in the new skin folder? Am I missing or
misunderstanding anything? Thanks!
Cheers,
Ricardo
--
Ricardo Rodríguez
Your EPEC Network ICT Team
8 Mar
8 Mar
6:45 p.m.
I am not sure if the following suggestion will help but it helps me
solve a websphere portal related skin/theme problem recently.
If there is any background tag or background-image defined after the
background-image in your skin, the later background tag will overwrite
your background-image tag defined previously. So you can try to use
background instead of background-image to check or rearrange the
sequence of your css file so your skin's tag is the last to fire on.
-Chengmin
On 3/8/08, [Ricardo Rodriguez] Your EPEC Network ICT Team
<webmaster(a)environmentalchange.net> wrote:
Hi,
I'm trying to customize a number of XWiki installations to be able to
show its potentialities minimizing the effort invested in modifying its
apparency. Using 1.3-SNAPSHOT.8231.
At the moment is out of my capacities to understand how Toucan has been
developed and is evolving, but I saw that copying a number of templates
and CSS files to the folder of a new skin helps a lot.
If I copy colorsblack.css to the new skin folder, it is quite easy to
modify margins, font sizes and other properties. But I would like to
understand how does the url in the background-image property work. For
instance here:
#globallinks {
background-image:url(headerperso-bg.jpg);
background-position:left bottom;
}
It seems that headerperso-bg.jpg is picked up from Albatross skin, the
base one, and not from the new skin folder where colorsblack.css is
stored. By using Firebug I can see that it is that new CSS the one the
site is using.
I can use any absolute URL there and it works fine.
Please, is this the expected behavior or must the browser pick up the
new background stored in the new skin folder? Am I missing or
misunderstanding anything? Thanks!
Cheers,
Ricardo
--
Ricardo Rodríguez
Your EPEC Network ICT Team
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
9 Mar
9 Mar
11:33 a.m.
New subject: [xwiki-users] trying to understand colorsblack.css -> background-image
Chengmin Ding wrote:
I am not sure if the following suggestion will help
but it helps me
solve a websphere portal related skin/theme problem recently.
If there is any background tag or background-image defined after the
background-image in your skin, the later background tag will overwrite
your background-image tag defined previously. So you can try to use
background instead of background-image to check or rearrange the
sequence of your css file so your skin's tag is the last to fire on.
-Chengmin
Thanks for the tip.
I think this was not the case here. The point was that all background
tags worked fine, but images where loaded from the base skin instead of
from the folder where the CSS for the customized skin is stored.
I've just upgraded to 1.3 and it is working fine now. I don't know why,
but it seems that any of the changes done between 1.3RC1 and 1.3
affected this behavior. Great! Although I've learned nothing :-(
I know skins and in general interface issues are hot issue right now, so
I will try to stop finding fancy solutions and keep an eye on
http://dev.xwiki.org/xwiki/bin/view/Design/InterfaceExtensions :-)
Cheers,
Ricardo
--
Ricardo Rodríguez
Your EPEC Network ICT Team
6132
days inactive
6133
days old
2 comments
2 participants
participants (2)
-
[Ricardo Rodriguez] Your EPEC Network ICT Team -
Chengmin Ding