tomhunt Posted January 15, 2013 Share Posted January 15, 2013 In the same way you can tab etc. from a file filter and select an action it would be great if we could action script filter results. A script filter returning urls could open them, copy to clipboard, insert as an <a> etc. I've also got an idea for a Alfred based text adventure which this kind of functionality would enable. As I see it the script filter developer would need to specify which actions would be available for each item in the returned object as they will not necessarily be files, urls etc, but could be of any type. Just a thought... Tom Link to comment Share on other sites More sharing options...
jdfwarrior Posted January 15, 2013 Share Posted January 15, 2013 This would be an awesome idea but I wouldn't count on that getting done anytime soon as this would eventually require you making your own actions for each script filter. The reason I say this is, yes, you can action things in Alfred now, but they are a known set of possible result types. With script filters having the ability to create any kind of result you want, there is no telling what kind of data would be coming from the script filter, back into the actions Link to comment Share on other sites More sharing options...
tomhunt Posted January 15, 2013 Author Share Posted January 15, 2013 Exactly my point. However it could be relatively doable... I envisage a system in which each chain in a workflow has it's own uid (it would seem after looking at workflow .plists that currently only each node has a uid). Ideally this uid would be user-definable in the same way as the Bundle Id. In the xml output from the Script Filter another property of each item could be 'actions' which would be an array of these uids. When actioned the args from the xml would be passed to the action workflow instead of down the chain of the 'parent' Script Filter workflow. I hope this makes sense. I'd love to hear Andrew's thoughts. Link to comment Share on other sites More sharing options...
alfredo Posted January 30, 2013 Share Posted January 30, 2013 I was going to make a similar suggesting, before finding this thread. How I see it implemented would be have a action type type attribute in the xml for the item. Then create a new action input that can register to this keyword. Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now