> >> So, what features does it have besides the ones in DOM standard?
Layers?
>
> >Generally, it's much more flexible in respect to what object properties
can
> >be changed "on the fly" after the page is represented. The only "dynamic"
> >aspects in the Mozilla object model are document.write() and the ability
> >to replace Image.src (in a limited fashion).
>
> I guess you mean before NS 4. I haven't studied the Dynamic capabilities
> of Netscape but I know it handles layers.
Eugh, DHTML in Mozilla can get painful. While layers can work, they were
never
really thought through. For example, you can use them to create a sort of
inline
frame <IFRAME> in a way that makes it look like a continuous part of the
page, however the
only way you can change the source for the layer is through ECMAscript (I'll
call
it that instead of JavaScript - just to confuse the issue a bit more =).
This is fine when
used from the parent page, unfortunately when called from the layer itself,
it dies...
Which isn't nice - why NS couldn't have gone with <IFRAME> (official
HTML4.0)
is anyone's guess.
The Dynamic properties of NS are okay, if not as clear & easy as IE to
implement.
That's not to say that IE is great but even my dislike of M$ can't detract
from the fact
that IE's DOM beats the hell out of Mozillas.
If Voyager has a clean DOM & CSS1 along the lines of W3C & the IE
implementation
then Ollie is IMHO the most prolific & amazing programmer I know of, no
joke - actually
he already is =)
Oh just one *ikle* thing of note though, will the PNG decoder look out for
alpha channels?
Due to the fact that not even IE, NS or Opera have got PNG right, we PNG
evangelists
(you know who you are) are going nuts. I'd love to see DHTML using RGBA
images....
Although it'd admittedly be hard on the processor & may scare the programmer
as well =D
Cheers,
Will.
PS. Apologies for using Outlook Express, no Miggy & MD2 ATM... <scream>
= Will Perdriau Wilson = [EMAIL PROTECTED] =
= http://lantic.cjb.net = lantic Web Design =
