Multi-processor support has been improvedI managed a whole three Activity Update posts last summer before Real Life (TM) got in the way. Ironically #3 mentioned switching to a two-week update to be more resilient to stuff in the real world! Well, 2 weeks has become 4 months but I'm back on top of all things Haiku and ready to once again attempt to provide a bi-weekly update.
It is stating the obvious to say that a lot has happened in the Haiku world in the last 4 months (my email backlog had grown to over 4000 emails) and so this update will cover less detail than the more regular ones and will mainly focus on the changes that have happened in the Haiku code.
In brief: Huge stability improvements in the kernel and VM, syscall optimisations, OHCI USB work, an AHCI SATA driver, hotplugging support for devices, USB 2.0 handling for legacy devices, work on partitioning support and DriveSetup, and new features in Kernel Debugging Land.
Read on for more...
What to do when you are bored at 1 am, and you see noone sending in new themes ? Make sure you can use more of the existing ones :)
I’ve never used BeTheme myself, but it seemed to have gained some fans. So hoping it would bring newer ideas I added some code to the Theme manager to import those themes. It currently supports background pictures, deskbar position and R5 decor.
Some people might wonder what exactly this “themes” stuff in the commits is all about. So let’s see how it all started, where we are and what’s left to do.
Features The Theme Manager is an addon-based desktop theme selector. It can selectively apply parts of a theme, create a new one based on the current configuration, add a screenshot to it.
Currently, themes contain settings for ui colors, system fonts, background pictures, window decorator, deskbar position, screensaver, Terminal colors, font and size, sounds, and even the selected winamp skin from CL-Amp and SoundPlay through a specific plugin.
As I write this first post, I’m in the process of sending off the initial OpenJDK project page content to Mark Reinhold for public posting. I’m grinning wildly, and I’m having some great flash-back style memories of working on the JDK 1.4 port.
I think now is a good time for a general status report, to communicate where we’re at, where we’re going, how we’ll get there, and how you can get involved.
To be honest, I was a bit desperate in the run up to BeGeistert 018. The fact that most of our core contributors were present gave me high hopes for a good push of Haiku development. Since my laptop was stolen, which was a really solid Haiku machine, I could not run Haiku natively on my main development computer. Even on some older computers I had, I could not run it anymore since the initial changes to the IDE stack. Next was the fact that I bought a new USB based KVM switch. The only USB stack with which I had a working keyboard and mouse was the original Dano stack. And even then I sometimes lost input when switching back to BeOS from another computer. With Haiku, the input devices were not working at all. So I was packing both my computer, monitor and the KVM switch for BeGeistert, all in all, it was quite a load. I was heading towards BeGeistert with a bit of mixed feelings, because Haiku wasn't working so well for me anymore and I didn't know if it was going to be fun only or with some disappointments mixed in.
i’m going to miss those of you at Haiku who are moving on. i’m in a dark time of my life, maybe the end, and i revisit the old good times now and then and BeOS is one of the bright, shining gems, despite the bittersweet facts of how it all went down.
i’m still breathing at the moment. i still run BeOS (GoBe Productive owns all my writing ;-) and i could use tips on getting out of the DNS nightmare i am having with Verizon and BeOS Pro R5.
Webkit rendering bebits.comIt looks like the Haiku Webkit port initiated by Ryan Leavengood has entered a productive second stage of development, and thanks to the recent work by one of the new project team members, Andrea "xeD" Anzani, tangible progress has been made as shown by the recent screenshot showing the HaikuLauncher application rendering bebits.com (shown to the right). I was curious about his work, so I went directly to the source and asked a few questions to Andrea; here are his answers.
Andrea: From the questions you wrote, it looks like you think we have a working browser here. Well, we don't. I'm sorry to tell you but what you see it's just a proof that the webkit is working. Still incomplete and with a lot of bugs. The webkit is, in short words, a framework for loading, parsing and drawing an html page (including net connections and javascript interpreter). We are working on fixing and finishing it. When we are done with porting the webkit, then we can speak about the development of a web browser.
The WebKit Haiku port team has seen some nice progress lately in the form of our first decent rendering. Read more to see it...
Demo machine at KOF Haiku boothNot surprisingly, it took me much longer than originally planned to find the time to write about the second day at the Kansai Open Source Forum conference (KOF). But no worries: memories are still quite fresh, as it's usually the case when things go well and you have fun. The second KOF day started earlier, especially for me. The exhibits were scheduled to open at 10:00AM, so with Momoziro we decided to meet at the hotel lobby at around 9:00AM. But I was up way before that, at around 5:30AM (compliments of my very jet-lagged old body). So I sat in front of my laptop to write some emails and then went through my Haiku presentation slides again, making little changes here and there, changing the order of a few slides and even adding a couple of slides based on some of the questions that I had received during the first day at KOF.
I know I have been very quiet for a while in regards to my Haiku WebKit port, but that is because I’ve been in a long session of coding. I am happy to report that this weekend I finally got WebCore compiling for Haiku:
Link ../../../generated/objects/haiku/x86/release/WebKit/WebCore/libwebcore.so Chmod1 ../../../generated/objects/haiku/x86/release/WebKit/WebCore/libwebcore.so SetType1 ../../../generated/objects/haiku/x86/release/WebKit/WebCore/libwebcore.so MimeSet1 ../../../generated/objects/haiku/x86/release/WebKit/WebCore/libwebcore.so SetVersion1 ../../../generated/objects/haiku/x86/release/WebKit/WebCore/libwebcore.so So what does this mean? Does it mean the port is now complete? Unfortunately, no it doesn’t.
