GObject Gtk, Gnome, Gtk+, Gl, Gtk2, Gtk3...I don't understand?

Question

all I need some window to host webkit or/and cairo drwaing, but i have to deal with all that first to understand what I'm doing.

now. I'm lost and no more understand what's all that about.

and things get worse when I try working with binding or trying to figure what are dependencies for something. for example: in python, pyGtk deprecated and replaced by pyGObject(sometimes called pyGl!!)

there are many sites, many downloads and versions, mixed outdated and new references,but not one architectural view of the whole thing.

what I don't understand..is how all these things mixed with each other in too many sites,packages and versions?

Pena

This is more a rant than a real question, I'm voting to close. PS. architectural view of the whole thing: developer.gnome.org/platform-overview/stable – Prod

exactly, and what gnome has to do with gtk? gnome is "desktop environment" that uses gtk and others right? ok, if there is such thing called "gnome platform", from where I can download it? if you don't like something in this question I'd be thankful if you edit it and rewrite it in your terms. – Pena

@ptomato, more like a cry for help. The stack can be bewildering. – Falbala

Answer 1

The short story:

If you're programming for GTK 2, use pyGTK.

If you're programming for GTK 3, use pyGObject.

The long story:

From what I understood, pyGTK was based on pyGObject. GObject is the "object" API of GTK. GTK is developped in C, which is not an object-oriented language. GObject is a library that provides advanced object-oriented facilies. All GTK objects inherit from the GObject class provided by that library.

Then came the GObject-introspection work. Its goal was to make bindings maintenance easier, and use source code annotations to automatically generate most of the bindings code for each language (python, C++, etc.). This resulted in the python side in pyGI, the python bindings based on the GObject introspection work. That's when people were told to use it for GTK3 development.

Since then, the GObject-introspection work once provided by pyGI has been integrated into GObject. pyGObject eventually became what developers should use for python development in GTK3.

Please read:

• https://wiki.gnome.org/Projects/PyGObject

About the GNOME/GTK relationship:

GTK is the toolkit used by the GNOME project. It has been extracted from the GIMP, hence its name (GTK stands for: GIMP Tool Kit). GTK is a core part of the GNOME project, and GTK developers often also are involved in the GNOME project.

Fumble

Answer 2

My understanding of those components you mentioned:

• Think of GI as an interface that the core GNOME libraries conform to.
• PyGI doesn't exist any more; it's now part of PyGObject in the GNOME 3 setup.
• What is the relation between GTK, GTK+ and GTK2?

Unconquerable