Jump to content

xilopaint

Member
  • Content Count

    538
  • Joined

  • Last visited

  • Days Won

    18

Everything posted by xilopaint

  1. Someone released a workflow for it: https://github.com/rx2130/alfred-safari-history-search
  2. The documentation search is a very handy functionality for workflow developers in general. I simplified the workflow to this single feature for my personal use.
  3. Deanishe, sorry for hijacking the thread for a simple question. But what versioning criteria do you use to release a new major version? I have read about SemVer that a new major version should come out when "any backwards incompatible changes are introduced to the public API". What can this mean in terms of an Alfred Workflow? Would it be the case of a new version for Alfred 3 that becomes incompatible with Alfred 2? Can I release a new major version just because of significant new features?
  4. Update (v2.9) Added progress bar for a more friendly tracking of the Optimize action. Thanks @jeffsui for the sample workflow and @deanishe for his contribution in that thread: _
  5. Oh, I didn't know the workflow worked with Things 2. In this case I might consider to set the icons of Anytime and Upcoming lists for Next and Scheduled. What do you think about this idea? Besides that, is there any workflow feature not working with Things 2?
  6. What do you mean here? I didn't get it, probably because of my bad English.
  7. Update (v1.3) This update changes how deadlines are displayed in subtitles for consistency with Things; Simplified connections in Alfred editor for better maintenance.
  8. Right-click on the workflow in Alfred Preferences and choose Open in Finder so you can edit its files.
  9. The most disruptive workflow in my opinion is an utility: OneUpdater by @vitor. Download it, update your workflows with the new features of v3 and set OneUpdater in all of them to ensure the Alfred community is up to date. Btw, could you update your Pirate Bay workflow using the variable for the cache folder? You hard coded the path of v2.
  10. Does the API enable us to mark events as "going" or "interested"? If so you could build the workflow to list all events that we are invited and we could conveniently use Alfred modifier keys to confirm, decline or show our interest on them. Otherwise the default use case would be better (I'm considering that replying to an event includes mark them as "going" or "interested", is this right?).
  11. No problem, you were not rude at all. Sometimes I just don't manage to make the question right because I don't understand entirely what my problem is. At the end it was a bit more complicated than a simple list, so I created a workflow that generates a dict by user input and the data is stored in a single file using Workflow.store_data(). It was helpful to improve my knowledge on dict.
  12. It's not an issue. I was just trying to figure out if there was a cleaner way of appending data to a datastore than the one I was thinking about. Alfred-Workflow is such an awesome library that in many occasions I try to implement something in a way until I realise that there is an even simpler method of achieving my goal. Sorry for bugging you with dumb questions. My English is too bad and my coding skills are even worse.
  13. Is there any way/method to append data to a datastore without having to retrieve the data with Workflow.stored_data() before?
  14. Hey @deanishe. I am building a workflow for my personal use in which I will need to store strings (dozens of phone numbers and a few places) for later use. Considering the simplicity of the data it would be better achieved with Workflow.settings or I should use Workflow.store_data()? As for Workflow.store_data(), is it possible to add new data in the same cpickle file? I have read in the docs that "datastore does NOT support mutliple threads", so it means the answer is no? If it's not possible maybe I should use Settings API in order to avoid having a bunch of files in the data folder, right?
  15. Well, so I presume it's stable. I will update my workflow with it. Thanks again, @vitor.
  16. @nikivi, do you know why it didn't work in your fist attempt?
  17. You shouldn't have edited your post. I will repost it here for the sake of discussion: I downloaded your workflow and didn't manage to update in the first attempts as well (don't have a clue why). After some attempts it started to work. The same thing occurred when I tried to test with my workflow, but I didn't tell anything here because I thought I was missing something. Now I'm afraid there's some unpredictable behaviour with @vitor's implementation of the new feature. I hope I am not misleading here. It's a very welcome feature.
  18. It was set to 0 for the test so the download action is triggered in the first run.
×
×
  • Create New...