Re: dom/ and content/ source reorganization

On 1/22/09 6:24 PM, Jonas Sicking wrote:
> Benjamin Smedberg wrote:
>> On 1/20/09 7:38 PM, Jonas Sicking wrote:
>>
>>>> 3) Use the following other directories:
>>> Don't really think the following deserve their own directories
>>>
>>> dom/json
>>
>> I can merge this into dom/window
> 
> Why dom/window? It's not window related at all. I'd say dom/base

It is a property of the DOM window object.

>>> dom/offline  (don't feel strongly here)
>>> dom/storage  (don't feel strongly here either)
>>
>> I can merge either/both of these with dom/window
> 
> Hmm.. why this facination with dom/window? I would have expected that it
> would only do the window objects, and maybe a couple supporting
> dom-level-0 objects like window.location and window.navigator?

Also because it is a global property off the DOM window object. I think
dom/base should be shared code for nodes/documents or utility code.

> Ok, so the structure will be something like:
> 
> dom/X/         (cpp, h and idl files go in here)
> dom/X/tests/   (mochitests, crashtests, reftests go in here)
> dom/locales/en-US/

Yes.

> dom/res/

Not sure I want to keep res/... I think the resources will probably live
with the code that uses them. But I haven't dealt with any of these yet.

--BDS