jason0x43

Ok, I uploaded a new version with a "log" command that will show the workflow's debug log in Console.app. Run that to show the log, then try accessing your nest. That should, hopefully, give us a better idea of what's failing.

It seemed to work fine. Try downloading it again. I uploaded a new version, then uploaded a bugfix version a few minutes afterwards. You may have the bad one.

Let me try installing a fresh copy and see if I can reproduce that.

I just posted an update with initial support for multiple Nests. In this version, a new "nest nest" command has been added to let you see the available Nests on your account and select an active one. Let me know how/if it works.

New update: the workflow now displays some basic help when no prisms are available (like right after you install the workflow).

Hmmm...that shouldn't actually be too hard, although me only having a single Nest to test with makes things trickier. I have the beginnings of a plan, though.

That was, indeed, an issue. It should be fixed now.

Ok, it kind of works. You can now start a prism at a particular URL with something like prism myPrism www.google.com. Unfortunately you can't open any URLs in an already opened prism, though. The method I'm using to make Prisms show up with a unique icon and name in the Dock is making it difficult to have Chrome do things like create new tabs or open URLs. I also changed how the workflow names apps. Before, the actual prism .app directory was named with a UUID, and the prism name was stored in a config file in the .app directory. That makes the dock look messy, though, since the name of the .app directory is what shows up on the Dock. So if you've made some prisms, they're going to have weird names when you update. I added a new modifier to the workflow to help with that -- you can hold Shift now to rename a prism.

It can't do that yet, but that sounds like a good idea. Let me see what I can do...

I just uploaded a new version of the workflow. This one adds support for Alleyoop updating, and it stores your Nest login info in the Mac OS Keychain

And now I've actually processed the rest of your post. It apparently takes several passes for me to actually read something. /sigh Anyway, the problem was that I hadn't tested the workflow with Python 2.6, which is what Snow Leopard comes with. I fixed a few incompatibilities, so it should work now.

I almost replied before I noticed the "I changed the keyword to uc" bit. Let me take a look at it and I'll see what's up...

Sorry about that. There was a bug in the prism creation function that wasn't storing the prism's config properly. It should be fixed now.

Added Alleyoop support

Now with Alleyoop support!

I just added a new freeform query mode to the workflow. Now you can use the uq keyword to do crazy things like: 1cm * 1in 1in^2 / 2mm^2 1cm + 2.5in - 3mm > ft

Yet another text reformatting fix -- the workflow now handles fractional extra info. For instance, if you query "1 cm in ft" you get back "0.032808399 feet (25/64 inch)".

This workflow lets you create and manage separate instances of Chrome. Each instance will have its own cache, settings, extensions, etc. This is handy for setting up different browser instances for work, testing stuff, whatever. There is only one command: "prism" (I like to keep things simple). By default, you'll see a list of available prisms. Type "+" to create a new Prism; you can supply a name (no spaces allowed) and description right in the Alfred command line, or dialogs will pop up for you to fill in. Selecting a prism can do three things:Just pressing enter will load the prism (or just bring it to the front if it's already running) Hold Cmd to edit the prism's JSON config file; this will let you add command line options for Chrome Hold Option to delete the prism Hold Ctrl to open the prism's app directory in Finder The source, and a more in-depth README, is available on GitHub. Download Update 2013/09/14: The README talks a bit more about the config file, and the config files for new prisms now have some instructional comments. Also, it's possible to set an initial URL for a prism by adding it to the options array in the config file (this may have worked before, but it definitely works now). Update 2013/08/28: The workflow now displays some basic help when no prisms are available (like right after you install the workflow). Update 2013/08/15: You can start a prism at a particular URL now. I also changed how prisms get named behind the scenes, so after you update all your prisms may show up with random looking names. You can use Shift to rename them. Update 2013/08/14: Fixed a bug that caused the workflow to break with newly created prisms. Update 2013/08/13: Added Alleyoop support

Couple of updates today to handle values with scientific notation and with spaces (Google uses spaces as thousands separators). Thanks to mganjoo for pointing the issue out (and for submitting a fix that I didn't see until I pushed my own).

Yeah, I've started using the keychain in some other workflows I've been playing around with on my system, although just directly from Python rather than with an app. It definitely makes life easier. That Authenticate app looks pretty neat, I'll have to try it out.

Thanks, I'm glad you like it!

Excellent, glad to hear it's working.

I'm still looking into this. Do you access the internet through a proxy or some kind of corporate firewall?

Yup, that does seem to be the case. What happens if you try to go to http://autocomplete.wunderground.com/aq?query=20001 in a web browser? You should get back the following text: { "RESULTS": [ { "name": "20001 - Washington, DC", "type": "city", "c": "US", "zmw": "20001.1.99999", "tz": "America/New_York", "tzs": "EDT", "l": "/q/zmw:20001.1.99999" } ] }

I posted another update to the workflow. This one includes a new "wset log" command that will open a window for you that displays the debug log. Download and install this new version, run "wset location", and then run "wset log". That should pop up a window that shows the debug log, and you can copy-and-paste from that. Just out of curiosity, what happens if you use an argument with the "weather" command, like "weather 20001" or "weather dc"? When you add an argument after "weather", it will take a few seconds to update.