rant
My Applescript Wishes
Apr 10, 2008 @ 04:21 PM - Filed in:
Other
I'll admit I'm not great at writing
scripts. With some time and patience I think I'm decent at getting
the job done assuming the job is even possible with
Applescript.
Let's take a stroll down Ranting Street...
1. I think using the language isn't exactly easy to use. But I think the language is easy to learn, but using it is a different matter. I have yet to come up with a good use for using just the language without actually automating an application. I suppose I could use it for a fancy calculator but I think there are other scripting languages and command line utilities and GUI apps already out there that would do a better job. Once you start automating an application, you have to learn how to automate that application. Then you move onto another application. The learning never stops. You can apply some things from what you learned with the 1st app, but the 2nd app could be drastically different and thus require more of your time and effort.
2. I think rant #1 would be addressed by addressing this rant. Where's Applescript's recordability in every Apple produced application? One of the features of Applescript is "recordability". Imagine being able to hit the Record button in the Script Editor and going through all the steps in the app you want to automate as you normally would. When your done you hit the Record button again to stop recording and your script is written for you. All of that without having to write a single line of code. You could record importing images from a directory, add some keywords after the import, apply some ratings, then export the project for whatever reason. Sounds pretty nice huh? So why isn't it available in Aperture? Because in order for an application to have recordability, the engineers developing the application have to implement recordability but unfortunately for us users they don't. I realize the Finder has some recordability but not much. I'm willing to bet there are more 3rd party applications with some recordability than all of Apple's software library.
Having this feature in Aperture would really make a workflow application a workflow application. It would save soooo much time and effort. Sure it wouldn't solve every problem out there. But it would surely save you tons of time, perhaps write the entire script for you, or at the very least give you a very good foundation to start with. I doubt this web site would even exist as well which is totally fine with me.
Also, why would Apple not implement it? Its their technology. Its an awesome time saver. And if you ask me, Automator is nice but its just a workaround for the lack of having good recordability. If recordability was in every application there would be no need for Automator.
3. Ever tried to write an application using Applescript Studio? The documentation isn't great as there are nothing specific to GUI controls and Applescript. The GUI control information is documented for the Cocoa programmer not the AS programmer. Well, I guess that's why they include so many examples. But that still doesn't answer many questions I have concerning what I can and can not do with a control and how I go about using a control, although the examples do help.
I'm sure I could come up with other gripes. But I think those are the real big ones for me. If you feel the same, I encourage you to contact Apple and let them know.
Let's take a stroll down Ranting Street...
1. I think using the language isn't exactly easy to use. But I think the language is easy to learn, but using it is a different matter. I have yet to come up with a good use for using just the language without actually automating an application. I suppose I could use it for a fancy calculator but I think there are other scripting languages and command line utilities and GUI apps already out there that would do a better job. Once you start automating an application, you have to learn how to automate that application. Then you move onto another application. The learning never stops. You can apply some things from what you learned with the 1st app, but the 2nd app could be drastically different and thus require more of your time and effort.
2. I think rant #1 would be addressed by addressing this rant. Where's Applescript's recordability in every Apple produced application? One of the features of Applescript is "recordability". Imagine being able to hit the Record button in the Script Editor and going through all the steps in the app you want to automate as you normally would. When your done you hit the Record button again to stop recording and your script is written for you. All of that without having to write a single line of code. You could record importing images from a directory, add some keywords after the import, apply some ratings, then export the project for whatever reason. Sounds pretty nice huh? So why isn't it available in Aperture? Because in order for an application to have recordability, the engineers developing the application have to implement recordability but unfortunately for us users they don't. I realize the Finder has some recordability but not much. I'm willing to bet there are more 3rd party applications with some recordability than all of Apple's software library.
Having this feature in Aperture would really make a workflow application a workflow application. It would save soooo much time and effort. Sure it wouldn't solve every problem out there. But it would surely save you tons of time, perhaps write the entire script for you, or at the very least give you a very good foundation to start with. I doubt this web site would even exist as well which is totally fine with me.
Also, why would Apple not implement it? Its their technology. Its an awesome time saver. And if you ask me, Automator is nice but its just a workaround for the lack of having good recordability. If recordability was in every application there would be no need for Automator.
3. Ever tried to write an application using Applescript Studio? The documentation isn't great as there are nothing specific to GUI controls and Applescript. The GUI control information is documented for the Cocoa programmer not the AS programmer. Well, I guess that's why they include so many examples. But that still doesn't answer many questions I have concerning what I can and can not do with a control and how I go about using a control, although the examples do help.
I'm sure I could come up with other gripes. But I think those are the real big ones for me. If you feel the same, I encourage you to contact Apple and let them know.