[CLOSED] [1.0] ResourcePlaceHolder Issue

  1. #1

    [CLOSED] [1.0] ResourcePlaceHolder Issue

    Hello,

    This morning I have been investigating the placement of script files and the Ext.onReady script block within the page.

    I have attempted to use the ResourcePlaceHolders to achieve moving the includes to the bottom of the page as this is said to improve the performance. My simple page is this:

    <html xmlns="http://www.w3.org/1999/xhtml" >
    <head runat="server">
        <title></title>
    </head>
    <body>
        <ext:ResourceManager runat="server" />
        <ext:Panel runat="server" Title="Hello World" Frame="true">
            <Content>
                <p>Hello World</p>
            </Content>
        </ext:Panel>
        <ext:ResourcePlaceHolder runat="server" Mode="Script" />
    </body>
    </html>
    This is throwing an index out of range error when processing the script tag placeholders in InitScriptFilter on the following line (line no. 183):

    this.html.Remove(index, placeHolderMarker.Length);
    It appears that it removes the <Ext.Net.InitScript> ... </Ext.Net.InitScript> block and then attempts to remove the placeHolderMarker. However, in removing the <Ext.Net.InitScript> block first you are changing the index location of <Ext.Net.InitScriptPlaceHolder> which then invalidates the call to this.html.Remove() shown above.
  2. #2

    RE: [CLOSED] [1.0] ResourcePlaceHolder Issue

    Hi,

    Fixed. Please update from SVN
  3. #3

    RE: [CLOSED] [1.0] ResourcePlaceHolder Issue

    ...as this is said to improve the performance.
    yes, in the typical use of JavaScript on the page, which is usually secondary to the html/css. So, if the .js files fail to load, or loads slowly, the content of the page should not be interrupted and is still accessible.


    In Ext.NET (and Coolite), the JavaScript creates the html/css and you'll want the .js files loaded early (and quickly). In the past I've run a few tests with bottom loaded .js files + Ext.NET and did not like the results.


    Certainly, run your own tests to determine which is best for your application.


    Hope this helps.




    Geoffrey McGill
    Founder
  4. #4

    RE: [CLOSED] [1.0] ResourcePlaceHolder Issue

    Hi Guys,

    I can confirm the problem is resolved.


    I will carry out some testing and see what I think.


    Cheers

Similar Threads

  1. [CLOSED] Pecilluar issue in the DropDown, UI Issue
    By Shanth in forum 1.x Legacy Premium Help
    Replies: 4
    Last Post: Feb 22, 2012, 12:02 PM
  2. [CLOSED] [1.0] ResourcePlaceHolder is ignored
    By tdracz in forum 1.x Legacy Premium Help
    Replies: 2
    Last Post: Dec 10, 2009, 11:12 AM

Posting Permissions