rice.shawn

Finally here: Update your workflows with the Packal Updater.
 
There is a longer explanation on the Packal page, so just check that one out, but I'll give you a short version here.
 
The updater will upgrade any workflows that you have downloaded from Packal when an upgrade becomes available. It cannot upgrade any workflows that you did not download from Packal.
 
When you launch it the first time, head over to the settings and configure how you want it to work. If you write workflows, then put in the name that you most often use. If you have a Packal account, put that name in there too. If you do those two things, then the updater won't try to upgrade your workflows. If there are workflows that you do not want to update if, say, you've modified them, then Blacklist them in the appropriate place, and the updater will ignore those workflows. 
 
If you're running Mavericks (or, theoretically, Yosemite), then you'll have access to a nifty little GUI. If you're not, then, well, you don't, but you can still configure and do everything from Alfred itself. See the animated screenshots below for a quick demo of both.
 
Three other notes:
 
(1) The Updater Workflow uses the Alfred Bundler, which has been receiving an overhaul. If you run into some trouble with it, then just go ahead and delete your bundler directory, and it will re-install itself. A newer version of the bundler should be coming out soon that will make some great fixes, but you needn't worry about that because the bundler will update itself.
 
(2) The Updater can send information to Packal about what workflows you have installed, enabled, and downloaded from Packal. It'll try to do this once a week if you do not disable the feature. It is anonymous reporting in that there is no way for me to figure out who you are from the data. Here's the command that I use to generate your unique identifier:
ioreg -rd1 -c IOPlatformExpertDevice | awk '/IOPlatformUUID/ { split($0, line, "\""); printf("%s\n", line[4]); }' If you just plug that into a terminal, then you'll probably see something akin to:
  .
 
(3) The Updater keeps backups of the workflows you've updated, so, if anything breaks, just open the backups folder and double-click the most recent version of the workflow to restore.
 
Anyway, go grab it from Packal, and start updating.
 
