• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: A bit more UI capabilities? (was: Re : on blocking target applications' GUIs)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: A bit more UI capabilities? (was: Re : on blocking target applications' GUIs)


  • Subject: Re: A bit more UI capabilities? (was: Re : on blocking target applications' GUIs)
  • From: Chris Page <email@hidden>
  • Date: Fri, 19 Dec 2008 17:38:29 -0800

On Dec 20, 2008, at 12:48 AM, Axel Luttgens wrote:

For example, should one need more than three choices (hence, more than three buttons), it is required to nest multiple dialogs ... or to devise some more or less clever (naughty?) tricks with the help of "choose from list".

That is exactly what ‘choose from list’ is for: choosing from several items. Can you provide an example where using a list would be "naughty"?


Do you mean you need nested controls? Like:

  () Choice A
     [] an option for A
     [] another option for A
  () Choice B
     [] an option for B
     [] another option for B

() is a radio button, [] is a checkbox.

They are also a bit too limited in their scope. For example, native progress bars and keyboard sensing would certainly delight more than one scripter.

Perhaps would it be a good idea to integrate such capabilities into AppleScript, while preserving its current KISS approach for such matters (I mean, no need to incorporate a full-fledged say, AppleScript-Studio into the language, just small incremental changes such as allowing more than three buttons in a dialog).

This is why AppleScript Studio was created. This enables people to use Interface Builder and Cocoa without us having to do a lot of work to duplicate that functionality. It was created so that we wouldn't have to turn ‘display dialog’ into something like Dialog Director.


Obviously, finding the right place to draw the line between using a plain AppleScript and using Studio is challenging.

It helps if people post specific enhancement requests, especially if you can provide concrete, real-world examples of the problem you need solved and a description of how you currently solve it:

  <http://bugreport.apple.com/>

--
Chris Page

 The other, other AppleScript Chris

_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users

This email sent to email@hidden
  • Follow-Ups:
    • Re: A bit more UI capabilities? (was: Re : on blocking target applications' GUIs)
      • From: Axel Luttgens <email@hidden>
References: 
 >A bit more UI capabilities? (was: Re : on blocking target applications' GUIs) (From: Axel Luttgens <email@hidden>)

  • Prev by Date: Re: Tell Blocks Considered Harmful
  • Next by Date: Re: Tell Blocks Considered Harmful (was Re: open for access)
  • Previous by thread: A bit more UI capabilities? (was: Re : on blocking target applications' GUIs)
  • Next by thread: Re: A bit more UI capabilities? (was: Re : on blocking target applications' GUIs)
  • Index(es):
    • Date
    • Thread