8 commits

Author	SHA1	Message	Date
Christopher Willis-Ford	772da24d9e	Add integration test for a non-worker extension	2017-10-02 12:02:44 -07:00
Christopher Willis-Ford	7a21d619bf	Add a way to load an extension without a Worker ... The new `_registerInternalExtension` method on the extension manager will register an extension object (an object with a `getInfo()` method) with the extension system without sandboxing the object in a Worker.	2017-09-27 00:01:47 -04:00
Christopher Willis-Ford	799d61ac98	Cleanup	2017-09-06 00:57:03 -06:00
Christopher Willis-Ford	d43749d675	WIP for demo	2017-09-06 00:57:03 -06:00
Christopher Willis-Ford	64bde25d22	Offer a promise for extension worker init	2017-09-06 00:57:03 -06:00
Christopher Willis-Ford	403adb743c	Track extension blocks in the Runtime	2017-09-06 00:57:03 -06:00
Christopher Willis-Ford	42255bbcfa	Collect extension info, prep scratch-blocks data ... The Extension Manager now calls an extension's `getInfo` method, then creates `scratch-blocks`-compatible XML and JSON block data from the results.	2017-09-06 00:57:03 -06:00
Christopher Willis-Ford	7fb7f0dc7b	WIP Extension Manager ... When asked to load an extension, the Extension Manager starts up a new Worker. That worker runs the message dispatch system as well as an instance of the new `ExtensionWorker` class, which will load the desired extension and register it with the extension system. Extensions, placed in `./src/extensions/*.js`, are now processed by Webpack as separate entry points and packed into an `extensions` subdirectory in the output. Still to do: query an extension's information, including the blocks it provides, and register that information with the VM, GUI, etc.	2017-09-06 00:57:03 -06:00