[g-a-devel]extensivle accessibility modules.
- From: Michael Meeks <michael ximian com>
- To: Bill Haneman <bill haneman sun com>
- Cc: Jody Goldberg <jody gnome org>, Padraig O'Briain <Padraig Obriain sun com>, Anders Carlsson <andersca gnu org>, Release Team <gnome2-release-team gnome org>, <gnome-accessibility-devel gnome org>
- Subject: [g-a-devel]extensivle accessibility modules.
- Date: Wed, 12 Dec 2001 06:19:00 -0500 (EST)
Hi Bill,
On Wed, 12 Dec 2001, Bill Haneman wrote:
> If we go this route we need to be sure that the GTK_MODULES loading
> mechanism continues to work for GTK+ apps and that it does not clash
> with gnome_program_foo code.
Clearly - that shouldn't be too difficult I think.
> I am dubious because I think that GTK+ apps (i.e. apps that don't use
> gnome-program) can use widgets that we need to add support for, so our
> extension mechanism probably should not be tied to g-p.
Well - the problem is it needs to be adaptive to a great extent -
we can do that with gnome_program_ but not with anything else.
Sure - anything that only has a gtk+ dependency needs to be in
gail - but I think other things - need to be dynamicaly loaded as needed.
Otherwise - we pull in lots of libraries we don't need every time we run a
gtk+ app eg. [libbonoboui, libgnomeui, eel, gal etc.] - of course - quite
correct, one can change GTK_MODULES to contain different things before
running each app - but this is a non-solution; which user knows he has to
edit an env-var to enter the deps of the program he's about to run :-)
I think we should be looking at getting some g_module hooks into
gnome_program ASAP. Anders - I'll have a look at hacking this today; does
it sound ok to you ? Of course - the easiest solution for now is to pull
the gtkhtml2 API down the stack - to underneath gail - which seems all we
can do for the beta.
Regards,
Michael.
--
mmeeks gnu org <><, Pseudo Engineer, itinerant idiot
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]