Hello Oliver,
On 16-Apr-99 22:59:13, you wrote:
>> I wonder what are the advantages of using bytecode compiler and then an
>> interpreter for Javascript when you always have to interpreter the
>> Javascript source code from the pages.
>It's both a design and a speed issue. The design issue is that it's easily
>implemented with a bison generated parser:), the speed issue is that it's
Ah, well, it's the usual tokenizing. With this all these new Internet
manias to invent new concepts, I thought you were actually saving a byte
code stream to disk cache.
>> >The Document Object Model I'm implementing is closely based on the
>> >one of the Microsoft Internet Explorer, because it is much more flexible
>> >than that of NS (that's what M$ calls "Dynamic HTML").
>>
>> I'm not sure if this would make more sense, but how about following the
>> actual W3C DOM specification?
>That's just a subset of the MSIE one, too.
So, what features does it have besides the ones in DOM standard? Layers?
Talking about MSIE, is Voyager going to have a progressive HTML table
layout engine that starts laying tables before they are fully loaded.
Voyager has been fast in many issues, but currently it is particularly
retarded rendering tables, even when compared with other Amiga browsers
that also wait to load the tables definition till the end.
Regards,
Manuel Lemos
E-mail: [EMAIL PROTECTED]
URL: http://www.e-na.net/the_author.html
PGP key: finger:[EMAIL PROTECTED]
--
