Hi,

I don't know why you are using "parent.parent.addWindow(parameters);". To add a window, we simply to use Add() method inside window level properties. I attached sample to show you how i add a new window. Please let me know if you also face the issue performance.

Regards,
Handy

Thank you for your reply.

My code is nearly identical to yours.  Instead of getting the instance of WebDesktopManager1 from the WebDesktopWindow using your code below....

        function Button1_onclick() {
            var desktop = window.parent.ISGetObject("WebDesktopManager1");
            var window2 = desktop.CreateWindow();
            window2.Text = "Window2";
            window2.Name = "Window2";
            window2.ContentURL = "http://google.com";
            window2.ContentMode = "UseIFrame";
            window2.AllowMinimize = "No";

            desktop.Windows.Add(window2);
            window2.Show();
        }

I call  parent.addWindow() which calls my own javascript function on the same page.  This prevents me from having to add a javscript function on each WebDesktopWindow page that will need to open a new window.

My method:

    function addWindow(name, text, imageURL, contentURL, width, height, allowMin, allowMax, allowClose, isMaximized, focusIfExists )
    {
        var dm = ISGetObject("WebDesktopManager1");
        var wnd = dm.GetWindow(name);
        if (wnd == null || focusIfExists == 'False')
        {
            wnd = new WebDesktopWindow();
            wnd.Text = text;
            wnd.Name = name;
            wnd.ControlBoxImage = "is_webdesktop-16.gif";
            wnd.ContentURL = contentURL;
            wnd.ContentMode = "UseIFrame";
            wnd.AllowMinimize = allowMin;
            wnd.AllowMaximize = allowMax;
            wnd.AllowClose = allowClose;            
            dm.Windows.Add(wnd);
            
            wnd.ResizeTo(width, height);

            if (isMaximized == 'True')
            {
                wnd.Maximize();
            }
            wnd.Show();
        }
        else
        {
            wnd.Activate();
            wnd.Show();
        }
    
    }

In either case, I am experience performance issues in Internet Explorer.

I SHOULD ADD, Internet Explorer also has poor performance when simply clicking on the Close icon (x) in the corner of each WebDesktopWindow.   It's not a horrible delay -- but takes nearly 1 full second to close the window.  Firefox does not have these performance issues.... and I don't have this delay when accessing the Developer Network UI.

Thank you in advance for any suggestions that you may have.

After further testing, I have determined that the WebDesktop responsiveness is only poor if a particular Window is open.  This "problem window" is very complex, with nested IFrames.  With the Window visible, many javascript function calls are slow (including maximize, minimize and close window functions) .... but with the window hidden, things are much more responsive.

Again, the performance in Firefox is GREAT.

This surely has to do with the complexity of my Window page.  Attached is a zipped example to show you my structure.  I respectfully ask that you take the time to overview them.

---------------------------------------------------

Scenario:

- WebDesktop shortcut opens Default.aspx   (this file contains the WebPaneManager)

   - WebPaneManager opens IFrame Navigation.aspx for navigational frame

   - WebPaneManager opens IFrame Default.aspx 

- Default.aspx loads inherits MasterPage MasterTabs.aspx   (WebTab control is within it)

- The WebTab control is then populated with tabs.  Each of those tabs opens another masterpage:

- MasterTabs2.aspx (WebTab control) is loaded within each tab.  This is the second WebTab control within the page and provides tabs with a position=bottom

-----------------------------------------------------

The above scenario uses nested IFrames to accomplish having Tabs displayed at the top of the page (primary navigation - MasterTabs.aspx) and secondary navigation (MasterTabs2.aspx), while inheriting the MDSPageFirmUserTab class to allow for easy dynamic creation of tabs.

Screenshot is provided 

-----------------------------------------------------

I prefer using IFrames to InlineContent because I find them easier to manipulate. 

This scenario is yielding poor performance.  I hope to have an explanation and workaround.  Thank you.

Hi,

Unfortunately, i could not run and replicate your issue in here. Your sample are missing some resources and namespaces.Btw, if your page are not inside WebPaneManager, only WebDesktopManager and WebDesktop window, does the issue also happen?

Regards,
Handy

Hello,

No I do not experience the performance problem  if I don't use WebPaneManager.  The problem clearly lies with me using nested IFrames within a WebPane.

Please do the following to reproduce this issue:

 - Create a page Default.aspx that contains a WebPaneManager and 1 pane, and loads Pane.aspx

- Create a MasterPage named MasterTab1.aspx that contains a WebTab control.

- Create a MasterPage named MasterTab2.aspx that contains a WebTab control

- Create a page Pane.aspx that uses masterpage layout MasterTab1.aspx

- Create a page Subtab.aspx that uses masterpage layout MasterTab2.aspx

- Dynamically create a WebTabItem in Pane.aspx that loads SubTab.aspx

- Dynamically create a WebTabItem in SubTab.aspx that loads Content.aspx (any static content)

----------------------------

Doing the above should replicate my problem.  The problem lies in creating multiple nested IFrame windows within a WebPane.  I'm not sure if the master page is contributing to this issue.

As I explained in my support ticket, I'll be happy to supply more code directly to a technician but not post it publicly.

I also have a live dev site that I can share with you to replicate the issue.

Alex