parekh

Pokédex
Look up Pokémon info, moves, abilities and items. (v 2.4)
 
Maybe many of you haven't seen my Pokédex Workflow yet, because I posted it as an improvement of withanx's Pokemondb Pokedex in that same topic. That's why I decided to start a new one.
 
 
Requirements:
 
- The complete experience requires the Super Effective! workflow. Please, check it out here.
 
 
Features:   - Works offline.   - Pokémon Info:  + Types and Forms Example: "dex bulbasaur" Pro tip: Press Enter on the Pokémon type to use Super Effective! workflow and check the effectiveness of your attacks.   + Moves learnt by Level up Example: "dex bulbasaur lvl" Filter by Move type: "dex bulbasaur lvl grass"   + Moves learnt by TM Example: "dex bulbasaur tm" Filter by Move type: "dex bulbasaur tm grass"   + Moves learnt by HM Example: "dex bulbasaur hm" Filter by Move type: "dex bulbasaur hm normal"   + Egg Moves Example: "dex bulbasaur egg" Filter by Move type: "dex bulbasaur egg grass"   + How to evolve Example: "dex bulbasaur evo"   + Location Example: "dex pidgey location" Filter for more info: "dex pidgey location route"   + Base Stats: Example: "dex bulbasaur stats"   + Mega Stats: Example:  "dex mewtwo stats mega" "dex mewtwo stats mega y"   + Forms Stats: Example: "dex deoxys stats attack" "dex aegislash stats blade"   + Abilities: Example: "dex bulbasaur ability"   + Name in Other Languages: Example: "dex bulbasaur langs"   + Shiny: Example: "dex bulbasaur shiny"   - Moves Info: + Type, Category, Description, Power, Accuracy, PP, Probability Example: "move psychic" or "move tm10" or "move hm02"   + Filter Moves learnt by Level Up, Machine, Breeding or Tutor. Example:    "move false swipe tm" lists all Pokémon which learns False Swipe by Machine.    "move false swipe lvl" lists all Pokémon which learns False Swipe by Level Up.    "move false swipe egg" lists all Pokémon which learns False Swipe by Breeding.    "move false swipe tutor" lists all Pokémon which learns False Swipe by Tutor.   - Items Info: + Description Example: "item plate"   - Abilities Info: + Description Example: "ability pressure"   + Abilities by Pokémon: Example: "ability pressure pkm" lists all Pokémon with Pressure. Filter by Pokémon: "ability pressure pkm mewtwo"   - Conditions to Evolve: Example:  "evo leaf stone" lists all Pokémon that evolves using the Leaf Stone. "evo trade" lists all Pokémon that evolves when traded with someone. Hold CTRL to see more Pokémon Info Hold Option to see more Item Info   - Location's Pokémon list: Example: "location route 2" lists all Pokémon you can find in Route 2, plus method and rarity.   - Serebii, Pokemondb and Bulbapedia easy access: Open Serebii, Pokemondb or Bulbapedia for more info about Pokémon, Moves, Items and Abilities. Hold Option key: Pokemondb Hold CTRL key: Serebii Hold Function key: Bulbapedia Protip: You can set your favourite website as default using "set dex" keyword.   - Use Large Type to read full information or description: If the Move description or Pokémon description isn't being fully displayed, hold CMD and press Enter to see in Large Type.   - Use /help to check keyword options for each feature: Example: “dex /help” “move /help”   You can look up Pokémon by name (English, Japanese, German, French or Korean) or by national number.     Screenshots:                               Download Link: https://db.tt/a6bhugxY     Contact: @MaximiliumM   Any feedback is welcome.

Generate relative dates based on a simple input format and your own date formatting parameters (there are some default placeholders you can delete).

Supports multiple locales/languages.



Downloading

Get the workflow from GitHub.

Keywords
date — Generate a formatted date using the [input format][] ↩ — Copy date to clipboard ⌘+↩ — Copy date to clipboard and paste into frontmost app datehelp — Open the help file dateformats — View saved date formats ⌘+↩ — Delete date format dateadd — Add a new date format ↩ — Save the date format datereset — Reset the saved date formats to the defaults Input format

(+/-)<NUM>(w|d|y) where w = week(s), d = day(s) and y = year(s)

You needn't specify a sign: + is understood as the default, so +1d and 1d mean the same thing.

Months are not supported, as it leads to ambiguity: what if today is the 31st, but the target month only has 30 days? Similarly, a year is naively defined as 365 days.

Examples
0 = now = today — today's date 1d — 1 day from now 7d = 1w — 1 week from now -21d = -3w — 3 weeks ago Supported formats

