5 Answers, 1 is accepted
0
Hello Paul,
You are corrct, the Default2006 and Gray skins are no longer supported since the "Futures" release of RadControls as explained below:
http://www.telerik.com/community/forums/aspnet-ajax/general-discussions/q1-2009-beta.aspx
However, we recommend to use the new Default skin which is very similar to the obsolete Deafult2006 skin - you can see how it looks in the demo below:
http://demos.telerik.com/aspnet-ajax-beta/editor/examples/skinning/defaultcs.aspx
Greetings,
Svetlina
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
You are corrct, the Default2006 and Gray skins are no longer supported since the "Futures" release of RadControls as explained below:
http://www.telerik.com/community/forums/aspnet-ajax/general-discussions/q1-2009-beta.aspx
However, we recommend to use the new Default skin which is very similar to the obsolete Deafult2006 skin - you can see how it looks in the demo below:
http://demos.telerik.com/aspnet-ajax-beta/editor/examples/skinning/defaultcs.aspx
Greetings,
Svetlina
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0

Mark
Top achievements
Rank 1
answered on 29 Apr 2009, 04:41 PM
Hi Svetlina,
Could you please post some links that work?
This one doesn't work at all:
http://demos.telerik.com/aspnet-ajax-beta/editor/examples/skinning/defaultcs.aspx
This one has a link to Full Release Notes that also doesn't work
http://www.telerik.com/community/forums/aspnet-ajax/general-discussions/q1-2009-beta.aspx
Could you please post some links that work?
This one doesn't work at all:
http://demos.telerik.com/aspnet-ajax-beta/editor/examples/skinning/defaultcs.aspx
This one has a link to Full Release Notes that also doesn't work
http://www.telerik.com/community/forums/aspnet-ajax/general-discussions/q1-2009-beta.aspx
0
Hello Mark,
I just answered you in the other forum post on the same subject. For convenience I paste my reply below:
In our meetings and discussions about the Q1 release and the major skin-lift that we applied to all our web controls, we decided not to include the Default2006 skin but to leave it as an external one. We also modified the Default2006 skin to use the new CSS naming convention (that is now common for all RadControls for ASP.NET AJAX) and you can use it with Q1 2009 as well. More information on the subject and the skin download is available here:
http://www.telerik.com/community/forums/aspnet-ajax/editor/radeditor-q3-2008-skins-available-for-download.aspx
Greetings,
Georgi Tunev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
I just answered you in the other forum post on the same subject. For convenience I paste my reply below:
In our meetings and discussions about the Q1 release and the major skin-lift that we applied to all our web controls, we decided not to include the Default2006 skin but to leave it as an external one. We also modified the Default2006 skin to use the new CSS naming convention (that is now common for all RadControls for ASP.NET AJAX) and you can use it with Q1 2009 as well. More information on the subject and the skin download is available here:
http://www.telerik.com/community/forums/aspnet-ajax/editor/radeditor-q3-2008-skins-available-for-download.aspx
Greetings,
Georgi Tunev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0

Aaron
Top achievements
Rank 1
answered on 07 Mar 2011, 07:01 PM
I have a major problem with this practice of changing skins. Why on earth would you change existing skins instead of introducing new skins??? We have a solution with several websites and a LOT of telerik controls that use "Default" skins. We recently upgraded, and now, most of our skins are broken. We're now in the process of tracking down a fix for this via the support forum and other web resources -- and it looks like, regarldess of the solution, there's TON of work in it for us. That' irritating and expensive.
Here's an idea: INTRODUCE NEW SKINS, DON'T OBLITERATE EXISTING ONES.
Here's an idea: INTRODUCE NEW SKINS, DON'T OBLITERATE EXISTING ONES.
0
Hello Aaron,
I am sorry to hear about the problems that you experience and I assure you that we are ready to help if needed.
This change was made 2 years ago so I assume that you are upgrading from an earlier version of the controls. To help the customers, we converted all old (pre-q1 2009) skins for the controls, to work with the Q1 2009 release - there is a link to the editor's skins up in the thread and there are such topics in every control's forum.
Greetings,
Georgi Tunev
the Telerik team
I am sorry to hear about the problems that you experience and I assure you that we are ready to help if needed.
This change was made 2 years ago so I assume that you are upgrading from an earlier version of the controls. To help the customers, we converted all old (pre-q1 2009) skins for the controls, to work with the Q1 2009 release - there is a link to the editor's skins up in the thread and there are such topics in every control's forum.
Greetings,
Georgi Tunev
the Telerik team
Registration for Q1 2011 What’s New Webinar Week is now open. Mark your calendar for the week starting March 21st and book your seat for a walk through all the exciting stuff we ship with the new release!