Re: [webkit-dev] PAL Strategy

2017-05-01 Thread Maciej Stachowiak
> On May 1, 2017, at 1:48 PM, Brady Eidson wrote: > > >> On May 1, 2017, at 12:41 PM, Michael Catanzaro wrote: >> >> I thought the original intent for PAL was to replace WebCore/platform, so I >> assume the criterion would be "stuff currently in WebCore/platform." If not, >> then I'd quest

Re: [webkit-dev] PAL Strategy

2017-05-01 Thread Brady Eidson
> On May 1, 2017, at 12:41 PM, Michael Catanzaro wrote: > > I thought the original intent for PAL was to replace WebCore/platform, so I > assume the criterion would be "stuff currently in WebCore/platform." If not, > then I'd question the value of having PAL at all, as we really don't need a

Re: [webkit-dev] PAL Strategy

2017-05-01 Thread Michael Catanzaro
I thought the original intent for PAL was to replace WebCore/platform, so I assume the criterion would be "stuff currently in WebCore/platform." If not, then I'd question the value of having PAL at all, as we really don't need a separate PAL on top of the platform abstraction library we already

[webkit-dev] PAL Strategy

2017-05-01 Thread Olmstead, Don
Hey all, As we mentioned during the contributors meeting we want to work towards fleshing out the PAL library. We have the cycles to really start rolling on it but are hitting some issues we wanted to run by the community. Currently the obvious stuff to move over into PAL, network, graphics and