WebKit2 have plugin support AFAIK, and it is plenty times explained: porting another WebBrowser is not a small task, and doesn’t magically solves all your problems. Don’t take the web features granted just because the broser supports it on other platforms, the integration is a really long road.
The phases of porting a webbrowser would look like this:
- Some weeks to become acquainted with the build system (1 week, 1 month, possibly even more)
- Recognize, that you have to port/re-port/update libraries, build-systems, even programming laguanges (hi ruby!)
- Get the build system compile the first source file, meet with platform differences deep in the code. Start to fix it.
- Stub out all the gui and other complicated platform dependant code.
- Get the browser built in headless mode (2-3 months, probably more)
- Write platform-specific gui code (months), probably you have to change/add stuff to Haiku too (app_server, etc)
- write/adjust the testcases
Now you have a working demo, which can brokenly render pages and it’s crashing only if you move your mouse.
- Stabilisation. Years. Do not forget about the users, who will tell: it isn’t working, and you should port their favorite browser instead this crap.
- After that you can try to start to enable the features like audio/video support, which also needs platform specific code.
- In the maintime upstream diverges from your startpoint every day with great speed, you have to rebase your changes on top of mainline frequently, you have to try to upstream your changes (if they even accept patches for Haiku).
Then, some years later it will be in the same state like WebPositive is today. It is mostly work ok, but crashing or locks up sometimes, while you are bombarded with feature requests (NetFlix working with this browser on Windows, so you only need to add -DDONT_DISABLE_NETFLIX, right?! It should be easy! And btw, you should’nt port this, but my favorite Browser, when will you do that too?)
Instead painfully go trough this, why don’t you guys trying to help to fix WebPositive? I think we want to have a working browser, not 5 differently broken or differently incomplete.
But that’s my 2 cents, feel free to start to work on any browser, we need diversity on WebBrowser front, but calculate with the listed things.