Changes:

- Setup base project files under `./src`
- Setup Rollup bundling to Javascript as ES and CommonJS file formats
- Using unit testing from Typescript files instead of the Javascript files; maybe look at this later
- gitignore and npmignore files setup

Issues:

- No unit tests yet
- No engine running yet
- Very touchy for the type of module loading I'm using; need to look into different module loading

Comments:
- Need to look into CommonJS vs ES vs AMD module loading
- For my project, should I look into building this just as a web app, or look into building this to an Electron application as well?
- I have a lot of devDependencies, is there a way to start cutting these down?

Changes:

Added in documentation building with the 'npm run docs' command. Going to continue adding scripts to build the project, as I will eventually need to add in additional build steps for running the engine. Also updated the Rollup bundler to use Babel to compile from the projects target modules ESNext to CommonJS modules for consumption. This threw errors when running Mocha tests. I now have an environment variable being set by the 'unittest' script for the user.

Issues:

* None found at this time.

Comments:

None at this time.

Changes:

Updated Rollup to bundle files from ESNext to Javascript. Working on unit testing the engine to test running of the engine. Going to have to redesign and configure however. 

Issues:

* Still working on getting unit testing working
* Redesign of the engine needs to occur

Comments:

The engine needs to be redesigned. I'm debating between a static calling of the class or a variable to hold onto the object to check. Either way, also need to get the engine and each component to work separately for testing as well.

Changes:

Updated unit tests for the engine. Added DObject, GameObject, Component, and FlagComponent classes with test cases. Currently debugging and working on but would like to set a save point to continue working later. Working on GameObjects currently so that I test getting developer game files when deploying the engine to a new project. This will also be tested for when the developer compiles all the typescript files and deploys. This should be compiled through the engine when running.

Issues:

Unit test cases currently failing, working on solutions and implementations.

Comments:

Still working on the base engine to get it running and off the ground. Will As soon as some more base classes are in then I will work on bundling the package and running on Electron or Angular as a test.

Changes:

Added the GameWindow class. Should this have the direct link to the canvas or should the Render system 🤔? (I will ponder this). That said, this will be the container to the window (so maybe it should have all the udpate calls and such, but the renderer should touch it as well). Also added some documentation building to the `docs` folder now.

Issues:

The GameWindow class is going to take some working on to get right. Going to have to do some testing with how it will work with the render system.

Comments:

Add some prepublish scripts to build and deploy the documents. Maybe I can get a hook to a website for this? I don't know quite yet. Also going to have to get Travis-CI working sooner than later. Maybe those will be my tasks for tomorrow

Changes:

Added an initial version of the readme. I've looked at other project's readmes, and this is one of the best templates I've found. Going to bulid off of it for my project. More to come and be added, but would like an initial file.

Issues:

See previous commit 7cc6c9a.

Comments:

None

Changes:

Added an initial Travis-CI script to run unit tests

Issues:

None

Comments:

None

Changes:

Fixed Travis file to run master and develop branches only. Also added documentation pushing and building to Github Pages from the docs folder.

Issues:

None

Comments:

None

None

…e/base_engine

Changes:

[This should be an overall summary of changes to the project at least done in point-form. More detailed prose format is of course allowed. The point of the description is to provide detail of changes and why.]

Issues:

[Please provide a point-form description of issues. Then please submit a formal issue on the GitHub project. Issue guidelines are doucmented in the project Wiki.]

Comments:

[Other general comments you wish to add]

Changes:

The developer will need to use my engine within their project - being browser, Electron or Angular based (working on just browser/electron first). 

Issues:

- When trying to test Electron.BrowserWindow within Mocha test, running into an error where the BrowserWindow constructor is undefined. For now I have the test not running at all.

Comments:

Developers first setup their own project THEN use my application within it (install or download it). Going to have to do some major revisions, but I think the best thing to do is make a diagram explaining this in a system architecture diagram. Going to have to do some thinking over the next week on how to do this, but also just need to sit down and work when I get back on it.

Changes:

