Voyager 3 Notes
===============
Ok, here's a short summary of what has been done, is being done
and (eventually) will be done for Voyager 3. This focusses
on "major" changes, and I've written it offhand, so I may
have forgot something.
Document revision: 1, 16.4.99
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.
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").
Status: mostly done, in testing stage, gathering real-world feedback now
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.
Status: done, in testing stage, gathering real-world feedback now
GUI
---
Main GUI is now completely customziable with the well-known "coolbar"
technology borrowed from the Windows world. Bookmarks are replaced with
the new embedded version of the Contact Manager. New IE4-alike history
allows finding
Status: mostly done
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 ![]()
based
tracking services. The same will probably be added for
cookies.
Status: mostly done
Java
----
The "Merapi" JavaVM seems to have died. Holger Kruse of Nordicglobal
recently
announced the Daytona JavaVM, and has invited all browser authors to
participate
in a design discussion about a potential plugin API for Daytona. If this
project has a future (and given hkr's track record, it surely will), I'm
definitvly going to support it.
Status: time will tell
Flash/Shockwave
---------------
David "Zapek" Gerber is working on integrating the free
flash
3 player as an V plugin.
Status: being worked on. It's either finished in time or someone in
Switzerland will have his buttock prodded :^)
Image decoders
--------------
Updated to current versions of libjpeg and libpng. Speed improvements
in the rendering code, and will now also deal fine with CGFX4
in-buffer bitmaps. Fixed tons of low-memory issues. Modularized
and loaded on demand based on the system architecture for
maximum efficiency with easy upgrading to PPC. Special support for
FBlit on AGA systems to totally eliminate the need to use chipmem.
Status: done, in testing stage
Plugins
-------
Nothing really done yet, but the Flash player is being designed as an
plugin and will stirr up some required changes.
Status: erm
--
Oliver Wagner http://www.vapor.com/
Finger: owagner@vapor.com ICQ: you're kidding :)