Hi,
I have just downloaded the latest release trial version to test, and I don't like the Segoe UI font used in some of the controls, specifically tooltips and radWindow title in the Web20 skin. I;d like to change this to something more suitable for our application. What's the best practice for this? Just add the relevant Css classes to our stylesheet or turn off embedded skins and copy the original stylesheet over and edit the appropriate bits (this seems like a lot of work for minor tweaks).
Cheers,
John
I have just downloaded the latest release trial version to test, and I don't like the Segoe UI font used in some of the controls, specifically tooltips and radWindow title in the Web20 skin. I;d like to change this to something more suitable for our application. What's the best practice for this? Just add the relevant Css classes to our stylesheet or turn off embedded skins and copy the original stylesheet over and edit the appropriate bits (this seems like a lot of work for minor tweaks).
Cheers,
John
1 Answer, 1 is accepted
0
ManniAT
Top achievements
Rank 2
Rank 2
answered on 06 May 2009, 08:04 PM
Hi,
I haven't analyzed the latest styles but from earlier versions I know that the styles are in generally good designed.
So most things can be found in the "base classes".
I would suggest to use fire bug or IE-toolbar (F12 with IE8) to see where the attributes (font's) come from.
If the font's are not "very distributed" it should be easy to add a css style overriding the "unwanted" attributes.
Let's say it is "Office2007" which brings the font-family all you have to do is to add a block like this to your CSS file:
.Office2007 {
font-family: Arial, Script !important;
}
I'm not sure if important is needed but in most cases it is since the telerik styles are emitted relatively late which results in a need for this attribute to override the "later coming" style. And of course I'm kidding with Script :)
Anyhow - if there are just a few attributes I would recommend to override the involved styles instead of using custom skins or any other "huge" thing.
Regards
Manfred
I haven't analyzed the latest styles but from earlier versions I know that the styles are in generally good designed.
So most things can be found in the "base classes".
I would suggest to use fire bug or IE-toolbar (F12 with IE8) to see where the attributes (font's) come from.
If the font's are not "very distributed" it should be easy to add a css style overriding the "unwanted" attributes.
Let's say it is "Office2007" which brings the font-family all you have to do is to add a block like this to your CSS file:
.Office2007 {
font-family: Arial, Script !important;
}
I'm not sure if important is needed but in most cases it is since the telerik styles are emitted relatively late which results in a need for this attribute to override the "later coming" style. And of course I'm kidding with Script :)
Anyhow - if there are just a few attributes I would recommend to override the involved styles instead of using custom skins or any other "huge" thing.
Regards
Manfred