Owen Taylor released development versions of GLib-2.3.6, Pango-1.3.6 and GTK+-2.3.6. Also, there was a GTK+-2.4.0 schedule change, while Owen posted a summary of a GTK+ team meeting regarding 2.4.
GTK+-2.3.6 Released
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
Any screenshots of the new file selector ?
But… I was looking on GNOME.org for some screenshots of 2.6.
Here’s the link: http://www.gnome.org/start/2.4/screenshots.html
Unfortunately it was just 2.4.
I decided to look at them anyway out of pure boredom.I just realized that the people with those screenshots are really mad at the new file selector. Note some of the names used in the pictures folder of the screenshots’ names “fucking armal” http://ximian.dulug.duke.edu/screenshots/large/iain.png
Fucking Amal is the name of a film. That is a directory containing movies.
On a different note: the GTK team have cut this one pretty close, haven’t they?
http://www.osnews.com/story.php?news_id=6279
On a different note: the GTK team have cut this one pretty close, haven’t they?
Yeah… However, the API was the big change in 2.4 and this was in development much longer. It’s only the new UI that was done at the last minute (almost literally). As long as the API is stable, the UI can always be updated in minor Gtk+ releases, so it’s not such a big deal if they don’t get it perfect at 2.4.
I was kidding, still I don’t think they should have screenshots that have fucking anything in them.
“I was kidding, still I don’t think they should have screenshots that have fucking anything in them.”
What would the point of taking the screenshot then?</sarcasm>
“I was kidding, still I don’t think they should have screenshots that have fucking anything in them.”
Fucking Åmål (Åmål is a town in Sweeden) … it’s a nice swedish teen movie.
http://imdb.com/title/tt0150662/
before you justice something by its name that offends your puritan heart, and jump the gun at the way a director names its movie. nothing to see here, move on.
or is GTK developed slowed down to a halt?
How many more YEARS will it take to get the new file selector? And it still the GUI is not ready, you say?
Oh, I see, it is because they were “trying to get the API right first”. Gee, an API for a file selector and directory manipulations must be a VERY HARD thing! Glad they (nearly) managed to complete it in only like 2 years.
Now, compare this pace with QT’s. Or even with GTK’s in the blooming years around 1999.
I’m very happy to see the ignorant ™ people are still out there.
And the new file selector did not take 2 years to design and implement.
(and also not 1 year, afaik)
You see, you want to criticise GTK on the basis of just the file selector, then it is ok. But GTK included a lot of stuff before KDE too. It had proper Internationalisation support first. Used freetype/fontconfig first, accessiblity support first(Qt still doesn’t have it in the stable versions), and other things. You could look and find more. so I guess thies means that each toolkit is ahead in some areas, and behind in others. Duh, is that worth mentioning even.
Well, and GTK included theming first, and Qt included many things first too. But that’s not important, what’s important is that in free software land, competing projects benefit from each other.
Also, the delays with the file selector were due mostly to:
a) More important enhancements to GTK (toolbar unification, GtkActions, etc.). Real work on the new file chooser started some months ago, not years.
b) How to add the file selector to a 2.x release without breaking ABI compatibility.
c) Making sure the API design was good enough not to require drastic changes (the UI can be changed, but the API changes could break working apps).
d) How to make it support things such as icons and VFS that are present in gnome, not making GTK depend on gnome libraries.
So it was not easy, no matter what some people say.
I thnk GTK/GNOME are being designed the right way. If you want to use the KDE dialogs, you have to use KDE, and not just Qt. therefore a pure Qt app and a KDE app have different file dialogs – See Opera. Since GTK gets the sexy dialog, GNOME does not provide one, and when everyone updates their apps to the new dialog, all GTK2 and GNOME2 apps get the same dalogs. Which is much better for consistency.
I think this creates a good synergy between GTK/NOME and frees up resources (like developer time) to be used doing the right things, not creating redundant implementations.
KDE’s file dialog is not written from scratch. Its wrapper over the already existing QT dialog which adds nice features such as KIO support etc.
So the problem you mention about Opera using diff. file dialog is still valid, but let not just claim that they are two different redundant implementations.