On 03/28/2014 11:15 AM, John Emmas wrote:
> On 27/03/2014 15:58, Mike Gorse wrote:
>> Atk was started during the GNOME 2 cycle and had version numbers that
>> were 1.x until GNOME 3 was released, at which point the version was
>> renumbered to 2.0.
>>
>> I don't see versions of glib or glibmm called 3.12. The latest stable
>> glib release I see is called 2.38, with a glib-2-38 branch.
>>
>
> Yeah, I think I was getting mixed up with gtk+ and gtkmm.  I noticed a
> ver2/ver3 thing going on with gtk+ and (apparently) also with atk so I
> wondered if they were related.  Many thanks for your clarification!

Probably you should revisit the thread that you started on November at
gtk-devel:
https://mail.gnome.org/archives/gtk-devel-list/2013-November/msg00048.html

You don't exactly ask the same questions, but are related.

>
> Just to make sure I understand it now...   are you saying that the
> current version of atk is usable when programming for either gkt+2 or
> gtk+3?  

Both gtk+2 and gtk+3 depends on ATK, but gtk+3 has a dependency with a
newer ATK version afaik. But atk 1.x and atk 2.x are API compatible.
That means that you can use the newer ATK with gtk+2, for example.

> In other words, even though the API changed for gtk+, glib mostly
> remained the same - so therefore if I'm using the current version of
> glib I'll need the current version of atk (regardless of which version
> of gtk+ I'm using)?  Does that sum it up?

glib also changed a lot, but it is API compatible. That means that the
old glib stuff would still work. But gtk+3 dedpends on some of the newer
glib stuff.



-- 
----
Alejandro Piñeiro

_______________________________________________
gnome-accessibility-devel mailing list
gnome-accessibility-devel@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel

Reply via email to