link: Proxi v0.20
In this update:
- Growl Notifier task
- Store Value task and extra value added
- AppleScript task now supports compiled AppleScripts
- “Save As Blueprint” added to trigger popup menu.
- Fixed a crash with Update preferences
- Fixed Check For updates command in dockless mode
- Filter items a little easier to select
- Fixed formatting of plan text extra values
- Launch Application task now shows icon of app to be launched as a badge
Yeah I know I shouldn’t really be adding new features to a “beta” but I couldn’t help myself. So a bunch of minor things and then the most requested addition: Growl Notification task. It’s pretty straightforward. Enter a title, description and select and image if you like. If you do not select an image, Growl will display the Proxi icon instead.
The next item is a bit more complicated and if you care nothing for storing values or later retrieval of these values both within Proxi and through other means, then you can stop reading now.
So, people have requested some means of storing a value and then retrieving it again later in another trigger. You could sort of do this with a Write To File task, but it was a bit clunky. Well, now you can use the Store Value task. Select the value you want to store from the popup menu and give it a name. You’ll use this name to retrieve it later. These stored values are persistent through relaunches and restarts.
To recall a stored value, add an extra value to your trigger. Select Stored Value from the popup menu and set the name to the name you used in the Store Value task. When your trigger fires, it will retrieve the value and make it available to your task/s.
Stored values use a SQLite database located in ~/Library/Application Support/Proxi/proxi.db. Mac OS X has included support for SQLite since the release of 10.4. sqlite3 is a command line tool that command line tool that comes with Mac OS X that can be used to query or modify these database files. And there are other 3rd party tools available. Bottom line, it’s a standard that Apple seems to be taking advantage of and so that’s they way I went. If you are going to poke around in proxi.db you should know the schema:
CREATE TABLE store (name text, type int, value blob);
Simple. The name is the name of the stored value. The value is data representing the stored value The type is a number indicating the type of stored variable:
0 = text
1 = number
2 = date
3 = image
If your going to be changing these records outside of Proxi it’s important to know that if you change the value of an image field to text but neglect to change the type field then you will probably anger Proxi when it goes to looking for this image data that is no longer there. So important safety tip: Never cross the streams.
Well there you have it. Hope you enjoy v0.20. Feedback here on the blog or the wiki is always welcome.
