This is a migrated thread and some comments may be shown as answers.

Setting a Default Skin on Prometheus Controls using Web.config

12 Answers 388 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
mikejoseph
Top achievements
Rank 1
mikejoseph asked on 11 Jan 2008, 05:49 PM
Is there a way I can skin all Prometheus controls by adding a value to my Web.config file?  I found an example on how to do this with the original RadControls, but a Google Search and a forum search gave me no results.  A link to that forum post is:
http://www.telerik.com/community/forums/thread/b311D-tctdd.aspx

Thanks in advance,

Mike Joseph

12 Answers, 1 is accepted

Sort by
0
Sebastian
Telerik team
answered on 14 Jan 2008, 08:37 AM
Hi mikejoseph,

Basically, you should be able to set the Skin property for all Prometheus controls (inside your web site) by adding similar appSettings -> key to the web.config file. The only thing you need to change is the namespace, namely:

<appSettings>    
    <add key="Telerik.Web.UI.Skin" value="Outlook"/>     
</appSettings>    
 

Best regards,
Stephen
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center
0
mikejoseph
Top achievements
Rank 1
answered on 22 Jan 2008, 04:31 PM
Thanks for the reply.  I figured it was something easy like that... :)
0
Joel Kraft
Top achievements
Rank 2
answered on 28 Jan 2008, 04:50 PM
Does this really work?  I am trying with Q3 SP1 with WebBlue specified in my master web.config file and I am getting nothing but the default skin...
0
Sebastian
Telerik team
answered on 29 Jan 2008, 07:57 AM
Hello Joel,

It seems that I spoke too soon - actually this feature has already been implemented by our developers but will be part of Q3 2007 SP2 of RadControls Prometheus (expected at the end of February). Here is some more info on the matter:

Global skin setting for the entire web site/web application project

If you need to register a common skin for all RadControls in your web site/web application project or you want to assign a particular skin for each instance of RadControl, you can do that very easily modifying the web.config
file as follows:

<appSettings> 
 <add key="Telerik.Skin" value="[SkinName]" />   <!-- Sets the skin for all Prometheus controls --> 
 <add key="Telerik.[ShortProductName].Skin value="[SkinName]" /> 
   <!-- Sets the skin for a specific control --> 
</appSettings> 

Setting the value to an empty string disables the skin for the control(s).

In the meantime you may consider using the ASP.NET 2.x Theme mechanism to apply global style settings for RadControls Prometheus.

Best regards,
Stephen
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center
0
Joel Kraft
Top achievements
Rank 2
answered on 29 Jan 2008, 05:40 PM
That's great.  I'll look for that in the next service pack then!

I assume that you guys designed it to look at the product-specific key first, then if that isn't found go to the global key?


Joel
0
Sebastian
Telerik team
answered on 30 Jan 2008, 07:45 AM
That is correct, Joel. The product-specific key will take priority over the global key if both are specified.

Best regards,
Stephen
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center
0
Joel Kraft
Top achievements
Rank 2
answered on 29 Feb 2008, 06:57 PM
Okay, I just looked at this in SP2.

It appears that the web.config value overrides what is specified on the control.
We were trying to look at different skins for a control on a particular page, but couldn't get it to change. Is this the desired behavior?
0
Paul
Telerik team
answered on 04 Mar 2008, 01:04 PM
Hi Joel,

This behavior is by design. Setting "<add key="Telerik.Skin" value="[SkinName]" />" in the web.config sets the skin for all Prometheus controls in the application.

Greetings,
Paul
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center
0
Rational Animal
Top achievements
Rank 1
answered on 26 Mar 2008, 04:47 PM
FYI, the futures build doesn't set the skin based on the default when using the Form Decorator.

Also I think that whatever you hard code a control's skin to should override the setting in the config file. If you don't set a skin, then it should use the config file.
0
T. Tsonev
Telerik team
answered on 27 Mar 2008, 12:32 PM
Hi,

I have tested the FormDecorator with the global settings and they seem to work fine. The setting should look like this:
      <add key="Telerik.FormDecorator.Skin" value="Default"/>

I agree with you, that the global setting should override the control setting. We will fix this problem in time for the official release. Thank you for bringing this issue to our attention.

Best wishes,
Tsvetomir Tsonev
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center
0
T. Tsonev
Telerik team
answered on 27 Mar 2008, 02:28 PM
Hi,

Just a quick follow-up: After some additional testing I have found that the FormDecorator really has a problem when only the global skin is set. We will fix this too for the release. Your Telerik points have been updated for your involvement.

Regards,
Tsvetomir Tsonev
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center
0
Rational Animal
Top achievements
Rank 1
answered on 27 Mar 2008, 02:32 PM
Thanks for following up with these! That's great!
Tags
General Discussions
Asked by
mikejoseph
Top achievements
Rank 1
Answers by
Sebastian
Telerik team
mikejoseph
Top achievements
Rank 1
Joel Kraft
Top achievements
Rank 2
Paul
Telerik team
Rational Animal
Top achievements
Rank 1
T. Tsonev
Telerik team
Share this question
or