- Tue, 2009-07-07 - Sat, 2009-07-11
- Wed, 2009-07-22 - Thu, 2009-07-23
- Sat, 2009-10-17 - Sun, 2009-10-18
Our first decent WebKit rendering!
Submitted by Ryan Leavengood on Tue, 2007-12-18 17:04. Tags: development :: porting :: WebKit
The WebKit Haiku port team has seen some nice progress lately in the form of our first decent rendering. Read more to see it...
I cannot take all the credit for this as the latest push to fix some bugs and implement font loading and text rendering has been courtesy of Andrea Anzani. In fact he created the above screenshot.
Now a few caveats about the above:
- BeBits is being loaded from disk, not the network. We still need to work out the bugs in the Haiku GCC4 port of CURL.
- Scrolling is disabled at the moment because we still have some work to do there. You can kind of see blank spots at the bottom and sides where scroll bars would render.
- There are obviously some rendering bugs here and there.
- The HaikuLauncher is still very basic without any chrome (back and forward buttons, URL bar, status bar, etc.)
But overall, not too bad! It makes me feel pretty good to see all my hard work finally producing a decent result, and I'm glad I have help now because it results in screenshots like the above.
As usual I will try to keep everyone updated as the port continues to progress.
leavengood's blog :: Login or register to post comments :: Email this page :: Printer-friendly version
I'm astounded. I had no idea it was actually so far developed! Major congratulations! :) Please please keep up the good work!
Good work WebKit team!
Excellent news!
Wow, looks awesome guys - keep it up. It's going to be so great having a native Haiku browser with native look and feel that's capable of dealing with all the crazy content that's out there these days. It was always the one point that really let me down when I tried using the BeOS as a day to day OS.
That and I could never get # to work correctly with the GB keymap... made C coding tricky to say the least!
Fantastic. Good to see that we soon have a browser from a project that actually are interested in smaller OS'es. At some point I'll have to look into WebKit.
Andrea Anzani ROXX!!!! :D thx thx thx for your work!
That's pretty cool!
Congratulations to all those involved...
BTW, it seems to me that the current owner of webpositive.org has been contacted?
(or so Babelfish combined with a very superficial understanding of the Italian language tells me)
Source: haiku-os.it
I'm glad you're finally rewarded for all your months of hard work on this, and it must be nice to have some help too. Sometimes it helps to have someone with a fresh look on things.
Anyway, keep up the good work, we're all eagerly awaiting the first version that can use the network and that has a url bar. What else could we possibly need? :) (well, maybe bookmarks then, and a back and forward buttons...) (and flash, and ...)
yes, I've been contacted, even though I didn't yet had a chance to contribute really, due to a missing gcc4 setup. but xmas holidays are arriving shortly, which gives a big relief from day job activities and some more time to fiddle around ...
cheers,
rossi
That's great, rossi...I assumed you were an outsider who had to be talked into handing over this domain :D but the situation is much better than that!
Yay, this is looking terrific! I'm really thrilled that we're looking at the beginnings of a proper native Haiku browser. It's really exciting.
A million congrats to all involved.
So, I've been thinking (and lurking) about this a bit. It seems Google has been good to Haiku as an organization (tech talks, summer of code, etc), and they have their Chrome browser project. When I read the benefits of and reasoning behind design decisions they made, it sounds a lot like the BeOS (and now Haiku) way of doing things. Multi-threaded, open-source, efficient resource use, etc. Once WebKit is fully functional, would it be (possible or) worth considering compiling Chrome for Haiku as a default browser? By the time we're ready for it, they should have most of their bugs and security flaws fixed. Added bonus, if it takes hold as a mainstream browser on other platforms, it makes a transition to Haiku that much easier for curious users.
It just seems to me that if Google is going to go through all the trouble of designing an open-source browser from scratch that seems to have many of the same goals as a browser we would write, it might be worth exploring as a possibility.
What do other people think?
It just seems to me that if Google is going to go through all the trouble of designing an open-source browser from scratch that seems to have many of the same goals as a browser we would write, it might be worth exploring as a possibility.
What do other people think?
Oh don't worry, once I heard about Chrome and tried it out, I also felt it would be a great browser for Haiku. The only problem is that even though it uses WebKit, there is still a lot of additional code that would need to be ported and written for Chrome to run on Haiku. In fact there is still a lot of work that needs to be done for Chrome to work on Mac OS and Linux. The current code base is very Windows-specific in places, and while I think there is certainly some work that could be done now for it to run on Haiku, it also does not hurt to wait a bit for more multi-platform Chrome code to be created. This is very similar to what happened with WebKit.
Of course I am also quite busy with my normal work and other "real life" issues, so I have not had time to work on the Haiku WebKit port for a while. Since the rest of the Haiku development community is also quite busy, not much has happened there for a while. But I still want to have a nice Haiku WebKit browser, so I don't plan on completely abandoning the project. But it may be a while before I can put a lot of time into it.