Category SoftDev

Software Engineering and Development

Resampling Needed

Those using Firefox 3.0 may have noticed that by default when someone scales the content of a page, the images are resized too, a behaviour long-pioneered by Opera. Those using Firefox 3.0 on linux will be sorry to find out that upscaled images are not resampled using anything but what seems to be nearest neighbour (I haven't checked the code): they are ugly, pixelated and definitely not pleasant to the eye. This is well documented on the Mozilla Bugzilla repository and sadly it may be the case that it's not fixed until Firefox 3.0 final is out. Which is a shame, as many people with higher resolution displays, especially high-resolution laptop displays that sometimes reach approximately 150dpi actually depend on the scaling functionality to be able to read stuff properly. Ironically GTK+ offers pretty decent image scaling functionality and hopefully it's not that hard to make use of it in Firefox in the near future. Here's an illustration of the problem. The picture on the left shows the original (unscaled) content of the ΜΠΛΟΟΓΚΛ hellenic blog search engine. The one in the middle shows the scaled version, as shown in Firefox 3.0 Beta 5 that shipped with Ubuntu 8.04. The one on the right shows a resampled version of the image using the (pretty computationally expensive) lanczos algorithm, which although not probable as a solution it's quite close to the (realistically possible) bilinear resampling for upscaled images of this size. Image Upscaling in Firefox 3.0B5 (Linux) You can follow the progress on this issue on the Mozilla Bug tracking page here.

10 Days to Hardy and GNOME's ugliness.

Following on from my earlier post on the upcoming Ubuntu 8.04 ‘LTS’ release, I fear that my prediction, albeit harsh, was pretty accurate: Ubuntu 8.04 LTS should have never been branded as a Long Term Support (LTS) release. Despite the obvious shortcomings of having β-quality software (Firefox 3.0, GVFS) and new frameworks that — statistically […]

C4[1] Videos

C4[1] Videos, have been available on Viddler for about a month. For Mac Developers this is probably of some interest. [via daringfireball.net]

Today Webkit is on ACID!

The following image says it all really: Webkit ACID3 bugfixes These past few days there's been a flurry of WebKit posts over at Surfin' Safari about its ACID3 performance. I guess when dealing with bugs, and given the fact that Microsoft typically needs around 5 years before simple CSS1 bugs are fixed (as an aside the first and only version of Internet Explorer to date that passes ACID2 is 8 Beta 1, released a couple of weeks ago), I was surprised to see how fast the WebKit developers worked towards passing the ACID3 test. Between 20:22 and 03:51 another three ACID3 bugs were fixed, taking the score to 99/100. I guess by tomorrow WebKit will officially be ACID3 compliant. Woohoo! By comparison, Firefox 3.0 Beta 4 that I'm using to write this post in Ubuntu Hardy Heron Beta1 scores a somewhat respectable 68/100, although I don't think they'll pass ACID3 before the final version is out.

DroidDraw

Android Logo (small)A first attempt at creating a visual UI designer for Android. While not exactly sophisticated compared to more mature visual UI design tools, it greatly simplifies the task for designers (cf. programmers). Worth a look for anyone interested in developing for Android.

Exploring Android: Preliminaries

Android is out and it seems pretty well designed. This is the first of what’s hopefully going to be a series of articles covering Android from cosmix.org. It’s also going to be the least technical in nature as I haven’t had much time to play around with it and also because introductions should rarely be […]

Dalvik: The new name of Sun's worst nightmares.

An excellent article about Java on Android, Sun's licensing trickery, Google's checkmate the slanted meaning of Openness. A must read. Also read this for a retrospective view of the open sourcing of Java one year ago.

FakeStevey got it…wrong.

Check this post by Fake Steve Jobs. It's hilarious and not just because it nails what the real Steve Jobs probably thinks of Openness, but also because it highlights what was always wrong with his approach: whenever his companies were weak (NeXT in the late 80s and early 90s, Apple in the late 90s and early 2000s) he touted Openness, standards and formed alliances with other companies. Take Adobe's Display PostScript in NeXTSTEP, Darwin, Display PDF, OpenGL, OpenAL, CUPS, UNIX certification, gcc and a number of other standards, APIs, libraries and applications between 2001 and today in OS X or his 'agreement' with Microsoft in 1997. But just when things do well, he tries to usurp the dominant position, showing complete disregard to their partners, development community, users and sometimes even employees. In my discussions about Android with friends over the past day I compared Google with Microsoft in the 80s. Many have done the same. This comment by 'chickenface' in the linked article is, I believe, representative of how I see Android evolving and eventually dominating the market:
This is 1984, the iphone is the 128K Mac, and GPhone is the PC. Look, there's no actual consortium; there's Google and its customers. Kinda like Apple and AT&T, but they've got so many customers we're calling it a consortium. When're you gonna get this straight: Microsoft were like the Klingons - we made a sort of peace with them and held our nose. Google, they're way worse -- they're the Borg.

Open Sesam…err iPhone.

A few completely unfounded (arguably bordering on stupid) excuses by salesman Steve. GBs of criticism on the web. A botched attempt at Reality Distortion. Numerous hacks. Dozens of semi-illegal third-party applications. Many bricked iPhones. And, now? Apple's spectacular realisation that the iPhone won't glitter forever. It was about time Apple did things right. The industry is not kidding. This is only the beginning...

The UI Ghosts

A common joke amongst Mac developers is talking about the Apple HIG, or more specifically the subject of how Apple manages to flout every single principle in user interface design and especially its own in successive revisions of OS X. I've written about this, in one way or another, several times ever since Jaguar came out in August 2002 and the first signs of this disturbing trend became obvious. New UI widgets, new styles and disregard to the HIG continued over the years with Panther, Tiger and now Leopard --- each revision bringing its own flavour of user interface widgets, colour themes and designs, each proving that Apple has no idea what 'consistency' means and that contrary to what they may tell you you should write your own custom widgets or you're probably screwed if you don't (Apple probably writes and uses more undocumented and custom widgets and controls than anyone). With Aqua so close to becoming part of UI history and Leopard just around the corner, bringing with it yet another completely different UI theme to OS X, it should probably not be surprising when Apple's own Developer Connection web site sports such an inconsistent look. The UI ghosts of yesteryear are still around!