I would like to share my comments on the future of the RadFormDecorator control.
In your previous answer you wrote:
"I do think that, unfortunately, you're barking up the wrong tree with FormDecorator as this can only offer a new way of displaying the control itself;"
Indeed, this is exactly
what the RadFormDecorator is about - it has been implemented like this on purpose - as an easy, unobtrusive way of "skinning" buttons, checkboxes, radiobuttons (and more to come soon) existing on the page. Thus, this is aimed to be a tool for developers to further enhance their existing applications and bring them closer to a true, fully-customized look of (say) a desktop application.
At present we have a TODO list of about 10 features that we need to wrap up before the control as such is fully complete - the most important of which being eliminating the intial short flickering when the page loads - when the "browser" controls are replaced with the "decorated" controls. This is a significant challenge by itself, given the fact that the decorator works on the client, and it can potentially update only a portion of the screen, needs to keep track of AJAX requests as well as of elements that were originally not visible. Still, we are getting somewhere and we are pretty sure we will be able to work around that.
Then, once the core feature set is complete you will have a control that seamlessly skins your existing page in a smooth, easy-to-do manner.
The next step then will be to add new server-side controls for additional flexibility - such as a three-state button, image button, as well as server-side versions of the [current] client-side implementations (e.g. telerik:CheckBox, telerik:TextBox). Thus, these are two different areas and we plan to cover both.
I hope this information helps,
the Telerik team