StevenHickson
Feature Requests: Some ideas...
So, here are some ideas I had which may be worth lokking at. I decided to open ONE issue for this, but if the developer thinks any of this should be handles in a seperate issue, then just mark that in the comments. Please dont consider this to be spam.
Idea 1: Using Regular Expressions for commands
I really like the idea of the ~ to be more flexible in the command. Maybe someone would like to be even more creative. Therefore I suggest to allow regular expressions as commands. E.g. define something like "_music_on==mpd start" to catch "Turn the music that I like so much on" (that might not be correct english here...), but I hope the Idea is clear. This can also be used to find the "nearest" command, e.g. you have defined a comman "futurama==..." but sometimes the command is evaluated to "future mama", then a regex can be found to match both.
Idea 2: Allowing mulltiple definitions for one command
E.g. "music on|play|radio on==mpd start". This could also be useful for the other side. One could define multiple responses, that are put out randomly, e.g. !response==Yes sir?|Whats up?|What can I do for you?.
Idea 3: Acknowledge Signal
Something like !acknowlegde=Got that! to know that the command is understood.
Idea 4: Repeat Command
Lets say I said "music on", but it was not recognised, then there should be an option to allow voicecommand to ask me to repeat that command, so I dont have to say the keyword again. This should be limited to a certain number.
Idea 5: Allowing more config files
I think its always a good idea to seperate the general config for the program (voicecomman) and the user specific commands. How about having the ability to include config file within another file? Or, even better I think, using a config.d structure, meaning that all files under .config.d/* are used as config file. This would also allow to have different files for different situations. E.g.,
.config.d/conf % Here are all special !... commands .config.d/music % all music related commands .config.d/email % all email related commands
In future, it might be usefull to load or unload different scenarios dynamically.
