GTK+ 3.4.0 released
| From: | Matthias Clasen <mclasen-AT-redhat.com> | |
| To: | gnome-announce-list-AT-gnome.org, gtk-devel-list-AT-gnome.org, gtk-app-devel-list-AT-gnome.org, gtk-list-AT-gnome.org | |
| Subject: | GTK+ 3.4.0 released | |
| Date: | Mon, 26 Mar 2012 15:39:02 -0400 | |
| Message-ID: | <1332790742.7589.1.camel@localhost> | |
| Archive‑link: | Article |
GTK+ 3.4.0 is now available for download at: http://download.gnome.org/sources/gtk+/3.4/ ftp://ftp.gtk.org/pub/gtk/3.4/ sha256 sum: 00af8be8bc60355e08a8f57e3e7503c916cec5cd5c6acb3eaedb01330b81f3e0 gtk +-3.4.0.tar.xz What is GTK+ ============ GTK+ is a multi-platform toolkit for creating graphical user interfaces. Offering a complete set of widgets, GTK+ is suitable for projects ranging from small one-off tools to complete application suites. GTK+ has been designed from the ground up to support a range of languages, not only C/C++. Using GTK+ from languages such as Perl and Python (especially in combination with the Glade GUI builder) provides an effective method of rapid application development. GTK+ is free software and part of the GNU Project. However, the licensing terms for GTK+, the GNU LGPL, allow it to be used by all developers, including those developing proprietary software, without any license fees or royalties. GTK+ is the only 100% free-of-cost open source industrial-strength GUI toolkit available today. Since its origins as the toolkit for the GNU Image Manipulation Program (GIMP), GTK+ has been used in a wide range of software. Notably, GTK+ is the foundation of the GNOME desktop. What's new in 3.4 ================= Major new features include: * Menu support in GtkApplication * A new color chooser * Add support for touch devices - New device types GDK_SOURCE_TOUCHSCREEN and GDK_SOURCE_TOUCHPAD for direct and indirect touch devices - New event GdkEventTouch and GDK_TOUCH_MASK - New signal GtkWidget::touch-event * Add support for smooth scrolling - Scroll events can contain scroll deltas, obtainable via gdk_event_get_scroll_deltas() - Scroll direction for such events is GDK_SCROLL_SMOOTH - To receive scroll events, widgets must now set either GDK_SCROLL_MASK or GDK_SMOOTH_SCROLL_MASK * GtkScrolledWindow will do kinetic scrolling with touch devices Platform support: * OS X support has been improved in many aspects: - Better keyboard handling (use 'Command' and 'Option' as modifiers) - Menu support in GtkApplication - Handle recursive CFRunLoops * This is the first version of GTK+ 3 that works well on Windows. Official builds of GTK+ 3.4.0 for Windows are expected in the near future * The Wayland backend has been updated to the current Wayland API, and the backend is much more complete now, with support for resize grips, grabs, geometry and window type hints, clipboard and selection support, etc. * The Broadway backend has been updated to support V7+ websockets. Other improvements: * Spin buttons have received a new look * Accessibility: the treeview accessible support has been rewritten and works much better now * Theming - More complete CSS support ('transparent' as color, 'background-clip', 'background-origin', 'background-size' CSS properties, linear-gradient syntax) - Support percentages, angles and other units in CSS - Better notebook tab rendering - Rounded corners for tooltips - Unfocused windows can be themed differently For more details and lists of fixed bugs, see the NEWS file that is included in the tarball, or see: http://git.gnome.org/browse/gtk+/plain/NEWS?id=3.4.0 For concerns about porting from older GLib release, see the README file that is included in the tarball, or see: http://git.gnome.org/browse/gtk+/plain/README.in?id=3.4.0 Where to get more information about GTK+ ======================================== Information about GTK+ including links to documentation can be found at: http://www.gtk.org/ An installation guide for GTK+ is found at: http://library.gnome.org/devel/gtk3/stable/gtk-building.html Common questions: http://library.gnome.org/devel/gtk3/stable/gtk-question-i... Contributing ============ GTK+ is a large project and relies on voluntary contributions. We are actively searching for new contributors in various areas and invite everyone to help project development. If you are willing to participate, please subscribe to the project mailing lists to offer your help and read over our list of vacant project tasks: http://live.gnome.org/GtkTasks Thanks to the many people who contributed to this release in the form of bug reports, patches and translations. Special thanks to Carlos Garnacho for his work on multitouch and to Ryan Lortie for his GtkApplication work. March 26, 2012 Matthias Clasen
Posted Mar 27, 2012 16:32 UTC (Tue)
by marduk (subscriber, #3831)
[Link] (30 responses)
Posted Mar 27, 2012 17:14 UTC (Tue)
by horen (guest, #2514)
[Link] (5 responses)
Posted Mar 27, 2012 18:08 UTC (Tue)
by slashdot (guest, #22014)
[Link] (1 responses)
Posted Mar 27, 2012 21:40 UTC (Tue)
by dgm (subscriber, #49227)
[Link]
Posted Mar 27, 2012 21:50 UTC (Tue)
by gus3 (guest, #61103)
[Link] (2 responses)
Posted Mar 28, 2012 13:05 UTC (Wed)
by man_ls (guest, #15091)
[Link] (1 responses)
Posted Mar 28, 2012 17:07 UTC (Wed)
by sorpigal (guest, #36106)
[Link]
I say it like this: Of couse it isn't strictly true by these measurements:
Posted Mar 27, 2012 17:51 UTC (Tue)
by atai (subscriber, #10977)
[Link]
Posted Mar 27, 2012 22:23 UTC (Tue)
by ebassi (subscriber, #54855)
[Link] (22 responses)
the color wheel has been moved to the "custom" color selector, and it's not a wheel any more; the wheel was kinda problematic, especially when used on touchscreens, so now it's a selector that ooks like this (the white space on the sides, to answer preventively the inevitable question, is there because we don't want to resize the dialog between the color palette and the color picker). yes, the eye drop picker was removed because it was hard to justify the use case in a generic toolkit, apart from the anedoctal evidence of: "I use it all the time". plus, the code was seriously iffy: in a composited environment you cannot get a pixel from the root window and expect that pixel to be exactly what you see on screen. plus, reading back from the GPU is always a synchronisation point, and it can be expensive, so you really want to do it at the right time. it doesn't mean that the eye drop tool won't be re-added at a later point, though, once the issue has been properly solved.
Posted Mar 27, 2012 22:50 UTC (Tue)
by Cyberax (✭ supporter ✭, #52523)
[Link] (9 responses)
>plus, reading back from the GPU is always a synchronisation point, and it can be expensive, so you really want to do it at the right time.
We're talking about a code that executes at most once every few seconds. And eye picker tool WAS useful.
Posted Mar 28, 2012 2:48 UTC (Wed)
by jmorris42 (guest, #2203)
[Link]
Yea, it should be a no brainer to realize that having the option to basically say "that color right -THERE-" in a color picker is going to be a popular feature. But GNOMEs remove things that work and replace them with things that suck. It is just what they do these days. Perhaps they will get over it soon and get back to making useful things again.
Posted Mar 28, 2012 6:46 UTC (Wed)
by ebassi (subscriber, #54855)
[Link] (7 responses)
have you even read what I wrote, or are you in write-only mode? just writing for shits and giggles, eh? I'm very happy that "your screenshot tool" works. now, go and try make it work on all the gtk platform, in every potential combination of environments, and future-proof it so that it exposes an API that may have to be frozen for the next 5 years. but it's obviously easy, because Cyberax did it.
Posted Mar 28, 2012 7:13 UTC (Wed)
by ekj (guest, #1524)
[Link] (3 responses)
It seems you're saying "Taking a screenshot is too difficult", if that's really the case, it's indicative of a problem. This is functionality that average users have expected for decades.
Posted Mar 28, 2012 16:26 UTC (Wed)
by ebassi (subscriber, #54855)
[Link] (2 responses)
anyway, supporting this feature correctly opens up another interesting issue of platform integration; gnome-screenshot currently asks the Shell for the data, because the compositor owns every pixel you're seeing on the screen, and X11 doesn't any more; so, on GNOME 3, it would work to ask the compositor for a single pixel. obviously, now, we have to negotiate with every other compositor, on the various platforms (Mac OS and Windows, mostly, but Wayland is coming up fast) that we support.
it's not as easy as it was in 1997, mostly because the platforms that we target are not as simple as they were 15 years ago.
Posted Mar 28, 2012 16:46 UTC (Wed)
by Cyberax (✭ supporter ✭, #52523)
[Link]
That's what I have to do right now. Manually. So I completely fail to see the problem.
Do a screenshot if you need. If you can somehow determine pixel color without making a screenshot - so much the better.
Posted Mar 28, 2012 20:30 UTC (Wed)
by ekj (guest, #1524)
[Link]
If you can do it faster, then go for it.
To me it seems like you're saying you've built a platform where even common and trivial things that have been taken for granted for decades, is now so hard you choose to drop the feature instead. That doesn't exactly instill confidence in the platform.
Come now: "what color is the pixel at x,y" should *not* be an unanswerable question in a grapical user-interface.
Posted Mar 28, 2012 14:34 UTC (Wed)
by Cyberax (✭ supporter ✭, #52523)
[Link] (2 responses)
Then I suggest removing the color picker altogether. After all, GTK is used on e-ink devices which can't display color at all! Better remove it ASAP.
I really really don't care about some obscure platforms (GTK on DirectFB? Just watch me ignoring it!). GTK is mostly used right now in Linux/*BSD and it probably should be somewhat of a priority to support them.
Posted Mar 28, 2012 17:21 UTC (Wed)
by mathstuf (subscriber, #69389)
[Link] (1 responses)
Doesn't gvim use GTK+ on all of the target platforms?
Posted Mar 28, 2012 17:28 UTC (Wed)
by Cyberax (✭ supporter ✭, #52523)
[Link]
You can certainly use gvim with GTK+ everywhere, but vim also supports native Win32 (and even Win16!): http://code.google.com/p/vim/source/browse/src/gui_w32.c and even native X11.
Posted Mar 29, 2012 11:14 UTC (Thu)
by daenzer (subscriber, #7050)
[Link] (9 responses)
Why not? The root window is still what's being displayed, compositing merely changes how its contents are drawn.
Posted Mar 29, 2012 12:11 UTC (Thu)
by cortana (subscriber, #24596)
[Link] (8 responses)
That said, if there's no other way to do it, the colour picker should just take a screenshot of the entire screen and use that. It sucks, but at least it's not a regression.
Posted Mar 29, 2012 12:24 UTC (Thu)
by daenzer (subscriber, #7050)
[Link]
Posted Mar 29, 2012 12:31 UTC (Thu)
by renox (guest, #23785)
[Link] (6 responses)
Hum, why does it suck?
Posted Mar 30, 2012 17:48 UTC (Fri)
by marduk (subscriber, #3831)
[Link] (5 responses)
Posted Mar 30, 2012 17:56 UTC (Fri)
by raven667 (subscriber, #5198)
[Link] (4 responses)
Posted Mar 30, 2012 17:58 UTC (Fri)
by rahulsundaram (subscriber, #21946)
[Link] (3 responses)
Posted Mar 30, 2012 18:09 UTC (Fri)
by marduk (subscriber, #3831)
[Link]
As a user, I had an eye dropper tool... less than a week ago, and I didn't notice any performance or quality issues. Now I don't have that tool. Perhaps you can cite the bug report[s]/mailing list threads pertaining to user complaints of performance/quality issues with the eye dropper tool.
Posted Mar 30, 2012 18:14 UTC (Fri)
by marduk (subscriber, #3831)
[Link] (1 responses)
What I was saying was.. in the "old days" despite the "performance/quality" issues with fake transparency, some developers apparently thought it was worth it to create/add this so-called feature.
The justification we're given for the eye-dropper tool is just the opposite: that it's too complex/finicky/not-universally-available for a feature that is *already* implemented. And so the baby gets thrown out with the bath water.
Posted Mar 30, 2012 18:21 UTC (Fri)
by rahulsundaram (subscriber, #21946)
[Link]
Posted Mar 29, 2012 22:16 UTC (Thu)
by blujay (guest, #39961)
[Link]
Fail. Touchscreens require separate UI. (cf. Windows 8, Metro)
> yes, the eye drop picker was removed because it was hard to justify the use case in a generic toolkit, after we ignored user feedback
FTFY.
> plus, the code was seriously iffy: in a composited environment you cannot get a pixel from the root window and expect that pixel to be exactly what you see on screen. plus, reading back from the GPU is always a synchronisation point, and it can be expensive, so you really want to do it at the right time.
Translation: "The code wasn't pretty enough, and we don't feel like beautifying it, so we ripped it out. Code elegance > usefulness."
I hate to be abrupt, but this is what it boils down to--developers' personal preferences over users' needs. That's reasonable for volunteers, except when it comes to removing existing functionality. Being responsible for a piece of code ought to entail making sure it continues working as expected, in spite of redesigns or rewrites.
Posted Apr 10, 2012 16:48 UTC (Tue)
by Zizzle (guest, #67739)
[Link]
The new GNOME/GTK motto?
If it doesn't work on touch rip it out?
Desktop users be damned, it's all about touch screens.
Posted Mar 27, 2012 21:14 UTC (Tue)
by scientes (guest, #83068)
[Link] (28 responses)
Are they relying on people not having heard the news of Qt relicensing under the LGPL too?
Posted Mar 27, 2012 22:09 UTC (Tue)
by ebassi (subscriber, #54855)
[Link] (12 responses)
Posted Mar 27, 2012 22:35 UTC (Tue)
by kragil (guest, #34373)
[Link]
Posted Mar 27, 2012 22:55 UTC (Tue)
by robert_s (subscriber, #42402)
[Link] (3 responses)
Posted Mar 27, 2012 22:57 UTC (Tue)
by rahulsundaram (subscriber, #21946)
[Link]
Posted Mar 27, 2012 23:24 UTC (Tue)
by ebassi (subscriber, #54855)
[Link] (1 responses)
Posted Mar 28, 2012 14:30 UTC (Wed)
by man_ls (guest, #15091)
[Link]
So, in a word: yes, it's free. It may not be effortless though.
Posted Mar 28, 2012 6:27 UTC (Wed)
by halla (subscriber, #14185)
[Link] (6 responses)
And, as Kragil said, it doesn't make Qt one whit less free, open or industrial strength. The only thing you can cavil about is that Qt isn't GUI toolkit; it's so much more. But of course, you already knew that.
Posted Mar 28, 2012 6:43 UTC (Wed)
by ebassi (subscriber, #54855)
[Link] (4 responses)
Posted Mar 28, 2012 6:55 UTC (Wed)
by halla (subscriber, #14185)
[Link] (3 responses)
Posted Mar 28, 2012 6:58 UTC (Wed)
by rahulsundaram (subscriber, #21946)
[Link] (2 responses)
Posted Apr 10, 2012 16:45 UTC (Tue)
by Zizzle (guest, #67739)
[Link] (1 responses)
Posted Apr 10, 2012 18:27 UTC (Tue)
by rahulsundaram (subscriber, #21946)
[Link]
Posted Mar 28, 2012 6:45 UTC (Wed)
by rahulsundaram (subscriber, #21946)
[Link]
Posted Mar 28, 2012 0:52 UTC (Wed)
by kripkenstein (guest, #43281)
[Link] (1 responses)
No idea what the basis is for that statement about GTK, it's bizarre.
Posted Mar 29, 2012 3:29 UTC (Thu)
by scientes (guest, #83068)
[Link]
> GTK+ is free software and part of the GNU Project. However,
However, I do agree that my post was not clear in this.
Posted Mar 28, 2012 3:13 UTC (Wed)
by elanthis (guest, #6227)
[Link] (9 responses)
It's just a bit of marketing speak. Nothing noteworthy or new going on here.
Posted Mar 28, 2012 5:14 UTC (Wed)
by eru (subscriber, #2753)
[Link] (5 responses)
Yes, but in this era of the internet, when anyone can check the truthfulness of claims like that in a minute or so, it would be a good idea to drop the practice. It really gives a bad taste to an otherwise interesting announcement.
Posted Mar 28, 2012 6:40 UTC (Wed)
by Company (guest, #57006)
[Link] (3 responses)
You kinda remind me of http://con.ca/img/news/00006244_FuckYouMomandDad.jpg
Posted Mar 28, 2012 7:47 UTC (Wed)
by Pawlerson (guest, #74136)
[Link] (1 responses)
Posted Mar 28, 2012 11:39 UTC (Wed)
by niner (subscriber, #26151)
[Link]
Of course there's still the next to 0 possibility, that he actually didn't know about all the other free toolkits which are 100 % free-of-cost, open source and industrial-strength (whatever that means exactly). But even that would not reflect too well on him. Especially since one shouldn't make such absolute statements if one has never even a single look outside his own project.
Posted Mar 28, 2012 10:41 UTC (Wed)
by dgm (subscriber, #49227)
[Link]
If that is true, then he's simply of the passive-agressive kind. If it's not, then he's a little bit too pretentious and self-contempt. He clearly cannot plead ignorance here. In any case, it only makes him (and GTK+ by extension) look bad.
Posted Mar 28, 2012 13:32 UTC (Wed)
by nhasan (guest, #1699)
[Link]
Posted Mar 29, 2012 3:15 UTC (Thu)
by scientes (guest, #83068)
[Link] (2 responses)
wxWidgets uses GTK, at least on Linux (and GTK 2 ATM, although a port is in process)
Posted Mar 29, 2012 3:20 UTC (Thu)
by scientes (guest, #83068)
[Link] (1 responses)
Posted Mar 29, 2012 20:01 UTC (Thu)
by oak (guest, #2786)
[Link]
Supporting UTF-8 or some other unicode encoding is just a first small step in internationalization and proper accessibility support is a requirement for software used in government.
Posted Mar 28, 2012 18:27 UTC (Wed)
by mclasen@redhat.com (subscriber, #31786)
[Link] (2 responses)
I'll make sure that the next GTK+ release announcement comes with a more accurate self-description.
Thanks for pointing this out,
Matthias
Posted Mar 28, 2012 20:21 UTC (Wed)
by drag (guest, #31333)
[Link] (1 responses)
Na. You really are spawn of satan for indirectly insinuating that the widget used in the a particular desktop preferred by certain peoples may be less then optimal compared to the project you spent a considerable portion of your life working on.
This sort of stuff is unforgivable. I am sure that people will be remembering your transgressions for years to come.
Posted Mar 28, 2012 20:22 UTC (Wed)
by Cyberax (✭ supporter ✭, #52523)
[Link]
Posted Apr 1, 2012 8:52 UTC (Sun)
by schabi (guest, #14079)
[Link]
http://www.gtk.org/language-bindings.php indicates that GTK# is the only "official" language binding which starved at version 2.12, but on the other hand, the table seems not to be updated for gtk+ 3.2 and 3.4.
GTK+ 3.4.0 released
"Less is more" -- Ludwig Mies van der Rohe (today's his 126th birthday)GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
$ man more | wc -c
5422
$ man less | wc -c
80998
Indeed.
This is fun:
GTK+ 3.4.0 released
$ du -sh /bin/more /bin/less
32K /bin/more
124K /bin/less
GTK+ 3.4.0 released
less is more, but more; most is more than less
$ man most | wc -c
15369
$ du -sh /usr/bin/most
60K /usr/bin/most
GTK+ 3.4.0 released
GTK+ 3.4.0 released
I do miss the old gtk color chooser, with the color wheel and the eye dropper tool (which I used a lot). I don't see an equivalent to the eye dropper in 3.4.
GTK+ 3.4.0 released
My screenshot tool does that just fine.
GTK+ 3.4.0 released
GTK+ 3.4.0 released
My screenshot tool does that just fine.
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
> and expect that pixel to be exactly what you see on screen.
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
Reading from the GPU is slow but noone cares one bit about the colour picker's performance!
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
only 100% free-of-cost open source industrial-strength GUI
toolkit available today.
you still have to jump through legal hoops if you want to contribute to Qt.
GTK+ 3.4.0 released
GTK+ 3.4.0 released
- not free-of-cost?
- not open source?
- industrial-strength?
- not a GUI toolkit?
GTK+ 3.4.0 released
GTK+ 3.4.0 released
yes, right, because forking is free.
GTK+ 3.4.0 released
As in beer? Yes. As in speech? Yes. As in software? It should; I refer you to this week's excellent quotes of the week, particularly to Greg KH's.
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
"Hoops"? That's a very, very tendentious way of describing something that is actually extremely simple: http://qt-project.org/legal.html#execution.
tell that to the legal department of a company.
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
> the licensing terms for GTK+, the GNU LGPL, allow it to be
> used by all developers, including those developing proprietary
> software, without any license fees or royalties.
GTK+ 3.4.0 released
It's just a bit of marketing speak. Nothing noteworthy or new going on here.
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
Misinform?
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
GTK+ 3.4.0 released
