Jump to content

loris

Member
  • Posts

    22
  • Joined

  • Last visited

Posts posted by loris

  1. The only constraint to use github, it's that developpers and users of APM must install git, it's a requirement to maintain workflow and theme up to date

     

    Forcing APM users to install git sounds like a bad idea, why not just fetching out the ZIP bundle (then unzip and replace the existing dir content) from the workflow repository on Github ? (Just append /archive/master.zip to the repository url ie, https://github.com/twitter/bootstrap/archive/master.zip)

  2. What about using a Github public repository like other package managers do (bower, npm, etc)?

    Simple, free and safe. Developers will have to push their workflows on their own Github repositories (a lot of workflows are already on Github anyway) and do a pull request to be added in the (un-)official repository after getting approved by a list of maintainers (let's say Andrew, David, ...).

    The workflow installer tools will be able to query the list of packages directly on Github without worrying about bandwidth or uptime

  3. Yeah, I know about keychain and the oob pin code concerning Twitter. I know this is not perfect for the user but it works!

    What i am more concerned about is the growing number of APIs (Facebook, Google, Pocket to name just a few) that just won't let you use authentication with PIN code or classic login/password.

  4. In order to build workflows that use third-party APIs, we sometimes need to authenticate the users.

    At the moment, we can ask the user for its credential and store them in the workflow settings. That is not cool.

    Futhermore, some API service are now OAuth only and won't let developers log users using their private credentials.

     

    My request is to give workflow developers a way to handle OAuth, especially the token response.

    The easiest way I see to implement that would be to extend alfred URI scheme to workflows.

    For instance, I have a workflow with the following bundle id: "com.foobar.bundle", with a single "foobar.php" php file inside the workflow folder. I could give to the third-party API the following URI as the OAuth return url: alfred://com.foobar.bundle/foobar.php

    The foobar.php script would then be able to get the token parameters and finalize the authentication.

  5. I use Alfred for a freaking lots of actions and that's why I love it so much, but my primary use (and I'm pretty sure that's the case of most Alfred users) is to use it as an Application Launcher.

    However lots of applications nowadays are web apps: Gmail, Facebook, Google Reader, Deezer, Remember the milk,...

    The issue I have when using Alfred to launch web app is that I can't switch to one of them if it's already opened, Alfred would launch a new duplicate tab.

    For instance, when using "Open Gmail" action in Alfred, I would love to have it check first if my default browser already has Gmail opened in any tabs and then would just switch to this tab instead.

    I know this can be kind of done using Applescript but it would be awesome to have this feature built-in as an option in the "Open url" feature

  6. Very nice work!

     

    I don't know if this is related to my current Alfred settings or something you can add to your workflow, but being able to autocomplete the query would be awesome.

    For instance, I start typing "gh github", I then select "github/d3", hit TAB, Alfred search input gets autocompleted to "gh github/d3" and then I can add " issues" and hit enter to get to the issues page of the d3 repo.

×
×
  • Create New...