MeeGo issues first update to Netbook OS

For those early adopters among us who have installed the first release of MeeGo on their netbooks – which includes me – today is an exciting day (depending on how excited you get about incrimental software updates, I suppose).  Today MeeGo launch the first update to their Core Software Platform & Netbook User Experience – according to the installer I’m staring at this update is Core Version 1.0.1.2, or thereabouts.

MeeGo claim they’ve squashed over 100 bugs with this software update, improves performance across the board (USB device connection time is down from 5 seconds to 1 second), added visual improvements, and an “Enhanced netbook window manager”.

First the good stuff – I noticed upon booting the new version was they’ve replaced the horrible janky Chrome icon they used before, which is great news because it really bugged me.  The boot time seems improved and there’s a noticeable snappiness to proceedings.  Not much has been added functionality-wise, it’s still missing the all-important Facebook sync in the web accounts section and it still doesn’t have a reset button that I can find, but it’s getting there.  The MyZones ta remains a great piece of design – there’s no need for a desktop if you use a netbook like I do (i.e. mostly in the cloud), so having a recent usage / social media aggregator is exactly what I want.

Next the bad – after I rebooted post-update there was a whole lot of crashing going on – I had it running for a almost an hour and had multiple crash messages, so many in fact that it crashed the crash reporting software!  I rebooted for a second time and this seems to have fixed most of the problems, but it was nonetheless disconcerting to have this happen straight after an update.

MeeGo is developing nicely and certainly with great speed – remember it was only a month and a half ago this software was launched.  My main complaint at this point is that it still doesn’t feel like a version 1.0 – it very much feels like a beta.  A few aspects of the OS, such as the gadgets panel, are incomplete almost to the point of obsolescence, while some others, like the MyZones panel, give us exciting glimpses of what this OS could become.

Source – MeeGo Blog

P.S. Remember MeeGo fans – the handset version launched last week too!

Jolicloud Applications: Taking a Closer Look at the Apps

How Painting works in Chrome with Brett Wilson

Because of Chromium’s multi-process architecture, painting within Chromium is far from typical. In this talk, Brett Wilson starts from Skia and the WebKit render tree, follows the bits across the process boundaries, and continues all the way to your screen. He also details many of the differences in painting between platforms, how things work in test shell, and interesting corner cases like resizing.

Via Chromium Blog

Learn about Chromium Layout Tests with Pam Greene

Layout Tests are the tests we inherit from the WebKit project and are a very important part of the Chromium’s testing infrastructure. Pam Greene talks about what they are, how to run them, how to debug problems within them, and even touches on how to write your own. She also covers advanced (but easy to use) tools for rebaselining and tracking flakyness. Any Chromium developer that works on WebKit really should check this out!

Via Chromium

Chrome’s WebKit Guts with Eric Seidel

A large percentage of Chromium’s code (and part of what makes it so fast) is WebKit. In this talk, Eric Seidel gives us a 30,000 foot view of how WebKit actually renders a page. He starts with how resources are loaded, explains how they’re parsed into a DOM tree, and then talks about the various trees involved in rendering. In addition, he touches on many other important topics like hit testing (figuring out what you’re hovering over and clicking on). This is a must-see for anyone working on the guts of WebKit.

Via Chromium Blog

Next Page »