I'm working on opening the slimLAUNCH API so that any slimKEYS Provider can extend what gets crawled, and launch anything. For example, I want to support special folders like the control panel, but for the moment slimLAUNCH only supports physical paths. Another great example is a PasswordSafe replacement. How would you like to search for saved paswords using slimLAUNCH? You press Win-S, then type "ebay", and slimLAUNCH suggests your saved eBay password. The password list provider (let's call it slimPASS 
) would copy the password to the clipboard if you press Enter, or the username if you press Alt-Enter, or open a web URL if you press Ctrl-Enter.
All this is neat. But I'm doomed to break the current config scheme used by slimLAUNCH and slimLAUNCHthis (oh, by the way, this would also work with slimLAUNCHthis), and the last thing I want to do is put more time on backward compatibility than on opening slimLAUNCH. This would mean that the first time you would load the new version of slimKEYS, previously saved last launch commands would be lost. The application would train itself back pretty quickly.
In short: I'm going forward with this breaking change. If you have arguments against, shoot!