Hello Oliver,
On 16-Apr-99 11:30:28, you wrote:
>Javascript
>----------
>Of course, the thing everyone wants (esspecially the ones asking for "Java"
>:) I've implemented the Javascript 1.2 core language with a nicely-done
>bytecode interpreter. Voyager first compiles the code down into a special
>P-Code (or "Bytecode", as it's nowadays called, although it really consists
>of 16 bit instructions) which is then executed by a special interpreter. This
>should give the fastest JS implementation available in the industry, and
>should esspecially help with the otherwise massive impact of event handler
>code or looping operations.
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.
>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?
>HTML
>----
>Numerous major and minor updates. Support for CSS 1 is being worked on
>and will most likely be ready in time. Note that "Dynamic HTML"
>is actually a JS-related issue.
Do you plan to support proper keyboard navigation as defined in HTML 4
spec, ie, honouring ACCESSKEY tag attributes, form LABEL tags and link and
form fields TABINDEX tag attribute? AFAIK, only IE4+ does this but this is
very important to make Web pages fully controlable by keyboard.
>Networking
>----------
>Cache system has been reworked to require less maintaince.
>Optional "blacklisting" for image fetching based on URLs
>allows one to get rid of banners and <IMG> based
>tracking services. The same will probably be added for
>cookies.
Does that mean that Voyager will warn about banners with embedded images
from other sites than the one of the current page?
Another topic: what about supporting HTTP and FTP resume for downloads?
Regards,
Manuel Lemos
E-mail: [EMAIL PROTECTED]
URL: http://www.e-na.net/the_author.html
PGP key: finger:[EMAIL PROTECTED]
--
