On Tue, Jan 29, 2013 at 11:58 PM, Maciej Stachowiak m...@apple.com wrote:
I agree that the regression should be fixed. But before we discuss that...
I am puzzled by the apparent stance of Alexey must immediately fix this
himself or we must revert immediately. That's not the standard we have
Hi Maciej, Thanks for your attention!
For reference: will the feature flag be comprehensive, or will parts of
the implementation/scaffolding be outside the ifdef?
It should be comprehensive. So it will.
Although some trivial inline stubs, like just returning null or false, or
even doing
On Jan 30, 2013, at 12:21 AM, Adam Barth aba...@webkit.org wrote:
On Tue, Jan 29, 2013 at 11:58 PM, Maciej Stachowiak m...@apple.com wrote:
I agree that the regression should be fixed. But before we discuss that...
I am puzzled by the apparent stance of Alexey must immediately fix this
Hello!
This is just a friendly heads-up that the Mac specific parts of WebKit2 will
soon start requiring C++11 features (move semantics and variadic templates
being the two most important).
Any recent version of Xcode (4.2 or later) should support this, and we're
already building all of
The future! Is now! :)
Very exciting. I hope some day we can use C++11 for the rest of WebCore too.
On Wed, Jan 30, 2013 at 12:17 PM, Anders Carlsson ander...@apple.com wrote:
Hello!
This is just a friendly heads-up that the Mac specific parts of WebKit2 will
soon start requiring C++11
Thanks for the advance warning! :)
- E
On Wed, Jan 30, 2013 at 3:17 PM, Anders Carlsson ander...@apple.com wrote:
Hello!
This is just a friendly heads-up that the Mac specific parts of WebKit2
will soon start requiring C++11 features (move semantics and variadic
templates being the two
*I wish we only had one build system (it were easy to add/remove/move
files).*
*
I believe changes like http://trac.webkit.org/changeset/74849 are an
unhealthy sign for the project. Adam is not the only person who has chosen
to empty files instead of removing them. The pain of updating 8 build
Thanks for sharing this.
On Jan 30, 2013, at 1:28 PM, Eric Seidel e...@webkit.org wrote:
I wish we only had one build system (it were easy to add/remove/move files).
I believe changes like http://trac.webkit.org/changeset/74849 are an
unhealthy sign for the project. Adam is not the only
Hi Eric,
These are great thoughts. I agree with you on all points. One informative
comment below:
On Jan 30, 2013, at 1:28 PM, Eric Seidel e...@webkit.org wrote:
I wish we only had one build system (it were easy to add/remove/move files).
I believe changes like
Hi Eric,
On Wed, Jan 30, 2013 at 10:28 PM, Eric Seidel e...@webkit.org wrote:
I wish we didn’t have to worry about platforms we couldn’t test.
It can’t be the job of the core maintainers to care about all the peripheral
ports which contribute very little core code. Our code needs to be
On Wed, Jan 30, 2013 at 1:28 PM, Eric Seidel e...@webkit.org wrote:
*
I wish I felt like reviewers understood/trusted each other more.
*
*I’ve worked at both Apple and Google. The WebKit community is full of
brilliant engineers. Yet I frequently feel a lack of trust in my (or
others)
Hi,
Am 30.01.2013 um 22:28 schrieb Eric Seidel:
I wish we only had one build system (it were easy to add/remove/move files).
I've created CMake files for two different ports at [1] and [2] already, but
did't get positive feedback from the port-maintainer. So I stopped working on
it. If any
On Wed, Jan 30, 2013 at 1:50 PM, Filip Pizlo fpi...@apple.com wrote:
Thanks for sharing this.
On Jan 30, 2013, at 1:28 PM, Eric Seidel e...@webkit.org wrote:
I wish we only had one build system (it were easy to add/remove/move files).
I believe changes like
Hi,
I'd like to delete all the ENABLE(WEB_INTENTS) code. As far as I know,
nobody ever shipped this and nobody intents to. Please speak up if
you'd like that code to stick around.
Nico
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
On Jan 30, 2013, at 3:24 PM, Dirk Pranke dpra...@chromium.org wrote:
On Wed, Jan 30, 2013 at 1:50 PM, Filip Pizlo fpi...@apple.com wrote:
Thanks for sharing this.
On Jan 30, 2013, at 1:28 PM, Eric Seidel e...@webkit.org wrote:
I wish we only had one build system (it were easy to
Hi !
I'd also like to add that I think a key related issue to common build
system is common feature configuration. The many different ways ports
control their feature flags is super confusing. I've long wanted to
implement common configuration management, but have not had time.
I think
Hello,
I would like to let you know that I plan to add support for the FontLoader
interface to WebCore. It provides ways to detect font loading is actually
occurred and when the loading finished.
The spec is here:
http://dev.w3.org/csswg/css3-fonts/#font-load-events
Here is the tracking bug:
On Jan 30, 2013, at 5:46 PM, Laszlo Gombos laszlo.gom...@gmail.com wrote:
Hi !
I'd also like to add that I think a key related issue to common build
system is common feature configuration. The many different ways ports
control their feature flags is super confusing. I've long wanted
On Thu, Jan 31, 2013 at 1:15 AM, Maciej Stachowiak m...@apple.com wrote:
On Jan 30, 2013, at 3:24 PM, Dirk Pranke dpra...@chromium.org wrote:
On Wed, Jan 30, 2013 at 1:50 PM, Filip Pizlo fpi...@apple.com wrote:
Thanks for sharing this.
On Jan 30, 2013, at 1:28 PM, Eric Seidel
On Wed, Jan 30, 2013 at 10:28 PM, Eric Seidel e...@webkit.org wrote:
I wish it were easy to work on feature branches.
We have no good solution for features. For one-patch features, you do them
on your own. For larger, you maybe use github or most likely you just land
on trunk behind a
20 matches
Mail list logo
