Re: Should I remove NSTabViews from the hierarchy?
Re: Should I remove NSTabViews from the hierarchy?
- Subject: Re: Should I remove NSTabViews from the hierarchy?
- From: James Dempsey <email@hidden>
- Date: Thu, 22 Feb 2007 17:45:18 -0800
On Feb 22, 2007, at 4:47 PM, Ricky Sharp wrote:
On Feb 22, 2007, at 6:34 PM, James Dempsey wrote:
Is the scriptability of the application an important piece of functionality for your users - or perhaps you are using UI Scripting more for automated testing of the app?
Scripting would be rarely used. I will have some customers that my be interesting in UI scripting on occasion (e.g. set up similar preferences for a group of students)
Thanks James, this really helps out a lot. I'll keep the deep hierarchy as-is. I suppose I could always add an attribute (e.g. title) at some point to the groups so that they can be referred to either by index or name.
Sure thing - and for automation I'd encourage you to look at application scriptability of your app rather than UI Scripting. Usually expressing things in terms of a scripting dictionary that represents a portion of the model of the app is a lot more compact than scripts that need to iterate through the UI.
If there are one or two use cases you think would be very useful for your customers (perhaps setting up similar preferences for a group of students, or maybe automatically gathering results or stats from the application via a script), a relatively simple scripting dictionary can often go a long way - and also serve as the basis for custom Automator actions.
-James
-------------------------------------------------- James Dempsey AppKit Engineering Apple
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden