As seen on the mailing list (and on HaikuWare) Ryan Leavengood has started a thread to try to see if there are enough motivated developpers to work on the creation of an Haiku native browser.

One year ago, Ryan succeded in porting the WebKit to Haiku (completing HaikuWare’s bounty) but since then nothing has realy been made out of it.  In his efforts he was helped by Andrea Anzani and Stephan Aßmus.

In the mean time tough the WebKit code evolved and the actual code should be ported again (eased by the work previously done).

Discussions were also raised on wether or not port Cairo, Firefox, Chrome, what about the BeZilla Browser, etc.

Nice initiative guys, we definitively need a technologically up-to-date NetPositive like app for our Haiku.

Category: News   -   Comments RSS   -   Post a Comment   -   Trackback  

« »

 

10 Comments

nbrophy on 2009-02-26 at 12:38 (Reply)
I wonder whether porting the ABrowser from the Syllable OS project would be a viable option. The ABowser is based off the Webkit and isn't Syllable OS API similar to BeOS/Haiku.
Ryan Leavengood on 2009-03-05 at 19:37 (Reply)
Actually the Syllable port of WebKit provided a lot of ideas for my Haiku port, and I have certainly taken a look at ABrowse. The code is quite simple and could possibly serve as a base for a Haiku browser, but I think it makes more sense to do a cleanroom browser using some of the best ideas now in the various mainstream browsers.

Plus the Syllable API is different enough to the Haiku/BeOS API to make porting ABrowse more trouble than it is worth.
Stephen B. on 2009-02-28 at 16:00 (Reply)
It also sounds like the Origyn Web Browser might be a decent choice (it uses WebKit and has already been ported to AROS and RiscOS).
DougTheBug on 2009-03-03 at 21:13 (Reply)
No. PLEASE. Just port Firefox and focus on everything else. I have been following the creeping slow development of Haiku for years and am disappointed there still isn't an R1 yet.
Stephen B. on 2009-03-03 at 22:48 (Reply)
The Firefox port has largely stalled in the 2.x series. Not due to any lack of effort on the part of BeZilla devs, but because newer versions have dependencies that either aren't present on Haiku yet, or aren't yet mature on Haiku (Cairo, the DB engine used for storing user data in newer versions, etc).

I also don't think that developing a native browser will have any effect on the speed of Haiku's overall development. No one appears to be suggesting that dev. of a native browser should take priority over more critical parts of Haiku development.
Ryan Leavengood on 2009-03-05 at 19:41 (Reply)
I understand your frustration but as Stephan B says getting a working Firefox is no easy task either, and in my opinion the direction Firefox 3 has taken is not the kind of browser I would want to use on Haiku. Though I would not complain if others made a nice port of it, and I might even help on that one day.

But believe it or not, right now I think the fastest way to get a nice, fast, modern browser on Haiku is to develop a native one using WebKit. It won't be trivial, but it certainly isn't as difficult as the work done to get Haiku to where it is now.

I also think the code will be much more accessible and easier to develop on than Firefox. I intend to make it that way because that is the kind of code I want to work with.
Jacob on 2009-04-28 at 15:01 (Reply)
Hear hear. Good riddance to Firefox. If we can get a Webkit browser, I'd use it any day based upon rendering speed, snapyness, and I'm sure the code base is also so that a lot more Haiku contributions could go in.

- What about Flash however?
Pat on 2009-05-18 at 01:44 (Reply)
What about NetSurf? The BeOS/Haiku binary for version 2.0 was released April 25th. It works great and has a very small memory footprint (6M).
chicas en tanga on 2009-07-19 at 20:29 (Reply)
I should email you about it.

Leave a Reply


Design Copyright © Meghan Davison 2008, Content Copyright © BeOSNews.com . All rights reserved.