Today, the GNOME team has released GNOME 2.28. It builds on the solid foundation laid out by all the previous releases, and adds in a number of new features and improvements, on top of all the bug fixes and performance improvements, of course.
The single biggest improvement in GNOME 2.28 is probably the inclusion of the GNOME BlueTooth module, which should finally make managing all your Bluetooth-capable devices a whole lot easier on the GNOME desktop. “GNOME Bluetooth supports hundreds of Bluetooth devices, including mice, keyboards and headsets. GNOME Bluetooth includes PulseAudio integration for Bluetooth headsets and headphones,” the release notes elaborate, “GNOME Bluetooth also includes support for Internet access through your mobile phone. After pairing your mobile phone with GNOME Bluetooth, NetworkManager will include an entry to use your mobile phone for Internet access.”
Empathy, GNOME’s instant messaging framework, has also seen lots of love. Managing your contact list should now be easier thanks to proper drag/drop organising and a view menu with quick sorting options. The messaging window now supports AdiumX styles too. Support for GNOME’s remote desktop viewer, Vino, has been integrated into Empathy, so you can share your desktop with your Empathy contacts.
Another big thing is that Epiphany, the GNOME browser, has ditched the Gecko rendering engine in favour of WebKit. The change should be transparent to users, but it will solve a number of long-standing Epiphany bugs.
Other changes include no more icons on buttons and menus, Evince supports PDF annotation, Cheese has seen UI love, and Terminal will use less memory – among other things, of course.
The new release will find its way to a distribution near you soon enough.
Congrats to Gnome on the release.
Something’s up with the fonts on the first screenshot that makes it look pretty awful. Either it’s been resized or the hinting is broken.. Not sure but it doesn’t make a good first impression.
The tech behind empathy (telepathy) is coming along nicely. It’s very quickly becoming the way to create connectivity applications, and we’re looking at using it at work for some projects. Very cool stuff.
One bug users may experience in Epiphany, due to the change to WebKit, is not being able to save logins and passwords in forms. This bug will be fixed during the 2.30 development cycle.
Yikes. That’s a pretty significant regression. Why was this not a showstopper for the release? I’m sure users could have dealt with gecko for another 6 months. Not being able to save passwords would make me ditch a browser for sure.
Otherwise some nice tweaks. Special kudos for the accessibility work, this is an area that is sorely lacking in most other open source projects.
Clearly the image has been resized.
Some would argue that Epiphany bugs shouldn’t prevent a full Gnome release when everyone on Linux is using Firefox anyway.
I don’t think he meant prevent the gnome release but prevent the switch over to webkit and just release gnome with the old browser.
Not everyone uses Firefox on Linux. I don’t use it exclusively, on any OS.
Where are the numbers that prove that 100% of desktop Linux users run Firefox exclusively?
Now if you had said Ubuntu users, that may be a different animal altogether (no offense meant towards Ubuntu).
It was not meant literally. I don’t even use firefox myself. The point is that users who won’t tolerate breakage will use ff, while other browsers can have some flaws.
gnome-shell is also part of this release. it is merely optional for the time being.
I think one of the biggest things that got me excited is this:
GNOME is now hooked into the fast developing rendering and javascript support – as much as some here love Ghecko, I for one am happy to see it go. In the future it’ll mean that new technologies will make their way quicker into Webkit (especially when it comes to acid test results) and better support for Google services.
Hopefully they’ll speed up the removing of deprecated parts so that the installation of GNOME becomes smaller and less parts reliant on rickety components.
Edited 2009-09-24 02:12 UTC
The improvements seem nice but scarce so isn’t this more a bug fix release instead of a new version?
I like how the GNOME improvement process performs.
Focused, and nice, but noticeable. Without wasting energy on meaningless changes, and without willing to break up all on each release, but replacing/improving internal key components whenever it is convenient and possible.
However, despite of all the pleasant experience with 2.16 – 2.28 release history, I’m kind of stressed thinking that 3.0 will be sort of a hell of new-everything where I won’t know how to use almost anything. Vista and KDE 4.0 are traumatic instances. Hopefully GNOME will not commit the same mistake.
Edited 2009-09-24 09:15 UTC
I doubt it. Most of the applications’ user interface will remain the same. The major change will lie in the window manager, and you could still use the old one, so no problem there.
Glad to hear that!
OOOOPPPS! No they don’t. On every screenshot in the release notes there is an icon in every pushbutton. Not a single button without an icon.
Edited 2009-09-24 10:33 UTC
Or, you read the release notes:
So they remove icons and …
http://library.gnome.org/misc/release-notes/2.28/figures/gnome-2.28…
Checkout the *size* of epiphany’s icons.
must be like 8x bigger than firefox’s.
yes ok, they’re probably optional, but most people agreed that icons were a good thing, just needed to be smaller in some cases, or better placed.
I’d also add:
“One bug users may experience in Epiphany, due to the change to WebKit, is not being able to save logins and passwords in forms. ”
Switching backend and lose such key functionality sounds rather stupid to me. Of course, everyone uses Firefox so they don’t care. But that’s one of the reasons I suppose.
“Due to improvements in VTE, GNOME Terminal users will notice much less memory is used.”
That one is nice.
So GNOME team are in fact switching to KDE’s HTML rendering engine, KHTML. Grats guys.
So GNOME team are in fact switching to KDE’s HTML rendering engine, KHTML. Grats guys.
Webkit and KHTML are two different projects.
It is actually more like Webkit is a derivative of KHTML.
It is actually more like Webkit is a derivative of KHTML.
Yes, Webkit was started with using KHTML as the base, but as far as I know they are very different beasts nowadays and don’t really have anything in common anymore. As such they are two very different projects now.
They always were different projects … but that is not the meaning of “derivative”.
http://en.wikipedia.org/wiki/Derived_work
A derivative work pertaining to copyright law, is an expressive creation that includes major, copyright-protected elements of an original, previously created first work.
As long as webkit still includes some KHTML code, which it does, then it will be a derivative work of KHTML.
Edited 2009-09-24 13:05 UTC
Well, in that case KDE badly needs to switch to a derivative work of KHTML too. More so than Gnome does, in fact.
I’m curious, are there people using it anyway?
I don’t get what is the point of Epiphany. We already have Midori as a fast webkit based browser and Firefox as a full featured browser.
Originally, when firefox didn’t use gtk, Epiphany was smaller while still giving most of the features of Firefox. But now Firefox uses native widget and they’ve broken accessibility on Epiphany. It’s no more than Midori, so what is the point?
Anyway, it looks like a great GNOME release.
Edited 2009-09-24 12:36 UTC
AFAIK, Mozilla has used gtk for the past ten years. Galeon and later Epiphany existed for the same reason that Camino and K-Meleon existed; the suite contained features that people didn’t need, and it didn’t look native on any platform. Firefox changed that (although one could make the argument that it is more bloated than Seamonkey these days). So Epiphany exists as something that the Gnome guys can maintain independently, and integrate as they see fit into their DE.
Midori is going to be part of Xfce.
Midori is a user interface nightmare. (or at least was last time I had the package installed)
No No No. Firefox is not native GTK, it looks similar, but it is not using GTK. Evidence? Try the menus, submenus to be specific, move the mouse on a diagonal to select a submenu item from the main menu, GTK works right, Firefox doesn’t. It may be using GDK to do the drawing at some level, but it isn’t GTK.
Epiphany is much more than Midori, it is a well designed clean browser, as it was when it was Galeon, or at least as Galeon was before Epiphany was started due to developer differences.
I started using Epi long ago, before Fx gained rudimentary integration with desktop and tagged bookmarks. Epiphany is still better in following points:
– passwords are stored in system keyring
– zeroconf bookmarks are supported
Congratulations to GNome team. You are one step closer to good desktop experience. GNome 2 onwards you have shown a great improvement in desktop side. Also you are becoming day by day more popular. I’ll also say that KDE is jump from 3.5 to 4 actually helped GNOME gain some user and now most the users are still sticking gnome and are not jumping back to KDE4.
The current work GNOME team is putting is assuring that KDE users are sticking to GNome.
Only thing that puzzles me is why one more brower (Epiphany) when we already have Firefox, Mozilla, Opera, Konqueror and soon Chrome…! Also there will be extensions and pluings to manage the Epiphany.
Gongratulations Gnome! Another step towards GNOME 3. Can’t see any big reason to change from KDE based on these upgrades but obviously that’s beside the point.
But I am more worried about Gnome 3.0
I think 6 month is far too short period for a new major release… If they release 3.0 in 6 month
1. Not future safe api’s or concept
2. Not well enough tested
3. Not enough time to get radical changes in upstream libraries and such
I think a gnome 3.0 “deserve” 2 year development cycle, otherwise it will deliver too litle and to bad quality.
Next release is 2.30 not 3.0
You are wrong, to quote gnome
“The final decision whether GNOME 2.30 (to be released in March 2010) or GNOME 2.32 (scheduled for September 2010) will become GNOME 3.0 will be made in early November 2009. This decision will be based on the progress of new and current GNOME applications and libraries and their impact on accessibility, stability and usability.”
Gnome has said that probably 2.30 or maybe 2.32 is to be Gnome 3.0.
But what I really said was that a 6 month is a far too short period to develop a major version, not that Gnome 3.0 would be released in 6 month, which I strongly doubt.
If 3.0 is all about taking 2.30 (or 2.32) and calling it 3.0, what is the point? It’s just the name? For marketing?
Just curious what there motivation is for a major version number jump when it could just as easily be 2.30. “They don’t do major disruptive jumps like KDE” is fine, but again, if it isn’t a major jump, why the major version number change?
3.0 will remove deprecated functionality from the 2.x series, thus breaking backward compatibility. One motivation of this is to enable future developments which are not possible within the old 2.x infrastructure.
Metacity is the current standard WM for GNOME. When GNOME Shell becomes the new standard, GNOME devs should completely remove any legacy of Metacity (calling Mutter) and make a faster and practical windowing system for the Shell.