May 11, 2012, 11:18 PM
[CLOSED] Components created in a Direct Response do not always generate correct script
Hi,
Consider this markup:
Because I have set the window to be hidden, it doesn't actually show. The reason is there is an error in the script that is generated. Although I have simulated a scenario where the window should be shown using window.Show();, the output creates MyWindow.show() instead of App.MyWindow.show().
I see on the first line you are able to figure out the namespace is App and destroy the component first, so hopefully this means this last line can be fixed too?
But this then got me wondering: as I understand it, the "App" namespace can be customzied in web.config and/or the resource manager and "App" is only the default. So
For example, if I do this:
Maybe this way you can then always safely use Ext.net.App.MyWindow in the above examples?
Consider this markup:
<%@ Page Language="C#" %>
<!DOCTYPE html>
<html>
<head>
<title>Example</title>
</head>
<body>
<ext:ResourceManager runat="server" Theme="Gray" />
<ext:Button runat="server" Text="Get Server Time">
<DirectEvents>
<Click
Url="WebServices/ServerTimeService.asmx/GetServerTimeWindow"
Type="Load"
Method="POST"
CleanRequest="true" />
</DirectEvents>
</ext:Button>
</body>
</html>using System;
using System.Web.Services;
using Ext.Net;
namespace Ext.Net2.Tests.Direct.WebServices
{
[WebService(Namespace = "http://tempuri.org/")]
[WebServiceBinding(ConformsTo = WsiProfiles.BasicProfile1_1)]
public class ServerTimeService : WebService
{
[WebMethod]
public DirectResponse GetServerTimeWindow()
{
var window = new Window("Server time", Icon.Time)
{
ID = "MyWindow",
Html = DateTime.Now.ToString(),
Hidden = true
};
// some condition makes us show it now
window.Show();
return new DirectResponse(window.ToScript());
}
}
}Ext.net.ResourceMgr.destroyCmp("App.MyWindow");
Ext.create("Ext.window.Window",{
id:"MyWindow",
height:100,
html:"12/05/2012 00:01:57",
renderTo:Ext.getBody(),
width:200,
title:"Server time",
iconCls:"#Time"});
MyWindow.show();Because I have set the window to be hidden, it doesn't actually show. The reason is there is an error in the script that is generated. Although I have simulated a scenario where the window should be shown using window.Show();, the output creates MyWindow.show() instead of App.MyWindow.show().
I see on the first line you are able to figure out the namespace is App and destroy the component first, so hopefully this means this last line can be fixed too?
But this then got me wondering: as I understand it, the "App" namespace can be customzied in web.config and/or the resource manager and "App" is only the default. So
- How will you know what namespace to use?
- If the namespace for the client objects is defined on the ResourceManager on the originating ASPX page you would not know which one to use?
For example, if I do this:
<ext:ResourceManager runat="server" Theme="Gray" Namespace="CompanyX" />Ext.net.ResourceMgr.destroyCmp("App.MyWindow");Ext.net.ResourceMgr.init({id:"ctl00",theme:"gray",ns:["CompanyX"]});Ext.net.ResourceMgr.init({id:"ctl00",theme:"gray",ns:["CompanyX"]});
Ext.net.App = CompanyX;Maybe this way you can then always safely use Ext.net.App.MyWindow in the above examples?
Last edited by Daniil; May 14, 2012 at 10:48 AM.
Reason: [CLOSED]
