The last week we got many reports that Script Bay stopped working. Apparently, something went wrong with the signature used many years ago. Most likely, it was a self-signed signature which expired and at the time, there was not an option to use a time stamp to keep the signature valid once it expired.
On a personal note, it was very encouraging to hear that so many people cared that Script Bay stopped working. I don’t get much feedback, and it’s good to know it’s appreciated. 
It’s been a very long time since I’ve worked on Script Bay and I did not even have the code on my current computer. Thankfully, it was just a matter of checking it out from SVN. Unfortunately (or fortunately depending on your perspective), the code was not really left in a stable state. I had started working on some new features before I stopped working on it and it could not be simply recompiled with a new signature. So, I took the opportunity to fix some issues which needed fixing for a long time:
The panel should now work much better in CC. The dark UI should be usable. There’s a preference dialog for setting preferences. All data is now saved in user-readable format in the Script Bay directory. This should make trouble-shooting and fixing problems much easier. (You can even hand edit the data if you so desire.)
The preference dialog has a section for setting categories, but it’s currently just a shell and does not work. I left the section in because it would have taken time to strip it out. If I get enough feedback on the feature, I might even finish it, so consider it a teaser… 😉
Of course, the panel is still Flash based, so Script Bay will not work in apps which now only support HTML panels (yes Photoshop, I’m talking about you). It would be a great project to migrate Script Bay to HTML, but I’m going to need a LOT of interest for that to happen…
So, for now, enjoy the new version of Script Bay. You can get it here.
I did not have time to do a lot of QA on this, so please leave a comment if I broke something.
Harbs
