1. RadCalendar (input box) and RadNumericTextBox both do not respect the form dectoator skin. while this is probably gonna have a big effect but that should be the correct behaviour IMO. I simply throw all my controls on a form and decorate it by setting the skin of form dectorator and it looks awesome, but once i add controls like mentioned then they look odd because the decoration is not being respected.
2. Form dectorator does not decorate controls that are inside a sliding zone (collapsed initially), simply throw a slide zone splitter and the controls not inside the slide zone will get decorated but not the ones inside.
3. General note, I believe now since you guys introduce the form decoration, all controls u develop (radcalendar, radinput, even rad combobox) should all apply skins based on formdectorator as the master, if no form dectoration then shoudl apply what ever skin is set. This will make all the controls look proper based on the skin set for the decorator.
What I have done in my project is basically throw a form decorator on my page, regular textboxes, radgrid, panelbar etc. then i globally set the skin of all telerik controls and everything is nice and pretty except those mentioned that dont respect the decotration.
2. Form dectorator does not decorate controls that are inside a sliding zone (collapsed initially), simply throw a slide zone splitter and the controls not inside the slide zone will get decorated but not the ones inside.
3. General note, I believe now since you guys introduce the form decoration, all controls u develop (radcalendar, radinput, even rad combobox) should all apply skins based on formdectorator as the master, if no form dectoration then shoudl apply what ever skin is set. This will make all the controls look proper based on the skin set for the decorator.
What I have done in my project is basically throw a form decorator on my page, regular textboxes, radgrid, panelbar etc. then i globally set the skin of all telerik controls and everything is nice and pretty except those mentioned that dont respect the decotration.
3 Answers, 1 is accepted
0
Hello Zoinky,
Up to your questions
1. At present the RadFormDecorator skips decorating controls such as RadNumericTextBox and RadDatePicker, as they have their own skinning. Yet, you are correct to expect that those skins should "match" - while they not. We will be taking action in this direction into "aligning" the look of the two products when the same skin is used.
2. As for problem #2 it could be from using an older Telerik.Web.UI.dll - where the sliding panes are [direct] children of the <body> element, and not of the splitter. In the current version of the sliding panes are children of the splitter - and they should work fine if you use DecorationZoneID property. To make sure it is so, we tested with a sample page and it worked fine with the Q3 2008 release. My advice would be to wait till the coming Q3 SP1 to be released in 1 or 2 days from now, and give it a try.
3. You can easily achieve the effect you are looking for - that is, controlling the skin of all Telerik controls on a page using a single control. It is only that RadFormDecorator is not this control :) As of Q3 we introduced a special new control called RadSkinManager. Setting its Skin property causes the skin to be applied to any other Telerik control.
Sincerely yours,
Tervel
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Up to your questions
1. At present the RadFormDecorator skips decorating controls such as RadNumericTextBox and RadDatePicker, as they have their own skinning. Yet, you are correct to expect that those skins should "match" - while they not. We will be taking action in this direction into "aligning" the look of the two products when the same skin is used.
2. As for problem #2 it could be from using an older Telerik.Web.UI.dll - where the sliding panes are [direct] children of the <body> element, and not of the splitter. In the current version of the sliding panes are children of the splitter - and they should work fine if you use DecorationZoneID property. To make sure it is so, we tested with a sample page and it worked fine with the Q3 2008 release. My advice would be to wait till the coming Q3 SP1 to be released in 1 or 2 days from now, and give it a try.
3. You can easily achieve the effect you are looking for - that is, controlling the skin of all Telerik controls on a page using a single control. It is only that RadFormDecorator is not this control :) As of Q3 we introduced a special new control called RadSkinManager. Setting its Skin property causes the skin to be applied to any other Telerik control.
Sincerely yours,
Tervel
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Zoinky
Top achievements
Rank 1
Rank 1
answered on 24 Nov 2008, 05:02 PM
1. Do you have some time frame when u will align the look of those controls with the form decorator when same skin is used?
2. I will try the SP1 as soon as it comes out, i just figured out another problem so hopefully this will be solved as well, the control inside a MULTIPAGE (multiview) do not get decorated if the page is not in-view. so if i have 2 pages of pageviews and first is the selected index, the controls in second page do not get decorated
3. I had a look at the skin manager, this doesnt help with my problem, I am not setting the skin on per page bases, i am using the web.config
<
add key="Telerik.Skin" value="Sunset"/>, Also i wish there was a way i could set this in code so that i could make all the telerik skins avaiable for my application instead of manually changing the webconfig every time i want one changed.
0
Hi Zoinky,
Up to your questions
1. We will do our best to address this for the current Q1 2009, which started couple of weeks ago. The official release is scheduled for sometime late February, but there will be a public beta about a month prior to that - e.g. late January.
2. I am not able to reproduce the reported behavior. You might have some setting that is causing things to not work right, or you are still using the older version. Here is an online demo that features a RadMultiPage with couple of tabs/pages containing decorated controls. The controls in the invisible page are skinned as well.
http://demos.telerik.com/aspnet/prometheus/FormDecorator/Examples/FormDecoratorAndRadControls/DefaultCS.aspx
3. I still believe RadSkinManager is the control that fits the task for skinning all controls on a page. You can add it to a master page, and all inherited pages will pick the skin from there. Of course, you can use the Web.config as you do now.
Best wishes,
Tervel
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Up to your questions
1. We will do our best to address this for the current Q1 2009, which started couple of weeks ago. The official release is scheduled for sometime late February, but there will be a public beta about a month prior to that - e.g. late January.
2. I am not able to reproduce the reported behavior. You might have some setting that is causing things to not work right, or you are still using the older version. Here is an online demo that features a RadMultiPage with couple of tabs/pages containing decorated controls. The controls in the invisible page are skinned as well.
http://demos.telerik.com/aspnet/prometheus/FormDecorator/Examples/FormDecoratorAndRadControls/DefaultCS.aspx
3. I still believe RadSkinManager is the control that fits the task for skinning all controls on a page. You can add it to a master page, and all inherited pages will pick the skin from there. Of course, you can use the Web.config as you do now.
Best wishes,
Tervel
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.