• 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: Accessing Localized File Menu String
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Accessing Localized File Menu String


  • Subject: Re: Accessing Localized File Menu String
  • From: Philip Aker <email@hidden>
  • Date: Tue, 21 Jul 2009 04:45:33 -0700

On 2009-07-20, at 19:49:56, Chris Page wrote:

The solution is to report bugs against those applications. <http://bugreport.apple.com/ >


I'm willing to bet that folks on this list have filed bugs pertaining to scripting years ago which still haven't been addressed. So that doesn't strike me as being a solution.

If people are encountering a problem and report it, it's more helpful for development teams trying to decide where to focus their finite resources.

Obviously, if there are no reports, they may never know the problem even exists, much less how to prioritize it.

Report bugs and enhancement requests for application scripting support so they know it's important to you. Otherwise, you're just waiting around for someone on the development team to notice it and decide that it's important even though no users have asked for it to be addressed.

Hey Chris,

Bugreporter has a hard time dealing with systemic errors (<radr://6694000 > e.g. which I filed and then was asked to re-file for every header in CoreFoundation!). Ridiculous. IOW, for the ~50 applications that Apple includes in a stock release, why don't you, from a non-Apple account, file 50 individual bugs and then tell us how long it takes. That's more like a full time job with a salary and perks. And, in the long run, not an effective solution because it caters to the bug reporting format and not the root cause of problem.

One would expect Apple, in the interest of having a better overall product, to have a category for systemic errors and the resources/ talent available to handle them. For the problem at hand, you seem to be suggesting that it's not an AppleScript problem per se. True. It's a scriptability problem in general. I believe a good method is for the AppleScript team to have an enforcer with some clout so that these types of things can be addressed efficiently.

I will file one bug on this problem.


Philip Aker echo email@hidden@nl | tr a-z@. p-za-o.@

Democracy: Two wolves and a sheep voting on lunch.

_______________________________________________
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
References: 
 >Accessing Localized File Menu String (From: Ian was here <email@hidden>)
 >Re: Accessing Localized File Menu String (From: Chris Page <email@hidden>)
 >Re: Accessing Localized File Menu String (From: Philip Aker <email@hidden>)
 >Re: Accessing Localized File Menu String (From: Chris Page <email@hidden>)
 >Re: Accessing Localized File Menu String (From: Philip Aker <email@hidden>)
 >Re: Accessing Localized File Menu String (From: Chris Page <email@hidden>)

  • Prev by Date: Re: Accessing Localized File Menu String
  • Next by Date: Re: AppleScript-Users Digest, Vol 6, Issue 324
  • Previous by thread: Re: Accessing Localized File Menu String
  • Next by thread: Re: Accessing Localized File Menu String
  • Index(es):
    • Date
    • Thread