Jump to content

Mr Pennyworth

Member
  • Posts

    175
  • Joined

  • Last visited

  • Days Won

    10

Posts posted by Mr Pennyworth

  1. Thanks @chris! When you want a panel to be shown at side, and some HTML to be show inside it, yep, you can use the AlfredExtraPane.app. All you got to do is add an html filepath to quicklookurl of the JSON and then pipe it to the app (the readme has an example).


    For building something like this GIF workflow, it is true that AlfredExtraPane.app was an inspiration, but it can't just directly be used to build the GIF workflow, it isn't flexible enough. For this GIF workflow, I simply took the code of AlfredExtraPane.app and modified it to fit the GIF needs, thus programming in swift was involved and understanding how AlfredExtraPane.app works internally was a prerequisite.

  2. Alfred GIF Search

    Download: Gif.Search.alfredworkflow

    Up-to-date README (this post is outdated)


    This workflow lets you search GIFs on Tenor from Alfred.


    Here's an example of searching and inserting a GIF in a google doc:
    alfred-gif-search.gif


    Installation

    1. Download the latest release.
    2. In Alfred, run .setup-gif-search.


    Usage

    • In Alfred, enter gif keyword followed by search query.
    • Press .
    • Use arrow keys or mouse to browse the GIFs.
    • To copy the selected GIF to clipboard:
      • either ⌘↩
      • or ⌘-click
    • To drop the GIF into apps that support it:
      • drag from Alfred and drop into that app


    Note


    Firefox and Chrome don't support pasting GIFs from clipboard. That is, if you copy a GIF to clipboard and paste it, it shows up as a static image, not an animated GIF. This is not a bug in this workflow, but rather just the way these browsers have decided to handle GIFs.


    Both Chrome and Firefox support drag-n-drop. If you use either of these browsers, sorry, you gotta use the mouse!

  3. FAstest eMOji Search (FAMOS)

     

    Instant search for emojis in Alfred with related keywords in 25 languages and Google Emoji Kitchen integration

     

    This post is outdated, link to up-to-date README
    Download the latest versions: github release


    FAMOS speaks many languages!


    multilingual.png
    FAMOS uses emojibase, which is an excellent library, meticulously curated. So, all the languages that emojibase supports, FAMOS automatically does too.


    FAMOS is the fastest!


    10x to 20x faster compared to alfred-emoji and EmojiTaco!


    FAMOS launches in under 20 miliseconds (imperceptible), while both the other workflows take hundreds of milliseconds to launch (very much perceptible).


    The reason FAMOS exists is that I wanted my emoji picker to:
     - launch instantly
     - search with zero lag
     - let me pick skin-tones for each individual emoji


    Skin-tone prefs for each individual emoji


    I like my emojis to reflect my skin-tone correctly. And also hair color! That means, I might not always get both. So, I want hand-emojis to have my skin-tone, but face-emojis to have my hair-color even if that means wrong skin-tone. In addition, if you're a stickler like me, you will understand that I want one skin-tone for the palm and a different one for the back of the hand. Back of the hand is a shade darker than the palm, isn't it!

    1. Search results show if an emoji has multiple tones available:
      skin-tone-1.png
    2. Hold command:
      skin-tone-2.png

    3. After pressing command+enter:
      skin-tone-3.png

    4. From now on, the chosen tone becomes the default tone for this emoji:
      skin-tone-4.png


    Feature comparison


    Both alfred-emoji and EmojiTaco are excellent workflows, and they have tonnes of features that FAMOS lacks, and has no plans of implementing. You should definitely check them out!

     

     

    comparison-chart-image-for-forums.png

     


    Downloads

    Chinese, Traditional apple  joypixels
    Chinese apple  joypixels
    Danish apple  joypixels
    Dutch apple  joypixels
    English, Great Britain apple  joypixels
    English apple  joypixels
    Estonian apple  joypixels
    Finnish apple  joypixels
    French apple  joypixels
    German apple  joypixels
    Hungarian apple  joypixels
    Italian apple  joypixels
    Japanese apple  joypixels
    Korean apple  joypixels
    Lithuanian apple  joypixels
    Malay apple  joypixels
    Norwegian apple  joypixels
    Polish apple  joypixels
    Portuguese apple  joypixels
    Russian apple  joypixels
    Spanish, Mexico apple  joypixels
    Spanish apple  joypixels
    Swedish apple  joypixels
    Thai apple  joypixels
    Ukrainian apple  joypixels

     

  4. @scafaj wow this is really puzzling I looked through all the permissions for alfred on my machine.

    The only outcome is: disable "System Events" and I get the exact same error that you get.
    Enable it back, and the error goes away.

     

    Given that that's not working on your machine, and I've tried everything that I can think of, now I'm out of ideas 🙁

    Good to hear that the "press shift for preview" thing at least works...

  5. @scafaj can you confirm that you aren't using 'Alfred Classic' theme?

     

    If you are, then either change the theme or duplicate it and use the duplicated one.

    If you are not, can you reboot and check if the problem persists?

    If you reboot and it persists, I'm not sure what might be going wrong... while I try to figure that out, you can do the following meanwhile:

    1. Open the workflow folder.
    2. Open the file search.sh
    3. The last two lines will be:
      echo "{ \"items\": $items }" \
        | 'AlfredExtraPane.app/Contents/Resources/scripts/alfred-extra-pane'
    4. Change that to:
      echo "{ \"items\": $items }"

      (remove last line, and remove the "\" from second last line)

    This will disable live preview, but you'll get the search results.
    Pressing shift on a search result will give you a preview.

  6. @scafaj: thanks! I had missed the update to your original post.

    The logs are helpful!

     

    I have a guess what is going on.

    Can you run this in terminal?

    osascript -e 'tell application "System Events" to display dialog "Hello!"'

     

    It should create a simple dialog box like this:

    image.thumb.png.03b8e94c185d74856576608c4b13a8c4.png

    If it does not, I'm not sure how to fix the problem, I had faced similar problem and wasn't able to find a solution.

    The only solution I know is rebooting :P

     

    Also, what Alfred theme are you using?

  7. @scafaj hmm... not much info to investigate...

    I imported both the dictionaries that you mention and they worked properly.

    Few questions to help me understand the problem better:

    1. After importing the fist dictionary, did that work?
    2. How long did you wait between finishing the first import and starting the second import?
    3. Did you get a "waiting for index to be ready..." box after each import? (see screenshot)
      image.png.0a3699d4d55b7f5545d87513ca4df230.png
    4. Can you post a screenshot of the workflow editor?
    5. Can you run this in terminal and post the output here?

      ls -alh ~/Library/Application\ Support/Alfred/Workflow\ Data/mr.pennyworth.betterDicts/

    6. Can you paste the contents of ~/Library/Application\ Support/Alfred/Workflow\ Data/mr.pennyworth.betterDicts/db.log
      https://dpaste.com and post the link here?
    7. In case you just want to reset everything and start from a clean state
      1. Delete the workflow
      2. Run killall alfred-dict-server; killall BetterDict; rm -rf ~/Library/Application\ Support/Alfred/Workflow\ Data/mr.pennyworth.betterDicts/
      3. Reinstall the workflow
  8. 4 hours ago, majjoha said:

    What would it take for me to allow the workflow to search other dictionaries (in my case, Danish)?

    @majjoha: is the Danish dictionary available in Dictionary.app that comes with macOS?
    If yes, I'm working on the next version of this workflow, where you will be able to use any dictionary that's available in Dictionary.app. If not, I'm sorry, but there's no easy way for me to add support. However, if you are a programmer, you could look at the code and see if you can re-use any of it.

  9. @Pinuz, I don't have a multi-monitor setup, so a bit difficult to test it out.
    I have a suspicion what the bug might be, but can't verify for sure.

     

    Can you help me out?

    1. Open the workflow directory in finder:image.png.939d6bc9fbe977d64953889b1747f351.png
    2. Run in terminal: killall AlfredExtraPane
    3. Download the modified AlfredExtraPane.app, extract it, and replace the one already present with the downloaded one.
    4. Run .setup-better-english-dictionary
    5. See if the issue is solved by doing a dictionary search or whether it still misbehaves.
  10. 7 minutes ago, Pinuz said:

    Though, I think I've found a bug when there are multiple screens (if I use only one, everything goes perfectly).

    @Pinuz, does it happen only when you search for the first time or does it happen all the time?
    Also, could you describe your screen setup?

  11. 5 hours ago, mikeswimm said:

    Cannot find .md files by content

    Just wanted to make sure, when you are searching by content, for example, you are searching for the content "installation instructions", are you typing "installation instructions" in alfred or "in installation instructions"? In alfred, you need to start with the "in" keyword to be able to search by content.

     

    Just putting this out there because I had faced the same problem and I took some time to discover the "in" keyword.

  12. @RCL: does this file exist on your machine?

    /Users/rcl/OneDrive/Alfred.alfredpreferences/preferences/appearance/options/prefs.plist


    Also can you tell me what the output for following command is when you run it in terminal?

    ls -LR '/Users/rcl/OneDrive/Alfred.alfredpreferences/preferences/appearance'

  13. 8 minutes ago, Andrew said:

    Native richer content natively within Alfred is something which has always been on the plan for the future

    Yayy! Awesome to hear that!!

     

    9 minutes ago, Andrew said:

    Having said that, for fun, I wouldn't be adverse to make it a defaults write on Alfred's prefs just to see this working better

    🎉🥳 you're the best!
    Keeping my fingers crossed! 🤞🏼

  14. 2 minutes ago, deanishe said:

    I don't think the distributed notifications are likely, for the reasons you give.

    Yep. I tried to make that list exhaustive.
    What I'm curious to know is which among the above are @Andrew's reasons.
    (must admit I'm clinging onto the teeeny tiny hope that he replies "no reason not to... watch out for it in some future release". but short of that, it's just a good thing to know the "why" :) )

  15. @deanishe @Andrew I totally get the idea that an HTML preview-pane isn't widely useful, and probably doesn't even fit into Alfred's core design philosophy. However, I think some workflows' UX could benefit considerably if they had such an option available.

     

    This POC could suddenly become so much more polished and robust if there was a Distributed Notification for "result selected/highlighted" that external processes could subscribe to. The data for that notification would contain entire json for the highlighted result. Then, instead of manually tracking keypresses and mouse-movements like the tool does now, it could simply subscribe to such a notification. It would also remove the need to crudely guess how alfred's "knowledge" works.

     

    I know it's quite unlikely that such a thing will be implemented, as I can already see so many reasons not to. I just wanted to pick your brain about what your reasoning would be...

    1. Performance: posting distributed notifications slows stuff down.
    2. Feature/code bloat: not worth adding to Alfred's codebase something that'll only be used by some obscure tool.
    3. Non-trivial implementation: would need time/refactoring disproportionate to usefulness.
    4. Undesirable extension: don't want to expose weird APIs.
    5. Priority: proposal sounds good, but there are just way too many things with greater priority that it'll be a very long time to come to this.
    6. Undesirable functionality: want to discourage such "alfred companion tools".

    If I were the developer, my reason to not implement would've been some combination of the above. How about you?

  16. @Nrevi Thesaurus is a good idea!

    I updated the workflow. Now, in the main search, results from the thesaurus show up too (they are not very highly ranked though, and this ranking is something I don't really know how to control well).

     

    Also, added another keyword "thesaurus" which will exclusively search in the thesaurus.
    So, if the thesaurus result doesn't show up in the main search (because the ranking algorithm somehow finds not very useful), you can this keyword instead.

     

    (Download it from the link in the main post)

×
×
  • Create New...