Posted by
michael
on from the now-better-splash-screens dept.
d3vi1 writes "Pango, Glib & GTK 2.4.0 have been released to the public. See gtk.org in general, or specifically: the announcements for pango, glib and gtk."
Re:As soon as I figure what this things does....
by
Anonymous Coward
·
· Score: 5, Informative
FTFA:
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 projects to complete application suites.
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 based on three libraries developed by the GTK+ team:
GLib is the low-level core library that forms the basis of GTK+ and GNOME. It provides data structure handling for C, portability wrappers, and interfaces for such runtime functionality as an event loop, threads, dynamic loading, and an object system.
Pango is a library for layout and rendering of text, with an emphasis on internationalization. It forms the core of text and font handling for GTK+-2.0.
The ATK library provides a set of interfaces for accessibility. By supporting the ATK interfaces, an application or toolkit can be used with such tools as screen readers, magnifiers, and alternative input devices.
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.
Re:KDE compatibility?
by
AuMatar
·
· Score: 5, Informative
As long as you have the KDE libraries installed, it doesn't matter what your desktop is.
--
I still have more fans than freaks. WTF is wrong with you people?
says the n00b: "it's good to see that GTK is catching up with the kernel version."
says the 1337: "..."
-- Esoteric reference.
Re:New File Dialog
by
niiler
·
· Score: 5, Informative
The problem is that if you want users to only be able to select a single package type, say *.tgz, you have to spin your own dialog. The current filtering is virtually non-existant. If you do try to use it, it can hide directories that don't have the correct extension.
From the release notice:
"The new GtkFileChooser widgets provide a radically simplified and improved way for users to select files. Application writers now are provided with such capabilities such as customizable filters and previews. The filesystem access is encapsulated as a dynamically loaded module; as an example of what this allows, libgnomeui now provides a gnome-vfs backend for GtkFileChooser so that it has the same view of remote filesystems as applications such Nautilus."
This is cool stuff as it will certainly improve the perception and use of GTK.
Re:It's the little things....
by
sydb
·
· Score: 5, Insightful
All hail Lord Stallman; praise to St Ignucius.
Those "linux libraries" are not "linux" libraries, they are GNU libraries.
That's why they run on things that aren't linux.
-- Yours Sincerely, Michael.
GTK release of 2.4
by
Mr+Thinly+Sliced
·
· Score: 5, Informative
It's a great release. It is something that finally the gnome-ers can get their teeth into. And it's not before time.
For anyone who has been following the good work that the gnome developers have been doing, its starting to look like vindication.
Xft and fontconfig use the same backends - whats that mean to you? - better fonts - everything GTK now plays the same game.
Fonts and character shapes can take a scripts 'hints' about a font into account - we win, the font creator wins - its about the best of everyones world.
Using bi-directional text is not forced by the application - it can be extracted or 'hinted' from the original source file itself.
GLIB:
GLIB update to use unicode 4.0 - many, many people benefit.
GLIB correctly recovers children processes.
GRandom is better at seeding. But not cryptographically secure. Yet.
The threading library with GLIB is now "operation or not" on integers and pointers.
There is a way to specify an OO 'singleton' or 'once initialisation'
Extra macros for GObject type writers
Properties can be added to interfaces (verbatim copied)
Private data within an instance can contain private data/references within and object (its not clean what this means in a C context, but I think they mean that it's not exposed).
GTK takes all of the above features, and uses those to make a fantastic release.
Lets give these people time,
They need it.
I don't see that a good thing necessarily. I've gone through the pain of compiling programs that had dozens of libraries needed because the author was too lazy to write a single function. Having all these libraries an arm reach away has made modern programmers lazy and less knowledgeable.
This is a tragic mis-statement. What it has done is extended the power of complex, standard behaviors and routines to other programmers, allowed for centralised bug fixing as well as system wide improvments and feature enhancements. Code reuse has allowed us to build complex software in short time periods to meet ever diminishing deadlines.
Even if the use of standard libraries made programmers 'lazy' and 'less knowledgeable' ( I can't believe I'm writing this ), how does this in any way negatively impact their output provided they have access to these amazing laze inducing libraries?
It almost makes me sad to read this post. My computing forebears slaved and suffered in a living hell of replicated work and wasted maintainance time - we have these tremendous advantages at our disposal, and they are characterised as some kind of enemy of programming moral fiber.
Slashdot Mirror
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 projects to complete application suites.
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 based on three libraries developed by the GTK+ team:
GLib is the low-level core library that forms the basis of GTK+ and GNOME. It provides data structure handling for C, portability wrappers, and interfaces for such runtime functionality as an event loop, threads, dynamic loading, and an object system.
Pango is a library for layout and rendering of text, with an emphasis on internationalization. It forms the core of text and font handling for GTK+-2.0.
The ATK library provides a set of interfaces for accessibility. By supporting the ATK interfaces, an application or toolkit can be used with such tools as screen readers, magnifiers, and alternative input devices.
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.
As long as you have the KDE libraries installed, it doesn't matter what your desktop is.
I still have more fans than freaks. WTF is wrong with you people?
says the n00b: "it's good to see that GTK is catching up with the kernel version."
says the 1337: "..."
Esoteric reference.
From the release notice: "The new GtkFileChooser widgets provide a radically simplified and improved way for users to select files. Application writers now are provided with such capabilities such as customizable filters and previews. The filesystem access is encapsulated as a dynamically loaded module; as an example of what this allows, libgnomeui now provides a gnome-vfs backend for GtkFileChooser so that it has the same view of remote filesystems as applications such Nautilus."
This is cool stuff as it will certainly improve the perception and use of GTK.
All hail Lord Stallman; praise to St Ignucius.
Those "linux libraries" are not "linux" libraries, they are GNU libraries.
That's why they run on things that aren't linux.
Yours Sincerely, Michael.
For anyone who has been following the good work that the gnome developers have been doing, its starting to look like vindication.
Ok, enough of the back slapping, lets see whats on offer: (PS - release notes for GTK at Gnome 2.6 update release notes
Font Changes:- Xft and fontconfig use the same backends - whats that mean to you? - better fonts - everything GTK now plays the same game.
- Fonts and character shapes can take a scripts 'hints' about a font into account - we win, the font creator wins - its about the best of everyones world.
- Using bi-directional text is not forced by the application - it can be extracted or 'hinted' from the original source file itself.
GLIB:- GLIB update to use unicode 4.0 - many, many people benefit.
- GLIB correctly recovers children processes.
- GRandom is better at seeding. But not cryptographically secure. Yet.
- The threading library with GLIB is now "operation or not" on integers and pointers.
- There is a way to specify an OO 'singleton' or 'once initialisation'
- Extra macros for GObject type writers
- Properties can be added to interfaces (verbatim copied)
- Private data within an instance can contain private data/references within and object (its not clean what this means in a C context, but I think they mean that it's not exposed).
GTK takes all of the above features, and uses those to make a fantastic release. Lets give these people time, They need it.This is a tragic mis-statement. What it has done is extended the power of complex, standard behaviors and routines to other programmers, allowed for centralised bug fixing as well as system wide improvments and feature enhancements. Code reuse has allowed us to build complex software in short time periods to meet ever diminishing deadlines.
Even if the use of standard libraries made programmers 'lazy' and 'less knowledgeable' ( I can't believe I'm writing this ), how does this in any way negatively impact their output provided they have access to these amazing laze inducing libraries?
It almost makes me sad to read this post. My computing forebears slaved and suffered in a living hell of replicated work and wasted maintainance time - we have these tremendous advantages at our disposal, and they are characterised as some kind of enemy of programming moral fiber.
One god, one market, one truth, one consumer.
Anyway common usage of litigious means it doesn't make sense to use the word that way.
not listed so far:
Opera (QT)
Adobe Photoshop Album (QT)