[Webkit-unassigned] [Bug 20632] WebKitWebFrame should be replaced with GdomFrame

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=20632





------- Comment #2 from lkcl at lkcl.net  2008-09-13 09:06 PDT -------
sorry, i'd forgotten about this bugreport - i've since worked out
that a much better suggestion would be for WebKitWebFrame to _use_
GdomFrame.

i.e. rather than having a Frame* have a GdomFrame*.

the reasoning is that there are a number of _functions_ which are
hand-created in WebKitWebFrame which could be replaced with
the gdom_frame_* equivalents.

plus, in some cases, especially the Location* ones - i remember
seeing someone talking on the irc about doing a URL class or
something, for WebKitWebFrame - of course, you now have gdom_location_*

ok - actually, you _don't_ have gdom_location_* yet because it's
a custom function in JSLocation which i haven't cut/paste over
to GDOM* yet.... )

... but you get the idea.

also, it would make it clearer to the qt porters that the possibility
exists to do exactly the same trick in there.  yes, they might
squawk a bit at #include <gobject.h> their competitor, but that would
kick them into gear to do a Qt bindings generator.

if WebKitWebFrame itself continues to have a Frame* then it remains
unclear as to exactly how other ports should go about adding in the
gdom bindings.


-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.