Howdy Steve, Tony, and WeatherCat AppleScript folks,
Yes, the AppleScripts running under Lion still need to have the user download keychain scripting.app. I just dropped it into the scripting additions folder and pointed to it when the Twitter script called for it.
Ya' see . . . . I'm not losing my mind . . . . at least not completely! I "pointed" the Twitter script to Keychain Access when it queried it whilst closing the script, works fine... so far!
Hmm, I see . . . . . definitely the plot now thickens!!
I suppose the explanation is that Apple has only "slimmed down" the available AppleScript tools in the Lion Keychain Access. However, back in the frenzy to get Steve running, it didn't occur to me to just ask Steve to try the Keychain Access application directly. The freebie is supposed to be 100% compatible with the Snow Leopard Keychain Access, to it is
supposed'ta work. Fortunately, Tony tried the
"even more better" solution and it works too (at least thus far.) If that continues to be the case, clearly, the easiest it to tell folks what Tony did intuitively. When the Twitter AppleScript complains, point it at the Lion Keychain Access and get on with it. However, if there are problems down the road, never hurts to have a
plan-B.Thanks gang for all the help with this!!
Cheers, Edouard