Here's a pretty advanced sample which demonstrates linking one <ext:Editor> to many <ext:Label> components and passing the Labels updated value back to the server for processing.
Example
<%@ Page Language="C#" %>
<%@ Register assembly="Ext.Net" namespace="Ext.Net" tagprefix="ext" %>
<script runat="server">
[DirectMethod(Namespace="CompanyX")]
public void Update(string id, string newValue)
{
X.Msg.Notify(id, newValue).Show();
}
</script>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head runat="server">
<title>Ext.NET Example</title>
</head>
<body>
<form runat="server">
<ext:ResourceManager runat="server" />
<ext:Label ID="EditLabel1" runat="server" Text="Double Click to Edit" />
<br />
<br />
<ext:Label ID="EditLabel2" runat="server" Text="Or, edit this Label" />
<ext:Editor
runat="server"
Target="${[id^=EditLabel] .x-label-value}"
ActivateEvent="dblclick">
<Listeners>
<Complete Handler="CompanyX.Update(editor.boundEl.parent().id, value);" />
</Listeners>
</ext:Editor>
</form>
</body>
</html>
The real hack in there is obviously the .Taget property which is set with a DomQuery string. This particular DomQuery string can be explained as follows...
1. Find all elements on the page which have an "id" attribute with a value that starts with "EditLabel". This will find both "EditLabel1" and "EditLabel2".
2. Then find the .x-label-value element inside the element from #1.
The ${...} syntax is a shortcut for an Ext.select function which takes the DomQuery string as a parameter. The Ext.select will return a list of elements to attach the Editor to. In this case, the two <ext:Label>'s.
The ajax callback to the server is handled by a custom DirectMethod, although you could fire a <Complete> DirectEvent as well. Either one will work.
The first parameter passed to the Update method is the <ext:Label>'s client-side ID. Second parameter is the new value for the Label.
More information for DomQuery available at the following location, see
http://www.extjs.com/deploy/dev/docs...s=Ext.DomQuery
This is a much more advanced sample than we typically provide, but it does demonstrate a very powerful technique and considering how much functionality is actually happening behind the scenes here, uses very little code.
Hope this helps.
