I have been documenting my progress on porting the WebKit project to Haiku on the Haikuware site, but decided to also post information here. You may want to read my previous blog article about this port and also the information at the WebKit bounty on Haikuware. Please consider donating to a bounty.
Before I started work on this port I asked in the #webkit IRC channel what the mimimum version of GCC that was required to compile WebKit. The general consensus was 4.0. So what does that mean?
Whenever I was with Axel and saw Haiku running on his IBM ThinkPad T40p, I was almost convinced, that he must have forgotten to commit a rather effective patch, though he swore that that was not the case. I have never seen the app_server perform so well on any other machine.
My backpack turned out really heavy, because at the moment, I have no mobile computer. Luckily I have one of those "industry embedded" machines, as big as an external CD-ROM drive. But I still had to pack my 17" flat screen. The travelling by train was nice, although I almost got off at the wrong station in Basel. I mean, I did get off, but I got back in in time.
Haiku Admin Meeting 2007-07-23: A quick GSoC status was discussed. It was agreed that having Axel and Ingo working together in the same location to focus on many of the VM and stability issues was a successful endeavor: It was proposed that this be done more often, with possible sponsorship from Haiku, Inc. to pay for costs whenever possible. It was agreed that Axel and/or Ingo will be reimbursed for any expenses that were incurred.
Haiku Admin Meeting 2007-07-02: Discussion about WalterCon planning. Things are moving along. The existence of a project called RadiantOS which claims to eventaully be a “distro” based on Haiku was mentioned. There was some discussion about the status of running GCC in Haiku: Haiku might be close to self-hosting capability (able to build itself). It was mentioned that once Haiku can self-host it’s probably time for an official alpha release.
Even though I had some private issues this week, all is going well with the PackageInstall. In its current form it is able to properly install all 3 test BeOS packages I tried on it, creating files and directories along with their data and attributes without flaw. So, what’s left to do right now?
For the API Documentation team I’ve prepared an overview of the messaging functions in the Application Kit, mind map style. This image should be the guide to writing the actual API documentation.
Please redirect comments on the technical content to the haiku-development list. They are highly appreciated!
A couple of articles I just read (here and its rebuttal) are written by Linux users about why Linux is the best and how to get a regular person (hereafter referred to as Joe User) to start using Linux. To save you the time of reading the two articles, the first is entitled “Understanding the Common User: Everything should be as simple as it is, “ by Keyto. The article is partly about how a Common User thinks, but primarily that quite a lot of the problem with Linux is the current users – geeks who have trouble relating to Joe at Joe’s level of expertise instead of the geek’s level.
Haiku Admin Meeting 2007-06-18: Discussion about some “missing” articles on the new website - specifically old newsletters. Also desired is a way to make them easier to locate. Mention of the continual “browser for Haiku” topic that pops up in the mailing list and elsewhere. An official decision should be discussed and published. It may be still too early to fully decide on a direction. More discussion took place about a potential physical “admin gathering” in the near future.
Haiku’s network stack follows a top-down approach with clear boundaries, pure object oriented design. However, TCP/IP protocol stack was designed more than 30 years ago with different idea in mind. It’s mostly speed, fast processing and stability that designers were looking for back then. That’s why many boundaries in the TCP/IP protocol suite design are blurred somehow.
Basic hierarchy is established. Datalink layer protocol (Ethernet, PPP, etc.) is followed by a Network layer protocol (IP), which is followed by a Transport layer protocol (TCP, UDP, SCTP, etc).