The Workflow includes a few defaults for the locales en_US, en_GB and de_DE.

You can specify your own custom date formats using the formatting options listed at the below links, and you can also specify a language with the format lang=de or lang=de_DE if you want to use dates formatted for a language different to your system's.

For a list of the formatting options, please see the GitHub page or the Packal page.

Examples
%d/%m/%Y — e.g. 21/01/2014 %A %B %d %Y — e.g. Wednesday March 12 2014 %A %d. %B %Y lang=de — e.g. Mittwoch 12. März 2014 Bug reports, feedback

Report any issues or feature requests either on GitHub or in this thread.

Licensing, thanks etc.

This Workflow is released under the MIT Licence.

It uses the docopt library.

This is almost certainly due to a daylight savings change in either your city or the city in question. Just run an update "keyword: timezone update" to refresh the workflow's list of city offsets and it should be correct again. (FYI, LA is showing up as PST for me.)
 
Cheers.

The workflow calculates the difference between the requested city and your local time (as per your computer's clock) and stores it as an offset from your computer time.
 
Are you doing a "live" lookup (ie. "tz place-not-saved"), or do you have Los Angeles stored in your quick list (ie. keyword "tz")? If the latter, then yes, the US has recently changed to DST so a refresh of saved offsets will have been required. If the former, then that result should be correct regardless.
 
I'm not sure why you had to update last week and again today. The only thing I can think of is that it might have been a long time (ie nearly 6 months) since you last used the workflow so DST had expired, and then it was re-implemented just this last weekend.
 
Perhaps in a future update, I'll be able to store the DST change dates with the saved cities and automatically account for it or, at the very least, remind the user to manually update. I'll see if I can find some time to have a look at that in the near future. Thanks for your input.

Is it possible to take and upload a screenshot if no file is selected?

Right now there is no plan to automate that but thank you for your suggestion. Noted.
 
 
Thank you. I'll fix it ASAP.

You should. The new versions are normally better.
 
Also, you could use
calls SKYPE_TARGET call -s SKYPE_TARGET to limit the function to just Skype. Or, even, you could customise the call script filter with something like "./bin/Uni\ Call -s {query}", then you can use "call SKYPE_TARGET" as before
 

try to remove the AppleScript entry in Manage API clients, and restart your Skype
 

 

Have you got the newest version of the workflow? http://guiguan.github.io/Uni-Call/

Fair enough, you might be able to remap cmd return using third party software.

Thanks for your notice, I got your idea this time,  fixed it and release the Short-URL v1.3, please have a check from the link below, re-install it.
https://github.com/hzlzh/Alfred-Workflows

I think that I've spotted the issue that was causing @parekh problems. I've updated the workflow, but it may have to be manually downloaded from this link, as I suspect that its self-update mechanism was affected by the bug.

Other workflows (like the Wikipedia, Amazon, and Google Suggest) use different APIs than Wolfram|Alpha. You see, Wikipedia, Amazon, and Google are very quick to respond when you send a request to their servers. The Wolfram|Alpha API is a bit sluggish, mainly because it does more processing of your request and sends real answers back (instead of suggested search queries).
 
All of this adds up to a notable lag between your keystrokes and the appropriate results. I wish I could do something about this, but I can't 
 
Hope this helps 

Just a quick note, it doesn't seem to be learning with previous choices, would that be possible?

The previously released menu search workflow has been universally panned due to the poor performance of the AppleScript that dumps menu contents. The caching of results worked very poorly as a stop-gap. So, I've re-written the menu extraction in Objective-C. It's much faster. The source is here: https://github.com/ctwise/alfred-workflows
 
You can download the workflow directly from http://tedwi.se/u/db
 
To recap, this workflow lets you trigger an application's menu's from Alfred. For example, if you're in iTerm and trigger Alfred, you can type 'm view' to get a list of all menu items with 'view' in the name or that belong to the 'view' menu. Selecting one of the entries triggers the corresponding menu entry in iTerm. In one sense it gives you a command-line to control your applications.
 
The workflow has the beginnings of shortcut key display as well but it's currently disabled due to numerous bugs.
 
Update: 
 
v1.3 - Provide error message when assistive devices isn't checked.
v1.2 - Skip the Safari History and Bookmarks menus. They take too long.
v1.1 - I fixed the bug with Alfred not remembering selections and added AlleyOop support. Download from the same link.
 
Requires OS/X 10.7+.
 
---
 
You need to turn on OS/X assistive device support to allow this workflow to operate. You can find the checkbox in Settings. The settings page looks very different in recent versions of OS/X but the wording for providing access for assistive devices is very similar no matter what OS/X version you're using. Here's an image of the settings from the latest version of Mountain Lion.
 

This is a fantastic workflow! Has the potential to replace a bunch of others e.g. currency conversion, weather etc.
 
Is it possible to wait a very short amount of time after the last keystroke before string is submitted to wolfram? It seems to submit as soon as I start typing, but without allowing me to finish typing (even when typing pretty fast). This means that I waste time waiting for the results to come back from (obviously) unfinished queries before it gets to submitting the finished query. Try a currency conversion like "10USD in GBP" to see what I mean.
 
Ideally it would only submit if there haven't been any keystrokes in, say, the last 0.25 seconds.

I know exactly what you mean! I wish the script would run faster, too. Wolfram|Alpha is a bit sluggish, and launching the script with only a few characters is wasteful.
Right now, the workflow waits until at least three characters have been entered (as suggested by David Ferguson). I would love it if I could throttle the script, but I can't. Andrew might add a feature like this later on; it has been suggested by a few people (http://www.alfredforum.com/topic/535-throttle-script-filters/).
Thanks for the feedback, and I'm glad you like it!

Ah yes... for now, to search with single quotes, use \'.
 
e.g. w en world\'s largest

Yes, it’s very simple with bash. There’s probably a way to do this using only applescript, but this also works.
On the script, change the line
property theURL : "" to be
property theURL : (do shell script "pbpaste") then simply delete these lines
tell application "Safari" set theURL to URL of current tab of window 1 end tell And it should work like you want.

If you just downloaded the latest version, I had put in en search on by default. To change that, you need to do the following:
Open up Alfred Preferences Locate the Wikipedia ML search workflow and select it Open up the Script Filter box (the one with the Wikipedia logo) by clicking it There will be a text area at the bottom where you need to check the following: The last line should be something like: "python w.py en {query}" - which means that the search will be against the English site. To make it use the Chinese version, you need to change that like to "python w.py {query}" (without en). Now, if you type in Alfred "w zh  中華民國" it should be against the Chinese site. Please let me know if this helps.
 
EDIT in fact, upon re-reading my original post for the workflow, I realized the cause of the confusion. So I have updated the workflow at the download link to work by default in multilanguage search mode. So you can re-download the workflow and use as is... and no need to mess about with the internals

I like this a lot! Well done.
 
Suggestion: What about having the password length default to 15 unless a number is entered in?

Actually, there is no "recommended method" for freeing RAM as it is a bad idea to begin with. OS X handles the RAM management quite well, there is no need to free RAM as it will only slow down the system.

Quite a simple workflow to search articles on wikipedia (English version). Inspired by a similar workflow here, but it appears the download link is broken...
 

 
Based on feedback from folks, I have an updated version of this workflow. It allows you to
Search against regional Wikipedia sites. E.g. to search against German wikipedia, type "w de what to search for" i.e. "w <language code> <search term>" Language codes are from Wikipedia. You can also configure it to search against just one default Wikipedia by modifying the script filter as mentioned in the workflow. Against each result, a snippet of the text from the wiki page is displayed Remember, you can press the Shift key against a search result to quickly view the associated web page from within Alfred.
 
Try the new version and let me know your comments.
 
 
Q: How can I set one language as the default?
 
Open the workflow's Script Filter in Alfred, and follow the steps mentioned in there.

Thanks for your detailed response. Is there any way for me to modify this workflow such that it checks online for every place every time? I don't mind that it would take several seconds longer.
 
Also, thanks for creating this great workflow. The best solution to this problem would be if countries all over the world decided to abandon the silly concept of daylight savings!

Yeah, I mentioned that in my initial post. That's the price of instant access. The reason why the workflow runs so fast is that all the time offsets are stored on your computer. If it was to check online for every place every time, then it would take several seconds at least to generate the main list.
 
Realistically, daylight saving changes are fairly predictable. AFAIK they all happen overnight between Sat-Sun, and it's around this time of year. So really, all you'd need to do is run "timezone update" once every Sunday for March & April, and again in Sept/Oct. And remember, you can always get the exact current time in any place by entering "tz name of place".
 
One way I could improve this is to store the date of the next daylight savings change for each city and then check that when showing the main list and updating if that date is passed. However, I don't know of a decent online source that can provide this information in an easy-to-parse format (ie. an API). If you know of such a thing, then I'd be happy to implement it.

When you say "stopped working", you mean it gives the wrong times now?
 
You should be able to run "timezone update" and it will acquire new offsets for all your stored places. Let me know how that goes.