Review of GNOME 2.26 and GTK+ 2.16
devg writes "The GNOME development community recently announced the official release GNOME 2.26, the latest version of the open source desktop environment for Linux. It adds the Brasero disc burning software, UPnP support in the Totem media player, and basic support for video chat in the Empathy instant messaging client. GNOME 2.26 will be shipped in upcoming Linux distributions, including Fedora 11 and Ubuntu 9.04. Some early reviews show that it is an incremental improvement with some good additions. GNOME 2.26 is accompanied by the release of GTK+ 2.16, a new version of the widget toolkit that is used to build the desktop environment. Ars Technica has published a detailed programming tutorial with code examples that demonstrate how developers can use the new features of GTK+ 2.16 in their own applications. Users can test GNOME 2.26 by downloading one of the official Foresight-based VM or ISO images via BitTorrent."
From the changelog:
Second is support for Microsoft Exchange's MAPI protocol. This is the protocol that Microsoft Outlook uses to communicate with Exchange. Previously, Evolution only supported Exchange's SOAP protocol, which is not available on all Exchange servers. This support significantly improves Evolution's integration with Exchange servers.
That sounds like a big deal. Anyone knows how well it actually works in practice?
They're nice. Especially as someone who use KDE, it allows me to easily see what's happening in that part of the world.
the gnome file manager also has an awesome bar like firefox now!
I left gnome when they removed all the options from the screen-savers because they decided that configuring the screen-savers was to complicated for users. Surely not all gnome users are retards!
Per application volume control is a MAJOR feature. Listening to music, while not having web pages blast out your ear drums is a major win. This is my favorite feature of Vista, and I am happy to see it integrated into Gnome.
Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
And I'm anticipating similar functionality appearing in Kontact really soon... this sort of friendly competition makes Open Source progress so fast.
Want to hear the voice of GOD? cat
Can I put a different wallpaper on different desktops yet? That's the main feature I miss from KDE when I use Gnome (I tend to have different versions of the same code open on different desktops, so a visual queue as to which one I'm looking at really helps).
Things went downhill the moment the first sound server became common. The first popular one was "esd" or "esound", the Enlightenment Sound Daemon.
With that came sound libraries by the dozen, because sound was no longer simple for app programmers. This in turn was an enabler for the evils of ALSA, which is totally unusable without the ALSA library. As the years went by, everybody and their dog wrote a sound server. We got sound servers feeding into sound servers. You could even connect them to each other in a loop, something easy to do with all the confusing config problems. We lost the "Just Works" feature long ago.
And for what? I certainly don't want sounds from different apps mixed into an ear-assaulting mess. I want one thing at a time. I'm totally fine with having one thing monopolize the hardware, with my audio stream unmolested by mixers of dubious quality and high latency. If you want to be fancy, a stack-based design that plays the most recent app (going back to the previous one when the recent one finishes) would be kind of nice. That assumes I want stuff interrupted, which is a big maybe.
I had to edit config files to get my laptop to recognize and bring up the second screen after docking. Editing config files should not be required for one of the core mobility scenarios.
Does this release fix the issue? I.e. if I just connect the monitor, will it get recognized automatically?
You can disable the labels from the "Interface" tab of the "Appearance Preferences".
If you had read T linked FA - fat chance on /., but still - or even if you knew a thing or two about Qt, it would have saved you from making a lame comment.
First: Qt is not just a widget library. It's a full framework that goes well beyond putting things on screens.
Second: What he did modify had nothing to do with widgets. K3b used a KProcess class that employed piping of I/O. In KDE4, that wraps QProcess, which is too high-level for the kind of data-passing throughput required by dvd burning, so he had the class re-written. Yes, the article title is lame (as is its rehashing by the GP post) - forking a class is nothing nearly like forking a framework - but its absurdity should have triggered curiosity instead of look-at-me-I'm-smart comments missing the point.
Friendly!? Haven't you seen any KDE-gnome flame war? Ok, ok, just kidding. It's lively discussion, but I guess it could be tagged as friendly
-- dnl