On Mon, Dec 27, 2010 at 7:17 PM, Maciej Stachowiak wrote:
>
> On Dec 27, 2010, at 1:11 PM, Sam Weinig wrote:
>
>
>
> On Mon, Dec 27, 2010 at 11:14 AM, Adam Barth wrote:
>
>> > Is it really a good idea to move platform out of WebCore? Lots of stuff
>> > there seems quite WebCore related.
>>
>> Th
On Dec 27, 2010, at 1:11 PM, Sam Weinig wrote:
>
>
> On Mon, Dec 27, 2010 at 11:14 AM, Adam Barth wrote:
> > Is it really a good idea to move platform out of WebCore? Lots of stuff
> > there seems quite WebCore related.
>
> There seem to be a couple people who aren't sold on moving platform
>
On Dec 27, 2010, at 12:04 AM, Adam Barth wrote:
> Here's a snapshot of my current thinking on where the files and
> folders currently in the top-level directory might go.
>
> There are a bunch of build-system related files that are currently in
> the root. I'm not sure whether we should leave t
> I think moving Platform out from WebCore is great long term goal, but right
> now, there is simply too many layering violations for it to be feasible. For
> those curious, the intent is for nothing in Platform to be dependent on
> anything else in WebCore (eg. dom, html, rendering, loader), so so
On Mon, Dec 27, 2010 at 1:25 PM, Darin Adler wrote:
> On Dec 27, 2010, at 11:14 AM, Adam Barth wrote:
>> On Mon, Dec 27, 2010 at 10:37 AM, Mark Rowe wrote:
>>> Can someone also elaborate on why "Sources" was chosen as the top-level
>>> directory name rather than "Source"? "Source code" is a mass
On Dec 27, 2010, at 11:14 AM, Adam Barth wrote:
> On Mon, Dec 27, 2010 at 10:37 AM, Mark Rowe wrote:
>> Can someone also elaborate on why "Sources" was chosen as the top-level
>> directory name rather than "Source"? "Source code" is a mass noun so it's
>> unclear why the abbreviated form of "so
On Mon, Dec 27, 2010 at 11:14 AM, Adam Barth wrote:
> > Is it really a good idea to move platform out of WebCore? Lots of stuff
> > there seems quite WebCore related.
>
> There seem to be a couple people who aren't sold on moving platform
> out of WebCore. It sounds like we should hold off on do
Got it. I didn't notice that manual was a sub directory.
Kenneth
On Mon, Dec 27, 2010 at 8:14 PM, Adam Barth wrote:
> Thanks fora ll your feedback. Responses inline.
>
> On Mon, Dec 27, 2010 at 2:06 AM, Kenneth Rohde Christiansen
> wrote:
> > So we have PerformanceTests, RegressionTests and m
Thanks fora ll your feedback. Responses inline.
On Mon, Dec 27, 2010 at 2:06 AM, Kenneth Rohde Christiansen
wrote:
> So we have PerformanceTests, RegressionTests and manual. Why not
> ManualTests?
My thought process was that these are manual regression tests, just
like the HTTP tests are HTTP r
On 2010-12-27, at 10:19, Mark Rowe wrote:
>
> On 2010-12-27, at 00:04, Adam Barth wrote:
>
>> Here's a snapshot of my current thinking on where the files and
>> folders currently in the top-level directory might go.
>>
>> There are a bunch of build-system related files that are currently in
>>
On 2010-12-27, at 00:04, Adam Barth wrote:
> Here's a snapshot of my current thinking on where the files and
> folders currently in the top-level directory might go.
>
> There are a bunch of build-system related files that are currently in
> the root. I'm not sure whether we should leave them i
Like it. I only have a few questions:
* Where would the build (WebKitBuild) directory would go? Perhaps a Build/
would fit in the root directory.
* Some manual-tests belong to the regression tests, and some are belong to
the performance test. Would be good to separate them.
* I think the build rel
Hi all,
I have a question for Webkit designers.
Intro:
The Css specifications are easy to translate
in logic formulas. Every logical formula could be
expressed in the Event Condition Action form.
For example:
Event: parser finds a selector
Action: currentSelector = selector
Condition: true
-
Hi,
also thank you for leading the reorg.
Adam Barth:
> Here's a snapshot of my current thinking on where the files and
> folders currently in the top-level directory might go.
>
> There are a bunch of build-system related files that are currently in
> the root. I'm not sure whether we should
Hi, thank you for leading the reorg.
> Sources/
> automake/
> cmake/
> JavaScriptCore/
> JavaScriptGlue/
> Platform/ (was WebCore/platform)
I'd like to keep platform directory under WebCore if there is no strong reason.
Classes under WebCore/platform have WebCore namespace,
and the boundary
So we have PerformanceTests, RegressionTests and manual. Why not
ManualTests?
Is it really a good idea to move platform out of WebCore? Lots of stuff
there seems quite WebCore related.
Cheers
Kenneth
On Mon, Dec 27, 2010 at 9:04 AM, Adam Barth wrote:
> Here's a snapshot of my current thinking
Here's a snapshot of my current thinking on where the files and
folders currently in the top-level directory might go.
There are a bunch of build-system related files that are currently in
the root. I'm not sure whether we should leave them in there or move
them into Sources somewhere. I'm tempt
17 matches
Mail list logo