Re: [webkit-dev] Question related to license in WK2 EFL port

There’s some specific policy about this that’s displayed in bugs.webkit.org when you attach a patch for review: > Hello and thank you for contributing a patch. Here is our licensing policy > and terms for contributing code to the WebKit project. > > • If you are sending in a patch to exis

Re: [webkit-dev] Multiple inheritance in the DOM

On Jul 25, 2012, at 3:50 PM, Adam Barth wrote: > On Wed, Jul 25, 2012 at 3:44 PM, Dirk Schulze wrote: >> On Jul 25, 2012, at 2:33 PM, Adam Barth wrote: >>> Eric Seidel points out that SVG uses multiple inheritance in its DOM >>> interfaces. However, the situation there is a bit different. >>> A

Re: [webkit-dev] Multiple inheritance in the DOM

From: Adam Barth Date: Wednesday, July 25, 2012 6:05 PM To: Sam Weinig Cc: Elliott Sprehn , Alan Stearns , Kentaro Hara , "webkit-dev@lists.webkit.org" Subject: Re: [webkit-dev] Multiple inheritance in the DOM On Wed, Jul 25, 2012 at 6:00 PM, Sam Weinig wrote: On Jul 25, 2012, at 5:53 PM

Re: [webkit-dev] Multiple inheritance in the DOM

On 7/25/12 6:12 PM, "Sam Weinig" wrote: > >On Jul 25, 2012, at 5:37 PM, Sam Weinig wrote: > >> >> On Jul 25, 2012, at 5:13 PM, Alan Stearns wrote: >> >>> On 7/25/12 4:49 PM, "Kentaro Hara" wrote: >>> A) Should we push back on the folks writing the CSS Regions specification

Re: [webkit-dev] Multiple inheritance in the DOM

If the only problem is to determine the type of JS wrappers, is it possible to make wrapSlow() a virtual method of some base class, instead of static functions? It need a tweak on the code generator. Also, it might need to avoid name conflicts by suffixing like wrapSlowForNode(), wrapSlowForRegion

Re: [webkit-dev] Multiple inheritance in the DOM

On Wed, Jul 25, 2012 at 6:00 PM, Sam Weinig wrote: > > On Jul 25, 2012, at 5:53 PM, Elliott Sprehn wrote: > > > On Wed, Jul 25, 2012 at 5:13 PM, Alan Stearns wrote: > >> ... >> >> From the WebIDL side, it's not strictly multiple inheritance. It's merely >> a supplemental interface that more tha

Re: [webkit-dev] Multiple inheritance in the DOM

On 7/25/12 5:37 PM, "Sam Weinig" wrote: > >On Jul 25, 2012, at 5:13 PM, Alan Stearns wrote: > >> On 7/25/12 4:49 PM, "Kentaro Hara" wrote: >> >>> A) Should we push back on the folks writing the CSS Regions >>> specification to avoid using multiple inheritance? As far as I >> know,

Re: [webkit-dev] Multiple inheritance in the DOM

On 7/25/12 4:49 PM, "Kentaro Hara" wrote: > A) Should we push back on the folks writing the CSS Regions > specification to avoid using multiple inheritance? As far as I know, > this is the only instance of multiple inheritance in the platform. > Historically, EventTarget

Re: [webkit-dev] Multiple inheritance in the DOM

>>> > A) Should we push back on the folks writing the CSS Regions >>> > specification to avoid using multiple inheritance? As far as I know, >>> > this is the only instance of multiple inheritance in the platform. >>> > Historically, EventTarget used multiple inheritance, but that's been >>> > fix

Re: [webkit-dev] Multiple inheritance in the DOM

On Wed, Jul 25, 2012 at 3:44 PM, Dirk Schulze wrote: > On Jul 25, 2012, at 2:33 PM, Adam Barth wrote: >> Eric Seidel points out that SVG uses multiple inheritance in its DOM >> interfaces. However, the situation there is a bit different. >> Although SVGSVGElement implements SVGLocatable, there ar

Re: [webkit-dev] Multiple inheritance in the DOM

