Linked by Thom Holwerda on Tue 29th Jan 2008 18:48 UTC, submitted by Michael Larabel
"Back in November we started sharing some of the exciting features planned for the GNOME 2.22 and 2.24 releases, and now that the first GNOME 2.22.0 Beta release is planned for later this week, we have taken another look at the packages set for inclusion and the changes that have actually been made. While nothing groundbreaking will be introduced in GNOME 2.22, this desktop environment does have some moderate changes worth noting. In this article are eight interesting packages that either have noticeable changes since GNOME 2.20 or are new to GNOME. This list isn't all-inclusive or ordered in any particular fashion, but just eight changes that had caught our attention."
Thread beginning with comment 298258
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-07-12
Bullocks.
Gnome in its current state has no default browser.
Gnome has a default browse. It's called Epiphany. The project page is even part of the gnome.org domain!
http://www.gnome.org/projects/epiphany/
From their website:
"Epiphany is the web browser for the GNOME desktop."
Most distros use Firefox because, well, it's Firefox, one of the most popular web browser in the world!! And since both projects use the Gecko engine to render pages, it would be just plain stupid not prefer Firefox, since it not only integrates well enough with most GTK themes, plus you get added bonus of familiarity which is often preferable to usability.
Gnome has no control over mozilla or web kit.
That's not an issue. ISV's have no control of the Windows platform, KDE has no cotrol over QT, Opera Software has no control over QT wich they use on Opera, etc.
One of the qualities of properly designed software is that you don't need to control the actual code to be able to interface with it. All you need is a well documented API.
Ironically I recall a few months ago when the KHTML guys (KHTML = Webkit - Apple Patches) where up in arms over the fact that the boys at Cupertino where committing massive changes to the project source without proper documentation, so they had to spend lots of time trying to figuring them out before they could merge them into the main source tree. Talk about not having control over you're own software...
Every project relies on 3rd party software so they don't have to reinvent the wheel over and over again.
The whole Gnome thing is lookign more like a bandaid solution.
After uneducated remarks about software development, a nice sprinkle of gnome bashing is just what the doctor ordered.
Are you insinuating that the bread and butter of software development, which is called Object Oriented Programing and it's centered around concept of reusing bits and pieces of code that is usually developed by 3rd party a band aid solution?!
Do propose have a better approach?
Whatever....
Regarding TFA, i think it's nice to see gnome plowing ahead. One step a a time, easy does it. I do think KDE 4 might yet become a serious contender for the crown of the OSS desktop. But only in about 1 or 2 years time. Until then, it's nice to know that Gnome will keep getting better one point release at a time.