• 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: [OT] Re: Smile and FruitMenu
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [OT] Re: Smile and FruitMenu


  • Subject: Re: [OT] Re: Smile and FruitMenu
  • From: Bill Cheeseman <email@hidden>
  • Date: Tue, 07 Dec 2004 18:12:12 -0500

on 2004-12-07 12:36 PM, Andrew Oliver at email@hidden wrote:

> On 12/7/04 9:28 AM, "Robert Poland" <email@hidden> wrote:
>
>> OS 10.3.6
>>
>> Since Smile and FruitMenu don't work together how do others navigate?
>> ...
>> Not sure which I should drop FruitMenu or Smile.
>
> Oooh, the challenge!
>
> I can feel Emmanuel's blood pressure rising from here! :)
>
> Anyone want to place bets on how long it'll take him to fix that one? :)

Just for the record, I had a very good experience working with Unsanity,
figuring out how to resolve a conflict between my product, PreFab UI
Actions, and the Unsanity Application Enhancer. Unsanity put a lot of time,
unasked, into debugging the interaction between UI Actions and the
Application Enhancer. With the help of Unsanity, for which I am grateful, we
figured out that UI Actions was running AppleScripts on the assumption that
UI Actions was always a one-thread application. In fact, the Application
Enhancer (as I understand it) forces applications to become multithreaded,
and AppleScripts can't be run reliably except on the main thread. As far as
I know, Application Enhancer is not alone in forcing applications to run
multithreaded -- I believe some Apple frameworks do, as well. The lesson for
developers: always write your applications defensively, assuming that you
might not be the main thread.

The end result was that I revised UI Actions slightly (before its final
public release) so that it always runs AppleScripts on the main thread.
There is a simple Cocoa method (in Panther and later, I believe) to do this.
UI Actions now lives happily alongside Application Enhancer and all the
little haxies, as far as I know.

I imagine Smile could do the same.

Paul Berkowitz was involved in my correspondence with Unsanity. He can chime
in with his own impressions, if he wants to. Speaking for myself, I feel
that Unsanity has gotten a bad rap, and the main reason it lives on is that
people keep repeating what other people say.

--

Bill Cheeseman - email@hidden
Quechee Software, Quechee, Vermont, USA
http://www.quecheesoftware.com

PreFab Software - http://www.prefab.com/scripting.html
The AppleScript Sourcebook - http://www.AppleScriptSourcebook.com
Vermont Recipes - http://www.stepwise.com/Articles/VermontRecipes


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: [OT] Re: Smile and FruitMenu
      • From: "John C. Welch" <email@hidden>
References: 
 >[OT] Re: Smile and FruitMenu (From: Andrew Oliver <email@hidden>)

  • Prev by Date: Re: Unwinding the containment hierarchy of a reference
  • Next by Date: Re: How to kill a process using AS
  • Previous by thread: Re: [OT] Re: Smile and FruitMenu
  • Next by thread: Re: [OT] Re: Smile and FruitMenu
  • Index(es):
    • Date
    • Thread