Hello everyone.
Well, just got confirmation from Haiku, Inc. that I can continue working on this during May. Thanks to everyone who donated money to Haiku, Inc. for making this possible!
As mentioned last week, I’m working on fixing the flickering and missing rendering on some pages. I didn’t get very good results yet, but I can at least give you an overview of the different ways WebKit can render things on screen.
Hey everyone!
Here’s an update on what’s happened so far.
TL;DR - PulkoMandy managed to build the bootstrap image and kallisti5 has made some progress in running the image on the qemu. This is a significant progress since bootstrap image build never succeeded but not quite usable on BBB. I’ve not made much significant contribution. Instructions for building the bootstrap image are at the end. Otherwise, read on.
Hello everyone,
Not so much exciting things this week…
Well, good news first, on wednesday I uploaded HaikuWebkit 1.3.1 packages. It should be more stable than the previous releases, and includes work from the last 3 weeks including some more bugfixes for audio/video support, working web socket support, and many smaller fixes.
I have chosen to take up Bruno Albuquerque's suggestion of porting the reference compiler and runtime of the Go programming language to Haiku.
Me, myself and I
Hello everyone, my name is Louis Feuvrier, I am a french student located in
Paris (GMT+2) studying computer science at EPITA. I am lucky enough to be part
of a laboratory (LSE) as my curriculum which allows me to work on interesting
and low-level problems! Here's the one that will keep me awake at night in the
following months (but hopefully not too much!)
Besides computer stuff, I enjoy listening to music, playing video games,
watching tv shows or going to gigs.
Hello Everyone!
Google Summer of Code 2014 is now underway, and I am one of the four students selected to work with Haiku. My project is completing the LibUSB Port to Haiku.
Hello world!
Work continues on the testsuite: I found one bug in the testsuite system that greatly improved the results. Things are now properly reset between each test, which avoids many of the issues I was having. The last test run breaks down as follows:
- 2 unexpected crashes
- 2300 unexected failures
- 400 unexpected successes
- 5000 tests have no reference
- And the remaining 30000 or so tests are now properly tagged
I will continue marking the failing tests as expected to fail, and review them in case I find one that’s easy to fix. The 5000 “no references” tests are easily fixed, we just need to generate a reference rendering of the page. This is because these tests have platform-specific results, so there is no common reference for all platforms, and we need a haiku-specific one.
Hello everyone!
Most of you know that 4 students have been chosen to work with Haiku during the Google Summer of Code(GSoC) 2014. My name is Arvind and I am one of the 4 students(yaay!). I will be improving the ARM port and hopefully make significant progress.
Hello everyone,
Slow progress on the code this week…
I fixed two small issues in the video decoding code: a useless notification was sent, leading to very high cpu usage on jamendo.com (and possibly other places). And, the video drawing was not always using B_OP_COPY. This led to CPU waste as the mode used could be slower (B_OP_OVER has to scan each pixel to see if it is transparent), and created some drawing glitches on some videos.
Hello world!
Progress on WebKit this week happens in various areas.
On the testsuite first: I fixed several small issues that triggered asserts when WebKit was built with asserts enabled. This includes a problem with the sequencing of events when loading an invalid URL, and a double deletion of an object when iframes are involved. These two problems could have created some real-world issues, so WebKit should be a little bit more stable now. Another problem was the lack of “key up” events and mixup of keycodes vs characters in the testsuite keyboard simulator, which prevented us to test the editing code in an useful way. Another problem was some browser settings were modified by some tests (such as the text size, and page zoom factor), and not reset before running the following tests. This led to some unexpected errors which are now avoided. With these issues fixed, I can have a look at the remaining failing tests, knowing that they are more likely to uncover actual bugs.
