ebul-cmp/TODO

To Do:
 * Test for ComponentState.{init,destroy} and driver-related stuff
 * Registry tests
 * Registry doc
 * General usage documentation
 * Uncouple component-provided names from the library
 * Automatically-updated singletons
 * Registry: get all component states
 * Document exceptions

Other ideas (maybe later if needed):
 * Unregistering components
 * Hierarchy of registries
 * Driver-related helpers (e.g. determine type of driver components, register/unregister drivers with main)
TODO list 2015-09-16 10:15:39 +02:00			`To Do:`
Component state and registry - Drivers support A component with "drivers" will initialise/start its drivers after it is initialised/started itself. It will also stop/destroy non-driver reverse dependencies before stopping/destroying its drivers. 2015-09-17 10:57:46 +02:00			`* Test for ComponentState.{init,destroy} and driver-related stuff`
TODO list update Items that had been forgotten and/or that were "obvious" 2015-09-17 08:53:09 +02:00			`* Registry tests`
			`* Registry doc`
TODO list 2015-09-16 10:15:39 +02:00			`* General usage documentation`
			`* Uncouple component-provided names from the library`
TODO list update Items that had been forgotten and/or that were "obvious" 2015-09-17 08:53:09 +02:00			`* Automatically-updated singletons`
			`* Registry: get all component states`
			`* Document exceptions`
TODO list 2015-09-16 10:15:39 +02:00
			`Other ideas (maybe later if needed):`
			`* Unregistering components`
Component state and registry - Drivers support A component with "drivers" will initialise/start its drivers after it is initialised/started itself. It will also stop/destroy non-driver reverse dependencies before stopping/destroying its drivers. 2015-09-17 10:57:46 +02:00			`* Hierarchy of registries`
			`* Driver-related helpers (e.g. determine type of driver components, register/unregister drivers with main)`