Jump to content

malkomalko

Member
  • Posts

    13
  • Joined

  • Last visited

Everything posted by malkomalko

  1. I'm starting to get into writing my own custom workflows, and one thing I can't find after reading the forums, is if it's possible to do some type of heavy lifting for a script only once. An example of this would be at the start of a workflow, pulling in some data, and then using what the user types in to filter that data out to update the display. Right now I have it setup and it's running all parts of the script with every key change, but I think it'd be faster to do the bulk up front and then just have the query update the data in memory. Is this possible?
  2. still having problems with being stuck at the updating cache... I downloaded newest version and nada
  3. Yup that makes sense. I'm actually prefixing all of my workflows with , (comma) so that I immediately filter down the workflows from everything else. This also feels natural to me coming from vim (leader key).
  4. I also +1 this idea even if it can't make it into 2.0, hopefully an update shortly after
  5. awesome... another idea: disable workflows. It'd be nice to keep them in the list but not have them active.
  6. This fixed the problem for me too. I like the idea of being able to turn off knowledge, I think that's very important
  7. https://gist.github.com/4555836 I wanted something in ruby that would allow me to create custom feedback items easily. Based off a comment from another thread, I also wanted the ability to search/filter that list as I was typing input. This uses amatch for computing the score of the match to decide what items to filter, and nokogiri for building up xml. There is an example in the gist. Let me know what you think. Best
  8. Thanks David on the suggestion for filtering in script. I just created something that I find useful and will be posting it up in another thread. Not sure if this is a bug, but I find that other menu items are creeping in to my custom feedback. For instance I see a list of my custom feedback items along side "Flash Player.prefPane".
  9. This is awesome. Thank you! One small bug: It appears the ordering of the forecast command is out of order, looks like a small problem on array positioning. I get back Sunday, Thurs, Fri, Sat
  10. First off, Alfred workflows are blowing my mind... so thanks . After creating a few test workflows and reading through a handful from this topic I have some things I've been thinking about. 1) Would it be possible, and what do you think, about having the ability to pass the output of one workflow into the input of another workflow. In this way, you would be able to create little modules of reusable functionality to build up more complex chains of workflows. 2) Filtering the list of Feedback items? If I manually want to build up a list of feedback items to be used as the input to some other step in a chain, I think it'd be nice right now to filter out the list. It appears that typing into Alfred doesn't do that yet. Am I missing something? 3) Script Filter -> Run Script -> Run Script isn't possible. It seems like you can only have one level of each type [Trigger/Input/Action/Output]. Thoughts on allowing for a more robust chain if you wanted things to pass sequentially through multiple script steps... say after you've chosen a feedback item in one step that lead to the next step.. so on and so on. This could probably be alleviated by #1. As a side question about Alfred, would fuzzy finding of results every be considered? The file action is awesome, but a little limiting in that it must match the start of a file/folder exactly. Cheers!
×
×
  • Create New...