So what is the process then if you have a blog ready to post? Just get one
person to review?
On 2 ʻAok 2010, at 9:02 PM, Maciej Stachowiak wrote:
I agree that it would be good to have more useful and interesting content. I
don't think it's good to do this by forcing the task on new
This is not the right mailing list for such questions. Please see
http://webkit.org/contact.html
On Tue, Aug 3, 2010 at 4:26 AM, Andrew Sealy-Bell
andyamsterdam2...@gmail.com wrote:
Hi,
I'd like to know if anybody has experience with rendering a PDF on an HTML5
canvas? I'd like to to this
http://build.webkit.org/builders/Leopard%20Intel%20Release%20(Tests)
We lost the slave over 3 days ago. :(
(The tree is also generally on fire right now...)
-eric
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
Hi,
There is a performance hit when using HTML canvas when using
ImageBufferCairo:
- As soon as something is rendered in the canvas, the
HTMLCanvasElement::willDraw method is called which in turn calls clearImage
on the imageBuffer if one is already present.
- When the render tree is traversed
On Mon, Aug 2, 2010 at 9:40 AM, Darin Fisher da...@chromium.org wrote:
On Mon, Aug 2, 2010 at 7:33 AM, Dan Bernstein m...@apple.com wrote:
On Aug 2, 2010, at 4:28 AM, Alexey Proskuryakov wrote:
29.07.2010, в 10:59, Darin Adler написал(а):
The directory should be eventually be named
I don’t buy in to this at all. We have done many successful renaming projects
in the past. The future is bigger than the past and it’s worthwhile to do
maintenance like this.
-- Darin
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
On Tue, Aug 3, 2010 at 1:27 PM, Darin Adler da...@apple.com wrote:
I don’t buy in to this at all. We have done many successful renaming projects
in the past. The future is bigger than the past and it’s worthwhile to do
maintenance like this.
Okie.
- a
Looks like the slave is back now.
But there are ~90 pending builds:
http://build.webkit.org/builders/Leopard%20Intel%20Release%20(Tests)
For future reference, I'm curious if it is safe to cancel some older builds
so that it will catch up.
On Tue, Aug 3, 2010 at 11:37 AM, Eric Seidel
Yes its safe to cancel old builds. The only danger is that it is
harder to track regressions. But caught-up builders missing a few
builds are more useful than behind ones. :)
On Tue, Aug 3, 2010 at 1:36 PM, Tony Gentilcore to...@chromium.org wrote:
Looks like the slave is back now.
But there
This would probably have to be verified, but I believe CG uses copy-on-write
semantics when creating an image from a bitmap context. Therefore I suspect
this is not a performance problem with CG just because of smarts in the
underlying CG implementation. Basically image() is a cheap call for
At the editing meeting at the WebKit conference in April, we discussed the
idea of coming up with a replacement to Position/Range, using that
throughout the editing code and then eventually exposing that API to the web
to supersede DOM Ranges. Specifically, the idea was to get rid of
node/offset
On Aug 3, 2010, at 4:32 PM, Ojan Vafai wrote:
Pros:
-Ensures that the APIs we expose to the web are at least good enough for our
own editing code
-Ensures that editing code never crashes (outside of JSC/V8 bugs)
-Gives a clean slate for starting the editing code anew
-Moves code out of
On Aug 3, 2010, at 4:32 PM, Ojan Vafai wrote:
At the editing meeting at the WebKit conference in April, we discussed the
idea of coming up with a replacement to Position/Range, using that throughout
the editing code and then eventually exposing that API to the web to
supersede DOM Ranges.
Some of us had a somewhat crazy idea to rewrite much of the editing code
(e.g. document.execCommand) in JavaScript.
Pros:
-Ensures that the APIs we expose to the web are at least good enough for our
own editing code
I don't think this necessarily follows. Not everything exposed to the
Resent from the proper address:
On Tue, Aug 3, 2010 at 6:00 PM, Martin Robinson
martin.james.robin...@gmail.com wrote:
I notice that Qt added imageForRendering() and felt they could not use
image() for some reason. I'd be curious if a Qt expert could weigh in on
that, since maybe with a
It was down for the last 36 hours due to Leopard bustage and moving
machines. It's back up and running again now. Apologies for (my
part) of the trouble.
http://queues.webkit.org/queue-status/commit-queue
-eric
___
webkit-dev mailing list
16 matches
Mail list logo
