Expand bevy plugin usage options

[garryod]

Ass ability to:

• Create a MatchboxSocket for direct insertion as a Resource
• Use MatchboxSocket as a Component

Todo:

• Utilities for MatchboxSocket as a Component

[johanhelsing]

I think we can keep the Command extensions, but I don't think there's any need to use actual commands? That would bring the sockets up and running immediately instead of at the next flush of command buffers.

[garryod]

I think we can keep the Command extensions, but I don't think there's any need to use actual commands? That would bring the sockets up and running immediately instead of at the next flush of command buffers.

Is there a reason you would want to bring them up immediately instead of joining the command queue? Surely joining the queue is the canonical way of behaving?

[johanhelsing]

I think we can keep the Command extensions, but I don't think there's any need to use actual commands? That would bring the sockets up and running immediately instead of at the next flush of command buffers.

Is there a reason you would want to bring them up immediately instead of joining the command queue? Surely joining the queue is the canonical way of behaving?

Just that we're kind of just reimplementing a special case of commands.insert_resource there's no need to do it. It will be available to other systems at the same time anyway.

[johanhelsing]

I think this is fine to merge as is, would be good to have it in 0.6.