Hi there,
I'm making enhancements to EWebLauncher the ewk backend
on a low end mips box.
A colleague of mine is disappointed that the screen
goes blank for several seconds before displaying
more complex pages like bbc news.#
What we would like to be able to do is leave the old
page on the screen
On Jun 8, 2011, at 11:48 AM, Peter Kasting wrote:
On Tue, Jun 7, 2011 at 11:18 PM, Maciej Stachowiak m...@apple.com wrote:
1) We definitely have consensus to fix the broken non-logically-const
accessors by making them non-const; consensus on also adding const accessors
is less clear.
On Jun 9, 2011, at 2:29 AM, D.J. Barrow wrote:
Hi there,
I'm making enhancements to EWebLauncher the ewk backend
on a low end mips box.
A colleague of mine is disappointed that the screen
goes blank for several seconds before displaying
more complex pages like bbc news.#
What we would
On Thu, Jun 9, 2011 at 2:49 AM, Maciej Stachowiak m...@apple.com wrote:
I'm not really convinced that casting away const from a return value is
intrinsically safer than casting away const from this.
Allowing the caller to mutate the return value is fine because the caller
had a non-const
On Mon, Jun 6, 2011 at 11:13 AM, Ademar Reis ademar.r...@openbossa.org wrote:
On Sun, Jun 5, 2011 at 2:03 AM, Eric Carlson eric.carl...@apple.com wrote:
On Jun 3, 2011, at 2:30 PM, Adam Barth wrote:
Either (1) or (2) is fine. Please pick one and do it. The status quo
is very annoying.
Hello,
I don't know if this is the right forum to ask this question. If it isn't
I'd appreciate any pointers to where I should be asking this:
I would like to build WebKit with Intel Compiler (ICC) and was wondering if
this has been already done or if anyone has pointers on what would be the
I don't think we should do this. EventTarget is really just an abstract
interface, and changing its implementation globally is of limited utility.
-Sam
On Jun 8, 2011, at 5:54 PM, Dominic Cooney wrote:
[If you don't care about JSC or V8 bindings you can safely ignore
this.]
TL;DR I want
Why should we implement this spec? We already have one flex box implementation
that we can never remove (and corresponds closely to Firefox's) so it seems to
me that we should work on standardizing that model. Adding a large bunch of
code that duplicates existing functionality seems foolish.
On Thu, Jun 9, 2011 at 1:19 PM, Sam Weinig wei...@apple.com wrote:
Why should we implement this spec? We already have one flex box
implementation that we can never remove (and corresponds closely to
Firefox's) so it seems to me that we should work on standardizing that
model. Adding a large
On Thu, Jun 9, 2011 at 3:51 PM, Maciej Stachowiak m...@apple.com wrote:
In principle, the return value could have been retrieved from a container
that the immediate callee only has a const reference to. So then casting
away const on the return value would be a hazard.
You're right; if the
(Resending from correct email)
For HTML5 canvas animations, painting speed is very significant.
Android uses a retain mode rendering approach as well; where paint
operations are recorded on a WebCore thread and painting is actually done on
the UI thread. It isn't necessarily the best approach.
I don't have a personal opinion on which way is technically better myself. But
I think the key is getting our code aligned with where standards are going,
wether by changing he code or the standards. EventTarget in the prototype chain
seems neither especially awesome nor especially terrible to
On Jun 9, 2011, at 3:00 PM, Tony Chang wrote:
On Thu, Jun 9, 2011 at 1:19 PM, Sam Weinig wei...@apple.com wrote:
Why should we implement this spec? We already have one flex box
implementation that we can never remove (and corresponds closely to
Firefox's) so it seems to me that we should
On 6/9/2011 8:24 PM, Pierre-Antoine LaFayette wrote:
Android uses a retain mode rendering approach as well; where paint
operations are recorded on a WebCore thread and painting is actually
done on the UI thread. It isn't necessarily the best approach. But I
suppose it depends the platform
14 matches
Mail list logo
