Brian Mains
Top achievements
Rank 1
Rank 1
Brian Mains
asked on 05 Nov 2009, 02:12 PM
Hello,
We recently upgraded from 2008.2.1125.35 to the latest release (well at that time, Q2, but will go to Q3). My co-worker created a custom skin, and it didn't properly work for our controls. Is that correct? When upgrading major versions, do you have to upgrade your style sheets?
Also, it seems the visual style builder doesn't cover every single style option that is in the Telerik framework? For instance, my co-worker mentioned to me it didn't include grouping styles for the rad grid? Is there a solution to this? Or at least, upgrading the control toolsuite, what would you recommend? Would you use the visual style builder to create the styles, or an alternative approach?
Thanks.
We recently upgraded from 2008.2.1125.35 to the latest release (well at that time, Q2, but will go to Q3). My co-worker created a custom skin, and it didn't properly work for our controls. Is that correct? When upgrading major versions, do you have to upgrade your style sheets?
Also, it seems the visual style builder doesn't cover every single style option that is in the Telerik framework? For instance, my co-worker mentioned to me it didn't include grouping styles for the rad grid? Is there a solution to this? Or at least, upgrading the control toolsuite, what would you recommend? Would you use the visual style builder to create the styles, or an alternative approach?
Thanks.
1 Answer, 1 is accepted
0
Hello Brian,
I did not quite understand from which to which RadControls version you have upgraded, but generally, in Q1 2009 we introduced new skin appearance for all controls and new CSS class names for some controls. If you have some custom skins, you can migrate them with this tool:
http://blogs.telerik.com/tervelpeykov/posts/09-03-20/using_pre-q1_2009_skins_with_q1_2009.aspx
Depending on the CSS code in your custom skin, you may need to make additional tweaks after migrating. In some cases it will be even easier to recreate your custom skin, using some of our new embedded skins as a base. Generally, I would recommend you to create custom skins with our Visual Style Builder's "colorize" and "shift colors" options, which is fastest and easiest.
Speaking of the style builder, yes, it does not cover every single CSS rule in our embedded skins in the WYSIWYG interface, because some elements are styled with several CSS rules, which are inter-related. You can modify these styles manually in the CSS code.
Regards,
Dimo
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
I did not quite understand from which to which RadControls version you have upgraded, but generally, in Q1 2009 we introduced new skin appearance for all controls and new CSS class names for some controls. If you have some custom skins, you can migrate them with this tool:
http://blogs.telerik.com/tervelpeykov/posts/09-03-20/using_pre-q1_2009_skins_with_q1_2009.aspx
Depending on the CSS code in your custom skin, you may need to make additional tweaks after migrating. In some cases it will be even easier to recreate your custom skin, using some of our new embedded skins as a base. Generally, I would recommend you to create custom skins with our Visual Style Builder's "colorize" and "shift colors" options, which is fastest and easiest.
Speaking of the style builder, yes, it does not cover every single CSS rule in our embedded skins in the WYSIWYG interface, because some elements are styled with several CSS rules, which are inter-related. You can modify these styles manually in the CSS code.
Regards,
Dimo
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.