I was wondering if it is possible to create a Control Extender that does not render a behavior, but renders binding information instead. From what I've seen, this doesn't seem to be possible and the way I should do this is to implement IScriptControl and then code my own extender per say.
Anybody else doing something like this?
Thx
IScriptControl will get you there - you'll just have to render out all the script manually...
Ok ... that's the path I was heading down.
If I have a control that's markup is like the following
...
<asp:Button id="button1" runat="server" text="Text" /
<Ext:BindingModifier id="BM1" runat="server">
<Ext:BindingModifierProperties TargetControlID="button1" />
</Ext:BindingModifier
can it still be considered an extender or are we just talking about something else at this point?
Generalizing my question, what's the definition of an Extender? Must it emit a behavior?
Thx for the help and being so active on the boards.
Well that's an extender for sure. What XML are you looking to emit exactly?
I'm looking to emit binding information that ties a series of controls to _PageRequestManager's "inPostBack" property.
The point is to disable a series of controls during a postback.
An example of the code I'm looking to emit can be foundat this post.
Thx
Yeah we don't help you too much there. Your other option it so instanitate a behavior that does this instead, either directly (e.g. finds the disabled property and toggles it) or by adding the bindings via the Atlas object model directly.
Ok ... we're going to mimic the way to write the markup of an extender because it makes sense, but implement IScriptControl to handle all of the script output.
Any thoughts on future plans on creating a pre-built library / project template to do something with other sections of xml-script other than behaviors?
No comments:
Post a Comment