Re: Should AtkDocument use GdomeDocument ?



Owen Taylor wrote:
> 
> A dependency on libxml2 is not acceptable for GTK+-2.0, no. In fact,
> any required dependency on another external library really can't
> be feasibly added at this point; that would apply to gdome2, even
> if it didn't depend on libxml2.
> 
> (gdome2, from a quick glance, seems to be a much more straightforward
> implementation of the DOM than the original gdome, which is a good
> thing. However, I'm not sure if it is useable for something like
> Mozilla without having to try and maintain a mirror of the entire DOM
> tree.)

Mozilla has their own problems in implementing this ;-) but they will
be exporting the DOM in some form.

OK, so how should we do this, if not via gdome2 ?  We do need to do it
somehow, though arguably the set methods of the API don't need to be
exposed to GTK... should we rely on an anonymous struct of some sort,
whose contents is opaque to GTK?  What's the best way to pass
typed-but-opaque "somethings" around in GTK+ ?

Thx,

Bill

> Regards,
>                                         Owen

-- 
--------------
Bill Haneman
Gnome Accessibility / Batik SVG Toolkit
Sun Microsystems Ireland




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