Added the CONTRIBUTING.md file to the project tree in ready to submit the first projects pull request.

Issues:

none

Comments:

none

* Building, unit testing, some base files

Changes:

- Setup base project files under `./src`
- Setup Rollup bundling to Javascript as ES and CommonJS file formats
- Using unit testing from Typescript files instead of the Javascript files; maybe look at this later
- gitignore and npmignore files setup

Issues:

- No unit tests yet
- No engine running yet
- Very touchy for the type of module loading I'm using; need to look into different module loading

Comments:
- Need to look into CommonJS vs ES vs AMD module loading
- For my project, should I look into building this just as a web app, or look into building this to an Electron application as well?
- I have a lot of devDependencies, is there a way to start cutting these down?

* Documentation building and compiling issues

Changes:

Added in documentation building with the 'npm run docs' command. Going to continue adding scripts to build the project, as I will eventually need to add in additional build steps for running the engine. Also updated the Rollup bundler to use Babel to compile from the projects target modules ESNext to CommonJS modules for consumption. This threw errors when running Mocha tests. I now have an environment variable being set by the 'unittest' script for the user.

Issues:

* None found at this time.

Comments:

None at this time.

* Compiling, unit testing and Rollup fixes

Changes:

Updated Rollup to bundle files from ESNext to Javascript. Working on unit testing the engine to test running of the engine. Going to have to redesign and configure however. 

Issues:

* Still working on getting unit testing working
* Redesign of the engine needs to occur

Comments:

The engine needs to be redesigned. I'm debating between a static calling of the class or a variable to hold onto the object to check. Either way, also need to get the engine and each component to work separately for testing as well.

* Added new engine files and unit testing

Changes:

Updated unit tests for the engine. Added DObject, GameObject, Component, and FlagComponent classes with test cases. Currently debugging and working on but would like to set a save point to continue working later. Working on GameObjects currently so that I test getting developer game files when deploying the engine to a new project. This will also be tested for when the developer compiles all the typescript files and deploys. This should be compiled through the engine when running.

Issues:

Unit test cases currently failing, working on solutions and implementations.

Comments:

Still working on the base engine to get it running and off the ground. Will As soon as some more base classes are in then I will work on bundling the package and running on Electron or Angular as a test.

* GameWindow and Documents

Changes:

Added the GameWindow class. Should this have the direct link to the canvas or should the Render system 🤔? (I will ponder this). That said, this will be the container to the window (so maybe it should have all the udpate calls and such, but the renderer should touch it as well). Also added some documentation building to the `docs` folder now.

Issues:

The GameWindow class is going to take some working on to get right. Going to have to do some testing with how it will work with the render system.

Comments:

Add some prepublish scripts to build and deploy the documents. Maybe I can get a hook to a website for this? I don't know quite yet. Also going to have to get Travis-CI working sooner than later. Maybe those will be my tasks for tomorrow

* Initial Readme

Changes:

Added an initial version of the readme. I've looked at other project's readmes, and this is one of the best templates I've found. Going to bulid off of it for my project. More to come and be added, but would like an initial file.

Issues:

See previous commit 7cc6c9a.

Comments:

None

* Travis-CI script

Changes:

Added an initial Travis-CI script to run unit tests

Issues:

None

Comments:

None

* Specifying branches for Travis-CI and uploading documentation

Changes:

Fixed Travis file to run master and develop branches only. Also added documentation pushing and building to Github Pages from the docs folder.

Issues:

None

Comments:

None

* Set theme jekyll-theme-merlot

* Updated travis.yml

* Added Travis-CI button

None

* 😕 Had to update mocha

* Updated package.json and tslint



Changes:

[This should be an overall summary of changes to the project at least done in point-form. More detailed prose format is of course allowed. The point of the description is to provide detail of changes and why.]

Issues:

[Please provide a point-form description of issues. Then please submit a formal issue on the GitHub project. Issue guidelines are doucmented in the project Wiki.]

Comments:

[Other general comments you wish to add]

