Default Browser workflow for Alfred

DefaultBrowser Alfred Workflow IconI am happy to release version 1.1 of the Default Browser workflow for Alfred.

This is a workflow that I have been putting together for some time and today I have released a major update to include more browsers, improved speed and a general overhaul of awesomeness.

If you have ever wanted to be able to quickly switch browsers on OSX, this might just be up your alley. My biggest desire was to be able to switch between Chrome (just an awesome browser) and Safari (for when I need to be power conscious while running on battery). This Alfred workflow fits that bill perfectly.

Where you can get it

  1. Download the .alfredworkflow file from github directly
  2. Check out the official post on the Alfred Community forums
  3. Have a browse of the workflow on Packal – the global repository for Alfred workflows

Donations

This workflow represents many hours effort of development, testing and rework. The images that have been licensed for this workflow from DepositPhotos also needed a bit of my moolah. So if you love the workflow, and get use out of it every day, if you would like to donate as a thank you to buy me more caffeine giving Diet Coke, some Cake, or to put towards a shiny new gadget you can donate to me via Paypal.

Paypal donate button

 

 

 

Browsers currently supported:

  • Chrome
  • Firefox
  • Opera
  • Safari
  • Chromium – New in V1.1
  • Canary – New in V1.1
  • SeaMonkey – New in V1.1

Change Log

  • Version 1.1 – Feature Release
    • Feature: Support additional browsers – added Chromium, Canary and SeaMonkey
    • Feature: Only show installed browsers
    • Feature: Indicate which browser is the current default
    • Feature: Added hotkey assignments (to launch workflow, launch with “chrome”, and launch with “safari”)
    • Improvement: Renamed description in Alfred to simply “Default Browser”
    • Improvement: Improved failure feedback
    • Improvement: Major code refactor to remove duplication and speed up the workflow
    • Improvement: Added an icon to the workflow
    • Improvement: defaultbrowser binary has been updated to better support integrating. This code has been put into a pull request for the official publication of defaultbrowser.

Credits

defaultbrowser binary for OSX has been created by Margus Kerma.

  • Margus has been kind enough to permit me to include the binary for defaultbrowser as part of this workflow to make distribution significantly easier.
  • For any issues with the defaultbrowser binary please log these to the official DefaultBrowser Issue Tracker.

DefaultBrowser Alfred workflow created by Stuart Ryan. If you would like to get into contact you can do so via:

License

With the exception of the workflow logo, this Alfred Workflow is provided free of charge under the GNU GENERAL PUBLIC LICENSE Version 2 June 1991.

The workflow logo is licensed only for use in this workflow and must be changed if the workflow is forked in the future.

The workflow logo has been licensed from DepositPhotos to Stuart Ryan.
DefaultBrowser Example Screenshot 1 - List Installed Browsers

DefaultBrowser Example Screenshot 2 -  Set Safari as Default

DefaultBrowser Example Screenshot 3

DefaultBrowser Example Screenshot 4 -  No such browser installed error

Rapid Browser Tabs Workflow for Alfred

Rapid Browser Tabs for Alfred LogoSome time ago while using the Search Tabs on Safari and Chrome workflow for Alfred developed by Clinton Strong, I came up with the idea to enhance the workflow to enable the addition of often used “favourites” to speed up getting access to the websites you need. After many hours of programming, many nights of testing, a splash of blood, sweat and tears and an inordinate amount of caffeine while learning how to program in Ruby :D, I can now present Rapid Browser Tabs for Safari and Chrome.

RBT for Alfred has been forked from the Search Tabs on Safari and Chrome workflow (with Clinton’s blessing) and could almost be considered v2 of Clinton’s original workflow. In addition to the ability to searching already open Chrome and Safari tabs and bring them into focus rapidly, it adds the ability to create favourites that can be searched and opened alongside already open tabs in Chrome and Safari.

So, if you are an avid Alfred user, you can get the workflow from the official Github repository directly and log any issues/ideas/feature requests on Github. You can get the full details on use of the workflow in the official Alfred Community Forum post, and it is also up on Packal as well.

