Mijathi

I really hoped the workflow process would be less a mess, but it seems it isn' t. No version management, no update feature. I agree with perldork, a central repo could already help out. I' m also a little puzzeled with this: A few weeks ago I opened a thread to ask if groovy support would be a possibility and it was not considered because there was a dependency with a groovy runtime... .

It has a negligible extra, but not in those figures I could not sleep overnight . http://keyzero.wordpress.com/2010/05/26/groovy-vs-ruby-vs-python-performance/ Just that support would be nice as there is a large groovy community. I understand the issues mentioned by David, but still I think this could be solved for example by not allowing to import workflows for which a environment is not present on the system. I' m not the alfred guru, so just asking.

Too bad because it would be very useful for a wide community. Back to the terminal .

Would it be possible to add support for groovy based scripts. #!/usr/bin/env groovy Example: #!/usr/bin/env groovy println("Hello world") for (a in this.args) { println("Argument: " + a) } For this of course a groovy environment is needed on the machine.