The upcoming version 1.0.6 of slimKEYS is now up to beta 3. I have fixed a color glitch with the gradient, made slimLAUNCH draw the description and icon asynchroneously to improve responsiveness, but most important, a missing feature with slimSEARCH's "Add new entry" button made implementing a custom slimSEARCH extension useless.
I found out the hard way, since I did not really test implementing a slimSEARCH extension in a separate assembly before this morning. Yesterday, Pascal told me he was using slimSEARCH to jump to FogBugz case numbers quickly. He wanted to use "Enter" as the "Go" key, so he added a new Web Query entry with the correct URL (with {keywords} where the case number is supposed to go), and removed all other entries.
I told him it would be really easy to implement a slimSEARCH extension that recognizes a decimal number and opens the appropriate FogBugz page, without having to put that new entry at the beginning of the search entry list (thus mapped to Enter). This way, he could type a number and Enter to open this FogBugz case number, or type anything else to search on Google (given the default Google search entry is left at the top of the list. I personally use Yahoo at the top).
This morning, I realized this would be a great slimKEYS SDK sample, so I made my little extension real quickly, then tested it with the beta 2 of slimKEYS, just to realize that the "Add new entry" button was always adding a web query entry instead of asking the user what to add. Checking the code clearly indicated this was left to do... doh!
The third beta of the next release fixes this missing feature, and I have made available both the slimSEARCH.FogBugz sample plug-in and sources.