Let me present you with some extra information about how the FormsDecorator works, what can and what cannot be done, how it should be done, and what our plans for the control are.
About the delay
Please note that at present all you needed to do is add the decorator to the page, no other changes to your code required. Obviously, the decorator does its work on the client.
The FormDecorator control is implemented as a standard MS AJAX control. What this means is that its initialization code runs at window.onload
. Thus, in most cases one will be able to see the original "browser" checkboxes and buttons, before the decorator replaces them.
Now, from 1 and 2 it follows that using this approach there will be
a delay, and it won't majically go away.
However, our plans for the development of the control is to provide a set of server classes that will inherit from the default ASP.NET classes - Button, CheckBox, etc. These classes will output from the server the same rendering that is currently created on the client - much like any other Telerik control. Thus, the delay will be gone, however you will need to do some extra work on your pages and replace the declarations, e.g. <asp:Button> with <telerik:Button>.
We also plan to provide "skinning" for <textarea> and <textbox> elements, and possibly some others (e.g. <label> elements). There also will be a mousedown CSS, as already mentioned.
I cannot give you an ETA on this, but since the FormDecorator si generating a lot of interest from the community, we will do our best to have these features implemented in Q2 2008.
I hope this information is helpful and I will keep you updated as new features come along.
All the best,
the Telerik team