Determine if any code should be migrated from other related repositories

[colinbdclark]

Quickly scanning my own Github repositories, there are a couple that may contain code we want here. They include:

• https://github.com/colinbdclark/flocking-midi-router
• https://github.com/colinbdclark/flocking-midi-clock-tools
• https://github.com/colinbdclark/web-xg-editor (maybe some useful sysex abstractions?)
• https://github.com/colinbdclark/old-flocking-midi/tree/gh-1(the old "new" flocking-midi library, which may have some improved sketches of components here)

@the-t-in-rtf, we should also look at some of your libraries and see if there are useful things we want to fold in here.

[the-t-in-rtf]

Sounds good. The biggest candidate is flocking-midi-select-ng, which IMO would be more properly done as a rewrite of the underlying component in flocking-midi. I will put in a ticket describing what I have in mind shortly.

We can also talk about perhaps abstracting out some of the "transforming routers" I've used in flocking-midi-interchange. It'd also be good to move the "MIDI patchbay" work from the same repo into flocking-midi, with a proper discussion of what a generally useful connector between two MIDI devices should look like.

[colinbdclark]

Since we've been passing flocking-midi-select-ng back and forth, I think the latest version of flocking-midi-select-ng is actually sitting in the Bubbles repository, unless you've made other modifications since around January 2019, @the-t-in-rtf?

[the-t-in-rtf]

I haven't even checked it out on my new computer, and I've had that for six months, so I think yours is more up-to-date.

[colinbdclark]

@duhrer, it looks like you made a couple of additional commits with useful functionality since Bubbles forked your flocking-midi-select-ng code. I'll merge the Bubbles version into this repo, and then see if I can apply your more recent changes here.