Re: Advice requested on deprecating AT-SPI/CORBA



Due to others hardcoding the string "atk-bridge" in their code (e.g.,
Firefox and OOo), the GTK+ a11y module has to be named "atk-bridge".  We
could ask Firefox and OOo to not hardcode the name, but we'd end up in a
versioning hell with external apps not tied to the GNOME release schedule.
 So, I'd like to make the simplifying assumption that they will not change
and we need to deal with "atk-bridge".

Can we force them to not hardcode it and yet preserve atk-bridge so
that we can change it in the future if needed? a pkg-config variable
would solve this I'd say.

We can certainly ask them to change. The problem is that the Firefox and OOo release schedules are completely de-coupled from GNOME's. As a result, by requiring them to change for AT-SPI/D-Bus to succeed, we have introduced another dependency that is another point of failure and delay.

Will




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]