Autoregister new handlers

[danryan]

No description provided.

[danryan]

groundwork laid by #16

[danryan]

I'm not sold on this idea yet. Auto registration makes sense for adapters and stores but less sense for handlers as one presumably holds more control over the code.

Still, the idea is trivial enough. It could make consuming plugins from others easier. This might look like the register hooks for adapters/stores. Then again, the package system already manages this quit well.

Automatically adding them to the robot, however, will probably never happen.

[tcolgate]

This is easy enough to do from user side, and might be annoying if people don't want it (I've set this up in my own project)

[danryan]

Hey, thanks for your input on this and other issues. I really appreciate it!

I agree with you. It's not difficult to add new handlers, and I appreciate the explicitness of adding them currently over an implicit registration. No surprises, less magic. A not found handler like #7 could provide a helpful error to log when a expected handler hasn't been loaded.

[tcolgate]

@danryan no probs, hal is looking nice. I had a dig around the various other similar projects (the code looks very similar to victor, are they related somehow?), hal came out on top. Would be nice to see a few more tests in the code, but it's definitely the easiest to get running with.