content-loading mechanism questions
"alan hill" <[email protected]> Fri, 05 Mar 2004 20:20:07 +0000
| Newsgroups | gmane.comp.windows.devel.netwindows |
|---|---|
| Message-ID | <[email protected]> |
>On the second point, we don't use an iframe for menu items since >iframes tend to be egregiously expensive in terms of memory >resources. If your app doesn't _really_ need an iframe, you might >look into the NW content loading mechanism. I always assumed netWindows used iframes for its content-loading. May I ask what it does use? Offhand, the alternative loading methods would be XMLHTTP (not supported by all target platforms), dynamically appending script tags using the DOM, setting cookies (javascript calls for dummy image and sends a query string, server sets cookies) or by using a java applet. Have I missed something? Still on the content-loader, are there any plans to "modularise" it as with the signals and slots? Cheers, Alan Hill _________________________________________________________________ Tired of 56k? Get a FREE BT Broadband connection http://www.msn.co.uk/specials/btbroadband _______________________________________________ The netWindows developers list: [email protected] http://netwindows.org/mailman/listinfo/devel_netwindows.org