Break up core.js

Most of the “browser” part of the Exokit browser is in core.js.

There is no good reason for it being contained in one file; it’s convenient but it makes the code seem scarier than it is to newcomers.

core.js should already have a reasonably coherent layout and factoring; we just need to classify the pieces and break them up into their own files that are required in.

A lot of this is just copy-paste.

File/directory sections

This is a rough idea for the files/directories we’d probably want:

• Network
• GL
• Audio
• Video
• Canvas
• Scripting contexts
• VR
• XR
• Magic Leap
• Leap Motion
• Events
• DOM
• Observers
• Window
• Document
• Bootstrap
• Runtime loop/queues

[ngokevin]

Yeah, after I dig in a bit and get set up, I think I’d get to playing with some unit tests.

[ngokevin]

Thanks for filing! I haven’t started working on the project or anything but benefits of splitting up IMO could be:

• Being able to see what parts of the codebase were changed in Git (imagine core.js ++500 additions --250 deletions versus vr.js +250 additions, xr.js +200 additions).
• Not having to jump up and down a single file when editing multiple parts of it.
• Easier to unit test individual modules.
• Split out and organize parts of the code to make it easier to find things (e.g., what parts run in a window worker and what parts doesn’t).
• Easier to avoid Git conflicts during large refactors.

When reading core.js, I’m not sure what’s contained inside it or what structure it has without reading the whole thing but would be easier to get a picture if I could see as directories + files. Plus your username is @modulesio 😃