* I finally get it 🔥

Changes:

The developer will need to use my engine within their project - being browser, Electron or Angular based (working on just browser/electron first). 

Issues:

- When trying to test Electron.BrowserWindow within Mocha test, running into an error where the BrowserWindow constructor is undefined. For now I have the test not running at all.

Comments:

Developers first setup their own project THEN use my application within it (install or download it). Going to have to do some major revisions, but I think the best thing to do is make a diagram explaining this in a system architecture diagram. Going to have to do some thinking over the next week on how to do this, but also just need to sit down and work when I get back on it.

* Contributing file added

Changes:

Added the CONTRIBUTING.md file to the project tree in ready to submit the first projects pull request.

Issues:

none

Comments:

none

Conventions

Changes:

Tested and used the engine in an electron application. There was a major issue with the babel configuration and not properly transpiling the code to commonjs. The app now runs while creating a new Entity child called Player in the electron application and prints the ID to the console (this was in a test project and is not setup or shown here). This is good as it means the engine can be installed and used as is which is great. Now I need to work on the engine to see if it can get which platform it's being used on.

Issues:

* Working on electron but not Angular2 or direct HTML5 canvas

Comments:

None.

* Fixed document building

Changes:

Fixed the documentation building and displaying. Will be merging this into master as well.

Issues:

Fixing issue #7 & addressing issue #10

Comments:

None.

Changes:

[This should be an overall summary of changes to the project at least done in point-form. More detailed prose format is of course allowed. The point of the description is to provide detail of changes and why.]

Issues:

[Please provide a point-form description of issues. Then please submit a formal issue on the GitHub project. Issue guidelines are doucmented in the project Wiki.]

Comments:

[Other general comments you wish to add]

Changes:

[This should be an overall summary of changes to the project at least done in point-form. More detailed prose format is of course allowed. The point of the description is to provide detail of changes and why.]

Issues:

[Please provide a point-form description of issues. Then please submit a formal issue on the GitHub project. Issue guidelines are doucmented in the project Wiki.]

Comments:

[Other general comments you wish to add]

…d pull requests. Fixed up now

Changes:

Added a .github/ folder for all templates as I did not know that Github had this feature originally. Fixed up some tests, and added a new component. There needs to be some work done, but I have some ideas on how to approach next.

Issues:

None at this time.

Comments:

I will be travelling the next 3 weeks and will not be updating my code. Currently my proposal needs to be submitted again and that will happen after I am back from my trip. This commit is to make sure that all my work the past 2 weeks (not that I touched it much after the first day) is saved.

Changes:

The Engine is now running. I have put in prompts to ensure that it can run in CLI. It runs out of sync as there is only the one system at the moment, but works.

Issues:

None.

Comments:

None.

Changes:

Travis CI now checks for TSLint to come back with no errors.

Issues:

Addresses issue #9 in the project.

Comments:

None.

Engine running, tests and GitHub additions

…npm file called tsuml that works by creating a UML of my project from a command line. Run tsuml --glob ./src/**/*.ts to create it

…e. Need to look at reconfiguring the engine to make sure the system is using the message system and run more tests.

…tomorrow

