They've been working on this project for about a month now, and so far, they've got a prototype of a multi-process browser, modelled after Google Chrome. Because Leavengood had already done work on WebKit, they had a good starting point. From what I understand, they currently employ a very, very basic rendering engine that displays a bitmap - this rendering engine will be replaced by WebKit once that port is completed.
They're currently working on or have completed the following aspects:
- diverse forwarding from main process to render process (mouse move, mouse click...)
- a bookmarking library
- a toolbar
- support for multiple rendering processes
- tab management
Chrome is quite clearly the source of inspiration for this browser, and that's a good thing, as Chrome's multi-process design really fits well into the BeOS world. Tab management will be modelled after Chrome's, according to Leavengood. The following things are currently on the to-do list:
- make WebKit work ( some essential functions specific to the platform have to be implemented ),
- integrate it into the browser,
- port the Chromium networking code (this could be an article on this blog),
- improve the back and forward buttons,
- create an omnibox-like url field,
- and other mysterious things...