Re: [MACTCL] Making a Tk app scriptable via AppleScript

[Kevin W. <kw...@co...>]

Hi Daniel,

On 8/17/09 7:49 PM, Daniel A. Steffen wrote:

>
> are you sure ScriptEditor is talking to the right app? that script
> works fine for me with HEAD.
> You won't get any output this way BTW, but the following does return
> the correct patchlevel string for me in Script Editor
>
> tell application "/path/to/embedded/Wish.app"
> 	do script "info patchlevel"
> end tell

Not sure what I was doing wrong before, but a fresh build of Wish using 
the latest commits to de-carbon-85 works great. Thanks.

>
>> I see the sdef in the app bundle, thanks. I do notice this blows away the
>> previous Cocoa-standard dictionary (standard suite and text suite)--is this
>> a problem? Not sure how relevant these things are to a Tk app, especially
>> since basic Apple events are supported in TkMacOSXHLEvents.c.
>
> right, the 'reqd' doesn't seem to pull in the required suite
> description by itself like it used to in an 'aete' :-(
> Attached an updated .sdef that adapts the only three relevant commands
> (odoc, pdoc&  quit) from the standard sdef
>      /System/Library/ScriptingDefinitions/CocoaStandard.sdef
> to have the params/results that Wish understands.
>
> the other AppleEvents Wish understands (oapp, rapp, pref) don't have
> entries in the standard sdef so presumably aren't usually listed in
> the standard AS dictionaries...
>
> It is in fact desirable that the default Cocoa standard suite and text
> suite commands no longer appear, Wish doesn't understand any of these
> anyway, there is no standard NSDocument or NSText-based structure in
> Tk that would allow Cocoa Scripting to do its magic...
>
>> Once this is final, can you please commit this to de-carbon-85 as well?
>
> already done in fact (for ease of testing) along with the other recent
> changes to notifier and NSView drawing, c.f. git log.
> Will commit to CVS HEAD once I get confirmation that all this fixes
> the aMSN issues and doesn't introduce any new breakage.
>
Looks good to me...

Thanks,
Kevin


-- 
Kevin Walzer
Code by Kevin
http://www.codebykevin.com