Jump to content

Yet Another Weather Workflow


Recommended Posts

Definitely planning on it, but no timeframe since I don't know when I'll be able to get around to it.

 

Anything in particular you're thinking of as far an update for Alfred 3? The only improvement on my radar at the moment is switching from my hand-rolled configuration to using the built-in one.

Link to post
  • Replies 64
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

I couldn't find any forecast workflows that were quite to my liking, so I whipped one up that gets a forecast from forecast.io:     Note: requires at least Mavericks. Not tested on

Just FYI, since forecast.io is becoming darksky.net, I've changed forecast.alfredworkflow accordingly to dark-sky.alfredworkflow:   https://github.com/kejadlen/dark-sky.alfredworkflow h

Well, that was pretty silly of me. I'll put the version somewhere in the next release. The latest versions of this workflow should have "config-forecast" instead of "forecast-config". If you're still seeing the latter, can you try deleting the workflow and installing the latest one?

 

 

Alfred migrates user keywords. If you've changed the keyword in an update (instead of deleting the old Keyword object and adding a new one), I think Alfred will overwrite your keyword with the user's (i.e. the old one) in the new version of the workflow.

Link to post
  • 4 weeks later...

Couple things with this version.

 

1. Clicking on a date doesn't open the page in a browser window.

2. It looks like you shipped it with your API keys, but that might be a bad idea because if people don't change it, you're going to run out of your 1000 calls a day on forecast.io. Unless I'm missing something. I've put in my APIs.

3. How do I config this now for settings like F/C degrees, location etc?

 

*edit* Never mind on 3. Forgot to read the updated github page. 

Edited by LiamW
Link to post

Another thing. Screenshot is from Wed. at 7:20am. It doesn't show today's forecast other than current weather, and next hour. The ⌘4 option is actually Thursdays forecast. There is no day for Thursday either since it's not labeled properly and makes it look like that's part of todays forecast. 

 

https://www.dropbox.com/s/9u0zxs3agoxpx30/Screenshot%202016-07-27%2007.18.43.png?dl=0

 

Am I just misunderstanding how this works?

Link to post

This version breaks as I believe I don't have exact versions of gems you're including like rake? Haven't really looked through it yet.

[2016-07-27 13:10:16][ERROR: input.scriptfilter] Code 1: /Library/Ruby/Gems/2.0.0/gems/bundler-1.10.6/lib/bundler/spec_set.rb:92:in `block in materialize': Could not find rake-11.1.2 in any of the sources (Bundler::GemNotFound)
from /Library/Ruby/Gems/2.0.0/gems/bundler-1.10.6/lib/bundler/spec_set.rb:85:in `map!'
from /Library/Ruby/Gems/2.0.0/gems/bundler-1.10.6/lib/bundler/spec_set.rb:85:in `materialize'
from /Library/Ruby/Gems/2.0.0/gems/bundler-1.10.6/lib/bundler/definition.rb:140:in `specs'
from /Library/Ruby/Gems/2.0.0/gems/bundler-1.10.6/lib/bundler/definition.rb:185:in `specs_for'
from /Library/Ruby/Gems/2.0.0/gems/bundler-1.10.6/lib/bundler/definition.rb:174:in `requested_specs'
from /Library/Ruby/Gems/2.0.0/gems/bundler-1.10.6/lib/bundler/environment.rb:18:in `requested_specs'
from /Library/Ruby/Gems/2.0.0/gems/bundler-1.10.6/lib/bundler/runtime.rb:13:in `setup'
from /Library/Ruby/Gems/2.0.0/gems/bundler-1.10.6/lib/bundler.rb:127:in `setup'
from /Library/Ruby/Gems/2.0.0/gems/bundler-1.10.6/lib/bundler/setup.rb:18:in `<top (required)>'
from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:135:in `require'
from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:135:in `rescue in require'
from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:144:in `require'
from forecast.rb:2:in `<main>'
Link to post

Looks good. 2 questions though.

 

1. When upgrading to new versions, variable settings in Alfred like forecast_units don't migrate over and I have to re-add them. Is this normal for Alfred 3? To be honest, haven't spent much time looking into what's new with it.

 

2. Minor thing, but when I pull up the forecast in alfred, if I pick a certain day and hit enter on it, it does open the forecast.io browser, but doesn't go to that date. Just shows current date. Would be nice if it opened that day.

 

Other than that looks and works great.

Link to post
  • 2 months later...

Just FYI, since forecast.io is becoming darksky.net, I've changed forecast.alfredworkflow accordingly to dark-sky.alfredworkflow:

 

https://github.com/kejadlen/dark-sky.alfredworkflow

https://github.com/kejadlen/dark-sky.alfredworkflow/releases/tag/v2.0.0

 

The only change needed (assuming I didn't screw up the transition) is moving from FORECAST_API_KEY to DARK_SKY_API_KEY after updating the workflow.

Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...