surrealroad

Added support for webkit nightly, grab the latest version. In terms of access to the source, everything should be readily available inside the workflow's bundle (once it's installed). The only other thing that I could do is provide the applescript in text format, but this would be a bit of a headache for me as I'd have to remember to save two copies of everything. The compiled applescript files that are included (*.scpt) *should* be editable by users, do let me know if that's not the case. One thing I haven't done, which perhaps I could, is to include some rudimentary documentation for the inner workings. I don't know if enough people would be digging around in this to make it worth my time though?

The latest version will allow you to do "r tomorrow at 11:00 to milk the goat". Tip: due to supporting both 12 and 24 hour clocks, you will get more predictable results when using "11am" instead of "11:00"

Now that the bugs are gone I feel ok about adding new stuff. Added "r in x days y hours" and "r in x hours y minutes" patterns to the latest version.

well any of those 38 are free to use any of my code if that helps.

You can dig around with the code if you like, it runs "cache-update.scpt" in the workflow folder with the bundle id as a parameter. But basically it pings a webpage (once every 4 days by default) with the bundle id, which replies with the latest version. If a new version is available, I simply add an action to alfred to download it. My implementation is a little more complex than that, mostly because I have a shared codebase between all my workflows.

Added support for Vienna. See the latest version.

You'd still need the cache to run successfully even just to be able to search for any existing reminders. The way it works now is that the cache will run every time you update any reminders using the workflow, or manually using the "r refresh", or otherwise if it hasn't been run for 2 hours. There's not much I can do to stop the CPU peaking, that's just how applescript works. EDIT: The latest version reduces the timeout to 10 seconds or so.

Yes, that latest version seems to have fixed it! Takes about 20 seconds for reminders to close, but it does close. I tried just 'r' and 'r in 5 mintes...' and both were fine. Thanks so much for sorting it. Unfortunately that hasn't quite fixed it yet; you'll find that the process simply timed out after loading 100 reminders, so "r all" will not actually show all the reminders. However, now I know that it should work I can tweak the parameters a little. Can you try the latest version? This one should allow up to 10,000 or so reminders to be processed, assuming it doesn't crash, of course-- reminders should stay open for no longer than 2 minutes.

EDIT: It's possible there's another cause for this. Can you try the new version I just uploaded? Based on your test log, it looks like Reminders is crashing. This is probably due to the high number (~500?) of incomplete reminders you seem to have, not having a test size that large to work with it's hard to know for sure. If you think it would be useful to you, I can modify the workflow so that you should at least be able to just use "radd" without it crashing.

Thanks for that. I've updated the workflow with one additional test, if you get a chance can you download and do it again?

EDIT: Looks like this is now fixed, everyone grab the latest version. Well clearly something is wrong Sorry everyone who is having this issue. I can't make it happen on either of my systems, so I need to gather more data from people who are having this problem. So if that's you, can you download today's version, which has two extra keywords, "rshow" and "radd" (will show existing, or add new reminders respectively). Try it with both of those, and let me know if one or the other works. I'll do my best to get a version out which can run some tests to see what exactly is breaking, I'll edit this post when it's ready (for those of you on the west coast, should be ready by breakfast ) Everyone having issues please now download and install the latest version, try "radd something" and "rshow all" and see if either of those work. Let me know if they do. Next run "rtest". It will take a few seconds to run, you'll get a notification that it's complete, with the results on your clipboard. Please post here with the results, or PM them to me. In the event that this doesn't flag anything up, I'll add a bunch more tests. Test results: OS version: 10.8.3 Current date: Tuesday, 9 April 2013 13:56:31 Initialize workflow path: /Users/jack/Dropbox/Alfred/Alfred.alfredpreferences/workflows/user.workflow.74D66E93-4C95-40CE-B93F-E89237A4CFAB Initialize alfred-library: OK Initialize wf-library: OK Reminders.app state: Running Fetch reminder count: 19 Fetch reminder info: OK Fetch reminder list count: 1 Fetch reminder list info: OK Run cache process: OK Fetch cache timestamp: Tuesday, 9 April 2013 13:56:39 Fetch cached reminder count: 19 Test basic query: OK Test today query: OK Test tomorrow query: OK Test in n minutes query: OK Test in n hours query: OK Test in n days query: OK Test at time query: OK Test in x list query: OK Subtitle generation: OK Test basic reminder filtering: OK Test remind today reminder filtering: OK Test due tomorrow reminder filtering: OK Test reminder list filtering: OK Current unix time: 1.365512199E+9 Test execution time: 8 seconds

Certainly can't have that! See the latest version.

Hmm. It may be that the latest version fixed a related bug, try that first. Otherwise can you let me know your OS version.

I believe that you have to have computers saved within "All Computers" in remote desktop. The current version of this workflow is quite rudimentary, it literally just (via applescript) asks remote desktop for a list of computers and then displays them. That said I've just updated the workflow which addresses some minor issues, maybe the new version will work better for you.

See the latest version.

I would think so-- how does holding ctrl down to make this happen sound?

Added support for Chromium, fixed the "option marks the reminder as complete" bug. See the latest version. In terms of the last letter getting cut off, I can't reproduce that. The only thing could be that you're a really fast typist… Whatever the cause, Alfred should catch up as long as you don't hit enter before the full query appears in the description.

Is there any particular keyword you're using where this happens? It seems to be working ok for me. Alternatively it could just be the case the very first time you run the workflow.

Fixed. See the latest version.

Here's a new theme I conceived as something of an experiment. You won't see anything you type, just a single result (you can still use the up and down keys though). For power users only! Download http://bit.ly/2wDE6Zj

From the top of the Alleyoop post: Note from Andrew: While this is a convenient method for updating workflows, I cannot endorse the use of it unless you are fully aware of the security implications of blanket updating all of your workflows. I'm currently working on a built in workflow auto-updater, for a future Alfred 2 release, that performs the standard verification checks that Alfred currently does on manual import, along with migrating your hotkey/keyword settings on upgrading. I'll also be adding 3rd party workflow developer signatures to keep you safe. I believe my own implementation of auto-update works fine. It checks once every 4 days (configurable) and just prompts as an action. If you action the the update, it merely downloads the new extension, you can then decide to install it (or not), and it will go through Alfred's standard update process. You can also disable the update checking functionality altogether, and just update manually when you like.

See the latest version.

See the latest version.

Sorry! That's my fault. I accidentally disabled all the other keywords in that release. Please download the updated version. (This is what happens when I write code late at night :/)

Funnily enough, that's the app I was thinking of too. I'll let you know.