Hi
All
Dear Nilesh Patil it can really be a good help if you share u'r experience
with us.After working on webkit for 2 years u can share the basic flow of
code to us and basic architecture block diagrams, this can be a grt help for
the beginners, who are jst joining the developer community.
Hi
all
I have few links and pdf files which I would like to share with the
developers which can help us in comming up with architecture design.
By the way I have successfully compiled webkit for X11, Now trying for
directFb so pls help with this as well.
I would like to share are
1)
Are there any new comments about this issue? I am blocked by this issue, any
help will be appreciated.
Thanks
Peng
- 原文 -
From: yyp...@sohu.com
Subject:回复: Re: [webkit-dev] Building Win32/Release WebKit: linker error LNK1106
Thanks, Brent:
The disk has more than 18GB free space
I'm a beginner to WebKit domain(linux qt platform). I'm try to understand
how to port another JavaScript Engine to webKit as chrome did.
Now I'm confused by the code of *webcore/binding/js*, I found the function
defined in webcore/bindings/js/*Custom*.cpp never be used when debugging
the webkit
I'm a beginner to WebKit domain(linux qt platform). I'm try to understand
how to port another JavaScript Engine to webKit as chrome did.
Read http://webkit.org/contact.html, your question is in the wrong list.
--
Ariya Hidayat, Software Engineer
Qt Software, Nokia Devices RD
On Jul 31, 2009, at 3:05 AM, lin ma wrote:
I'm a beginner to WebKit domain(linux qt platform). I'm try to
understand how to port another JavaScript Engine to webKit as chrome
did.
Now I'm confused by the code of webcore/binding/js, I found the
function defined in
Hello.
I have two WebKit sourcetrees. One that shows a simple Gtk+ window and
displays the page. Besides that the page gets painted onto a cairo
source which I save to a PNG image. The image correctly shows the
page.
The other source tree is the same as the first but now I don't show
the Gtk+
On Jul 31, 2009, at 4:37 AM, yyp...@sohu.com wrote:
Are there any new comments about this issue? I am blocked by this
issue, any help will be appreciated.
This looks like another instance of https://bugs.webkit.org/show_bug.cgi?id=19743
. The problem is not due to disk space; the linker is
After a discussion this morning about the potential for parallel CSS
layout with Erik Aarvidson, he pointed out a group at Berkeley doing
research in this area:
http://www.eecs.berkeley.edu/~lmeyerov/projects/pbrowser/
The bits that jumped out to me were:
* the source is available [0]
On Jul 31, 2009, at 2:59 PM, Alex Russell wrote:
After a discussion this morning about the potential for parallel CSS
layout with Erik Aarvidson, he pointed out a group at Berkeley doing
research in this area:
http://www.eecs.berkeley.edu/~lmeyerov/projects/pbrowser/
I think Dave Hyatt
Adding Leo to the thread. Leo works down the hall from me.
Adam
On Fri, Jul 31, 2009 at 11:59 AM, Alex Russellslightly...@chromium.org wrote:
After a discussion this morning about the potential for parallel CSS
layout with Erik Aarvidson, he pointed out a group at Berkeley doing
research in
On Fri, Jul 31, 2009 at 12:08 PM, Adam Roben aro...@apple.com wrote:
On Jul 31, 2009, at 2:59 PM, Alex Russell wrote:
After a discussion this morning about the potential for parallel CSS
layout with Erik Aarvidson, he pointed out a group at Berkeley doing
research in this area:
I think parallel layout is an interesting topic to explore, in light
of where CPUs are going. We probably can't use code in Cilk++
directly, but there might be useful ideas. It also seems to me from
their paper that they are only handling some of the more basic aspects
of CSS layout so
Hi folks,
Adam Treat, David Levin, Jakob Petsovits, Kenneth Rohde Christiansen, and I
have been working on ./WebKitTools/Scripts/check-webkit-style to check code
for WebKit style violations. Let me introduce the tool to you.
Simply, check your current patch by running the tool:
%
Thanks, Adam.
Yes, I have run the update-webkit before every build process, so i think the
version should be the newest. I saw the fix happened on April, so i think the
current version i am using should include this fix. Or need I patch the fix
seperately?
Thanks
Peng
- 原文 -
681.70s total testing time
That's 11.5 minutes for every patch I want to land.
(because I run the layout tests before landing anything, as part of
bugzilla-tool).
I'm very interested in any suggestions folks have to make that number
smaller. I know Chromium runs the layout tests in parallel
16 matches
Mail list logo
