[Webkit-unassigned] [Bug 16401] [GTK] GObject/C DOM binding

[bugzilla-daemon at webkit.org]

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





------- Comment #173 from christian at imendio.com  2009-02-13 09:04 PDT -------
(In reply to comment #172)
> (In reply to comment #164)
> > Alternatively we could explicitly make
> > WebKitAttr => WebKitDomAttr and still go with WebKitFooElement.
> 
> To be complete, this is naming possibility (4): we could use the Dom prefix
> only for certain generic-looking names such as Attr.  To do this, we'd have to
> agree on exactly when this happens.  For example, is it WebKitDomNode, or
> WebKitNode?  WebKitDomText, or WebKitText?  These decisions seem pretty
> arbitrary, so I might lean away from this possibility.

In fact WebKitText is technically out of the question, because it would
conflict with for instance GtkText in object oriented programming languages.

To make my suggestion less arbitrary, how does it sound to leave out the *Dom*
for all *Element classes? Considering that this comes down to *HTML*Element
anyway.


-- 
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.