kejadlen Posted June 10, 2016 Author Share Posted June 10, 2016 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 comment
deanishe Posted June 10, 2016 Share Posted June 10, 2016 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 comment
kleerkoat Posted June 11, 2016 Share Posted June 11, 2016 nice! thank you!what font are you using in your screen grab btw. Link to comment
LiamW Posted July 5, 2016 Share Posted July 5, 2016 (edited) Any idea why mine returns results like this? https://www.dropbox.com/s/8o8d00xfkwpdn2k/Screenshot%202016-07-05%2008.25.54.png?dl=0 It was working fine the first few times I used it, but now it's been like this for about a day.'' It also hasn't updated in a few days and is still showing results from Tuesday as of today Thursday. Edited July 7, 2016 by LiamW Link to comment
kejadlen Posted July 12, 2016 Author Share Posted July 12, 2016 @LiamW The wrong ordering is a bug in the workflow - I'll fix that in the next release. If you select one of the options, Alfred will remember that and move it higher up in the list. Link to comment
Dolge Posted July 20, 2016 Share Posted July 20, 2016 This is great - working in Alfred 3, love the config options. Thanks! Link to comment
kejadlen Posted July 26, 2016 Author Share Posted July 26, 2016 FYI, I released 1.0.5, which adds support for Alfred 3 by using the built-in environment variable support for API keys: https://github.com/kejadlen/forecast.alfredworkflow/releases/tag/v1.0.5 Link to comment
LiamW Posted July 26, 2016 Share Posted July 26, 2016 (edited) 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 July 26, 2016 by LiamW Link to comment
LiamW Posted July 27, 2016 Share Posted July 27, 2016 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 comment
kejadlen Posted July 27, 2016 Author Share Posted July 27, 2016 Thanks, LiamW! Revoked those keys and fixed the issues you pointed out in 1.0.6: https://github.com/kejadlen/forecast.alfredworkflow/releases/tag/v1.0.6 Link to comment
LiamW Posted July 27, 2016 Share Posted July 27, 2016 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 comment
kejadlen Posted July 28, 2016 Author Share Posted July 28, 2016 D'oh! Getting my process working with the new environment variables has been somewhat hairy. Released 1.0.7 which should now properly include the vendored dependencies: https://github.com/kejadlen/forecast.alfredworkflow/releases/tag/v1.0.7 Link to comment
LiamW Posted July 29, 2016 Share Posted July 29, 2016 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 comment
kejadlen Posted August 4, 2016 Author Share Posted August 4, 2016 It's a side effect of switching to Alfred 3 for this particular workflow. Other workflows might handle it better, but it would've been a lot of pretty complicated work for a problem that's pretty easy to manually fix. Released 1.0.8 which goes to the right day: https://github.com/kejadlen/forecast.alfredworkflow/releases/tag/v1.0.8 Link to comment
kejadlen Posted October 15, 2016 Author Share Posted October 15, 2016 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. xilopaint 1 Link to comment
bargepole Posted January 25, 2022 Share Posted January 25, 2022 @kejadlen, hi there! I wanted to try out your pirate-weather workflow, but I get tripped up by MacOS's (12.1) malware protection. Yours is the only workflow that I have this trouble with. I even browsed into Alfred's storage, and executed "alfred-weather" from the right-click menu, in case this would help (like with other applications), but to no avail. Any advice? Thanks! Link to comment
giovanni Posted January 25, 2022 Share Posted January 25, 2022 (edited) Hi @bargepole have you tried the instructions here? Edited January 25, 2022 by giovanni bargepole 1 Link to comment
bargepole Posted January 26, 2022 Share Posted January 26, 2022 @giovanni, thank you! This solved my problem. I was not able to find this article while searching. Link to comment
barkingsheltie Posted January 29, 2022 Share Posted January 29, 2022 On 11/18/2014 at 1:30 PM, kejadlen said: 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: http://i.imgur.com/eTuONUQ.png Note: requires at least Mavericks. Not tested on Yosemite. Download: https://github.com/kejadlen/dark-sky.alfredworkflow/releases GitHub: https://github.com/kejadlen/dark-sky.alfredworkflow In general the workflow 'works', but wondering if the switch to Darksky eliminated the forecast in-line for the Alfred window? Link to comment
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now