An anonymous reader writes "Chrome is open source, and there's clearly still some work to be done on it. In this article, Neil McAllister decided to take a peek under Chrome's hood and view it through the eyes of the developers who will improve and maintain it in the coming years. It seems Google's open source browser currently has much to offer prospective hackers — provided they use Windows. Quoting: 'The Chromium site explains how to download the source code for Linux, Mac OS X, or Windows. Unfortunately, if you're eagerly awaiting a Mac version of Chrome, you shouldn't hold your breath. As the Mac OS X area of the Chromium developer site explains, "Right now, the Mac build is a work in progress that is much closer to the start than the finish." In fact, according to the latest status report, the Chrome developers have yet to get even the browser core running under Mac OS X. Rendering actual Web pages is still a long way off, to say nothing of a usable Aqua GUI. Then again, the Linux version is in arguably even worse shape.'"

jcatcw writes "Steven J. Vaughan-Nichols reports that Mark Shuttleworth, CEO of Canonical, is using his millions to improve the Linux user experience, hiring people to work on X, OpenGL, Gtk, Qt, GNOME and KDE. He had doubted that desktop Linux could ever equal the smooth, graceful integration of the Mac OS. Now, between the driving pace of open-source development, and Shuttleworth's millions, it might be happening. Why not? After all, Mac OS itself is based on FreeBSD. Desktop Linux's future is starting to look brighter."

dotne writes "Microsoft has submitted Embedded OpenType (EOT) to W3C and a slimy campaign for EOT has been launched. EOT is a DRM layer on top of normal TrueType/Opentype files; EOT ties a font file to a certain web page or site and prevents reuse by other pages/sites. Microsoft's IE has supported EOT for years, but it has largely been ignored due to the clumsiness of having to regenerate font files when a page changes. Now that other browsers are moving to support normal TrueType and OpenType on the web (Safari, Opera, Mozilla, Prince), W3C is faced with a question: should they bless Microsoft's EOT for use on the web? Or, should they encourage normal font files on the web and help break Microsoft's forgotten monopoly?"

Martin writes "Mozilla Labs have released a prototype version of the Firefox add-on Ubiquity. It is basically Launchy (the application launcher) for Firefox with the difference that Ubiquity makes use of web APIs and the Firefox browser. The official website contains examples, a command list, information about creating your own commands and of course the Ubiquity extension that is compatible with Firefox 3.x. Ubiquity can pull and send data to various services like Twitter, display, find and embed Google Maps, perform searches, write emails, add entries to the calendar, digg stories and more."

Wills writes "Apple has been running an iPhone ad saying 'all parts of the internet are on the iPhone', but it had to be withdrawn after Britain's Advertising Standards Authority ruled that it gave 'a misleading impression of the internet capabilities of the iPhone' because the iPhone cannot access Flash or Java – features that are essential to some websites. This raises an interesting issue of where do you draw the line between essential and non-essential features of websites. What should the web look like? Should government authorities be the ones making that decision?"

An anonymous reader writes "In a prediction of the open-source future, InfoWeek speculates on What Linux Will Look Like In 2012. The most outlandish scenario foresees Linux forsaking its free usage model to embrace more paid distros where you get free Linux along with (much-needed) licenses to use patent-restricted codecs. Also predicted is an advance for the desktop based on — surprise — good acceptance for KDE 4. Finally, Linux is seen as making its biggest imprint not on the PC, but on mobile devices, eventually powering 40 million smartphones and netbooks. Do you agree? And what do you see for Linux in 4 years?"

flosofl writes "Matthew Paul Thomas has an entry on his blog called Why Free Software Has Poor Usability, And How To Improve It. While this advice is helpful and may indeed lead to improvements in many open source programs, the guidelines may be much more difficult for smaller projects. From the entry, 'Free Software has a long and healthy tradition of "show me the code." But when someone points out a usability issue, this tradition turns into "patches welcome," which is unhelpful since most designers aren't programmers. And it's not obvious how else usability specialists should help out.'" Thomas has been developing the ideas in this essay for years. The critique is comprehensive, listing 15 challenges in the way software projects, and in particular free software projects, are structured, with suggestions for improving each one.

Comatose51 writes "Does the Slashdot crowd know of any software, tools, or even techniques for reviewing the UI of an application? Right now at our company this is a long and arduous task of looking at slide after slide of pages and menus from our UI, and taking notes and arguing over what should go where or how the UI elements should behave and interact with the user. It takes many, many hours to do this and with all our UI developers involved, it adds up. This has to be a common and recurring problem so there must be a better way to do this. If there is open source software to help, great, but any helpful suggestion would be appreciated."

StoneLion writes "After months of development and controversy, the KDE project announced the release of KDE 4.1 today. Linux.com (a Slashdot sister site) took a hands-on look at the new code, and reviewer Jeremy LaCroix says, 'KDE 4.1 simply rocks.'" Bruce Byfield's review is quite positive, as well.

