Jump to content

Rubberbanding: Toggle Mac OS X's rubber band (i.e., elastic) scrolling on and off

Recommended Posts

Hi there,


Long time listener, first time caller here.  I just built my first Alfred workflow and would love to hear your feedback.  The workflow simply toggles on or off Mac OS X's native rubber band scrolling (also called elastic scrolling), which was introduced back in Lion.


If you're interested, please check it out here:






I'm particularly interested in exporting workflows in a manner friendly to version control in Github.  I placed the exported .alfredworkflow file in my repo alongside a src directory which contains a number of the workflow's components — mainly the raw text of the Applescript that does the workflow's heavy lifting.


I'd be grateful for any advice with regards to best practices for exporting, versioning, and sharing workflows.




Edited by adampage
Link to comment

There aren’t really best practices, and everyone just does it how they find it most convenient. It is clear however that most workflow authors would embrace a really good, convenient, frictionless, and easy way to handle it, that would be widespread and clear to use (and if official, even better) that would also be known to users as the resource to use. Packal largely fills that role, currently, but still feels like a hacked on solution (it is completely third-party, after all) and that a better one could be arrived at if allowed to interact with Alfred directly in an official capacity (such as thing has been hinted at being worked on, at least conceptually, by Alfred’s authors).
You do, naturally, find some similarities in how others do it, and may find interesting solutions to incorporate in your own way of work.

As two examples, deanishe has his workflows on Github, one per repo, each with a src directory, and the rest of the root populated with the packaged workflow as well as other information such as README, TODO, and an animated gif of the workflow in action. The README explains in detail what the workflow does, and links to downloads on both the current repo and packal. He also provides the packaged workflow via Github’s Releases feature.

I have all my workflows under a single repo, one per directory (with the workflow’s name), each containing only the source. The README contains only a single-line description of each workflow, with links to both its thread in these forums (where it is explained in greater detail) and a download link to packal, which is the only place I keep packaged workflows.

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...