* Changed the DOjbect structrue and updated tests to reflect changes
* Updated the Entity structure and changed the test file to reflect the changes.
* Removed gamewindow test (not at that stage of the project)
* Removed message test; merged into messsagessytem test
* Removed system interface
* Updated issue template (addressing issue #22)

Current issues
* #21
* #17

Still working on this commit. Will upload when complete.

…l need to be pondered. I also am having an issue on how to setup the game loop. Should it be a web worker, or run on the main UI thread as it should be dependent on it for timing. Will be thinking this over for a bit. Tests currently fail. Consider looking at the game loop. Should I be utilizing my message system more?

…for connecting with the GameWindow, scenes and Electron, Browser

… time!

Changes:

Puppeteer has been added to the Unit Tests to check UI and in browser variables of the engine. So far Divine is "undefined" but that is what I'm working to fix. New tests can be run with `npm test` and `npm run-script unit-test` as Istanbul now gives a coverage mapping as well.
Mostly build tools were added in this commit. There is lot's of debugging to come.

Issues:

* "Divine" must be a global variable in the browser scope
* GameWindow is still not being populated as "document" is undefined.

Comments:

[Other general comments you wish to add]

Changes:

Puppetter has been added to the project for Chrome testing. This will allow me to check and see if the "users'" application is running in the browser. However, as much as I would like to continue this right now, I am not having the best time with it. Therefore, I am moving on to another part of the project, the renderer. 
Rollup was previously spitting out the wrong formatted files, that has been fixed to UMD and ES modules (named accordingly).

Issues:

* Puppetter not working. After this commit, the tests will be turned off until I return to them.

Comments:

This has been a long time working at this, and needs to be put aside until I can find some help in the matter. This will be saved on a separate branch labelled "feature/puppeteer"

Changes:

Note: browser should work for electron as well.
The engine now runs in browser! This will now allow me to see real time loading and rendering. This is a great step but should have been done weeks ago. Will continue working on this later. Next step is rendering.

Issues:

n/a

Comments:

The greatest power is often simple patience. Joseph E Cossman

…lease

Issue 39

This is a big merge of the message_system. From here I believe things should get easier, but time will tell...
---
* 🍺 Removed commitizen. Version control comes built into npm

* 👍 Finishing scripts and will work on the feature scene now. Going to stick to standards from here on out

* 0.1.0

* 0.2.0

* Major working feature (keep to 50 characters)

Changes:

* Added file: RELEASE_TEMPLATE.md
* Updated the coverage for nyc (Istanbul)
* Minor changes to NPM commands

Issues:

n/a

Comments:

Minor changes

* Base Engine startup

Changes:

[This should be an overall summary of changes to the project at least done in point-form. More detailed prose format is of course allowed. The point of the description is to provide detail of changes and why.]

Issues:

[Please provide a point-form description of issues. Then please submit a formal issue on the GitHub project. Issue guidelines are doucmented in the project Wiki.]

Comments:

Began writing subsystem class test files. Work on this later.

* aMajor working feature (keep to 50 characters)

Changes:

[This should be an overall summary of changes to the project at least done in point-form. More detailed prose format is of course allowed. The point of the description is to provide detail of changes and why.]

Issues:

[Please provide a point-form description of issues. Then please submit a formal issue on the GitHub project. Issue guidelines are doucmented in the project Wiki.]

Comments:

[Other general comments you wish to add]

* DObject extending MessageReceiver

Changes:

[This should be an overall summary of changes to the project at least done in point-form. More detailed prose format is of course allowed. The point of the description is to provide detail of changes and why.]

Issues:

[Please provide a point-form description of issues. Then please submit a formal issue on the GitHub project. Issue guidelines are doucmented in the project Wiki.]

Comments:

Tests failing at the moment

* DObjects extending MessageReciever interface

Changes:

DObject extending from MessageReciever
GameWindow circular dependency fixed
Continuing base engine creation.

Issues:

[Please provide a point-form description of issues. Then please submit a formal issue on the GitHub project. Issue guidelines are doucmented in the project Wiki.]

Comments:

[Other general comments you wish to add]

* SceneManager, Scene and Engine

Changes:

Engine now has a SceneManager and loads in the Scene for the Engine. The Engine loads the basic scene for now, but it is HARDSET in Engine.ts (in the start method). SceneManager runs in tests, and also tests the Engine's startup of the scene. Scene tests still need to be written.
Helper functions have been written to read/write JSON data in files. This needs to be tested to see if the engine is pulling the files locally. This also needs to be tested to be running in a developers environment (Electron, HTML, etc). Helper functions to write the Scenes to JSON files should be tested. The idea is that the the scene will be written and read on start/stop of the Engines running to aid with compilation. Helper functions currently have no tests. These need to be added in when possible.
Scene file basic JSON file needs to be written. How are scenes going to be read/written?

Issues:

* Tests currently fail
    * File reading/writing has been hanging tests

Comments:

* Add todo items in files to the GitHub Project
* Add issues that are currently in the system to the Issues section
* TravisCI .yml file has been updated

* 💤 Fixing vulnerabilities

* 💤 Going to bed. I can't work on this tonight. Mabye I'll have some cake 🍰 too

* Typescript Watch Working

Changes:

This will rebuild the library as a Rollup file each save. This will keep tests constant and concurrent. This will make testing in multiple environments much, much easier. Also a major feature of the engine implemented. This has been a long time coming and just has been slacked on.
Updated includes. Removed all default exports. Default exports are not
correct to use; see issue #28
[comment](#28 (comment))

Issues:

Test still aren't running...
Issue #16
Issue #28
Issue #11

Comments:

Major feature complete.

* Pinpointing fs issue in Rollup and plugins

Changes:

* Helper function error logging
* Error log codes
* Rollup config order

Issues:

Creating issue #37 at this moment. Commiting now for reference.

* 🍺 Saving for a reference point. Going to try and implement a Rollup config change

* Using prototypes for DObject messaging functions.

Changes:

As the title describes. Going to be using the engine to define
prototype functions and hopefully remove the circular dependency issue.
Testing is needed for DObject to test these functions.

Issues:

This is a continuation of issue #37

* 😪 File loading isn't happening tonight. Going to call it and go to bed "early"

* 🍺 Test's running again. Better prints for logging - COLORS! Continuing researching loading from file

* WebGL, MessageSystem and Assets

Changes:

Message system has had a major overhaul; lot's of errors failing because of this reason. WebGL is beginning to be added in as I need to start getting work done on this. I'm loading this in with three.js and my package size has skyrocketed. Such as it needs to be however. Asset loading is next to begin testing. I need to see if I can get an asset loading for scene files.

Issues:

Current project issues:
* Asset loading needs to happen fast.
* Message tests need to be fixed up again...
Current relevant  GitHub issues:
* #28
* #11

Comments:

Time crunch is real.

* Message system overhaul

Changes:

I have done a complete message system overhaul. As there was a lot of
circular dependency issues with the original system, I believe this may
be a soltuion. It still relies on an event based system, but it now also
has a priority cue order as well. To be included is a low, and urgent
cue, but this is to be implemented later - shouldn't be too bad as a
later task I have bigger fish to fry.
There is also an asset loader from the previous commit that will need to
be tested. This is the next priority item.
After asset loading testing is complete, triage is going to need to be
done on the rest of the project. Begin breaking down tasks and attacking
them head on.

Issues:

GitHub issues changed with this commit:
* #28: This commit will close issue #28 as the message system tests are
all working. The current failing tests are from the Engine itself.
* #11: An older issue that is more top level. I will reference this when
working on the physics engines' queue however, for now it can be closed.

Other issues:
* Currently the tests fail, going to have to continue debugging this
tomorrow.

* 0.3.0

* fixed broken link in README.md that didn't point to CONTRIBUTING.md

* fixed 2nd broken link in README.md that didn't point to CONTRIBUTING.md

* 💤 All Unit Test's are passing. Going to bed as this is enough work for the day. Look at merging this in as version 0.3.1 because there has been major changes to previous systems.

* 0.3.1

* 💤 Updated document generator. Note, the generator is not ouputting errorsystem.ts

* 💰 -m Should not have removed types

* If Engine.instance is undefined in Engine.shutdown(), throw a warning not an error. Calling shutdown on an undefined system should be silently handled

* 😫 Added Entity.getChild test. Adding to pull rquest

* 🍺 Updated travis.yml

* Addressing issue #44

* Addressing issue #44

* Addressing issue #44

* Update .travis.yml

* Update .travis.yml

* Update .travis.yml

* Update .travis.yml

* Update .travis.yml

* Update .travis.yml

* Update .travis.yml

* Update .travis.yml

* Update .travis.yml

* Update .travis.yml

* Testing .gitignore adding coverage

* Update .gitignore

* Exporting coverage report as lcov instead of json

I need to run `nyc` to generate the report

* ☺️ Finally got a message system that works. I have installed a local npm file called tsuml that works by creating a UML of my project from a command line. Run tsuml --glob ./src/**/*.ts to create it

* 🍺 Message system working. Need to run more tests before fully complete. Need to look at reconfiguring the engine to make sure the system is using the message system and run more tests.

* 💤 Updated message system tests

* 🐼 Message class tests complete. Will work on implementing the system tomorrow

* Many fixes to the system and tests.

* Changed the DOjbect structrue and updated tests to reflect changes
* Updated the Entity structure and changed the test file to reflect the changes.
* Removed gamewindow test (not at that stage of the project)
* Removed message test; merged into messsagessytem test
* Removed system interface
* Updated issue template (addressing issue #22)

Current issues
* #21
* #17

Still working on this commit. Will upload when complete.

* 💀 Fixed some tests

* 😅 Working on npm audit issues with the project

* 💀

* 😕 Don't know where I want to setup my client for the engine. This will need to be pondered. I also am having an issue on how to setup the game loop. Should it be a web worker, or run on the main UI thread as it should be dependent on it for timing. Will be thinking this over for a bit. Tests currently fail. Consider looking at the game loop. Should I be utilizing my message system more?

* 😪 Removed unecessary node modules

* 🍺 Working on a lot of changes. The engine will have to be redesigned for connecting with the GameWindow, scenes and Electron, Browser

* 👎 Not working, changing to Windows

* 👎 Still not working. Going to try a new implementation

* 💰 -m Currently npm test is not running. Made issue #24

* 😫 Still not working, but here is my up to date file

* 🔥 Adding changes since last commit

* 😅 Fixed tests compilation with help from @loganfsmyth on the Babel slack

* 👍 Added Istanbul test coverage to the suite

* 👎 Falsifying 2 tests to check if Travis-CI is working

* 🍺 Changed tests back to what they should be

* 🐼 Testing DOM with Puppeteer

* 🐼

* 💤 Document is undefined still. Cant get it working and Im sleepy. Bed time!

* Puppeteer working, Divine global and Document aren't

Changes:

Puppeteer has been added to the Unit Tests to check UI and in browser variables of the engine. So far Divine is "undefined" but that is what I'm working to fix. New tests can be run with `npm test` and `npm run-script unit-test` as Istanbul now gives a coverage mapping as well.
Mostly build tools were added in this commit. There is lot's of debugging to come.

Issues:

* "Divine" must be a global variable in the browser scope
* GameWindow is still not being populated as "document" is undefined.

Comments:

[Other general comments you wish to add]

* Puppeteer, Rollup and Modules

Changes:

Puppetter has been added to the project for Chrome testing. This will allow me to check and see if the "users'" application is running in the browser. However, as much as I would like to continue this right now, I am not having the best time with it. Therefore, I am moving on to another part of the project, the renderer. 
Rollup was previously spitting out the wrong formatted files, that has been fixed to UMD and ES modules (named accordingly).

Issues:

* Puppetter not working. After this commit, the tests will be turned off until I return to them.

Comments:

This has been a long time working at this, and needs to be put aside until I can find some help in the matter. This will be saved on a separate branch labelled "feature/puppeteer"

* 🏃 Fixed unit test commands

* Game loop complete for console and browser

Changes:

Note: browser should work for electron as well.
The engine now runs in browser! This will now allow me to see real time loading and rendering. This is a great step but should have been done weeks ago. Will continue working on this later. Next step is rendering.

Issues:

n/a

Comments:

The greatest power is often simple patience. Joseph E Cossman

* chore(package.json): Adding commitizen to the project for semantic-release

* chore:

* ci: Commitizen and Semver

* Major message system rework. (#42) Merging from message_system

This is a big merge of the message_system. From here I believe things should get easier, but time will tell...
---
* 🍺 Removed commitizen. Version control comes built into npm

* 👍 Finishing scripts and will work on the feature scene now. Going to stick to standards from here on out

* 0.1.0

* 0.2.0

* Major working feature (keep to 50 characters)

Changes:

* Added file: RELEASE_TEMPLATE.md
* Updated the coverage for nyc (Istanbul)
* Minor changes to NPM commands

Issues:

n/a

Comments:

Minor changes

* Base Engine startup

Changes:

[This should be an overall summary of changes to the project at least done in point-form. More detailed prose format is of course allowed. The point of the description is to provide detail of changes and why.]

Issues:

[Please provide a point-form description of issues. Then please submit a formal issue on the GitHub project. Issue guidelines are doucmented in the project Wiki.]

Comments:

Began writing subsystem class test files. Work on this later.

* aMajor working feature (keep to 50 characters)

Changes:

[This should be an overall summary of changes to the project at least done in point-form. More detailed prose format is of course allowed. The point of the description is to provide detail of changes and why.]

Issues:

[Please provide a point-form description of issues. Then please submit a formal issue on the GitHub project. Issue guidelines are doucmented in the project Wiki.]

Comments:

[Other general comments you wish to add]

* DObject extending MessageReceiver

Changes:

[This should be an overall summary of changes to the project at least done in point-form. More detailed prose format is of course allowed. The point of the description is to provide detail of changes and why.]

Issues:

[Please provide a point-form description of issues. Then please submit a formal issue on the GitHub project. Issue guidelines are doucmented in the project Wiki.]

Comments:

Tests failing at the moment

* DObjects extending MessageReciever interface

Changes:

DObject extending from MessageReciever
GameWindow circular dependency fixed
Continuing base engine creation.

Issues:

[Please provide a point-form description of issues. Then please submit a formal issue on the GitHub project. Issue guidelines are doucmented in the project Wiki.]

Comments:

[Other general comments you wish to add]

* SceneManager, Scene and Engine

Changes:

Engine now has a SceneManager and loads in the Scene for the Engine. The Engine loads the basic scene for now, but it is HARDSET in Engine.ts (in the start method). SceneManager runs in tests, and also tests the Engine's startup of the scene. Scene tests still need to be written.
Helper functions have been written to read/write JSON data in files. This needs to be tested to see if the engine is pulling the files locally. This also needs to be tested to be running in a developers environment (Electron, HTML, etc). Helper functions to write the Scenes to JSON files should be tested. The idea is that the the scene will be written and read on start/stop of the Engines running to aid with compilation. Helper functions currently have no tests. These need to be added in when possible.
Scene file basic JSON file needs to be written. How are scenes going to be read/written?

Issues:

* Tests currently fail
    * File reading/writing has been hanging tests

Comments:

* Add todo items in files to the GitHub Project
* Add issues that are currently in the system to the Issues section
* TravisCI .yml file has been updated

* 💤 Fixing vulnerabilities

* 💤 Going to bed. I can't work on this tonight. Mabye I'll have some cake 🍰 too

* Typescript Watch Working

Changes:

This will rebuild the library as a Rollup file each save. This will keep tests constant and concurrent. This will make testing in multiple environments much, much easier. Also a major feature of the engine implemented. This has been a long time coming and just has been slacked on.
Updated includes. Removed all default exports. Default exports are not
correct to use; see issue #28
[comment](#28 (comment))

Issues:

Test still aren't running...
Issue #16
Issue #28
Issue #11

Comments:

Major feature complete.

* Pinpointing fs issue in Rollup and plugins

Changes:

* Helper function error logging
* Error log codes
* Rollup config order

Issues:

Creating issue #37 at this moment. Commiting now for reference.

* 🍺 Saving for a reference point. Going to try and implement a Rollup config change

* Using prototypes for DObject messaging functions.

Changes:

As the title describes. Going to be using the engine to define
prototype functions and hopefully remove the circular dependency issue.
Testing is needed for DObject to test these functions.

Issues:

This is a continuation of issue #37

* 😪 File loading isn't happening tonight. Going to call it and go to bed "early"

* 🍺 Test's running again. Better prints for logging - COLORS! Continuing researching loading from file

* WebGL, MessageSystem and Assets

Changes:

Message system has had a major overhaul; lot's of errors failing because of this reason. WebGL is beginning to be added in as I need to start getting work done on this. I'm loading this in with three.js and my package size has skyrocketed. Such as it needs to be however. Asset loading is next to begin testing. I need to see if I can get an asset loading for scene files.

Issues:

Current project issues:
* Asset loading needs to happen fast.
* Message tests need to be fixed up again...
Current relevant  GitHub issues:
* #28
* #11

Comments:

Time crunch is real.

* Message system overhaul

Changes:

I have done a complete message system overhaul. As there was a lot of
circular dependency issues with the original system, I believe this may
be a soltuion. It still relies on an event based system, but it now also
has a priority cue order as well. To be included is a low, and urgent
cue, but this is to be implemented later - shouldn't be too bad as a
later task I have bigger fish to fry.
There is also an asset loader from the previous commit that will need to
be tested. This is the next priority item.
After asset loading testing is complete, triage is going to need to be
done on the rest of the project. Begin breaking down tasks and attacking
them head on.

Issues:

GitHub issues changed with this commit:
* #28: This commit will close issue #28 as the message system tests are
all working. The current failing tests are from the Engine itself.
* #11: An older issue that is more top level. I will reference this when
working on the physics engines' queue however, for now it can be closed.

Other issues:
* Currently the tests fail, going to have to continue debugging this
tomorrow.

* 0.3.0

* fixed broken link in README.md that didn't point to CONTRIBUTING.md

* fixed 2nd broken link in README.md that didn't point to CONTRIBUTING.md

* 💤 All Unit Test's are passing. Going to bed as this is enough work for the day. Look at merging this in as version 0.3.1 because there has been major changes to previous systems.

* 0.3.1

* 💤 Updated document generator. Note, the generator is not ouputting errorsystem.ts

* 💰 -m Should not have removed types

* If Engine.instance is undefined in Engine.shutdown(), throw a warning not an error. Calling shutdown on an undefined system should be silently handled

* 😫 Added Entity.getChild test. Adding to pull rquest

* 🍺 Updated travis.yml

* Addressing issue #44

* Addressing issue #44

* Addressing issue #44

* Update .travis.yml

* Update .travis.yml

* Update .travis.yml

* Update .travis.yml

* Update .travis.yml

* Update .travis.yml

* Update .travis.yml

* Update .travis.yml

* Update .travis.yml

* Update .travis.yml

* Update .gitignore

* Testing .gitignore adding coverage (#45)

* Testing .gitignore adding coverage

* Update .gitignore

* Exporting coverage report as lcov instead of json

* Update .travis.yml (#46)

* 🔥 Adding Codecov for code coverage reporting (#48)

I need to run `nyc` to generate the report

* 🐼 Updated README and GitHub template files (#49)

Changes:

* AssetManager using JSONFileLoader

Issues:

* Asset manager test failing. Cannot find the file from console (have not tried in browser yet, will tomorrow morning in a test project.

Comments:

I need to get this done by end of tomorrow, or else just move on to the render engine regardless.

Added test to check if the instance is undefined that the system throws a critical error.

This is a duplicate of allListenerCount()

Changes:

Assets are now loading! I can now load assets by name as long as they are given as relative paths in NodeJS. Next I need to ensure XMLHttpRequests are getting the proper files.

AssetsManager calls shall only ever be from the IOSystem. Use the message system to request files from any other system or entity even (who knows). Engine should have a recollection of all types of DObjects being created(?). Scene will have a list of all entities in the system so far. MessageSystem will have all messages in the system as well as handlers.

Issues:

#11, #18

Comments:

[Conditional importing in ES6 as of stage 3](https://stackoverflow.com/questions/36367532/how-can-i-conditionally-import-an-es6-module)

…. The container is not being defined and sent to the engine