Webkit

Articles like this one and initiatives like “pre-fix the Web”, aim to highlight to web-developers how important is to build a cross-browser web. The importance of such a point has been explained in so many places, there is no point in me saying anymore. People like Tim Huegdon can give you a far better lesson on this. But if you are after a “one sentence to blame them all”: If you write a website caring only to test it on WebKit based browser (worse, only your iPhone!!!), you are a MORON. ...

This article was originally written on another blog. That blog was never officially published, and it will probably never be. It was written on the 3rd of June 2010, but is still “somewhat important” and relevant. Since the post was published, Richard Moore <rich @linux…fpb.site> has done a commit in the Qt examples directory that resamples very closely my code below. So, I decided to repost it here. Qt and Proxy Configuration What’s great of Qt, is that it comes with a very rich set of libraries to cover almost everything you can think of. As a Qt developer, you should always double check the Documentation first, to see if “it’s already there”, before jumping into coding. It saves tons of time. ...

I don’t have an answer to this, it’s too early (we don’t even have a screenshot of it). But I strongly suggest to take a look a the Google Chrome Comic Book: a very new, fresh, funny and precise (!!!) way to introduce an incoming software. They discuss a lot of different topics: * Problems they wanted to solve * Performance * Process Isolation * Javascript VM and Performance * Sandboxing * Phishing and Malware * UI principles Very interesting. And, again, very innovative. Ah, the Rendering Engine they chosen is… WebKit (what a surprise!!! ;-) ) and… it’s fully open source. An early leaked screenshot follows. ...