On Feb 3, 2013, at 8:18 PM, Mike Lawther wrote:
> Hi Maciej!
>
> On 31 January 2013 11:15, Maciej Stachowiak wrote:
> It's far simplest for us if:
> (a) There is an Xcode project (or a Makefile) that builds the Mac port
> checked in to source control.
> (b) The generated project invokes only
Hi Maciej!
On 31 January 2013 11:15, Maciej Stachowiak wrote:
> It's far simplest for us if:
> (a) There is an Xcode project (or a Makefile) that builds the Mac port
> checked in to source control.
> (b) The generated project invokes only tools that are part of the default
> Mac OS X install.
>
03.02.2013, в 11:46, Adam Barth написал(а):
> Yeah, another example is ResourceHandle, which is theoretically a
> platform-agnostic abstraction but in reality is heavily constrained by
> the capabilities of CFNetwork.
Can you please give some examples of where we are constrained by this? Perhap
On 2/3/13 11:12 PM, "ext Maciej Stachowiak" wrote:
>> Maybe the problem is less about the WK1 API layer and more about
>> WebCore/platform.
>
>I'm sure that's one problem, but I am still curious what Eric had in mind.
Yes, me too, and I don't mean to hijack that conversation :)
>> In many othe
On Feb 3, 2013, at 11:58 AM, Adam Barth wrote:
> On Sun, Feb 3, 2013 at 11:46 AM, Adam Barth wrote:
>>
>> Yeah, another example is ResourceHandle, which is theoretically a
>> platform-agnostic abstraction but in reality is heavily constrained by
>> the capabilities of CFNetwork.
>
> To be pre
On Feb 3, 2013, at 11:34 AM, noam.rosent...@nokia.com wrote:
>
>
> On 2/3/13 7:46 PM, "ext Maciej Stachowiak" wrote:
>
>> If you're asking about phasing it out entirely, we don't have any
>> immediate plans to deprecate or remove the WebKit1 mac API. There are
>> quite a few Apple and third-p
OK, this sounds fantastic. And I've noticed how much faster Chromium
incrementally builds using ninja when I've done that.
So, ignoring the discussion of a single build system for a moment, how
can I, as a developer using the OS X + WK2 port, living mostly
in Xcode for editing and debugging, use n
On Sun, Feb 3, 2013 at 11:46 AM, Adam Barth wrote:
> On Sun, Feb 3, 2013 at 11:34 AM, wrote:
>> On 2/3/13 7:46 PM, "ext Maciej Stachowiak" wrote:
>>>If you're asking about phasing it out entirely, we don't have any
>>>immediate plans to deprecate or remove the WebKit1 mac API. There are
>>>quit
On Sun, Feb 3, 2013 at 11:34 AM, wrote:
> On 2/3/13 7:46 PM, "ext Maciej Stachowiak" wrote:
>>If you're asking about phasing it out entirely, we don't have any
>>immediate plans to deprecate or remove the WebKit1 mac API. There are
>>quite a few Apple and third-party apps using it, and WebKit2 i
On 2/3/13 7:46 PM, "ext Maciej Stachowiak" wrote:
>If you're asking about phasing it out entirely, we don't have any
>immediate plans to deprecate or remove the WebKit1 mac API. There are
>quite a few Apple and third-party apps using it, and WebKit2 is not even
>public API on Mac OS X currently
On Feb 2, 2013, at 10:44 PM, Eric Seidel wrote:
> On Wed, Jan 30, 2013 at 1:57 PM, Maciej Stachowiak wrote:
>>
>>> I wish WebCore was not trapped by Mac WebKit1’s legacy designs.
>>>
>>> WebKit2 is obviously a step towards the future. But until we can kill the
>>> Widget tree, the insanely f
11 matches
Mail list logo