(And, as always, I think I've removed all the bugs, but, as I release this into the wild, I expect to find more. Just report them here.)
 
Lastly, the updater can update itself according to my tests. Cool, right?
 
Demo — Packal "GUI"
 

 
 
Demo — Packal Script Filter Interface
 

I'm certain that this will be added when I overhaul the theme editor

Well, the Packal updater is perfectly accurate because it will always update your workflows to the newest version on Packal, which is not necessarily the newest version. 
 
I designed Packal in a way that only the workflow author could update their workflows in order to make all of the releases there as authoritative and official as possible. Since the update can come only from them, it's the workflow authors' responsibility to keep their workflow up to date on Packal. For me, it's also a question of letting the authors choose to distribute their work on Packal rather than choosing for them. They might not want to put the newest version on Packal for some reason or another. It may be that they want the most stable ones on there only. Or they may have come to dislike Packal and decided to stop using the repository.
 
That being said, I have some code on the backburner that will make it much easier for authors to submit and to keep their workflows up to date on Packal. It's basically a mixture of ways to use metadata from the workflow internals along with some supplement that will allow releases to be pushed via Github hooks as well as from Alfred itself. Hopefully those improvements will help keep versions updated on Packal.

See if MouseTools works for you.

Finally here: Update your workflows with the Packal Updater.
 
There is a longer explanation on the Packal page, so just check that one out, but I'll give you a short version here.
 
The updater will upgrade any workflows that you have downloaded from Packal when an upgrade becomes available. It cannot upgrade any workflows that you did not download from Packal.
 
When you launch it the first time, head over to the settings and configure how you want it to work. If you write workflows, then put in the name that you most often use. If you have a Packal account, put that name in there too. If you do those two things, then the updater won't try to upgrade your workflows. If there are workflows that you do not want to update if, say, you've modified them, then Blacklist them in the appropriate place, and the updater will ignore those workflows. 
 
If you're running Mavericks (or, theoretically, Yosemite), then you'll have access to a nifty little GUI. If you're not, then, well, you don't, but you can still configure and do everything from Alfred itself. See the animated screenshots below for a quick demo of both.
 
Three other notes:
 
(1) The Updater Workflow uses the Alfred Bundler, which has been receiving an overhaul. If you run into some trouble with it, then just go ahead and delete your bundler directory, and it will re-install itself. A newer version of the bundler should be coming out soon that will make some great fixes, but you needn't worry about that because the bundler will update itself.
 
(2) The Updater can send information to Packal about what workflows you have installed, enabled, and downloaded from Packal. It'll try to do this once a week if you do not disable the feature. It is anonymous reporting in that there is no way for me to figure out who you are from the data. Here's the command that I use to generate your unique identifier:
ioreg -rd1 -c IOPlatformExpertDevice | awk '/IOPlatformUUID/ { split($0, line, "\""); printf("%s\n", line[4]); }' If you just plug that into a terminal, then you'll probably see something akin to:
  .
 
(3) The Updater keeps backups of the workflows you've updated, so, if anything breaks, just open the backups folder and double-click the most recent version of the workflow to restore.
 
Anyway, go grab it from Packal, and start updating.
 
(And, as always, I think I've removed all the bugs, but, as I release this into the wild, I expect to find more. Just report them here.)
 
Lastly, the updater can update itself according to my tests. Cool, right?
 
Demo — Packal "GUI"
 

 
 
Demo — Packal Script Filter Interface
 

The overdue Packal Updater has now been released. Go look at the thread.

I forgot to mention, if you have Alfred Cron installed, the workflow will give you an option to install a script that will check for workflow updates once per day. You can easily change the timing by editing the job after "installing" it into Alfred Cron.
 
If it finds any updates, it will notify you via Terminal Notifier. If you click the "show" button on the notification, then it'll show you the updates.

Glad it fixed it.
 
Open the GUI. In the status tab, you should see "xxx workflows can be downloaded from packal" or something. If you don't see that, then all that are possible have already been downloaded from Packal. If you do see that, click the "details" just below that, and you'll see a list of them. If you click any of those workflows, then it'll open the workflow page on Packal in your default browser.
 
I have some commented out code in the workflow to have an option to "force packal" — the wording is terrible, which basically will automatically re-download all of the workflows that are available on Packal but you haven't downloaded from Packal yet. I haven't gotten in working in a satisfactory way for me to have it implemented, so I figured I'd delay that feature for now. Currently, it's too aggressive for my taste.

Finally here: Update your workflows with the Packal Updater.
 
There is a longer explanation on the Packal page, so just check that one out, but I'll give you a short version here.
 
The updater will upgrade any workflows that you have downloaded from Packal when an upgrade becomes available. It cannot upgrade any workflows that you did not download from Packal.
 
When you launch it the first time, head over to the settings and configure how you want it to work. If you write workflows, then put in the name that you most often use. If you have a Packal account, put that name in there too. If you do those two things, then the updater won't try to upgrade your workflows. If there are workflows that you do not want to update if, say, you've modified them, then Blacklist them in the appropriate place, and the updater will ignore those workflows. 
 
If you're running Mavericks (or, theoretically, Yosemite), then you'll have access to a nifty little GUI. If you're not, then, well, you don't, but you can still configure and do everything from Alfred itself. See the animated screenshots below for a quick demo of both.
 
Three other notes:
 
(1) The Updater Workflow uses the Alfred Bundler, which has been receiving an overhaul. If you run into some trouble with it, then just go ahead and delete your bundler directory, and it will re-install itself. A newer version of the bundler should be coming out soon that will make some great fixes, but you needn't worry about that because the bundler will update itself.
 
(2) The Updater can send information to Packal about what workflows you have installed, enabled, and downloaded from Packal. It'll try to do this once a week if you do not disable the feature. It is anonymous reporting in that there is no way for me to figure out who you are from the data. Here's the command that I use to generate your unique identifier:
ioreg -rd1 -c IOPlatformExpertDevice | awk '/IOPlatformUUID/ { split($0, line, "\""); printf("%s\n", line[4]); }' If you just plug that into a terminal, then you'll probably see something akin to:
  .
 
(3) The Updater keeps backups of the workflows you've updated, so, if anything breaks, just open the backups folder and double-click the most recent version of the workflow to restore.
 
Anyway, go grab it from Packal, and start updating.
 
(And, as always, I think I've removed all the bugs, but, as I release this into the wild, I expect to find more. Just report them here.)
 
Lastly, the updater can update itself according to my tests. Cool, right?
 
Demo — Packal "GUI"
 

 
 
Demo — Packal Script Filter Interface
 

Finally here: Update your workflows with the Packal Updater.
 
There is a longer explanation on the Packal page, so just check that one out, but I'll give you a short version here.
 
The updater will upgrade any workflows that you have downloaded from Packal when an upgrade becomes available. It cannot upgrade any workflows that you did not download from Packal.
 
When you launch it the first time, head over to the settings and configure how you want it to work. If you write workflows, then put in the name that you most often use. If you have a Packal account, put that name in there too. If you do those two things, then the updater won't try to upgrade your workflows. If there are workflows that you do not want to update if, say, you've modified them, then Blacklist them in the appropriate place, and the updater will ignore those workflows. 
 
If you're running Mavericks (or, theoretically, Yosemite), then you'll have access to a nifty little GUI. If you're not, then, well, you don't, but you can still configure and do everything from Alfred itself. See the animated screenshots below for a quick demo of both.
 
Three other notes:
 
(1) The Updater Workflow uses the Alfred Bundler, which has been receiving an overhaul. If you run into some trouble with it, then just go ahead and delete your bundler directory, and it will re-install itself. A newer version of the bundler should be coming out soon that will make some great fixes, but you needn't worry about that because the bundler will update itself.
 
(2) The Updater can send information to Packal about what workflows you have installed, enabled, and downloaded from Packal. It'll try to do this once a week if you do not disable the feature. It is anonymous reporting in that there is no way for me to figure out who you are from the data. Here's the command that I use to generate your unique identifier:
ioreg -rd1 -c IOPlatformExpertDevice | awk '/IOPlatformUUID/ { split($0, line, "\""); printf("%s\n", line[4]); }' If you just plug that into a terminal, then you'll probably see something akin to:
  .
 
(3) The Updater keeps backups of the workflows you've updated, so, if anything breaks, just open the backups folder and double-click the most recent version of the workflow to restore.
 
Anyway, go grab it from Packal, and start updating.
 
(And, as always, I think I've removed all the bugs, but, as I release this into the wild, I expect to find more. Just report them here.)
 
Lastly, the updater can update itself according to my tests. Cool, right?
 
Demo — Packal "GUI"
 

 
 
Demo — Packal Script Filter Interface
 

Note: the original version of this workflow utilized an unofficial API that Google Translate exposed. Unfortunately, the Google has shut down the API. There is an alternative workflow that uses the official (paid) Google Translate API that you can find here: http://www.packal.org/workflow/translate-api. It's actually pretty cheap. 
 
Here's a little ditty that interfaces with Google Translate. The upside of this one is that it gives you access to all of Google Translate's languages (or at least about 80 of them). You can enable/disable languages from inside the workflow.
 
Find it on Packal.
 
Demo:
 

 
 
Current Languages:
Afrikaans Albanian Arabic Armenian Azerbaljani Basque Belarusian Bengali Bosnian Brazilian Portuguese Bulgarian Catalan Cebuano Chinese Croatian Czech Danish Dutch English Esperanto Estonian Filipino Finnish French Galician Georgian German Greek Gujarati Hatian Creole Hausa Hebrew Hindi Hmong Hungarian Icelandic Igbo Indonesian Irish Italian Japanese Javanese Kannada Khmer Korean Lao Latin Latvian Lithuanian Macedonian Malay Maltese Maori Marathi Mongolian Nepali Norwegian Persian Polish Portuguese Punjabi Romanian Russian Serbian Slovak Slovenian Somali Spanish Swahili Swedish Tamil Telugu Thai Turkish Ukranian Urdu Vietnamese Welsh Yiddish Yoruba Zulu

I have been investigating this for a while, and have a fix lined up for 2.4 where http_proxy and https_proxy will be set into the task's environment variables

Note: the original version of this workflow utilized an unofficial API that Google Translate exposed. Unfortunately, the Google has shut down the API. There is an alternative workflow that uses the official (paid) Google Translate API that you can find here: http://www.packal.org/workflow/translate-api. It's actually pretty cheap. 
 
Here's a little ditty that interfaces with Google Translate. The upside of this one is that it gives you access to all of Google Translate's languages (or at least about 80 of them). You can enable/disable languages from inside the workflow.
 
Find it on Packal.
 
Demo:
 

 
 
Current Languages:
Afrikaans Albanian Arabic Armenian Azerbaljani Basque Belarusian Bengali Bosnian Brazilian Portuguese Bulgarian Catalan Cebuano Chinese Croatian Czech Danish Dutch English Esperanto Estonian Filipino Finnish French Galician Georgian German Greek Gujarati Hatian Creole Hausa Hebrew Hindi Hmong Hungarian Icelandic Igbo Indonesian Irish Italian Japanese Javanese Kannada Khmer Korean Lao Latin Latvian Lithuanian Macedonian Malay Maltese Maori Marathi Mongolian Nepali Norwegian Persian Polish Portuguese Punjabi Romanian Russian Serbian Slovak Slovenian Somali Spanish Swahili Swedish Tamil Telugu Thai Turkish Ukranian Urdu Vietnamese Welsh Yiddish Yoruba Zulu

Note: the original version of this workflow utilized an unofficial API that Google Translate exposed. Unfortunately, the Google has shut down the API. There is an alternative workflow that uses the official (paid) Google Translate API that you can find here: http://www.packal.org/workflow/translate-api. It's actually pretty cheap. 
 
Here's a little ditty that interfaces with Google Translate. The upside of this one is that it gives you access to all of Google Translate's languages (or at least about 80 of them). You can enable/disable languages from inside the workflow.
 
Find it on Packal.
 
Demo:
 

 
 
Current Languages:
Afrikaans Albanian Arabic Armenian Azerbaljani Basque Belarusian Bengali Bosnian Brazilian Portuguese Bulgarian Catalan Cebuano Chinese Croatian Czech Danish Dutch English Esperanto Estonian Filipino Finnish French Galician Georgian German Greek Gujarati Hatian Creole Hausa Hebrew Hindi Hmong Hungarian Icelandic Igbo Indonesian Irish Italian Japanese Javanese Kannada Khmer Korean Lao Latin Latvian Lithuanian Macedonian Malay Maltese Maori Marathi Mongolian Nepali Norwegian Persian Polish Portuguese Punjabi Romanian Russian Serbian Slovak Slovenian Somali Spanish Swahili Swedish Tamil Telugu Thai Turkish Ukranian Urdu Vietnamese Welsh Yiddish Yoruba Zulu

You can use a terminal command to do it, or you can just use Tyler's simple 'set blur' workflow that you can find on Packal.

DHCP Toggle
 
Find it on:
Packal: DHCP Toggle Github: DHCP Toggle Repository Short Description
Set your DHCP Settings via Alfred.
 
Long Description
DHCP Toggle allows you to alter your DHCP settings between a manual and an automatic configuration. When you set an automatic configuration, which is normal, your computer will receive an IP address directly from the router that you’re connected to. If you choose manual, you have the option of setting your own IP address. If the router’s IP address is 10.0.1.1, then you’ll be able to get an IP with a prefix of 10.0.1 and a suffix between 2 and 255. If the IP address is already used, then you’ll have to try again. DHCP Toggle will also set your router address to the IP prefix that you use, followed by 1, which is always reserved for the router.
 
You can use this when your Internet connection is weak, or if a router is clogged, or if, for some random reason, the router doesn’t like you connecting with an automatic IP address (the original need for this workflow).
 
Commands
dhcp <arg>
 
Available arguments:
None: defaults to your default IP prefix + random number 2–255 Switch to auto: auto IP Address: 10.0.1.192 Number: 2–255, i.e. 32 Configure c Configuration
 
Default Prefix
You can set a default prefix, the first three numbers of an IP address, which will be given precedence over the other available prefixes. If you just type a three-digit number (between 2–255), then it will set your IP address to DEFAULTIP.NUMBER.
 
IP Prefixes
You can set a list of prefixes that you commonly use, and those will appear in the script filter to choose easily. If no prefixes file is found, then the following list will be populated:
10.0.0 10.0.1 192.168.0 192.168.1 192.168.2 192.1.10 You can add and remove from this list from the configuration option.
 
Passwordless Execution (sudo)
 
If you would prefer to use this workflow without a password, you can select the option to add a record to your sudoers file. The script will add the line
$USER ALL=NOPASSWD:/usr/sbin/networksetup to your /etc/sudoers file, where $USER is your username; so, the $USER will now be able to execute the command networksetup without needing to enter a password. The script checks the syntax with visudo to make sure that it doesn’t bork your /etc/sudoers file. So, it’s safe.
 
Demo
 

 
Credit
Thanks for version 2.0 goes to Pryley (Github | Alfred Forum) who opened a pull request for the added features and contributed some code.
 
Issues
Please report coding issues on the Github issue queue. Other support should be posted on the Alfred Forum thread.

Here's a very minimal, transparent theme. I kind of like it, and it looks great with a blur, but it's almost unusable without one.
 
Find it on Packal.
 

RSS feed for new workflows: http://www.packal.org/new-workflows.xml

Here's a very minimal, transparent theme. I kind of like it, and it looks great with a blur, but it's almost unusable without one.
 
Find it on Packal.
 

Okay, I see what's happening.
 
(1) Your timezone settings are set in your php.ini (don't worry about this). I included some code that was supposed to get past that error by getting the TZ from your system and temporarily setting it, but, apparently, it's either (1) not working in regards to the sunset/sunrise time functions or (2) I'm not calling it early enough.
 
(2) Flux doesn't write the plist settings for values until you set them. I'll add in the error handling for those.
 
I have a long day of grading papers, but I'll try to squeeze in some time to fix these errors in between. Otherwise, I'll fix it up tomorrow.
 
Thanks for the log. It's just what I needed.

RSS feed for new workflows: http://www.packal.org/new-workflows.xml

This is a very simple workflow that displays and sets Alfred's background blur radius. Obviously, you'll only see its effects when running a version of Alfred that supports the background blur (namely, Alfred 2.0+ on OS X 10.6 through 10.8, Alfred 2.3+ on OS X 10.9).
 
Enjoy!
 
Download from Packal

Tyler made a nice little workflow to help set the blur for you. Works in 2.3 on.

F.lux's file structure changed a bit in its newest release. I've updated the workflow on my end, but I'm adding a few more features, and I'll release it shortly.

Tyler wrote one of these for 2.3 and Mavericks. You can find it here: http://www.packal.org/workflow/blur