Hi,
What's the status of Webkit2? I've built the latest webkit version on
Windows with --webkit2 option and I see that there is only one process
shown in Task Manager irrespective of the number of Windows that I
open.
Reagrds,
Nayan.
On 4/13/10, Geoffrey Garen gga...@apple.com wrote:
Will I be
Date: Wed, 28 Apr 2010 16:40:14 +0530
From: naya...@gmail.com
To: gga...@apple.com
CC: webkit-dev@lists.webkit.org
Subject: Re: [webkit-dev] Announcing WebKit2
Hi,
What's the status of Webkit2? I've built the latest webkit version
On Wed, Apr 28, 2010 at 7:10 AM, Nayan naya...@gmail.com wrote:
Hi,
What's the status of Webkit2? I've built the latest webkit version on
Windows with --webkit2 option and I see that there is only one process
shown in Task Manager irrespective of the number of Windows that I
open.
Reagrds,
On Apr 9, 2010, at 2:40 AM, Xan Lopez wrote:
Another issue seems to be that parts of the public C API expose
CoreFoundation, which definitely would be an issue for the other
ports. I'm told on the side that this was just done as a quick
solution to have something running and that if there's
On Fri, Apr 9, 2010 at 2:33 AM, Adam Treat tr...@kde.org wrote:
On Thursday 08 April 2010 09:24:32 pm Darin Adler wrote:
On Apr 8, 2010, at 6:23 PM, Adam Treat wrote:
Can someone please point to the bug report and the forum where this
development was discussed by the greater WebKit
On Fri, Apr 9, 2010 at 2:47 AM, Xan Lopez x...@gnome.org wrote:
I suppose I could wait until you land the patches and see by myself, but:
- In the wiki you mention that one goal of the new framework is to
provide a stable C-based API. Is this meant as a public API for
WebKit, the same in all
On Apr 9, 2010, at 3:36 AM, Jeremy Orlow wrote:
I hope this post clarifies why the Chromium WebKit port is not
really a viable solution for our needs as it stands today.
It was _very_ helpful. Thanks for taking the time to explain it so
well. (It might be worth moving some of that
Hi!
Your wiki says:
DrawingArea - an abstraction for a cross-process drawing area. Multiple
drawing strategies are possible, the simplest is just a shared memory
bitmap.
Could you tell me more about it? I am working on a parallel painting
feature (GraphicsContext commands can be forwarded to
hi ,
why only multi-process and not multi-thread like android. It is useful for
mobile environments.
thanks,
Zaheer
On Fri, Apr 9, 2010 at 5:15 PM, Maciej Stachowiak m...@apple.com wrote:
On Apr 9, 2010, at 3:40 AM, Maciej Stachowiak wrote:
On Apr 9, 2010, at 3:36 AM, Jeremy Orlow wrote:
Hi,
It looks supporting multi-threaded model.
See WebProcessLauncher.mm for detail.
--
morita
On Fri, Apr 9, 2010 at 9:11 PM, zaheer ahmad zaheer@gmail.com wrote:
hi ,
why only multi-process and not multi-thread like android. It is useful for
mobile environments.
thanks,
Zaheer
On
On Friday 09 April 2010 06:24:51 am Maciej Stachowiak wrote:
Given what proportion of overall maintenance work on WebKit I done by
Apple, I don't think anyone is entitled to veto us adding a new API
Whaa? Who is talking about veto of Apple's work? Rather, I am suggesting
that it would have
Another issue seems to be that parts of the public C API expose
CoreFoundation, which definitely would be an issue for the other
ports. I'm told on the side that this was just done as a quick
solution to have something running and that if there's interest by
other ports in using this we'd
On Apr 8, 2010, at 5:58 PM, Maciej Stachowiak wrote:
- Does your new framework require any significant changes in WebCore?
Could you briefly summarize them?
No WebCore changes are required - it works with the existing WebCore.
Right now WebCore needs to be built with some different flags
On Apr 9, 2010, at 7:14 AM, Adam Treat wrote:
On Friday 09 April 2010 06:24:51 am Maciej Stachowiak wrote:
Given what proportion of overall maintenance work on WebKit I done by
Apple, I don't think anyone is entitled to veto us adding a new API
Whaa? Who is talking about veto of Apple's
On Apr 9, 2010, at 2:34 AM, Jeremy Orlow wrote:
On Fri, Apr 9, 2010 at 2:33 AM, Adam Treat tr...@kde.org wrote:
On Thursday 08 April 2010 09:24:32 pm Darin Adler wrote:
On Apr 8, 2010, at 6:23 PM, Adam Treat wrote:
Can someone please point to the bug report and the forum where this
On Fri, Apr 9, 2010 at 1:53 PM, Cameron Zwarich cwzwar...@webkit.org wrote:
We seem to welcome pretty much any port that has an active maintainer.
IMHO, that's a good thing. I wonder if we should archive ports that
don't have an active maintainer (e.g., by moving them into a branch).
Adam
Which ports are considered unmaintained?
Kenneth
On Fri, Apr 9, 2010 at 6:03 PM, Adam Barth aba...@webkit.org wrote:
On Fri, Apr 9, 2010 at 1:53 PM, Cameron Zwarich cwzwar...@webkit.org wrote:
We seem to welcome pretty much any port that has an active maintainer.
IMHO, that's a good thing.
On Apr 9, 2010, at 2:03 PM, Adam Barth wrote:
On Fri, Apr 9, 2010 at 1:53 PM, Cameron Zwarich
cwzwar...@webkit.org wrote:
We seem to welcome pretty much any port that has an active
maintainer.
IMHO, that's a good thing. I wonder if we should archive ports that
don't have an active
On Apr 9, 2010, at 2:09 PM, Maciej Stachowiak wrote:
On Apr 9, 2010, at 2:03 PM, Adam Barth wrote:
On Fri, Apr 9, 2010 at 1:53 PM, Cameron Zwarich cwzwar...@webkit.org wrote:
We seem to welcome pretty much any port that has an active maintainer.
IMHO, that's a good thing. I wonder if
On Friday 09 April 2010 02:11:33 pm Maciej Stachowiak wrote:
There were in fact bugs opened with patches attached, and webkit-dev
was notified before any of the patches were committed afaik. However,
Indeed, but the post to webkit-dev had no link to the patches and no time was
given for anyone
On Friday 09 April 2010 04:53:31 pm Cameron Zwarich wrote:
In the past we have accepted the Chromium port despite it having a new JS
engine, new DOM bindings, an overreaching catch-all #ifdef for unrelated
changes, numerous layering violations, and seemingly unnecessary changes
or replacements
On Fri, Apr 9, 2010 at 2:36 PM, Darin Fisher da...@chromium.org wrote:
On Fri, Apr 9, 2010 at 1:53 PM, Cameron Zwarich cwzwar...@webkit.orgwrote:
On Apr 9, 2010, at 2:34 AM, Jeremy Orlow wrote:
On Fri, Apr 9, 2010 at 2:33 AM, Adam Treat tr...@kde.org wrote:
On Thursday 08 April 2010
On Apr 9, 2010, at 2:13 PM, Adam Treat wrote:
On Friday 09 April 2010 02:11:33 pm Maciej Stachowiak wrote:
the new piece of tech really is just a new API layer for the Mac
and
Win ports. We are interested in other people being able to reuse this
technology, but fundamentally, this is an
Hello everyone,
This is a heads-up that we will shortly start landing patches for a new WebKit
framework that we at Apple have been working on for a while. We currently call
this new framework WebKit2.
WebKit2 is designed from the ground up to support a split process model, where
the web
On Thu, Apr 8, 2010 at 3:01 PM, Anders Carlsson ander...@apple.com wrote:
Hello everyone,
This is a heads-up that we will shortly start landing patches for a new
WebKit framework that we at Apple have been working on for a while. We
currently call this new framework WebKit2.
WebKit2 is
On Thu, Apr 8, 2010 at 4:25 PM, Gustavo Sverzut Barbieri
barbi...@profusion.mobi wrote:
On Thu, Apr 8, 2010 at 3:01 PM, Anders Carlsson ander...@apple.com
wrote:
Hello everyone,
This is a heads-up that we will shortly start landing patches for a new
WebKit framework that we at Apple
On Fri, Apr 9, 2010 at 1:01 AM, Anders Carlsson ander...@apple.com wrote:
Hello everyone,
This is a heads-up that we will shortly start landing patches for a new
WebKit framework that we at Apple have been working on for a while. We
currently call this new framework WebKit2.
WebKit2 is
On Apr 8, 2010, at 5:47 PM, Xan Lopez wrote:
- In the wiki you mention that one goal of the new framework is to provide a
stable C-based API. Is this meant as a public API for WebKit, the same in all
platforms (like JSC), or a stable internal API for embedders to use in order
to implement
On Apr 8, 2010, at 5:47 PM, Xan Lopez wrote:
I suppose I could wait until you land the patches and see by myself,
but:
- In the wiki you mention that one goal of the new framework is to
provide a stable C-based API. Is this meant as a public API for
WebKit, the same in all platforms (like
On Fri, Apr 9, 2010 at 2:52 AM, Darin Adler da...@apple.com wrote:
As I understand it, the goal is to have a C API that is suitable and works
well cross platform for all the many platform independent operations; it is
indeed analogous the one for JavaScriptCore in that respect.
When you
If its in a separate process, does Accessibility still work as expected?
On Apr 8, 2010, at 4:01 PM, Anders Carlsson wrote:
Hello everyone,
This is a heads-up that we will shortly start landing patches for a new
WebKit framework that we at Apple have been working on for a while. We
Hi,
Can someone please point to the bug report and the forum where this
development was discussed by the greater WebKit community?
Cheers,
Adam
On Thursday 08 April 2010 08:58:22 pm Maciej Stachowiak wrote:
On Apr 8, 2010, at 5:47 PM, Xan Lopez wrote:
I suppose I could wait until you land
On Apr 8, 2010, at 6:19 PM, Chris Fleizach wrote:
If its in a separate process, does Accessibility still work as
expected?
It does not yet work in this rough initial version, but it's certainly
our intent to make it work.
Cheers,
Maciej
On Apr 8, 2010, at 4:01 PM, Anders Carlsson
Great.
I think Google chrome has taken a similar approach and have had trouble making
accessibility work because of the inter-process separation, so when we come up
with a solution, maybe they can adopt as well.
On Apr 8, 2010, at 6:30 PM, Maciej Stachowiak wrote:
On Apr 8, 2010, at 6:19
On Thursday 08 April 2010 09:24:32 pm Darin Adler wrote:
On Apr 8, 2010, at 6:23 PM, Adam Treat wrote:
Can someone please point to the bug report and the forum where this
development was discussed by the greater WebKit community?
The time for that discussion is now. The forum is here.
I
Hi,
On Apr 8, 2010, at 4:01 PM, Anders Carlsson wrote:
Hello everyone,
This is a heads-up that we will shortly start landing patches for a new
WebKit framework that we at Apple have been working on for a while. We
currently call this new framework WebKit2.
Awesome! I can't wait to see
36 matches
Mail list logo
