I have an application that allows the user to choose which skin they want to use. I currently have it working with Telerik.EnableEmbeddedSkins = true. So, all the built-in skins are working fine. I'm using RadSkinManager to set the skins globally for the pages. However, I have some custom skins too that I would like to support. So far, as far as I can tell, RadSkinManager only works for built-in embedded skins? Also, I'm wondering is it possible to use embedded skins, and then only have the custom skins as separate files in the file system? Or, do I have to extract all the standard skins out to the files system and then turn off embedded skins? And if I do that, does that mean that RadSkinManager will no longer work?
8 Answers, 1 is accepted
0
Hi Jon,
RadSkinManager currently supports only embedded skins. We will probably research and enhance its functionality to support custom skins as well in the future.
In order to switch between embedded and non-embedded skins, you should use a custom control similar to the one shown below:
http://blogs.telerik.com/vladimirenchev/posts/08-07-11/change_skins_dynamically_for_all_telerik_radcontrols.aspx
The above control is actually similar to RadSkinManager in its "early days". You will have to detect whether the chosen skin is an embedded one or not and if it isn't, then set EnableEmbeddedSkins to "false" for all RadControls and also take care of the custom CSS files' registration.
Greetings,
Dimo
the Telerik team
RadSkinManager currently supports only embedded skins. We will probably research and enhance its functionality to support custom skins as well in the future.
In order to switch between embedded and non-embedded skins, you should use a custom control similar to the one shown below:
http://blogs.telerik.com/vladimirenchev/posts/08-07-11/change_skins_dynamically_for_all_telerik_radcontrols.aspx
The above control is actually similar to RadSkinManager in its "early days". You will have to detect whether the chosen skin is an embedded one or not and if it isn't, then set EnableEmbeddedSkins to "false" for all RadControls and also take care of the custom CSS files' registration.
Greetings,
Dimo
the Telerik team
Browse the vast support resources we have to jumpstart your development with RadControls for ASP.NET AJAX. See how to integrate our AJAX controls seamlessly in SharePoint 2007/2010 visiting our common SharePoint portal.
0
Johan
Top achievements
Rank 1
Rank 1
answered on 25 Jan 2011, 09:52 AM
Another workaround for a simple task that you know in advance that everybody will encounter.
In short this says: it is broken. Adding a custom skin renders the RadSkinManager useless.
This is such a pity since for the rest it works like a charm. Please fix this soon.
In short this says: it is broken. Adding a custom skin renders the RadSkinManager useless.
This is such a pity since for the rest it works like a charm. Please fix this soon.
0
Hi Johan,
Indeed, we are working on this issue and I hope in some of the next version of the controls you will be able to use RadSkinManager with custom skins.
Kind regards,
Iana
the Telerik team
Indeed, we are working on this issue and I hope in some of the next version of the controls you will be able to use RadSkinManager with custom skins.
Kind regards,
Iana
the Telerik team
Browse the vast support resources we have to jump start your development with RadControls for ASP.NET AJAX. See how to integrate our AJAX controls seamlessly in SharePoint 2007/2010 visiting our common SharePoint portal.
0
Johan
Top achievements
Rank 1
Rank 1
answered on 28 Jan 2011, 10:40 AM
Hi Iana,
that would be great! I have now spent two days crafting a workaround (on the basis of some broken examples i found) and it works but I have a renewed respect for the one that writes a telerik worthy solution. I have too much hardcoded stuff/ugly code in my solution now.
In the process I found the online visual style builder which is great and I found a tool somewhere that can generate an assembly from the downloaded zip file (142703_telerik-webresourcebuilder). Then I have to register every component (26 of them) with the style manager for every custom skin (the solution where you register only the assemby containing the custom skin with the style manger doesn't seem to work anymore) and have to replace the skinmanager with a user control that checks if a skin is embedded or not and if not I have to not only recursively set the skin for the control tree but also disable the EnableEmeddedSkins property.
What I would like the new solution to do (if I may request so):
- Provide a telerik supported tool for generating the assembly from the download zip file from the visual style builder. Let this tool accept more than one input file (see below) so that multiple custom skins can be embedded in one assembly.
- Beeing able to register this assembly with the stylemanager or skinmanager with one line (not one line per control, or worse, one line per control per custon skin)
- The SkinManager then handles the custom skin equal to the embedded skin (no need to fiddle with EnableEmbbeddedSkins).
For example: I create a skin "TestSkin1" with the visual style builder. Then I run the assembly generator to create a "TestSkin1File.dll" file.
With the tool I use now (142703_telerik-webresourcebuilder) this dll is 7Mb so maybe it could be made more efficient to create smaller dll's.
I would like to register thiss TestSkin.dll file with one line. Something like:
Also, if I create a subsequent skin, TestSkin2 I would like to be able to use the assembly generation tool to accept TestSkin1.zip and TestSkin2.zip as input files and generate, say, a TestSkins.dll file which I can register with one line etc.
That would be great.
regards,
Johan
that would be great! I have now spent two days crafting a workaround (on the basis of some broken examples i found) and it works but I have a renewed respect for the one that writes a telerik worthy solution. I have too much hardcoded stuff/ugly code in my solution now.
In the process I found the online visual style builder which is great and I found a tool somewhere that can generate an assembly from the downloaded zip file (142703_telerik-webresourcebuilder). Then I have to register every component (26 of them) with the style manager for every custom skin (the solution where you register only the assemby containing the custom skin with the style manger doesn't seem to work anymore) and have to replace the skinmanager with a user control that checks if a skin is embedded or not and if not I have to not only recursively set the skin for the control tree but also disable the EnableEmeddedSkins property.
What I would like the new solution to do (if I may request so):
- Provide a telerik supported tool for generating the assembly from the download zip file from the visual style builder. Let this tool accept more than one input file (see below) so that multiple custom skins can be embedded in one assembly.
- Beeing able to register this assembly with the stylemanager or skinmanager with one line (not one line per control, or worse, one line per control per custon skin)
- The SkinManager then handles the custom skin equal to the embedded skin (no need to fiddle with EnableEmbbeddedSkins).
For example: I create a skin "TestSkin1" with the visual style builder. Then I run the assembly generator to create a "TestSkin1File.dll" file.
With the tool I use now (142703_telerik-webresourcebuilder) this dll is 7Mb so maybe it could be made more efficient to create smaller dll's.
I would like to register thiss TestSkin.dll file with one line. Something like:
<telerik:RadStyleSheetManager ID="RadStyleSheetManager1" runat="server">
<StyleSheets>
<telerik:StyleSheetReference Name="TestSkin1File.TestSkin1.css" Assembly="TestSkin1" />
</StyleSheets>
</telerik:RadStyleSheetManager>
(Currently this does not work, although in an example from 2005 I had to conclude that it had worked in the past)
I do not want to have to register every control separately, with a line for every <Control>
<telerik:StyleSheetReference Name="TestSkin1File.TestSkin1.<Control>.TestSkin1.css" Assembly="TestSkin1" />
Currently I have to register 26 controls separately, per custom skin.Also, if I create a subsequent skin, TestSkin2 I would like to be able to use the assembly generation tool to accept TestSkin1.zip and TestSkin2.zip as input files and generate, say, a TestSkins.dll file which I can register with one line etc.
That would be great.
regards,
Johan
0
Robert
Top achievements
Rank 1
Rank 1
answered on 21 Oct 2011, 03:32 PM
I am using version RadControls for ASP.NET AJAX Q2 2011 SP1 and was wondering if it is now possible to use custom skins and manage them via skinmanager? I'm hoping there is a seamless UI interface and implementation for users to be able to select any skin, even custom ones.
0
Hello Robert,
Do go through the following help article - I believe it contains the answer to your question.
All the best, Tsvetoslav
the Telerik team
Do go through the following help article - I believe it contains the answer to your question.
All the best, Tsvetoslav
the Telerik team
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed now
0
Oliver
Top achievements
Rank 1
Rank 1
answered on 23 Feb 2012, 06:10 PM
I too am looking for this functionality and the last Telerik reply from Tsvetoslav does not contain a link to the help article suggested!
0
Hello Oliver,
Sorry for having left-behind the link. Here you go:
http://www.telerik.com/help/aspnet-ajax/radskinmanager.html
Regards, Tsvetoslav
the Telerik team
Sorry for having left-behind the link. Here you go:
http://www.telerik.com/help/aspnet-ajax/radskinmanager.html
Regards, Tsvetoslav
the Telerik team
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed now.