autopilot
autopilot copied to clipboard
v0.5.0 - Make inheritance structure unitary from root object
This is the defining enhancement of v0.5.0
following from the conversation on https://github.com/wehr-lab/autopilot/issues/39
you know what this is now the defining enhancement of v0.5.0 - everything should have a registry, because everything should inherit from a root object that allows every module to have plugins. A Universal Plugin System From A Unitary Root Object. what if one wanted to implement their own networking plugin module that replaced a network node element. it should be possible to do that yes? plot objects should spawn from a registry because there should be some metaclass that can mutually coordinate their framerate if they're videos, and so the thought goes ever on.
Every object should have certain properties & methods, like some identifier, ability to make logger, have net node, etc.
Should implement a root AutopilotObject inherited by everything else. this would make giving unique names to every object a lot easier, keep a registry, not reimplement extremely common methods multiple times, etc.
Currently in https://github.com/wehr-lab/autopilot/tree/registries
will implement task and hardware registries for v0.4.0, and then create v0.5.0 branch to start this