Jump to content

vdesabou

Member
  • Posts

    466
  • Joined

  • Last visited

  • Days Won

    22

Posts posted by vdesabou

  1. Hi Vitor, 

     

    Nice workflow, thanks!

     

    I’ve been using this for a while without issues. While you do not need to worry about an API key, that means results may be a tad slower (particularly since Alfred does that whole thing where it fires the script filter for every keystroke, and you’re sometimes forced to see results for stuff that were relevant only for the first keys you pressed, like an animal).

     

    One possible way is to use the logic implemented in this workflow (I'm not the author)  http://www.alfredforum.com/topic/4636-libgen-search-and-download-pdfs-and-ebooks-from-the-library-genesis-project/#entry28261
     
    It requires the user to type a period (.) after the query in order to initiate the search. 
    Just a thought
  2.  

    This is the downside of multiple HTML requests: When you start typing, the workflow immediately starts searching for the first letter you entered, and Alfred waits for it to return the results. Only after the results for “T” have appeared, Alfred accepts the results for “transformers” (which you finished typing by that time) from the second instance of the workflow's command line app.

     

    Unfortunately, this will always happen.

     

    One possible way is to use the logic implemented in this workflow http://www.alfredforum.com/topic/4636-libgen-search-and-download-pdfs-and-ebooks-from-the-library-genesis-project/#entry28261

     

    It requires the user to type a period (.) after the query in order to initiate the search.

     

    I think it could make sense to use same logic in all (awesome) workflows you released (this one + all the MAS/iBook/iTunes searches)

     

    Just a thought

     

    Thanks!

  3. You are in fact setting a UID of '' in your XML... For Alfred to generate a random UID, you need to miss the UID field altogether...

    <item valid="no" autocomplete="Playlist▹spotify:user:trickyofficial:playlist:1u5vQfIxo8X1zoOInXxSGn▹">

    This should fix the sorting issue you're seeing. The code / behaviour around this hasn't changed for quite some time, so it may have just been lucky that having all UIDs set to the same empty string would have sorted them arbitrarily correctly for you.

     

    Moving to [closed], but do let me know if this fixes your issue or not.

     

    Cheers,

    Andrew

     

    Thanks Andrew, I figured out I was using an old version of David's Workflows.php that's why UID was set to ''

    My bad

     

    Thanks for your support

  4. Alfred Nike Plus Running


    Description

    This is an Alfred Workflow to browse your Nike Plus statistics and running activities.


    Screen%20Recording%202014-10-16%20at%200

    Features

    • Hotkey to trigger the workflow
    • Update of activities directly from the workflow
    • Browse by Year/Month
    • Auto-Updater: it checks once per day and download automatically the new version

    Settings

    • Check for workflow update
    • Use Miles instead of KM
    • Install/Refresh of the library

    Auto-Update

    The workflow checks for update once per day, if an update is available, it will download the new version in your Downloads folder.

    Note that you can also force a check for update in Settings section


    Credits

    Download the workflow on Packal

    alfred-workflow-icon.png

  5. Thanks for these explanations!

     

    I've removed all calls to exec() in the performance path of my workflow (Spotify Mini Player http://www.alfredforum.com/topic/1892-spotify-mini-player-version-15/) which were in the Workflows.php from David.

    I've only one remaining but I think I have no choice because I need to call an applescript to get current playing song from Spotify, and I can't see a way to do that without call to exec().

     

    Anyway even with this, it takes now only between 100 and 250 ms for my workflow to return all results and I'm very happy with that! :)

  6. Version 4.41 is live with improvements from 4.4:

     

    4.41:

    • Compliant with latest Spotifious version

    4.4:

    • Improved performances
    • New command to unstar a track

    2I5Jg9uLgu.png

    • Added new command (with external trigger) spot_mini_update_library to update library
    • Automatically update Alfred Playlist after adding track, album or playlist
    • Automatically update starred playlist after star/unstar track
    • New theme
    • Shortcuts to Settings/Alfred Playlist/Playlists (need to configure hotkeys)

    9msSHFbr8h.png

     

     

     

    To be downloaded on Packal http://www.packal.org/workflow/spotify-mini-player

  7. ok, figured the second one out...

    i had to change the keyword in the second "bubble" (the Script filter) in the Spotifious Workflow form "spotifous" to "spot"

     

    so just problem No 1 is still open

     

    That's strange because I just re-downloaded Spotifious from Packal and script filter is set to 'spot'. Did you rename it by yourself?

     

    For No 1, hold on a few minutes, I'm going to release version 4.4 which fixes the issue

  8. I finally had some time to investigate this and I believe this is due to use of exec(). I've read here http://stackoverflow.com/questions/14277910/php-exec-performance: "When you call exec php does not create a thread, It creats a new child process. Creating a new process is big overhead."

     

    So I've done a pull request to David's workflow (https://github.com/jdfwarrior/Workflows/pull/9) to avoid as much as possible the use of exec() in Workflows constructor.

    The best improvement is when you set bundleid when creating Workflows:

    $w = new Workflows('com.repro.slow.problem');
    
    instead of
    
    $w = new Workflows();
    

    I've created a workflow to show the improvements, get it here https://cloudup.com/cBiUwDy104X

    See:

    b4b831e0-094b-11e4-8cfe-6da5e5cd3370.png
     

×
×
  • Create New...