Slashdot is powered by your submissions, so send in your scoop


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 internet speed test! ×
User Journal

Journal Journal: GNOME Usability Ideas

GNOME Usability (a list which I'm a very occaisional contributor to) has been particularly active with all sorts of Topaz-talk. Topaz (which for you unknowing/uncaring is GNOME Three-Point-Zero) is years off, but it's nice to be able to have some input at the very early stages & maybe get some decent features in there.

The current state of GNOME, after the 2.10 launch in March, is that we have a nice development environment, still rough around the edges, which is reasonably usable. For the userish types HAL has been improved & major-suite integration has been applied liberally. Evolution now integrates with the desktop clock/calendar, which is fantastic.

For GNOME 2.12 we look forward to the new power-management features which should be coming out of Project Utopia. Hibernating a Linux desktop through GNOME is pretty high up there on my wish-list. With any sort of luck whatsoever, we'll have Cairo (so fancy graphics which should ooze Clearlooks-themed style) & can start integrating apps like Tomboy (a wiki-ish note taking system, which I thought was pretty innovative), F-Spot & Beagle. These apps all use Mono, so don't stand much chance of getting integrated in 2.12, but they desperately SHOULD be.

So while Usability has been abuzz with talk of moving to a 'user-interesting-object model', stuffing drag'n'drop into every nook & cranny, automatic versioning & even migrating to an OSX-like global menubar, it seems to me that we should reach some kind of consensus as to which programming languages should be properly supported by the GNOME project. If Mono just isn't right politically, then can't we implement a GNOME framework to build apps within? Using VFS, GConf & even GTK automatically when you begin developing HAS to be good for the project, right?

I'm not saying copy .NET to the last or just develop Mono up to this. I'm saying 'implement a cross-platform API-set with all of the current GNOME features wrapped in a nice hierarchy with one point of access (in Python, 'import gnome'?).

Slashdot Top Deals

The only perfect science is hind-sight.