[Webkit-unassigned] [Bug 27436] gobject bindings need access to keyCode on KeyboardEvents!

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Aug 3 16:14:38 PDT 2009


--- Comment #18 from Luke Kenneth Casson Leighton <lkcl at lkcl.net>  2009-08-03 16:14:37 PDT ---
(In reply to comment #16)
> (In reply to comment #15)
> > (In reply to comment #14)
> > > I think it would be a relatively easy change to add some sort of
> > > ALLOW_ARGUMENT_OVERLOADS or similar define which encapsulated !JAVASCRIPT and
> > > GOBJECT.  That wouldn't involve re-writing the world, but it also wouldn't be
> > > poluting our IDL files more.
> > 
> > Except for the small issue that JavaScript DOM bindings support overloaded
> > functions.
> Sounds like either I have the ! reversed in my example text above, or I'm
> misunderstanding the issue.  Are you saying that it would not be
> good/possible/sufficient to replace the proposed !JAVASCRIPT && GOBJECT && ...
> with a single define?

 see https://bugs.webkit.org/show_bug.cgi?id=27435#c29 and previous.

 overloaded functions = same function with different numbers of arguments.

 think: "the usual c / c++ problem, basically".

 XULrunner have run into exactly the same problem:


 except there, the users have c++ as the native API, and the python bindings
are direct to that.  any mess-ups are due to implementation flaws (as can be
seen from the above two bugs) and precedence given to javascript rather than
any particularly good reason.

 MSHTML does two tricks:

 * adds rolling numbers onto the overloaded functions.  burden is passed to
users to work out which one to use.

 * and, also, i thiiink what they do is create different COM interfaces and
then create a coclass merging them all together.  IDispatch can cope with
telling users about the interfaces and their functions (at run-time) and in
this way, dynamic use of the MSHTML interface simply passes the burden onto the

 both of which are greeeaat.

 but.  seriously.   see https://bugs.webkit.org/show_bug.cgi?id=27435#c29 - the
conclusion is that i don't believe it's that big a deal.  even if what small
API changes are required happen in 6 months or a year.

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

More information about the webkit-unassigned mailing list