Jump to content

xilopaint

Member
  • Posts

    896
  • Joined

  • Last visited

  • Days Won

    24

Posts posted by xilopaint

  1. Would you consider to integrate your workflow with transmission-cli? It can be installed with `brew install transmission` and work headless. That would allow us to start downloading the file from Alfred without the need of any GUI BitTorrent client which is the perfect scenario.

     

    A possible implementation would include a check for the existence of the CLI in the user machine, otherwise the current flow is used. An environment variable on the workflow configuration sheet would make the job as well (the user would set the value to 1 to use the flow with the integration).

  2. What is the average Alfred user profile? Is he/she aware of Homebrew? If so I'm in favor of promoting Homebrew Python/Ruby rather than bundling runtime. There's no difference in UX when you have Python installed via Homebrew and I don't think the comparison with node is accurate. With node you have the workflow installed in some shady path.

     

    I'm more curious to know what will be the future of Alfred-Workflow. Will it be converted to Python 3 since there's no longer advantages to stick with Python 2?

  3. 3 hours ago, vitor said:

    It’s not like there aren’t ways to bundle those languages as single executables. Ruby has a few (that I never tried) such as Ruby Packer. I’d be surprised it there isn’t something similar for Python. If there isn’t, this is an incentive to get on it.

     

    I'm completely unaware of this discussion but wonder how big the workflow size could get by doing this.

  4. 4 hours ago, Sridhar Katakam said:

    Can you tell me how to use this workflow to use a macOS service in Alfred's file actions panel?

     

    If by macOS services you mean those you can see in the right-click menu the answer is "you can't". This workflow is meant to search the commands of the menu bar, not the right-click menu.

     

    Also that workflow was built for Alfred 2 and is currently unmaintained. This other one, written in Swift, is newer with a similar implementation and works with Alfred 3 and 4.

  5. 18 hours ago, bazerman said:

    Anyone using this successfully with Alfred 4?

     

    It works for me, but with this important caveat:

     

    Quote

    Overusing this workflow might lead to your IP being blocked by Google Search servers. Searches through Chrome or another browser might still work but this workflow will stop working. I recommend keeping a 10-15 seconds gap after each usage of this workflow. In most cases, much lower gaps or even continuous use of the workflow will still work but still this is something to be kept in mind. If you see a 'rate limit' or a 503 error, it's best to stop using the workflow and try back after some time (~1 minute).

     

    The rate limit makes the workflow unfeasible for my routine.

  6. 6 hours ago, Carlos-Sz said:

     

    As soon as possible, I'll try the system attribute alternative.

     

    Thank you.

     

    Carlos, have you ever considered to push the source code of your workflows to GitHub?


    There's a lot of advantages on it:


    1) better discoverability;
    2) ease to document;
    2) contributions from the community to expand the workflow, fix bugs and report issues;
    3) versioned releases;
    4) using OneUpdater to allow auto-updates.


    It's very simple, straightforward and even fun. Maybe you are familiar with all of this and just don't want to do it for whatever reason, but if it's not the case you can check out my Things workflow as a reference. It's written in AppleScript as well.

  7. On 5/30/2019 at 4:38 AM, Tatarin said:

     

    [11:35:23.526] ERROR: Evernote[Script Filter] Code 1: 0:48: execution error: mkdir: /Users/tatarin/Library/Application Support/Alfred 3/Workflow Data: No such file or directory (1)

     

    How fix these?

     

    The problem is the workflow data folder path is hard coded for Alfred 3. You can fix this by changing the line 7 of the workflow.scpt file to this:

    set my _data to (system attribute "alfred_workflow_data")

     

    I encourage @Carlos-Sz to use script environment variables in his workflows.

×
×
  • Create New...