bug #18283 / change "Enable applescript in NextStep"

bug #18283 / change "Enable applescript in NextStep"

[David Reitter]

Question - what’s up with this change?

Author: Anders Lindgren <andlind@gmail.com>
Date:   Tue Nov 24 22:05:05 2015 +0100

    Fixed bug#18283: Enable applescript in NextStep.

    * nextstep/templates/Info.plist.in: Set NSAppleScriptEnabled to YES.


So, this does not enable AppleScript handling.  All it does is it declares that we  can handle AppleScript.  But can we?  It would be news to me.  The URL below details all the things that have to be done to handle AppleScripts.  For example, we have to have a scripting definition file (sdef) and actually handle incoming events.

So,  the reporter of bug #18283 literally requested this change, but I think that may have just been a somewhat silly way to say:  “Can you please support AppleScript?”

But perhaps I’m misunderstanding all of this and there’s a grand master plan. 
Anders?




[1] https://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/ScriptableCocoaApplications/SApps_implement/SAppsImplement.html#//apple_ref/doc/uid/20000037-BBCJEEEC

Re: bug #18283 / change "Enable applescript in NextStep"

[Anders Lindgren]

[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]

Hi,

This change allows applescripts like the following to work:

    tell application "Emacs"
         set the bounds of the first window to {100, 100, 500, 500}
    end tell

Without the change, the following error message is issued:

    test.oas:23:89: execution error: Emacs got an error: Can’t set bounds
of window 1 to {100, 100, 500, 500}. (-10006)

However, after the change, Emacs repositions and resizes its frame nicely.


So,  the reporter of bug #18283 literally requested this change, but I
> think that may have just been a somewhat silly way to say:  “Can you please
> support AppleScript?”
>
> But perhaps I’m misunderstanding all of this and there’s a grand master
> plan.
>

The original poster asked for this change in order to write automatic tests
for the NextStep user interface. Concretely, it was used to verify that the
recent problems with tool-bar-mode setting the wrong frame size was solved.
I am absolutely sure that he did not implicitly expected a full AppleScript
interface to be implemented.

    -- Anders Lindgren

[-- Attachment #2: Type: text/html, Size: 1534 bytes --]

Re: bug #18283 / change "Enable applescript in NextStep"

[David Reitter]

Anders, 
Thank you.  That sounds like a good change then, but I needed your explanation to understand.

- David


> On Nov 25, 2015, at 12:44 AM, Anders Lindgren <andlind@gmail.com> wrote:
> 
> Hi,
> 
> This change allows applescripts like the following to work:
> 
>     tell application "Emacs"
>          set the bounds of the first window to {100, 100, 500, 500}
>     end tell
> 
> Without the change, the following error message is issued:
> 
>     test.oas:23:89: execution error: Emacs got an error: Can’t set bounds of window 1 to {100, 100, 500, 500}. (-10006)
> 
> However, after the change, Emacs repositions and resizes its frame nicely.
> 
> 
> So,  the reporter of bug #18283 literally requested this change, but I think that may have just been a somewhat silly way to say:  “Can you please support AppleScript?”
> 
> But perhaps I’m misunderstanding all of this and there’s a grand master plan.
> 
> The original poster asked for this change in order to write automatic tests for the NextStep user interface. Concretely, it was used to verify that the recent problems with tool-bar-mode setting the wrong frame size was solved. I am absolutely sure that he did not implicitly expected a full AppleScript interface to be implemented.
> 
>     -- Anders Lindgren
>