zettt / launchbar-scripts Goto Github PK

I'm having a hard time to decide what to do with legacy LaunchBar scripts, which still work, and coming up with a new convention for the newer LaunchBar Actions format, which has some neat advantages.

My main goal with the changes I have in mind:

• A user that is not so familiar with Git, and only a little versed with Terminal should be able to check out the repository and get most of the stuff up and running in a short(er) period of time.
• Advanced users should be able to check out the repo and commit changes (to send pull requests).
• Ideally transitioning to LaunchBar Actions would be easier for me.
• The folder structure should make sense and shouldn't be such a mess as it is at the moment. Right now, when a user checks out this repo and has no idea what he/she is doing, they end up with all scripts in _Archive (which are not functioning) activated by default.
• The entire folder hierarchy needs to be changed to accommodate for clearer and more precise usage. This repo started fully as a full LaunchBar-only repo, then Alfred appeared and I started tinkering with Keyboard Maestro. So a lot of scripts from that time were optimized to work in all three. With the introduction of LaunchBar Actions, and this repo being named "LaunchBar Scripts", it makes sense to think about either a name change "App Launcher Scripts", or a full focus back on LaunchBar.

My least favorite is, frankly, a full focus on LaunchBar. I know LaunchBar is great and we all love, but so do a lot of Alfred users love Alfred. I wouldn't say Keyboard Maestro is that bad either. (If you read my blog, you know that's quite an understatement.) So I'm left with a difficult problem:

This repo needs serious restructuring!

I thought something like different folders for the scripts would make sense. Something like this:

_Archive
LaunchBar Actions
LaunchBar Scripts
Alfred Extensions
Alfred Scripts
Keyboard Maestro Macros
Keyboard Maestro Scripts

A user could check out this repository to say ~/Coding/App Launcher Scripts/ and then symlink only the folders they need to ~/Library/Application Support/LaunchBar/Actions.
Only preferred scripts would be activated by default. Only some scripts would require manual deactivation in the LaunchBar index. I'm not certain, but thought Alfred had something similar.

The only problem then is where or rather how do I keep a script that runs in either launcher? Would a copy not make maintenance more difficult?

With all the changes coming to this repo (#4) a new name is required.

This action should use an empty list property that users are able to add folders to with LaunchBar, making them available inside LaunchBar, but also making them able to remove them.

Action that gives a list of all bookmarklets currently in one's browser, allows to execute them on the current page.

http://www.macosxautomation.com/applescript/features/appobject.html

Execution should Toggle iTunes Repeat (6025495).

Tapping into action should give options None, Repeat, Repeat All.

It is hard to know which script is for what app and how to use it. It would be better if the various scripts were sorted into subfolders.

Idea: Get App Infos like Bundle Identifier and other things

Inspiration: Bundle ID: http://cl.ly/2Z173M1Z2x3Q

Hi, I've managed to launch the color picker, but is there a way to get the hex code for the selected color? Thanks

On El Capitan the Toggle Bluetooth script doesn't work for me displaying notification "No blueutil binary found" even though blueutil is installed and which blueutil gives /usr/local/bin/blueutil. I restarted the computer just in case but the error stays there. Blueutil itself works, toggling BT off/on allright.

You probably know this already but just wanted to add that the getpocket scripts do not work anymore. Gives a sent to pocket response but really it's giving a 400 bad request error. I don't even think it is possible anymore to have an applescript send to pocket without using their api. I know some python scripts that do so but other than that no idea. Thanks for the great scripts though. Very useful.

LB Action that reads all menu items of the front app and displays them as list. The user can then search for a command and execute it.