Hi Robin,
The div creation process in DHTML is somewhat complicated - and depends
on what browser it's running in.
There are at least two divs created for every view - one in the clickdiv
tree, and one in the visual div tree. The zIndex is set for each div
because some browsers (IE) don't respect implicit z-ordering. If a view
is made clickable, a div is added to the click tree to handle mouse
events. If a view needs a visual resource, a div is created for
multiframe resources, unless stretches is on in which case an img is used.
A good way to understand what's happening is to use Firebug to inspect
the div hierarchy. I'd also recommend reviewing the DHTML sprite code,
available at
http://svn.openlaszlo.org/openlaszlo/trunk/WEB-INF/lps/lfc/kernel/dhtml/
- in particular,
http://svn.openlaszlo.org/openlaszlo/trunk/WEB-INF/lps/lfc/kernel/dhtml/LzSprite.js
Of course, feel free to ask me any specific questions. If you do notice
a difference in behavior between swf and dhtml, it's likely a bug -
they're supposed to behave the same. Please isolate to test cases
and/or file bugs when you come across this!
[email protected] wrote:
Hi Max,
How is everything going?
Recently, Frank and I keep fixing Jade P1 bugs. Most of which connect to
runt time difference of swf & dhtml
Seems that all lz.view inheritance will be populated at least one div. I
can observe tremendous amount of nested divs with different z-index level.
This makes me curious to know more about how dom tree has been build
from middle language translation.
If that okay for you to give me some hints or path to go to better
understand that?
Thanks,
Robin
--
Regards,
Max Carlson
OpenLaszlo.org
