Joseph Bonanno
Top achievements
Rank 1
Rank 1
Joseph Bonanno
asked on 01 Oct 2009, 04:29 PM
I am trying to figure out a good way to strucure our conversion to the new AJAX skins. We are currently runnning mulitple themes, each which contain mulitple skins for each control. For example, a grid can have 3 - 5 different skins, a menu can have 2 or 3 depending on location within the system. The previous folder architecture grouped Skins by control, then by skin, where the new folder architecture groups by skin, then by control.
Is there a way to include mulitple skins (or css files) with a particular skin folder?
for example is it possible to set up a structure like this
Skins
-> Default
-> -> tabstrip.Default.css
-> -> tabstrip2.Default.css
We currently support about 35 themes within our application, and each theme contains multiple skins for each control in the RadControl set.
Alternatively, is there a way to go back to the old folder grouping, by control, then by skin?
Is there a way to include mulitple skins (or css files) with a particular skin folder?
for example is it possible to set up a structure like this
Skins
-> Default
-> -> tabstrip.Default.css
-> -> tabstrip2.Default.css
We currently support about 35 themes within our application, and each theme contains multiple skins for each control in the RadControl set.
Alternatively, is there a way to go back to the old folder grouping, by control, then by skin?
1 Answer, 1 is accepted
0
Hello Joseph,
Judging by the provided information, I conclude that you are using non-embedded custom skins. Since the RadControls for ASP.NET AJAX do not register custom CSS files automatically, the organisation and physical location of the CSS files and images is entirely up to your preference. Generally, you can have several CSS files in one skin folder, but I don't recommend mixing different skins and their images in one folder.
By the way, you can consider using embedded custom skins. This will bring the following benefits:
1) there will be no need to take care of the physical location of the CSS files
2) you will be able to combine the registered skins on the page with RadStyleSheetManager, so that the number of HTTP requests is reduced.
There is one drawback though - since the CSS files will not be located inside the ASP.NET theme anymore, they will not be registered automatically by the .NET framework. You will have to register them with RadStyleSheetManager.
Sincerely yours,
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.
Judging by the provided information, I conclude that you are using non-embedded custom skins. Since the RadControls for ASP.NET AJAX do not register custom CSS files automatically, the organisation and physical location of the CSS files and images is entirely up to your preference. Generally, you can have several CSS files in one skin folder, but I don't recommend mixing different skins and their images in one folder.
By the way, you can consider using embedded custom skins. This will bring the following benefits:
1) there will be no need to take care of the physical location of the CSS files
2) you will be able to combine the registered skins on the page with RadStyleSheetManager, so that the number of HTTP requests is reduced.
There is one drawback though - since the CSS files will not be located inside the ASP.NET theme anymore, they will not be registered automatically by the .NET framework. You will have to register them with RadStyleSheetManager.
Sincerely yours,
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.