Jump to content

KAT


godbout

Recommended Posts

* configuration done in the Configuration Sheet

* no updater

* binary signed and notarized

* no libraries

* instructions in English, with screenshots

* icon is 256*256


1. i'm the author

2. Alfred forum link: https://www.alfredforum.com/topic/12403-alfred-kat/#comment-65419

3. Github link: https://github.com/godbout/AlfredKat

4. testing is straightforward. install a torrent client, make it default, and use the Workflow

5. screenshots below:

image.thumb.png.d6c0a4391da8bc31eafae27d4fe100a9.png

image.thumb.png.12014d2f6e97db975f85a6e857bb7efd.png

image.thumb.png.fbcbe984157d13a39c42d4f3d7ee0997.png

thanks again.

 

 

 

Edited by godbout
updating images
Link to comment
Share on other sites

28 minutes ago, godbout said:

i could replace the screenshots by something other than movies or music.

 

@godbout Thanks for submitting the workflow, and I fully agree that torrents can be used for legitimate and legal content.

 

If you could please choose screenshots that reflect legal content, that'd be great.

Link to comment
Share on other sites

8 hours ago, xilopaint said:

 

You forgot to add configuration to the CLI.

 

good catch. you're probably the only one to use it 😂

Link to comment
Share on other sites

6 hours ago, godbout said:

* added the `cli` in Configuration Sheet.

 

Just a minor note: /usr/local/bin is the Homebrew path for Intel Macs which are mostly vintage nowadays. Apple silicon uses /opt/homebrew/bin so a more up-to-date placeholder would be /opt/homebrew/bin/transmission-remote -a {magnet}.

Edited by xilopaint
Link to comment
Share on other sites

Worth noting, as a note on the note, that Alfred includes both Homebrew paths in its PATH. This allows you to use the name of the tool without the full path and not have to worry about that distinction, meaning less things to worry about as a creator and less configuration for users to do.


Also worth mentioning (though I don’t think it applies here, it’s just as a curiosity) that /usr/local/bin is a standard location that’s used by non-Homebrew tools as well (e.g. a GUI app installing its own CLI, I think VS Code does exactly that). Homebrew used that path despite that because otherwise (at the time this was implemented) a ton of tools wouldn’t work correctly anywhere else. Thankfully that situation has improved, so the transition to /opt/homebrew has gone well and it leads to fewer (albeit rare) conflicts.

 

Edited by vitor
Fixed typo
Link to comment
Share on other sites

thank you both. this Workflow has been confirmed by pm that it is not suitable for the Alfred Gallery. so i guess it's time to switch it to completed. thanks.

Link to comment
Share on other sites

18 minutes ago, vitor said:

Worth noting, as a note on the note, that Alfred includes both Homebrew paths in its PATH. This allows you to use the name of the tool without the full path and not have to worry about that distinction, meaning less things to worry about as a creator and less configuration for users to do.

 

I tried without /opt/homebrew/bin/ and it didn’t work with this workflow.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...