License

All code in this workflow is released under the MIT License. Images used as part of the workflow are licensed only for use in this workflow and must be changed if the workflow is forked in the future.

All images have been licensed from DepositPhotos to Stuart Ryan.

Donations

This workflow represents many many hours effort of development, testing and rework. The images licensed for this workflow from DepositPhotos also needed a bit of my moolah. So if you love the workflow, and get use out of it every day, if you would like to donate as a thank you to buy me more caffeine giving Diet Coke, some cake, or to put towards a shiny new gadget you can donate to me via Paypal.

Contributing

If you are a coder head over to the official Github repo:

  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am ‘Add some feature’
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request :D

Command your browser tabs… and don’t let them command you!

Rapid Browser Tabs Workflow for Safari and Chrome on Alfred App - Pre Configure Screen
Rapid Browser Tabs Workflow for Safari and Chrome on Alfred App - Configure Screen

Rapid Browser Tabs Workflow for Safari and Chrome on Alfred App - Facebook Example

Rapid Browser Tabs Workflow for Safari and Chrome on Alfred App - Favourites Example

Foxtel iQ3 – The worst piece of technology this year?

Foxtel IQ3 Website
Ladies and gentlemen, it appears that we have a definite contender (and likely winner) of the 2015 Shonky Awards! When you pay a premium for cable television, it is every Australian’s right that, they get premium hardware… or that at least works… or that works on occasion… at least I now know, this was a woeful fallacy I was under.

On IT News (http://www.itnews.com.au/CXOChallenge/404155,innovating-for-your-life.aspx#ixzz3aeJON2n7) an article which seemingly Ms Nell Payne (Group Director Technology and Operations at Foxtel) had input into states the following:

“The company faced a bit of a hiccup when the iQ3 first launched over performance issues, though the cacophony of complaints has now hushed.”

To IT News (which was likely paraphrasing discussions with Ms Payne) and to Ms Payne herself, I provide the following response… I have an “iQ3 Saga File” My summary file on the saga currently sits at the following (time to grab some popcorn):

The first block is things that I have personally raised or have encountered myself. Wherever possible I have provided a link to at least one relevant forum post for the major items. I also highly recommend the “Overall less than spectacular operations during release” section.

At the very bottom (“Posts that say it all”) I have gone through the last two pages only of one of the forums (user feedback only, I figured this was more than enough to illustrate my point).

Throughout the process I have been very active on the forums (some of the post linked below are my own or posts I have been involved in), I like to think I am an extremely level-headed individual and I work in I.T. and know what system design, development, and testing is like… I do it day-to-day. This is one such post that I believe is quite level headed http://community.foxtel.com.au/t5/Foxtel-iQ3/class-action-regarding-IQ3/m-p/56879# (first reply).

The only way I have succeeded in using my box is to use it primarily for watching TV live or download SD catchup (recordings have been too flaky). I have been lucky enough that after much complaining and a formal complaints process, Foxtel agreed to re-activate my old IQ-HD box for 6 months at no cost until the issues were ironed out (I feel it is only fair to now let the community know) they also agreed to refund the full cost of install and the IQ3 (not all has been applied to my account yet).

The questions I ask of Foxtel are:

  1. Why have we gone just shy of 60 days since release with no update? Bundling everything into one will only likely cause new bugs rather than logical, incremental fixes with time to test in between.
  2. Why has senior management not addressed the Foxtel community yet?
  3. What will be done to compensate those that have suffered had crippled iQ3 boxes for two months (and counting)?
  4. What is being done to review your user acceptance testing plans and procedures? As has become apparent, the testing that the iQ3 was put through has failed to reveal an embarrassing number of issues.
  5. What plans are being put in place (if any) to put in place a sufficient beta testing program including real life users to test real world scenarios of future updates (to better put them through their paces)?

So feel free to vent and/or add your comments below is there anything I have currently missed from the below?

Cheers,
Stuart

My current outstanding list of bugs include:

User Interface Issues:

In some ways it has been a step backwards as well:

Overall less than spectacular operations during release:

Posts that say it all: