Commands about keyboardcowboy HOT 7 CLOSED

It would be interesting if command could implement Input and Output protocols so that you should chain commands.

If a command that produces output is followed up by a command that takes input, it would use that input as its parameter. That why we could run shell script that open URL's etc. By introducing this form of composability I think we can elevate the usefulness of Command's and workflow by a ten fold.

from keyboardcowboy.

Perhaps a linked list of input/output commands would be better than having stray commands that you can't really combine because of the conflicting types.

from keyboardcowboy.

Could you make an early prototype of command types in code, without thinking about reusability, like if they were plain structs? Just want to see all the fields for every command before we can build more sophisticated abstractions.

from keyboardcowboy.

I was actually tinkering with this yesterday but I quickly went to far into implementations and hit a roadblock. I think your approach is better, so I'll make a PR adding the different commands mentioned above with the underlying data structures. I think that will give us a good starting point for further discussions.

from keyboardcowboy.

If you look at #5, I managed to reduce the amount of commands down to four. Pretty happy about how they ended up because it would be kinda easy to extend it with other "sub" commands by relying on Kind (if you look at both OpenCommand and ScriptCommand.

from keyboardcowboy.

The only thing missing here is an implementation to handle keyboard commands.
I think that would be the next logical step for me.

from keyboardcowboy.

Closing this issue because we currently support all the referenced types of commands.
Sure there is room for improvement here and there but they can be their own issues.

from keyboardcowboy.