On Wed, 3 Mar 2010 16:17:13 +0000, Ulai Beekam <ulaibee...@hotmail.com> said:
>get the point. Just so the user (but mainly the developer for testing purposes) >can somehow make the app do things that cannot be done in the UI. This might be a reason to build some scriptability (AppleScript-type) into the app. In fact, it is the usual reason. Granted, it might also be overkill for your app. But it's a very good way to build in some "hidden" preferences. On the other hand if you are just saying you want to automate the choosing of a certain menu item or pushing of a certain button 100 times, you could use GUI scripting without bothering to make your app scriptable at all. GUI scripting is a very good "poor man's" way to automate interface testing, and on Cocoa apps it just works, out of the box, for most interfaces. m. -- matt neuburg, phd = m...@tidbits.com, <http://www.tidbits.com/matt/> A fool + a tool + an autorelease pool = cool! AppleScript: the Definitive Guide - Second Edition! http://www.tidbits.com/matt/default.html#applescriptthings _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
