mattsmith321
11 May 2007, 6:52 AM
Hi all,
We currently have Ext in several places in our app with great success. We've had a simple BorderLayout implementation (header, collapsible left nav, content, footer) in place during development for about six months now.
Everything works great with the layout for most of the people most of the time. However, there are situations on specific screens (and especially with specific users with slow machines) where you can see the contents of the page prior to getting rendered into the BorderLayout. Usually it is pretty brief, but it does look pretty ugly and can actually show for several seconds if we have some slower queries or a lot of data being sent down to the page.
So what we would like to do is to switch to an iframe implementation of the BorderLayout (like the Ext docs). This way, we can just push the header, left nav, and footer once, render it once into the layout and then just update the iframe content area.
In theory, this shouldn't be too hard for the basic navigation when you are already in the site: left nav links should change the iframe url (same way the docs do) and links within the content area should just refresh the content area. No big deal. However, I'm not quite sure what to do for links for pages from outside of the app (bookmarks, direct links to pages via sent via email, etc.). Specifically, it seems like I'm going to need to check the referrer url to determine which MasterPage I should use to render a page. Has anyone else implemented BorderLayout with iframes with ASP.Net 2.0 MasterPages? Anything I should look out for?
It could be that this is really simple but I'll be working on it this weekend and wanted to get this posted and get some feedback before everyone left for the weekend.
Thanks!
Matt
We currently have Ext in several places in our app with great success. We've had a simple BorderLayout implementation (header, collapsible left nav, content, footer) in place during development for about six months now.
Everything works great with the layout for most of the people most of the time. However, there are situations on specific screens (and especially with specific users with slow machines) where you can see the contents of the page prior to getting rendered into the BorderLayout. Usually it is pretty brief, but it does look pretty ugly and can actually show for several seconds if we have some slower queries or a lot of data being sent down to the page.
So what we would like to do is to switch to an iframe implementation of the BorderLayout (like the Ext docs). This way, we can just push the header, left nav, and footer once, render it once into the layout and then just update the iframe content area.
In theory, this shouldn't be too hard for the basic navigation when you are already in the site: left nav links should change the iframe url (same way the docs do) and links within the content area should just refresh the content area. No big deal. However, I'm not quite sure what to do for links for pages from outside of the app (bookmarks, direct links to pages via sent via email, etc.). Specifically, it seems like I'm going to need to check the referrer url to determine which MasterPage I should use to render a page. Has anyone else implemented BorderLayout with iframes with ASP.Net 2.0 MasterPages? Anything I should look out for?
It could be that this is really simple but I'll be working on it this weekend and wanted to get this posted and get some feedback before everyone left for the weekend.
Thanks!
Matt