Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


jonathanwiesel last won the day on May 3 2016

jonathanwiesel had the most liked content!

Contact Methods

  • Twitter

Profile Information

  • Location

Recent Profile Visitors

831 profile views

jonathanwiesel's Achievements


Member (4/5)



  1. I know it's been a while since the last time I asked this, maybe something changed. Like you mention that an install would be as simple as unzip the .alfredworkflow and place it in the alfredpreference directory, is there a similar method for updating existing workflows? I recall a while back that the problem when updating was the stripping a migration of hotkeys and keywords. BTW, this is looking to continue my work on https://github.com/jonathanwiesel/awm Regards, Jonathan
  2. It would be awesome if this workflow would be uploaded to http://packal.org
  3. Hi Jeff, The intention of the project goes far beyond just updating workflows, it focuses on the whole process of managing workflows from beginning (searching) to end (updating or removal), based on a centralized repository of workflows (packal).
  4. Hello there, I've been building a CLI application to manage workflows the way package managers like npm and Homebrew does, I called it "awm" (acronym for Alfred Workflow Manager). Using http://packal.org (by Shawn Patrick Rice) as workflow's central repository, the intention of this project is to easily install and update workflows for shell lovers (like me). The project still needs user intervention for installing and updating workflows, unfortunately I'm unable to keep working on it for the moment, so any node.js developer that would like to contribute on the remaining features is more than welcome. For more information feel free to check it out: https://github.com/jonathanwiesel/awm https://www.npmjs.org/package/awm
  5. Random Opener+ Open a random file in a given directory. To setup your directory just type *"randomsetup full_path_to_your_directory"*, or even better, type only *"randomsetup"* and your frontmost Finder window's open directory will be selected** To run just type *"random open"* in Alfred bar. A random file within the given directory will be open and will not be randomly selected unless every other file has been opened. Reset and count options also available. More on the repository.
  6. Well this is my implementation of adding reminders to the default list of the Reminders.app It supports also supports due dating. Full details and instructions in the repo page.
  7. I encountered a couple of errors on the last version: On the icon assignment there's an extra else: ... elif [ $SWVER == 10.8 ]; then OSICON=MountainLion.png else # <=== this one elif [ $SWVER == 10.9 ]; then OSICON=Mavericks.png else OSICON=Yosemite.png fi This breaks the workflow. On the other hand, I'm getting the following error, the workflow seems to work despite this: [ERROR: alfred.workflow.input.scriptfilter] Code 0: cat: SPDisplaysDataType: No such file or directory cat: SPDisplaysDataType: No such file or directory /bin/bash: line 119: [: ==: unary operator expected /bin/bash: line 123: [: ==: unary operator expected /bin/bash: line 127: [: ==: unary operator expected Hope it helps. Keep up the nice work.
  8. Well if you put it like that, it sounds really good and achievable actually. +1 PS: Still want cli management =P
  9. Thanks deanishe, Yes, this would probably be good for non-devs. Still, the concept of a consolidated workflow ecosystem ("npmish") would help a lot the community because ALL workflows must be published in the registry. Packal on the other hand, has it's own implementation, not bad at all but it would be nice if this was the default for Alfred, even supporting a cli interface; however for this to become a reality it would need a lot of commitment from the Alfred team to build and maintain a solution like this.
  10. Would be great if all your preferences (or most of them) could be exported/imported. Would help when provisioning computers you use be it either a new one, your work computer or whatever. Right now the process could be done my manually backup all you .plist files inside your Alfred.alfredpreferences directory, yet this is pretty manual stuff that could introduce misbehavior based on user's actions in the process.
  11. I think it would be really helpful for the community to consolidate all workflows as packages and be able to publish, install and update them the way npm or Atom editor does. This way packages would be easy to search and find. Also will provide a great way to provision new computers with all your preferred workflows by just executing a script that installs all your useful workflows. It will even be helpful for version management, sometimes a new version is out that it just doesn't work for a particular user, implementing this will allow users to have the exact version the know it worked for them without lurking the internet for the workflow's author support.
  12. Agree with that, it would be extremely useful for finding what you want, please consider it.
  13. Great indeed, now I don't need to head up to the forum to check for new post every now and then. Thank you =D
  14. The workflow broke for me with the latest update. I get this in the log files: Traceback (most recent call last): File "feedback.py", line 154, in <module> do_feedback() File "feedback.py", line 16, in do_feedback if (cache.get("cache_time", None) + day_secs > time.time()) and not force: TypeError: unsupported operand type(s) for +: 'NoneType' and 'int'
  • Create New...