Jump to content

forgetfulfellow

Member
  • Posts

    98
  • Joined

  • Last visited

  • Days Won

    4

Reputation Activity

  1. Like
    forgetfulfellow got a reaction from Don Dahl in Text/Message on iMessage directly from Alfred   
    Thanks for the picture; since this is my first big workflow, I'm taking some time out of each day to debug it. I'm not exactly sure why it's sending to the last recipient, and I'll update you when I find a fix.
     
    I also updated my workflow to get some small bugs out of the way (which are in the change log above). Thanks for "testing" this app out; I don't think I would have been able to really understand an alfred workflow (and applescript) without you guys
  2. Like
    forgetfulfellow got a reaction from Don Dahl in Text/Message on iMessage directly from Alfred   
    Yeah, definitely! I'm definitely trying to get there, but the problem is that iMessage only recognizes an iMessage contact after it has sent the text to the number. I'm trying to study online to see if I can find a solution, but I haven't found anything yet
  3. Like
    forgetfulfellow got a reaction from S036 in Text/Message on iMessage directly from Alfred   
    So to outline my procedure: I basically just feed a name into iMessage and "trust" iMessage to pick the correct number. For me, 4 out of 5 times, it chooses correctly. (I know that isn't a great statistic, but as of this moment, I'm not sure how else to improve it). Currently, there isn't a way to extract the correct iMessage number out of a contact. I'm trying to see how to force iMessage to choose correctly, and I'll get back to you when I figure something out.
  4. Like
    forgetfulfellow got a reaction from Don Dahl in Text/Message on iMessage directly from Alfred   
    So to outline my procedure: I basically just feed a name into iMessage and "trust" iMessage to pick the correct number. For me, 4 out of 5 times, it chooses correctly. (I know that isn't a great statistic, but as of this moment, I'm not sure how else to improve it). Currently, there isn't a way to extract the correct iMessage number out of a contact. I'm trying to see how to force iMessage to choose correctly, and I'll get back to you when I figure something out.
  5. Like
    forgetfulfellow got a reaction from willregla in Text/Message on iMessage directly from Alfred   
    iMessage Workflow V3
     
    My workflow has been easily surpassed by others, please use theirs  ---------> http://www.alfredfor...red/?hl=unicall
     
    However, I'm updating this workflow to Alfred 3 for posterity's sake. Sorry for taking so long guys...
     
    Archive
     
    Change log:
     
    2/12/2017 - Because of a specific error, I've updated this app. Alongside the minor bug, thanks to Amos Manneschmidt's workflow "Call or SMS contact", I learned how to use OSX's built in Contact app to feed out contacts. Furthermore, I updated this app to be compatible with Alfred 3.  
     
    4/30/13 - Non-Latin languages are now supported! I have verified Korean, Chinese, and Japanese. If it works for your language, please tell me!
     
    11/27/13 - My extension prioritizes numbers that have been used before. This should allow Alfred to choose the correct number associated with a contact MUCH more accurately. Works only with phone numbers, not email addresses;
    A notification is now displayed when contacts are not updated successfully (mostly a response to Exceptions thrown when trying to update) 
     
    11/21/13 - Emoticons should now work; Alfred now opens up iMessage if its closed
     
    ------------------------------------------------------------------------------------------------------------------------------------------------
     
     
     
    If using the OLD way:
    Setup:  Run command 'IMU' before you start using the workflow
     
     
    Find Contacts and Send Messages:
    Keyword: "im"
     

     
    1b. Send a message to the aforementioned contact
     

     
      2. Reply to most recent iMessage or Group Message (Thanks to David Ferguson's Workflow)
          Keyword: ".."
     

     
    Download Link: https://github.com/NolanChan/iMessageWorkflow/raw/master/iMessage.alfredworkflow
     
    Please post up bugs in the comments below! 
  6. Like
    forgetfulfellow reacted to ctwise in Menu Search   
    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.
     

×
×
  • Create New...