Hi, Steve,
That surely is something! Although I believe it's not the best idea to
put part(or all) of main contents of a webpage in dynamically generated
DOM objects (since nothing will show up once the script engine
screwed), I think it could be great they(or somebody) apply the neat
trick for some CMS(contents management system) or Blog
system(specifically for the author mode).
When it comes to one of our oldest foes that we experience loosing
handle on the attempt of moving a WW object fast, you were right that
the DHTML window objects at NetVibes.com shows better characteristic.
The reason is, they just use DIV rather than IFRAME to hold the main
contents for each window object by changing the value of DIV.innerHTML
property.
Have you played with the sample file named 'directHTML.htm'?
In Wednus Window, the mode so called 'direct html' uses the same trick
what NetVibes.com uses.
sample1: WW direct html mode(uses DIV for content expressing
http://wednus.com/wednus0.3.5b2/samples/directHTML.htm
sample2: WW default mode(uses IFRAME for core:content holding)
http://wednus.com/wednus0.3.5b2/samples/parameters.htm
Unlike sample2, in sample1, like the NetVibes.com's, you won't
experience the loosing -handle-thingy when you manage to move around
the WW.
especially in IE, many mouse events vanish away when the mouse move
into the domain of other document(IFRAME).
so it seems the problem will follow us as far as we are stick on using
IFRAME for the core.
by the way, fortunately, minimizing the use of IFRAME is the way what
WW is currently evolving to.
I cannot promise when it will be, but when the new version of WW
released, I hope I could present you some feasible solution for the
mundane headache.
Steve, I always please to talk to you, and again, thanks for your
advice.
--
Sundew Shin
Wednus Project
Manager/Developer
http://wednus.com