Jump to content

CarlosNZ

Member
  • Posts

    392
  • Joined

  • Last visited

  • Days Won

    11

Reputation Activity

  1. Like
    CarlosNZ reacted to idea4IT in Pocket for Alfred   
    Thanks, CarlosNZ!
     
    It does make sense to open the link by default without archiving it.
     
    I've just updated the workflow accordingly and also added notifications!
  2. Like
    CarlosNZ got a reaction from idea4IT in Pocket for Alfred   
    Great stuff. Just one comment — it would seem the default action is to visit the link and archive it in Pocket and you have to hold "Ctrl" to visit without archiving. Personally, I'd prefer it if this was the other way round and it didn't archive by default.
     
    I realise I can probably just tweak the workflow to change this around, but thought I'd let you know anyway.
     
    Oh, and one more little thing — it would be good to get a notification when archiving links.
     
    But well done. I'll find this really handy, I think.
  3. Like
    CarlosNZ reacted to idea4IT in Pocket for Alfred   
    Hi guys,
     
    this workflow lets you manage your Pocket list with Alfred.
     

     
    Features
    Actions to copy, visit and archive, archive and delete links from your Pocket list (fn, ctrl, alt and cmd) Hotkey to add new links from Chrome, Safari or your clipboard (ctrl + L) Action to deauthorize the workflow (shift) Background cache refresh Supports notifications Uses OAuth 2.0 to authorize the workflow Saves your access_token securely in OS X's keychain  
    Github: https://github.com/fniephaus/alfred-pocket
    Download: https://github.com/fniephaus/alfred-pocket/releases/latest/
     
    Feel free to give some feedback!
     
    Cheers,
    Fabio
  4. Like
    CarlosNZ got a reaction from Carlos-Sz in TimeZones - a World Clock script filter [updated to v1.7]   
    I've finally got round to addressing this. The city list will now always display the results in the same order. (I just removed the "uid" parameter.) Updated version 1.7 now available for download from the first post.
  5. Like
    CarlosNZ reacted to rice.shawn in Packal: Workflow and Theme Repository   
    Re: #1 — Not yet. Packal is collecting download statistics, but I haven't written a way for workflow authors to see them. That is on the todo list. Also, the Packal workflow has a "reporting" mechanism (which can easily be turned off) to send workflow information back to the Packal server. Basically, it sends a report approximately 1/week about which workflows are installed and which of those are enabled/disabled. I figure that information could be great for workflow developers to have. That functionality is mostly written, so it should be included in the initial release.
     
    Re: #2 — Not yet, but good idea. I'll put that on the todo list and let everyone know when it's there.
     
    One new thing about Packal, though: when you release a workflow, you can now specify a Github Repo if you use one, and the workflow page will link to the repo.
  6. Like
    CarlosNZ reacted to Andrew in Cheeky little transparency blur hack for themes   
    Just to let you know, this will be making an appearance back in 2.2.1 in Mavericks... woohooo
  7. Like
    CarlosNZ reacted to rice.shawn in TimeZones - a World Clock script filter [updated to v1.7]   
    It is weird, but it's so ingrained that it's hard to remove. It's like names: I live in NYC and everyone knows where the Triboro bridge is, except that it doesn't exist anymore because it was renamed the Robert F Kennedy Bridge six years ago. When I mentioned this to New Yorkers, they have no idea and will still refer to it as the Triboro bridge.
     
    The main upshot about DST is that it helps move regular business hours in line with seasonal light levels, which does have an effect that it conserves some energy usage. The other great thing is that once a year, the bars get to stay open an extra hour in the US. It's always a magical weekend. Everything else about it sucks.
     
    Anyway, adding accounting information for DST might be fairly hard in bash, but I do know that PHP has some great built-in functions to detect DST. A fix might be to use PHP to check for DST and adjust accordingly. The drawback is that it will make the workflow's performance suffer a bit.
  8. Like
    CarlosNZ got a reaction from utsolomon14 in EggTimer v2 [updated to 2.0 final]   
    Hey folks,
     
    I've been chugging away building a new version of my EggTimer extension to take advantage of Alfred 2's new features. And now it's ready for whoever would like to to have a playaround with it and see what they think:
     
    EggTimer v2.0
     
     
    It will also be available at Tom's Alfred Repo, but I personally haven't had a chance to test that yet, so let me know how it goes for you.
     
    Now, it's very much a beta, as there's several things that don't work as well as I'd like yet, but I'm pretty pleased with how the integration with Alfred 2's new live results feedback via the Script Filter is working. My aim is to have a really nicely polished, easy-to-use (no users fiddling with config files) workflow ready to release by the time Alfred 2 goes public, so any comments or suggestions are most welcome.  It's ready! (22 March 2013)
     
    I've included a full summary of all the functionality in the documentation included in the download (enter timer help in Alfred), but here's just a quick overview of the features:
    Simple timers Auto-repeating timers Alarms (set a specific time) Snooze function Repeat function Recent Timers list (choose one to restart) Full integration into Alfred's results window. Couple of quick caveats:
    EggTimer currently requires growlnotify to display notifications when timers finish. This is because the timer process completely decouples from Alfred to run in the background, so it can’t feed back its output to Alfred. I’m working on a solution to use a Notification Centre alert option to make this as seamless as possible to the user.
    Currently, running timers won’t restart after a crash or a reboot. I’m working on a solution to this which I aim to have working soon.
    Okay, that's about it. Enjoy, and let me know how it works for you.
     
    ----
     
    21 January 2013: Updated to beta 2
     
    Changes:
    Timers/Alarms now use a “while…” loop to check due time against time of day (instead of just sleeping for a duration). This prevents the problem of timers running late if the computer was put to sleep. (Don't know why I didn't just do this to begin with.) ----
     
    24 January 2013: Updated to beta 3
     
    Changes:
    Now uses recommended working folders for storing timer info and preferences. The main benefit from the user point of view is that future updates won’t overwrite your timers and preferences. Timers and Auto-timers now accept hour:minute input. Syntax is timer HRS:MINS Reminder. Can now stop timers from the timer list using the option-key modifier. Kind of an ugly implementation though, as it will display the same information regardless of whether it’s context-appropriate. Trying to think of a better way to make this work. (Suggestions welcome!) Timers will be restored if they have crashed. This is only partially implemented though, because it’ll only check if you actually run the workflow. It won’t restore them at login yet, which is more important. Working on it. Miscellaneous minor tweaks. ----
     
    27 January 2013: Updated to beta 4
     
    Changes:
    The big one: will now resume timers after restart/re-login. EggTimer adds an entry to the OS X launchd daemon to check for and resume timers at startup. You will be prompted to give permission for this on first launch of EggTimer. New keyword/workflow structure. Check out the workflow config panel to see what’s what. If you’d prefer the old ones (all starting with timer), just change them yourself (eg. repeat -> timer repeat). You’ll note that from the timer list (timers or hotkey Ctrl-T) you can also select to launch a new timer or alarm (courtesy of Alfred’s new Applescript-ability). Now has a “nuke” option (timer nuke) to reset EggTimer back to initial blank config. (Deletes all working folders, cancels running timers, uninstalls startup item.) Fixed bug with “08” and “09” minutes entries when using hrs:mins timer format. More specific icons and other miscellaneous UI tweaks. beta4a
    Fixed minor (and embarrassing) regression. ----
     
    28 January 2013: Updated to beta4b
     
    Changes:
    Fixed absolute path reference preventing permission dialog from launching.  
    28 January 2013: Updated to beta4c
     
    Changes:
    Doh! One more pesky absolute path eliminated. There's still a bit of weirdness with resuming timers after a login though, so I'm still trying to figure that out. Maybe answer "no" to installing startup item for now.. beta4d
    Okay, the problem was fairly minor (just me being scatterbrained ), so the startup check should work nicely now. Here's hoping! ---
     
    22 March 2013: Updated to v2.0 (final)
    I've finally integrated proper notifications for the completed timers. It will work with either Growl or Notification Centre, depending on what you have selected in the workflow config. growlnotify is no longer required, and you'll find "EggTimer" as a properly registered application within Growl's preferences (where you can tweak it). Miscellaneous tweaks and tidy-ups (including documentation - timer help to display)
  9. Like
    CarlosNZ reacted to Benzi in Battery - view summary stats about your laptop battery   
    Description: Shows summary information about your laptop battery (charge, time, status, charge cycles, and health - % of maximum charge your battery can now hold compared to its original design capacity)
    Usage: enter the keyword "battery"
    Tested on: Mountain Lion, MacBook Pro
    Download: from here
     
     
  10. Like
    CarlosNZ got a reaction from parekh in TimeZones - a World Clock script filter [updated to v1.7]   
    This is almost certainly due to a daylight savings change in either your city or the city in question. Just run an update "keyword: timezone update" to refresh the workflow's list of city offsets and it should be correct again. (FYI, LA is showing up as PST for me.)
     
    Cheers.
  11. Like
    CarlosNZ got a reaction from parekh in TimeZones - a World Clock script filter [updated to v1.7]   
    The workflow calculates the difference between the requested city and your local time (as per your computer's clock) and stores it as an offset from your computer time.
     
    Are you doing a "live" lookup (ie. "tz place-not-saved"), or do you have Los Angeles stored in your quick list (ie. keyword "tz")? If the latter, then yes, the US has recently changed to DST so a refresh of saved offsets will have been required. If the former, then that result should be correct regardless.
     
    I'm not sure why you had to update last week and again today. The only thing I can think of is that it might have been a long time (ie nearly 6 months) since you last used the workflow so DST had expired, and then it was re-implemented just this last weekend.
     
    Perhaps in a future update, I'll be able to store the DST change dates with the saved cities and automatically account for it or, at the very least, remind the user to manually update. I'll see if I can find some time to have a look at that in the near future. Thanks for your input.
  12. Like
    CarlosNZ got a reaction from nikivi in EggTimer v2 [updated to 2.0 final]   
    Hey folks,
     
    I've been chugging away building a new version of my EggTimer extension to take advantage of Alfred 2's new features. And now it's ready for whoever would like to to have a playaround with it and see what they think:
     
    EggTimer v2.0
     
     
    It will also be available at Tom's Alfred Repo, but I personally haven't had a chance to test that yet, so let me know how it goes for you.
     
    Now, it's very much a beta, as there's several things that don't work as well as I'd like yet, but I'm pretty pleased with how the integration with Alfred 2's new live results feedback via the Script Filter is working. My aim is to have a really nicely polished, easy-to-use (no users fiddling with config files) workflow ready to release by the time Alfred 2 goes public, so any comments or suggestions are most welcome.  It's ready! (22 March 2013)
     
    I've included a full summary of all the functionality in the documentation included in the download (enter timer help in Alfred), but here's just a quick overview of the features:
    Simple timers Auto-repeating timers Alarms (set a specific time) Snooze function Repeat function Recent Timers list (choose one to restart) Full integration into Alfred's results window. Couple of quick caveats:
    EggTimer currently requires growlnotify to display notifications when timers finish. This is because the timer process completely decouples from Alfred to run in the background, so it can’t feed back its output to Alfred. I’m working on a solution to use a Notification Centre alert option to make this as seamless as possible to the user.
    Currently, running timers won’t restart after a crash or a reboot. I’m working on a solution to this which I aim to have working soon.
    Okay, that's about it. Enjoy, and let me know how it works for you.
     
    ----
     
    21 January 2013: Updated to beta 2
     
    Changes:
    Timers/Alarms now use a “while…” loop to check due time against time of day (instead of just sleeping for a duration). This prevents the problem of timers running late if the computer was put to sleep. (Don't know why I didn't just do this to begin with.) ----
     
    24 January 2013: Updated to beta 3
     
    Changes:
    Now uses recommended working folders for storing timer info and preferences. The main benefit from the user point of view is that future updates won’t overwrite your timers and preferences. Timers and Auto-timers now accept hour:minute input. Syntax is timer HRS:MINS Reminder. Can now stop timers from the timer list using the option-key modifier. Kind of an ugly implementation though, as it will display the same information regardless of whether it’s context-appropriate. Trying to think of a better way to make this work. (Suggestions welcome!) Timers will be restored if they have crashed. This is only partially implemented though, because it’ll only check if you actually run the workflow. It won’t restore them at login yet, which is more important. Working on it. Miscellaneous minor tweaks. ----
     
    27 January 2013: Updated to beta 4
     
    Changes:
    The big one: will now resume timers after restart/re-login. EggTimer adds an entry to the OS X launchd daemon to check for and resume timers at startup. You will be prompted to give permission for this on first launch of EggTimer. New keyword/workflow structure. Check out the workflow config panel to see what’s what. If you’d prefer the old ones (all starting with timer), just change them yourself (eg. repeat -> timer repeat). You’ll note that from the timer list (timers or hotkey Ctrl-T) you can also select to launch a new timer or alarm (courtesy of Alfred’s new Applescript-ability). Now has a “nuke” option (timer nuke) to reset EggTimer back to initial blank config. (Deletes all working folders, cancels running timers, uninstalls startup item.) Fixed bug with “08” and “09” minutes entries when using hrs:mins timer format. More specific icons and other miscellaneous UI tweaks. beta4a
    Fixed minor (and embarrassing) regression. ----
     
    28 January 2013: Updated to beta4b
     
    Changes:
    Fixed absolute path reference preventing permission dialog from launching.  
    28 January 2013: Updated to beta4c
     
    Changes:
    Doh! One more pesky absolute path eliminated. There's still a bit of weirdness with resuming timers after a login though, so I'm still trying to figure that out. Maybe answer "no" to installing startup item for now.. beta4d
    Okay, the problem was fairly minor (just me being scatterbrained ), so the startup check should work nicely now. Here's hoping! ---
     
    22 March 2013: Updated to v2.0 (final)
    I've finally integrated proper notifications for the completed timers. It will work with either Growl or Notification Centre, depending on what you have selected in the workflow config. growlnotify is no longer required, and you'll find "EggTimer" as a properly registered application within Growl's preferences (where you can tweak it). Miscellaneous tweaks and tidy-ups (including documentation - timer help to display)
  13. Like
    CarlosNZ got a reaction from surrealroad in EggTimer v2 [updated to 2.0 final]   
    Hey folks,
     
    I've been chugging away building a new version of my EggTimer extension to take advantage of Alfred 2's new features. And now it's ready for whoever would like to to have a playaround with it and see what they think:
     
    EggTimer v2.0
     
     
    It will also be available at Tom's Alfred Repo, but I personally haven't had a chance to test that yet, so let me know how it goes for you.
     
    Now, it's very much a beta, as there's several things that don't work as well as I'd like yet, but I'm pretty pleased with how the integration with Alfred 2's new live results feedback via the Script Filter is working. My aim is to have a really nicely polished, easy-to-use (no users fiddling with config files) workflow ready to release by the time Alfred 2 goes public, so any comments or suggestions are most welcome.  It's ready! (22 March 2013)
     
    I've included a full summary of all the functionality in the documentation included in the download (enter timer help in Alfred), but here's just a quick overview of the features:
    Simple timers Auto-repeating timers Alarms (set a specific time) Snooze function Repeat function Recent Timers list (choose one to restart) Full integration into Alfred's results window. Couple of quick caveats:
    EggTimer currently requires growlnotify to display notifications when timers finish. This is because the timer process completely decouples from Alfred to run in the background, so it can’t feed back its output to Alfred. I’m working on a solution to use a Notification Centre alert option to make this as seamless as possible to the user.
    Currently, running timers won’t restart after a crash or a reboot. I’m working on a solution to this which I aim to have working soon.
    Okay, that's about it. Enjoy, and let me know how it works for you.
     
    ----
     
    21 January 2013: Updated to beta 2
     
    Changes:
    Timers/Alarms now use a “while…” loop to check due time against time of day (instead of just sleeping for a duration). This prevents the problem of timers running late if the computer was put to sleep. (Don't know why I didn't just do this to begin with.) ----
     
    24 January 2013: Updated to beta 3
     
    Changes:
    Now uses recommended working folders for storing timer info and preferences. The main benefit from the user point of view is that future updates won’t overwrite your timers and preferences. Timers and Auto-timers now accept hour:minute input. Syntax is timer HRS:MINS Reminder. Can now stop timers from the timer list using the option-key modifier. Kind of an ugly implementation though, as it will display the same information regardless of whether it’s context-appropriate. Trying to think of a better way to make this work. (Suggestions welcome!) Timers will be restored if they have crashed. This is only partially implemented though, because it’ll only check if you actually run the workflow. It won’t restore them at login yet, which is more important. Working on it. Miscellaneous minor tweaks. ----
     
    27 January 2013: Updated to beta 4
     
    Changes:
    The big one: will now resume timers after restart/re-login. EggTimer adds an entry to the OS X launchd daemon to check for and resume timers at startup. You will be prompted to give permission for this on first launch of EggTimer. New keyword/workflow structure. Check out the workflow config panel to see what’s what. If you’d prefer the old ones (all starting with timer), just change them yourself (eg. repeat -> timer repeat). You’ll note that from the timer list (timers or hotkey Ctrl-T) you can also select to launch a new timer or alarm (courtesy of Alfred’s new Applescript-ability). Now has a “nuke” option (timer nuke) to reset EggTimer back to initial blank config. (Deletes all working folders, cancels running timers, uninstalls startup item.) Fixed bug with “08” and “09” minutes entries when using hrs:mins timer format. More specific icons and other miscellaneous UI tweaks. beta4a
    Fixed minor (and embarrassing) regression. ----
     
    28 January 2013: Updated to beta4b
     
    Changes:
    Fixed absolute path reference preventing permission dialog from launching.  
    28 January 2013: Updated to beta4c
     
    Changes:
    Doh! One more pesky absolute path eliminated. There's still a bit of weirdness with resuming timers after a login though, so I'm still trying to figure that out. Maybe answer "no" to installing startup item for now.. beta4d
    Okay, the problem was fairly minor (just me being scatterbrained ), so the startup check should work nicely now. Here's hoping! ---
     
    22 March 2013: Updated to v2.0 (final)
    I've finally integrated proper notifications for the completed timers. It will work with either Growl or Notification Centre, depending on what you have selected in the workflow config. growlnotify is no longer required, and you'll find "EggTimer" as a properly registered application within Growl's preferences (where you can tweak it). Miscellaneous tweaks and tidy-ups (including documentation - timer help to display)
  14. Like
    CarlosNZ got a reaction from alexcory in New workflow - Upload to ImageShack [updated to v1.01]   
    You can actually just select the files you want in the Finder, then use the "File Selection" hotkey to show it in Alfred:

    I've changed mine from the default, but you can find the hotkey in the Preferences under Features->File Search->Actions.
     
    Cheers.
  15. Like
    CarlosNZ got a reaction from daxdavis in Dial with your iPhone from Alfred [updated to v1.41a]   
    Hey folks,
     
    I've updated the workflow to allow for the punctuation characters that can be in a valid phone number (brackets, *, #, etc). Also, now has a GUI prompt for your API key rather than requiring the user to manually edit the code.
     
    Hope it works well for you all.
     
    C
  16. Like
    CarlosNZ reacted to marct in Tiny PNG workflow [Updated to v1.2]   
    Thanks for this fantastic work!
  17. Like
    CarlosNZ reacted to ohennig in EggTimer v2 [updated to 2.0 final]   
    I had the same issue with recent timers and discovered that I didn't have the carlosnz.eggtimer2-folder.
    I tried "Timer Nuke" and that worked for me.
  18. Like
    CarlosNZ got a reaction from marct in Tiny PNG workflow [Updated to v1.2]   
    Yes -- they have released a new version of the TinyPNG API.
     
    I'll try and get a chance to update the workflow in the next few days. Hopefully by the weekend, so stand by.
     
    Glad to hear you're finding it useful.
     
    Cheers,
    Carl.
  19. Like
    CarlosNZ got a reaction from ivofrolov in EggTimer v2 [updated to 2.0 final]   
    Hey folks,
     
    I've been chugging away building a new version of my EggTimer extension to take advantage of Alfred 2's new features. And now it's ready for whoever would like to to have a playaround with it and see what they think:
     
    EggTimer v2.0
     
     
    It will also be available at Tom's Alfred Repo, but I personally haven't had a chance to test that yet, so let me know how it goes for you.
     
    Now, it's very much a beta, as there's several things that don't work as well as I'd like yet, but I'm pretty pleased with how the integration with Alfred 2's new live results feedback via the Script Filter is working. My aim is to have a really nicely polished, easy-to-use (no users fiddling with config files) workflow ready to release by the time Alfred 2 goes public, so any comments or suggestions are most welcome.  It's ready! (22 March 2013)
     
    I've included a full summary of all the functionality in the documentation included in the download (enter timer help in Alfred), but here's just a quick overview of the features:
    Simple timers Auto-repeating timers Alarms (set a specific time) Snooze function Repeat function Recent Timers list (choose one to restart) Full integration into Alfred's results window. Couple of quick caveats:
    EggTimer currently requires growlnotify to display notifications when timers finish. This is because the timer process completely decouples from Alfred to run in the background, so it can’t feed back its output to Alfred. I’m working on a solution to use a Notification Centre alert option to make this as seamless as possible to the user.
    Currently, running timers won’t restart after a crash or a reboot. I’m working on a solution to this which I aim to have working soon.
    Okay, that's about it. Enjoy, and let me know how it works for you.
     
    ----
     
    21 January 2013: Updated to beta 2
     
    Changes:
    Timers/Alarms now use a “while…” loop to check due time against time of day (instead of just sleeping for a duration). This prevents the problem of timers running late if the computer was put to sleep. (Don't know why I didn't just do this to begin with.) ----
     
    24 January 2013: Updated to beta 3
     
    Changes:
    Now uses recommended working folders for storing timer info and preferences. The main benefit from the user point of view is that future updates won’t overwrite your timers and preferences. Timers and Auto-timers now accept hour:minute input. Syntax is timer HRS:MINS Reminder. Can now stop timers from the timer list using the option-key modifier. Kind of an ugly implementation though, as it will display the same information regardless of whether it’s context-appropriate. Trying to think of a better way to make this work. (Suggestions welcome!) Timers will be restored if they have crashed. This is only partially implemented though, because it’ll only check if you actually run the workflow. It won’t restore them at login yet, which is more important. Working on it. Miscellaneous minor tweaks. ----
     
    27 January 2013: Updated to beta 4
     
    Changes:
    The big one: will now resume timers after restart/re-login. EggTimer adds an entry to the OS X launchd daemon to check for and resume timers at startup. You will be prompted to give permission for this on first launch of EggTimer. New keyword/workflow structure. Check out the workflow config panel to see what’s what. If you’d prefer the old ones (all starting with timer), just change them yourself (eg. repeat -> timer repeat). You’ll note that from the timer list (timers or hotkey Ctrl-T) you can also select to launch a new timer or alarm (courtesy of Alfred’s new Applescript-ability). Now has a “nuke” option (timer nuke) to reset EggTimer back to initial blank config. (Deletes all working folders, cancels running timers, uninstalls startup item.) Fixed bug with “08” and “09” minutes entries when using hrs:mins timer format. More specific icons and other miscellaneous UI tweaks. beta4a
    Fixed minor (and embarrassing) regression. ----
     
    28 January 2013: Updated to beta4b
     
    Changes:
    Fixed absolute path reference preventing permission dialog from launching.  
    28 January 2013: Updated to beta4c
     
    Changes:
    Doh! One more pesky absolute path eliminated. There's still a bit of weirdness with resuming timers after a login though, so I'm still trying to figure that out. Maybe answer "no" to installing startup item for now.. beta4d
    Okay, the problem was fairly minor (just me being scatterbrained ), so the startup check should work nicely now. Here's hoping! ---
     
    22 March 2013: Updated to v2.0 (final)
    I've finally integrated proper notifications for the completed timers. It will work with either Growl or Notification Centre, depending on what you have selected in the workflow config. growlnotify is no longer required, and you'll find "EggTimer" as a properly registered application within Growl's preferences (where you can tweak it). Miscellaneous tweaks and tidy-ups (including documentation - timer help to display)
  20. Like
    CarlosNZ got a reaction from emilingerslev in TimeZones - a World Clock script filter [updated to v1.7]   
    Here's another little tool I've just whipped up:
     

    Get an instant list of the current time in various cities around the world. Which you can customize, of course.
     
    Main keyword: tz (for TimeZones) - this just shows the World Clock list (seen above). (Select a city for a Large Type display.) To remove a city from the list - option-select it. To add a new city - timezone add Name of City To update all cities' timezone offset information - timezone update To look up the time in a place without storing it (custom loookup), just keep typing the place name after the initial tz (eg. tz timbuktu) To move the location of your stored city list - timezone move Download v1.7a
     
    This workflow saves a list of your cities and their UTC offsets locally, so the basic world clock will display instantly. Adding new city information is done via an API call to Google Wolfram Alpha. The only downside to locally cached offsets is that there's no provision for automatically updating for Daylight Savings changes, but a manual timezone update will refresh all the cities with their current offset.
     
    Enjoy. As usual, I welcome comments, bug reports, feature requests, etc.
     
    ----
     
    28 March 2013 - UPDATE to v1.5
    Major rewrite - now uses Google Maps APIs, which should be a lot more reliable and consistent. Flag icons! Bit of eye candy, courtesy of http://www.free-country-flags.com (and managed to squeeze flags for every country in the world into just over 400k - thank you TinyPNG ) More detail retrieved and displayed, including timezone name, country, etc. When doing a full "update", a text file is saved to your Desktop summarising any changes found. General enhancement and tweaks. PLEASE NOTE: Because this version stores its data substantially different to previous versions, it will create a new timezones.txt file with default cities. However, it will attempt to save your old timezones.txt file to your Desktop, so you should be able to rebuild your previous list without too much hassle.
     
    A quick note about the flags: The workflow simply compares the retrieved name of the country and does a simple name match against the workflow's local repository of flag icons. From my testing, it's working very well, but I'd appreciate it if you'd report back if you find any countries that don't properly match a flag icon. Cheers.
     
    ----
     
    31 March 2013  - UPDATE to v1.6
    New feature: Custom lookups. Just keep typing a new place name after the tz keyword to look up the time in a place without saving it to your saved list. Added support for phyllisstein's Alleyoop auto-updater. [EXPERIMENTAL] - support for autocomplete for adding place names (timezone add). You'll need to add a keyword yourself to the script filter if you want to try it out. The reason I haven't enabled it by default is that I've found it kind of slow and I'm not sure it's actually an improvement over the current method. Let me know what you think.
    [Add a keyword to this script filter if you'd like to try it out] Novelty: Added (unofficial) Antarctica flag to flag repository. (Try tz south pole.   ) ----
     
    2 April 2013 — UPDATE to v1.61
    Small fix for Dutch (Netherlands) flag matching.  
    ----
     
    22 March 2014 — UPDATE to v1.7
    City List now always shows in the same order. (Achieved by removing “uid” parameter.) Removed Alleyoop updater. ----


    22 March 2014 — UPDATE to v1.7a
        New 256x256px icon
  21. Like
    CarlosNZ reacted to michaelwills in TimeZones - a World Clock script filter [updated to v1.7]   
    This is really nice. Found it highlighted here.
  22. Thanks
    CarlosNZ got a reaction from bivalvegruff in TimeZones - a World Clock script filter [updated to v1.7]   
    Here's another little tool I've just whipped up:
     

    Get an instant list of the current time in various cities around the world. Which you can customize, of course.
     
    Main keyword: tz (for TimeZones) - this just shows the World Clock list (seen above). (Select a city for a Large Type display.) To remove a city from the list - option-select it. To add a new city - timezone add Name of City To update all cities' timezone offset information - timezone update To look up the time in a place without storing it (custom loookup), just keep typing the place name after the initial tz (eg. tz timbuktu) To move the location of your stored city list - timezone move Download v1.7a
     
    This workflow saves a list of your cities and their UTC offsets locally, so the basic world clock will display instantly. Adding new city information is done via an API call to Google Wolfram Alpha. The only downside to locally cached offsets is that there's no provision for automatically updating for Daylight Savings changes, but a manual timezone update will refresh all the cities with their current offset.
     
    Enjoy. As usual, I welcome comments, bug reports, feature requests, etc.
     
    ----
     
    28 March 2013 - UPDATE to v1.5
    Major rewrite - now uses Google Maps APIs, which should be a lot more reliable and consistent. Flag icons! Bit of eye candy, courtesy of http://www.free-country-flags.com (and managed to squeeze flags for every country in the world into just over 400k - thank you TinyPNG ) More detail retrieved and displayed, including timezone name, country, etc. When doing a full "update", a text file is saved to your Desktop summarising any changes found. General enhancement and tweaks. PLEASE NOTE: Because this version stores its data substantially different to previous versions, it will create a new timezones.txt file with default cities. However, it will attempt to save your old timezones.txt file to your Desktop, so you should be able to rebuild your previous list without too much hassle.
     
    A quick note about the flags: The workflow simply compares the retrieved name of the country and does a simple name match against the workflow's local repository of flag icons. From my testing, it's working very well, but I'd appreciate it if you'd report back if you find any countries that don't properly match a flag icon. Cheers.
     
    ----
     
    31 March 2013  - UPDATE to v1.6
    New feature: Custom lookups. Just keep typing a new place name after the tz keyword to look up the time in a place without saving it to your saved list. Added support for phyllisstein's Alleyoop auto-updater. [EXPERIMENTAL] - support for autocomplete for adding place names (timezone add). You'll need to add a keyword yourself to the script filter if you want to try it out. The reason I haven't enabled it by default is that I've found it kind of slow and I'm not sure it's actually an improvement over the current method. Let me know what you think.
    [Add a keyword to this script filter if you'd like to try it out] Novelty: Added (unofficial) Antarctica flag to flag repository. (Try tz south pole.   ) ----
     
    2 April 2013 — UPDATE to v1.61
    Small fix for Dutch (Netherlands) flag matching.  
    ----
     
    22 March 2014 — UPDATE to v1.7
    City List now always shows in the same order. (Achieved by removing “uid” parameter.) Removed Alleyoop updater. ----


    22 March 2014 — UPDATE to v1.7a
        New 256x256px icon
  23. Like
    CarlosNZ got a reaction from dfay in EggTimer v2 [updated to 2.0 final]   
    Hey folks,
     
    I've been chugging away building a new version of my EggTimer extension to take advantage of Alfred 2's new features. And now it's ready for whoever would like to to have a playaround with it and see what they think:
     
    EggTimer v2.0
     
     
    It will also be available at Tom's Alfred Repo, but I personally haven't had a chance to test that yet, so let me know how it goes for you.
     
    Now, it's very much a beta, as there's several things that don't work as well as I'd like yet, but I'm pretty pleased with how the integration with Alfred 2's new live results feedback via the Script Filter is working. My aim is to have a really nicely polished, easy-to-use (no users fiddling with config files) workflow ready to release by the time Alfred 2 goes public, so any comments or suggestions are most welcome.  It's ready! (22 March 2013)
     
    I've included a full summary of all the functionality in the documentation included in the download (enter timer help in Alfred), but here's just a quick overview of the features:
    Simple timers Auto-repeating timers Alarms (set a specific time) Snooze function Repeat function Recent Timers list (choose one to restart) Full integration into Alfred's results window. Couple of quick caveats:
    EggTimer currently requires growlnotify to display notifications when timers finish. This is because the timer process completely decouples from Alfred to run in the background, so it can’t feed back its output to Alfred. I’m working on a solution to use a Notification Centre alert option to make this as seamless as possible to the user.
    Currently, running timers won’t restart after a crash or a reboot. I’m working on a solution to this which I aim to have working soon.
    Okay, that's about it. Enjoy, and let me know how it works for you.
     
    ----
     
    21 January 2013: Updated to beta 2
     
    Changes:
    Timers/Alarms now use a “while…” loop to check due time against time of day (instead of just sleeping for a duration). This prevents the problem of timers running late if the computer was put to sleep. (Don't know why I didn't just do this to begin with.) ----
     
    24 January 2013: Updated to beta 3
     
    Changes:
    Now uses recommended working folders for storing timer info and preferences. The main benefit from the user point of view is that future updates won’t overwrite your timers and preferences. Timers and Auto-timers now accept hour:minute input. Syntax is timer HRS:MINS Reminder. Can now stop timers from the timer list using the option-key modifier. Kind of an ugly implementation though, as it will display the same information regardless of whether it’s context-appropriate. Trying to think of a better way to make this work. (Suggestions welcome!) Timers will be restored if they have crashed. This is only partially implemented though, because it’ll only check if you actually run the workflow. It won’t restore them at login yet, which is more important. Working on it. Miscellaneous minor tweaks. ----
     
    27 January 2013: Updated to beta 4
     
    Changes:
    The big one: will now resume timers after restart/re-login. EggTimer adds an entry to the OS X launchd daemon to check for and resume timers at startup. You will be prompted to give permission for this on first launch of EggTimer. New keyword/workflow structure. Check out the workflow config panel to see what’s what. If you’d prefer the old ones (all starting with timer), just change them yourself (eg. repeat -> timer repeat). You’ll note that from the timer list (timers or hotkey Ctrl-T) you can also select to launch a new timer or alarm (courtesy of Alfred’s new Applescript-ability). Now has a “nuke” option (timer nuke) to reset EggTimer back to initial blank config. (Deletes all working folders, cancels running timers, uninstalls startup item.) Fixed bug with “08” and “09” minutes entries when using hrs:mins timer format. More specific icons and other miscellaneous UI tweaks. beta4a
    Fixed minor (and embarrassing) regression. ----
     
    28 January 2013: Updated to beta4b
     
    Changes:
    Fixed absolute path reference preventing permission dialog from launching.  
    28 January 2013: Updated to beta4c
     
    Changes:
    Doh! One more pesky absolute path eliminated. There's still a bit of weirdness with resuming timers after a login though, so I'm still trying to figure that out. Maybe answer "no" to installing startup item for now.. beta4d
    Okay, the problem was fairly minor (just me being scatterbrained ), so the startup check should work nicely now. Here's hoping! ---
     
    22 March 2013: Updated to v2.0 (final)
    I've finally integrated proper notifications for the completed timers. It will work with either Growl or Notification Centre, depending on what you have selected in the workflow config. growlnotify is no longer required, and you'll find "EggTimer" as a properly registered application within Growl's preferences (where you can tweak it). Miscellaneous tweaks and tidy-ups (including documentation - timer help to display)
  24. Like
    CarlosNZ got a reaction from nik in Tiny PNG workflow [Updated to v1.2]   
    Hi Nik,
     
    you need to launch Alfred with the "File Selection" hotkey, which you'll find at the bottom of this preference page:

    (I can't remember what the default hotkey is, since I've changed mine).
     
    A lot of new users don't seem to aware of the "File Selection" hotkey, I've found, so hopefully that will sort you out.
     
    I might add an option in a subsequent update to act on the current Finder selection when launched from Alfred's main window, like I've done with my DeskDrawer workflow.
  25. Like
    CarlosNZ got a reaction from nik in Tiny PNG workflow [Updated to v1.2]   
    This workflow will take a set of PNG or JPG files and compress them using the online TinyPNG service.

    For more info on what it does to the image, see http://tinypng.com/

    Usage:

    This workflow works as either a File Action or a regular keyword process.

    Either:
    1) Select the PNG or JPG files you want processed (in Finder or Alfred), then select the "Compress with TinyPNG" File Action in Alfred.
    2) Select the PNG or JPG files you want processed in Finder, launch Alfred, then use the “tinypng" keyword.

    The processed files will be downloaded to a TinyPNG folder on your Desktop, along with a Report showing the success/failure of each file, and how much it has been compressed by.

    The process may take some time, especially if you have selected several large image files, but you will notified on completion. However, if you have Growl/growlnotify installed, you will get a per-file notification as it progresses.
     
    A Note on Heavy Usage:
     
    The TinyPNG API has a limit of 500 files per month. As you can imagine, once a few people are using the workflow substantially, this doesn't take long to reach. I have provided a default API key built-in so you can use the workflow immediately. However, if you intend to continue using it in any substantial capacity I strongly suggest you visit https://tinypng.com/developers and register for your own API key. You can jump there with the keyword “tinypng_getkey” in Alfred. Once you’ve got your key, save it into the workflow configuration with the keyword  “tinypng_config”
     
    Download v1.3
     
    Cheers,
    Carl
     
    ----
     
    28 November 2013 - updated to v1.1
    Updated to use the new TinyPNG.com API Now works as a regular Alfred keyword (with Finder selection) as well as File Action  
    19 March 2014 - updated to v1.2
    Now gives better error reporting on failures. (You’ll be able to tell if the monthly limit has been exceeded.) Consolidated processing to a single bash script. The Finder Selection script now just parses the input and sends it to the main script. (Irrelevant to user experience.) User can enter their own API key to prevent reaching the Free account limit when using a shared key. Updated icons (from TinyPNG.com)  
    6 October 2015 - updated to v1.3
        Now supports JPG files as well.  
×
×
  • Create New...