On Jul 25, 2012, at 2:33 PM, Adam Barth wrote: > Eric Seidel points out that SVG uses multiple inheritance in its DOM > interfaces. However, the situation there is a bit different. > Although SVGSVGElement implements SVGLocatable, there aren't any > interfaces with methods that return SVGLocatab

Re: [webkit-dev] Multiple inheritance in the DOM

According to WebIDL, every platform object has a "primary" interface, as defined by . As long as that's the case, DOMInterface::interfaceName() should be sufficient to figure out which JavaScript wrapper to use. Adam On Wed, Jul 25, 2012 at 2:4

Re: [webkit-dev] Multiple inheritance in the DOM

At least DOMInterface::interfaceName() is no where near as bad as COM's QueryInterface. Provided we don't end up with any diamond inheritance hierarchies, we shouldn't need something as complicated as QueryInterface. -Darin On Wed, Jul 25, 2012 at 2:33 PM, Adam Barth wrote: > Eric Seidel poi

Re: [webkit-dev] Multiple inheritance in the DOM

Eric Seidel points out that SVG uses multiple inheritance in its DOM interfaces. However, the situation there is a bit different. Although SVGSVGElement implements SVGLocatable, there aren't any interfaces with methods that return SVGLocatable, which means we don't need to implement toJS(SVGLocata

Re: [webkit-dev] Building on Mountain Lion

On 7/25/12 2:21 PM, "Mark Rowe" wrote: > >On 2012-07-25, at 14:15, Jacob Goldstein wrote: > >> Has any tried to build WebKit on Mountain Lion? >> >> I just attempted with a new install of Mountain Lion and Xcode 4.4 and >>the build keeps failing while trying to compile >>AlternativeTextUICont

Re: [webkit-dev] Building on Mountain Lion

On 2012-07-25, at 14:15, Jacob Goldstein wrote: > Has any tried to build WebKit on Mountain Lion? > > I just attempted with a new install of Mountain Lion and Xcode 4.4 and the > build keeps failing while trying to compile AlternativeTextUIController. If > anyone has thoughts as to why thi

[webkit-dev] Building on Mountain Lion

Has any tried to build WebKit on Mountain Lion? I just attempted with a new install of Mountain Lion and Xcode 4.4 and the build keeps failing while trying to compile AlternativeTextUIController. If anyone has thoughts as to why this could be, please let me know. ___

[webkit-dev] Multiple inheritance in the DOM

The CSS Regions specification [1] defines a CSSOM interface named Region, which can be mixed into interfaces for other objets that can be CSS regions. That means that Region introduces a form of multiple inheritance into the DOM. For example, Element implements Region but Node does not implement

Re: [webkit-dev] WebKit memory instrumentation

It turns out that clang has good API for plugins and a simple plugin for checking the instrumentation coverage contains ~200 loc. Thus the first option looks useless. Regards, Tim. On Wed, Jul 25, 2012 at 11:34 PM, Maciej Stachowiak wrote: > > On Jul 25, 2012, at 2:08 AM, Yury Semikhatsky wro

Re: [webkit-dev] Delaying Applying CSS Effects

For the SVGResoruceCache route, how would I specify that some element depends on another element with id x, where x does not exist in the DOM yet? I have noticed SVGDocumentExtensions::addPendingResource which sounds like what I want, but it only excepts SVGStyleElements. On Tue, Jul 24, 2012 at

Re: [webkit-dev] WebKit memory instrumentation

On Jul 25, 2012, at 2:08 AM, Yury Semikhatsky wrote: > > > On Tue, Jul 24, 2012 at 10:34 PM, Maciej Stachowiak wrote: > > On Jul 24, 2012, at 12:39 AM, Yury Semikhatsky wrote: > >> >> >> On Tue, Jul 24, 2012 at 12:47 AM, Maciej Stachowiak wrote: >> >> On Jul 23, 2012, at 8:09 AM, Yury

Re: [webkit-dev] Easing printf based debugging in WebKit with an helper.

>> That possibility aside, the stronger part of my objection is language >> purity. WebCore uses C++ as "C with classes" and I don't think it's worth >> it to confuse new (or existing) contributors about that going forward. >> > > Can you elaborate why WebCore uses C++ as "C with classes"? Proba

Re: [webkit-dev] Easing printf based debugging in WebKit with an helper.

On Jul 25, 2012, at 8:25 AM, Yong Li wrote: > 2012/7/19 Brady Eidson : >> >> On Jul 19, 2012, at 10:53 AM, Andreas Kling wrote: >> >> On Tue, Jul 10, 2012 at 4:52 PM, Brady Eidson wrote: >>> >>> >>> On Jul 10, 2012, at 5:25 AM, Alexis Menard >>> wrote: >>> On Mon, Jul 9, 2012 at 6:5

Re: [webkit-dev] Easing printf based debugging in WebKit with an helper.

2012/7/19 Brady Eidson : > > On Jul 19, 2012, at 10:53 AM, Andreas Kling wrote: > > On Tue, Jul 10, 2012 at 4:52 PM, Brady Eidson wrote: >> >> >> On Jul 10, 2012, at 5:25 AM, Alexis Menard >> wrote: >> >> > On Mon, Jul 9, 2012 at 6:53 PM, Brady Eidson wrote: >> >> >> >> On Jul 9, 2012, at 2:43

Re: [webkit-dev] Do we need a "webkitBackground" property for XMLHttpRequest?

There is no such thing as "pushing to trunk" for Chromium. All development happens on trunk. That sounds like a regression. I'll follow up with the networking folks. Thanks for checking! Adam On Wed, Jul 25, 2012 at 12:57 AM, xuewen wrote: > As I tested, the chromium Version 22.0.1217.0 (14

Re: [webkit-dev] Do we need a "webkitBackground" property for XMLHttpRequest?

> From: webkit-dev-boun...@lists.webkit.org > [webkit-dev-boun...@lists.webkit.org] on behalf of Brady Eidson > [beid...@apple.com] > > I think there are corporate/financial apps that would break if this was > policy. Any idea which? Joe ---

Re: [webkit-dev] Do we need a "webkitBackground" property for XMLHttpRequest?

> From: webkit-dev-boun...@lists.webkit.org > [webkit-dev-boun...@lists.webkit.org] on behalf of Adam Barth > [aba...@webkit.org] > > The network stack folks did a round of removing auth dialogs for > subresources a while back. I'm not sure why they didn't remove the > dialog from XHR. It's po

Re: [webkit-dev] Question related to license in WK2 EFL port

Thank you for your kind reply. My curiosities are solved. I will discuss which license we will use with my co-workers. Cheers, Gyuyoung. --- Original Message --- Sender : Kenneth Rohde Christiansen Date : 2012-07-25 18:46 (GMT+09:00) Title : Re: [webkit-dev] Question related to license

Re: [webkit-dev] Question related to license in WK2 EFL port

Hi, The license is basically up to the contributor, though there might be a few advantages using the BSD license. Using BSD licensed code means that the code can be re-factored in the future and parts can be moved into WebCore or elsewhere. If you use LGPL you have to make sure to not reuse the c

Re: [webkit-dev] WebKit memory instrumentation

On Tue, Jul 24, 2012 at 10:34 PM, Maciej Stachowiak wrote: > > On Jul 24, 2012, at 12:39 AM, Yury Semikhatsky wrote: > > > > On Tue, Jul 24, 2012 at 12:47 AM, Maciej Stachowiak wrote: > >> >> On Jul 23, 2012, at 8:09 AM, Yury Semikhatsky wrote: >> >> * >> >> First option we consider is to defi

Re: [webkit-dev] Do we need a "webkitBackground" property for XMLHttpRequest?

As I tested, the chromium Version 22.0.1217.0 (148296) shows auth dialogs for both XHR and sub-resources. Perhaps the changing has not been pushed to trunk !? On 07/25/2012 12:58 AM, Adam Barth wrote: > On Tue, Jul 24, 2012 at 9:28 AM, xuewen.wang > wrote: >> Do you know why the chromium has not