andrewmin writes "Recently, Gnome's been gaining a lot of ground on its KDE counterpart in the desktop environment wars. The KDE developers were hoping to change this with KDE 4, the new radical release of KDE, but it was not to be. KDE 4.0 was buggy and unstable, leaving everyone except the hard-core KDE lovers. Mainly, this was because it just didn't work most of the time. However, the developers were not without hope. They promised that KDE 4.1 would be more stable and fix all the holes and problems with KDE 4.0. That time is coming soon: in just four days, K Desktop Environment 4.1 will be released to the Linux masses." A release candidate for 4.1 came out just over a week ago, with binaries available "for some Linux distributions, and Mac OS X and Windows."

slatterz writes "The computer mouse is set to die out in the next five years and will be usurped by touch screens and facial recognition, analysts believe. Steven Prentice, vice president and Gartner Fellow, told the BBC that devices such as Nintendo's MotionPlus for the Wii and Apple's iPhone point the way to the future, offering greater accuracy in motion detection."

Jiilik Oiolosse writes "PJ at Groklaw speaks with a member of the KDE team about some of the common myths circulating about KDE 4. 'There has been a bit of a dustup about KDE 4.0. A lot of opinions have been expressed, but I thought you might like to hear from KDE. So I wrote to them and asked if they'd be willing to explain their choices and answer the main complaints. They graciously agreed.' Among the topics discussed are: 'Releasing KDE 4.0 was a mistake,' 'I cannot put files on my desktop,' and 'KDE should just have ported KDE 3.5 to Qt 4 and not add all that other experimental stuff right away.'"

benuski writes "Today at GUADEC, the Gnome User and Developer European Conference, the gtk+ team announced their plans for gtk+ 3.0; immediately after, the Gnome release team announced their plans for Gnome 2.30 to be changed into Gnome 3.0. This would mean a release date a year and a half to a year in the future. Details are short at the moment, but the Gnome team seems to be following in KDE's footsteps, but hopefully will avoid the problems that plagued KDE 4.0's release."

jammag writes "Linux pundit Bruce Byfield takes a look at the latest KDE beta and finds it wanting: 'Very likely, KDE users will have to wait for another release or two beyond 4.1 before the new version of KDE matches the features of earlier ones, especially in customization.' He notes that the second beta is still prone to unexplained crashes, and goes so far as to say, 'Everyone agrees now that KDE 4.0 was a mistake.' I'm not too sure about that — really, 'everyone?'"

hweimer writes "Most problems when opening Word documents under GNU/Linux are due to missing fonts. Therefore, Red Hat published a set of fonts metric-compatible with the Windows core fonts last year. However, there were some concerns regarding the licensing that prevented many other distros to ship them. We finally managed to settle these problems, leading to better document interoperability for all GNU/Linux users."

jsuda writes "At least a half-dozen times in the book 'Foundations of Mac OS X Leopard Security' the authors state that there is a misconception that the Macintosh computer is immune from security problems. That allegation may explain why there are very few books published (and nearly none in recent years) about security for the Mac. This book is meant to change all that. The authors acknowledge that the Mac OS X software has had little of the security problem experience of Windows (and other operating systems, to a lesser extent) but they spend 455 pages detailing exactly where and how the Macintosh platform is (or may be) vulnerable." Read below for the rest of Jsuda's review.

stoolpigeon writes "I remember the first time I saw a program I had written after the interface had been revamped by a designer. I had been pretty happy with what I had made. It worked very well and met the client's requirements. It was extremely functional and I thought it didn't look bad either. But when I saw the new interface, not functionally different, just so much better looking, I was really blown away. My application had gone from useful to cool. (That might be a slight exaggeration, it was still just a database app but it sure looked cool to me.) Since then I've learned to primarily leave the user interface work to the experts in that arena, and I stick to the getting the functionality in place. But sometimes I don't have the luxury of a design team at my disposal. Or when I do, I still need to be able to talk to them and discuss what is going on. I found Dr. Ji Young Park's new book "Visual Communication in Design" to be a friendly and accessible introductory primer in visual design." Read below for the rest of JR's review.

Johannes Eva writes "As IBM Lotus Symphony shows its first public version 1.0, the Chinese OpenOffice.org derivative RedOffice offers the first beta of its new version 4.0. The open source RedOffice gets a new UI inspired from Microsoft Office 2007, with a vertical 'ribbon.' Is this the future of OpenOffice.org?"

appelza contributed a link to Tuesday's announcement of the next step toward KDE 4.1: "The KDE Project is proud to announce the first beta release of KDE 4.1. Beta 1 is aimed at testers, community members and enthusiasts in order to identify bugs and regressions, so that 4.1 can fully replace KDE 3 for end users. KDE 4.1 beta 1 is available as binary packages for a wide range of platforms, and as source packages. KDE 4.1 is due for final release in July 2008." I haven't used KDE much for the past few years, but the screenshots of a "grown-up" plasma are enough to make me correct that.

nimble99 writes "I am a computer software engineer, focused mainly on the Windows platform — but most of my development time is spent in .NET. I would like to move my .NET development to Linux in the form of Mono, in an attempt at building a media-center type of device. All I require, is a base operating system with simple hardware support, Mono, and a window manager that (preferably) does nothing but act as a host for mono applications. Is this available? I dont know a lot about Linux, so I thought I would ask if there is already something like this available. Obviously a 'Mono Operating System' would be the cleanest solution, but a similar thing could be achieved with the barest minimum of Linux distros right?"