Re: [webkit-dev] Request for comments on some bindings generator patches

> On Jul 19, 2016, at 8:36 PM, Nikos Andronikos > wrote: > > https://bugs.webkit.org/show_bug.cgi?id=158830 > This patch stops the IDL preprocessor from looking for the IDL file at all, > and all is well. What about “option 2” from this bug? Why aren’t we

[webkit-dev] Request for comments on some bindings generator patches

Hey all, We’ve got some web animations related patches that are stalled waiting on feedback about options to update the bindings generator. There’s currently three patches waiting to be reviewed, one Web Animations, two binding generator fixes. Patch 1. Web Animations:

Re: [webkit-dev] Request for Comments: DoYouEvenBench

FYI, DoYouEvenBench has been renamed to Speedometer, and it's hosted at http://browserbench.org/Speedometer/ as noted in my blog post: https://www.webkit.org/blog/3395/speedometer-benchmark-for-web-app-responsiveness/ - R. Niwa On Wed, Sep 18, 2013 at 5:30 PM, Ryosuke Niwa rn...@webkit.org

Re: [webkit-dev] Request for Comments: DoYouEvenBench

Hi Ryosuke, It's awesome to see the results on the dashboard! I'll test DYEB later next week, and I'll also provide feedback. Thanks for putting this together! Cheers, Zoltan On Fri, Jan 17, 2014 at 12:43 PM, Ryosuke Niwa rn...@webkit.org wrote: I've finalized the benchmark and started making

Re: [webkit-dev] Request for Comments: DoYouEvenBench

I've finalized the benchmark and started making measurements on the perf bots. You can see results at https://perf.webkit.org/#mode=dashboard You can run the benchmark inside DRT/WTR using run-perf-tests: Tools/Scripts/run-perf-tests PerformanceTests/DoYouEvenBench/ To manually run, open

[webkit-dev] Request for Comments: DoYouEvenBench

Hi, I just added DoYouEvenBench, a new browser DOM benchmark, in http://trac.webkit.org/changeset/156073. This benchmark uses http://todomvc.com and emulates user actions: adding 100 todo items, completing them, and then deleting them with Ember.js, Backbone.js, jQuery, and plain-old DOM. I'm

Re: [webkit-dev] Request for comments

From: ext Maciej Stachowiak [mailto:[EMAIL PROTECTED] Sent: 14 August, 2008 21:19 To: Rainisto Jonni (Nokia-D/Tampere) Cc: webkit-dev@lists.webkit.org Subject: Re: [webkit-dev] Request for comments On Aug 13, 2008, at 6:37 AM, [EMAIL PROTECTED] wrote

Re: [webkit-dev] Request for comments

] Sent: 14 August, 2008 21:19 To: Rainisto Jonni (Nokia-D/Tampere) Cc: webkit-dev@lists.webkit.org Subject: Re: [webkit-dev] Request for comments On Aug 13, 2008, at 6:37 AM, [EMAIL PROTECTED] wrote: Hello

Re: [webkit-dev] Request for comments

, Jonni From: ext Maciej Stachowiak [mailto:[EMAIL PROTECTED] Sent: 14 August, 2008 21:19 To: Rainisto Jonni (Nokia-D/Tampere) Cc: webkit-dev@lists.webkit.org Subject: Re: [webkit-dev] Request for comments On Aug 13, 2008, at 6:37 AM, [EMAIL PROTECTED] wrote: Hello, I've been following the webkit

Re: [webkit-dev] Request for comments

On 2008-08-14, at 21:07, Jack Wootton wrote: I hope this signals a better start for Nokia. Before Nokia can submit anything back to the WebKit community they'll have to: [snip] Speaking as developer of WebKit, if Nokia wishes to resume contributing code to the WebKit project then they

Re: [webkit-dev] Request for comments

I think perhaps this depends on how you choose to categorise what has (not) happened to the s60 webkit port. I choose to view it at a company granularity, here's why: It is the same company, the same legal entity, the same policies, same guidelines, same work ethics etc. While you no doubt feel

Re: [webkit-dev] Request for comments

2008/8/14 Jack Wootton [EMAIL PROTECTED]: I think perhaps this depends on how you choose to categorise what has (not) happened to the s60 webkit port. I choose to view it at a company granularity, here's why: It is the same company, the same legal entity, the same policies, same guidelines,

Re: [webkit-dev] Request for comments

On Thu, Aug 14, 2008 at 11:02 AM, Kalle Vahlman [EMAIL PROTECTED] wrote: 2008/8/14 Jack Wootton [EMAIL PROTECTED]: I think perhaps this depends on how you choose to categorise what has (not) happened to the s60 webkit port. I choose to view it at a company granularity, here's why: It is the

Re: [webkit-dev] Request for comments

Wootton Cc: webkit-dev@lists.webkit.org; Rainisto Jonni (Nokia-D/Tampere) Subject: Re: [webkit-dev] Request for comments On 2008-08-14, at 21:07, Jack Wootton wrote: I hope this signals a better start for Nokia. Before Nokia can submit anything back to the WebKit community they'll have

Re: [webkit-dev] Request for comments

. Regards, Jonni -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ext Mark Rowe Sent: 14 August, 2008 12:23 To: Jack Wootton Cc: webkit-dev@lists.webkit.org; Rainisto Jonni (Nokia-D/Tampere) Subject: Re: [webkit-dev] Request for comments On 2008-08-14, at 21

Re: [webkit-dev] Request for comments

On Thu, Aug 14, 2008 at 11:33 AM, Kalle Vahlman [EMAIL PROTECTED] wrote: 2008/8/14 Jack Wootton [EMAIL PROTECTED]: On Thu, Aug 14, 2008 at 11:02 AM, Kalle Vahlman [EMAIL PROTECTED] wrote: 2008/8/14 Jack Wootton [EMAIL PROTECTED]: I think perhaps this depends on how you choose to categorise

Re: [webkit-dev] Request for comments

On Aug 13, 2008, at 6:37 AM, [EMAIL PROTECTED] wrote: Hello, I've been following the webkit-dev list for a while now, and I though that it might be good time to introduce myself and the project that we have been working on with a small team. First some general high level introduction

Re: [webkit-dev] Request for comments

Hi Jack, On Aug 14, 2008, at 2:07 AM, Jack Wootton wrote: I hope this signals a better start for Nokia. Before Nokia can submit anything back to the WebKit community they'll have to: I understand that you may be frustrated by Nokia's absence for some time from mainline WebKit development.

Re: [webkit-dev] Request for comments

On Aug 14, 2008, at 11:23 AM, Maciej Stachowiak wrote: Hi Jack, On Aug 14, 2008, at 2:07 AM, Jack Wootton wrote: I hope this signals a better start for Nokia. Before Nokia can submit anything back to the WebKit community they'll have to: I understand that you may be frustrated by