I have confirmed you are correct that the code was missing a parent container. Because I built this code snippet as a sample to show the problem, I guess I produced a different problem.
But it's a problem I keep running into as I convert more pages from my application to 1.0 preview. Essentially, I'm wondering, is there a plan to have the compiler catch more of these discrepencies because it's really challenging diagnosing the actual problem when all you have is a an javascript error.
So like for instance, the code you saw above, the full code looks like this:
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Test.aspx.cs" Inherits="Test" %>
<!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></title>
</head>
<body>
<form id="form1" runat="server">
<ext:ResourceManager ID="extsm" runat="server" HideInDesign="True" />
<ext:FitLayout ID="AdF" runat="server">
<Items>
<ext:Panel ID="test" runat="server" Title="title" Html="Test" >
</ext:Panel>
</Items>
</ext:FitLayout>
</form>
</body>
</html>
This produces Expected ':' in Testa.aspx at line 14: char 63.
The defective output is :
Ext.onReady(function(){Ext.QuickTips.init();{id:"t est",xtype
:"panel",html:"Test",title:"title"}}); ...
Wrap the FitLayout in a viewport and the error goes away.
This code produces a similar effect
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Test.aspx.cs" Inherits="Test" %>
<!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></title>
</head>
<body>
<form id="form1" runat="server">
<ext:ResourceManager ID="extsm" runat="server" HideInDesign="True" />
<ext:ViewPort ID="vw" runat="server" HideBorders="true" StyleSpec="margin: 2px 2px 2px 2px;" BoxMinWidth="600" BoxMinHeight="400" Layout="Fit">
<Items>
<ext:RowLayout ID="r1" runat="server" Title="test">
<Rows>
<ext:LayoutRow>
<ext:ColumnLayout ID="tt" runat="server">
<Columns>
<ext:LayoutColumn>
<ext:Panel ID="Panel3" runat="server" HideBorders="false" Title="FirstRow">
<Content>
Test
</Content>
</ext:Panel>
</ext:LayoutColumn>
<ext:LayoutColumn>
<ext:Panel ID="Panel2" runat="server" HideBorders="false" Title="Test">
<Content>
Test<br />test
</Content>
</ext:Panel>
</ext:LayoutColumn>
</Columns>
</ext:ColumnLayout>
</ext:LayoutRow>
<ext:LayoutRow>
<ext:Panel ID="Panel1" runat="server" HideBorders="false" Title="TEST">
<Content>
Test<br />test
</Content>
</ext:Panel>
</ext:LayoutRow>
<ext:LayoutRow>
<ext:Panel runat="server" Title="Test" />
</ext:LayoutRow>
</Rows>
</ext:RowLayout>
</Items>
</ext:ViewPort>
</form>
</body>
</html>
Same issue, an incomplete js fragment
... ;{id:"Panel3",xtype:"panel",title:"FirstRow",conte ntEl:"Panel3_Content"}...
Hope this information helps to improve final release of version 1.0. These types of problems where an outter panel needs to be added as a parent used to be caught before the client js runtime.
