[webkit-gtk] Are you using unstable GObject DOM API?

Tomas Popela tpopela at redhat.com
Thu Sep 1 04:26:12 PDT 2016


On Thu, 2016-09-01 at 09:23 +0200, Carlos Garcia Campos wrote:
> We have finally frozen the GObject DOM bindings API, moving all the
> generated code to the source tree. But now we have a bunch of unused
> code there that I would love to remove. The unstable API no longer
> makes sense, because that code is not auto-generated so all API there
> is going to be stable. So, the idea is to move the unstable API
> currently used by applications to the stable part, to not break any
> existing application, and then remove the rest of the API. Of course,
> we can add new API on demand if needed.
> But to do this we need to know what unstable API is currently used by
> applications. 

I've not followed the current situation closely, but I think that in
the end it will be good for you (us) as it should avoid the API
breakages (and the extra work to deal with them) and in the end for the
API consumers the situation won't change at all. If they will need some
new unstable API we can still add it and expose it through Unstable.h.

Also this could actually increase the quality of our APIs as hacking on
them would be much easier as you will hack on the actual code and not
on the scripts that are generating them (at least I know about some
improvement to webkit_dom_element_set_attribute() and possibly others).

> I've already checked the GNOME apps (evo, ephy and yelp), so if you
> are
> using unstable DOM API (you can easily check it by grepping
> for WEBKIT_DOM_USE_UNSTABLE_API in your code) in you application (and
> it's not ephy, evo or yelp), please let us know either here or
> commenting on bug https://bugs.webkit.org/show_bug.cgi?id=161440

Thank your Carlos for looking at the Evolution.


More information about the webkit-gtk mailing list