184449 - [10.3] Most AppleScript doesn't work and can't open AppleScript dictionary (Shockwave needs a resource file)

Status: RESOLVED FIXED

(Camino Graveyard :: OS Integration, defect, P3)

Description

[Stephane Moureau]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021206 Chimera/0.6+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021206 Chimera/0.6+

The Apple Script Editor says ~"can't open the AS dictionary or is not
scriptable", however Navigator appears in the open list and can execute some AS.

Reproducible: Always

Steps to Reproduce:

Comment 1

[Robert Zimmerman]

I have this same problem with the 2002-12-20 build of Chimera in OS X 10.2.2.
Dragging the Chimera icon onto the script editor Smile brings up a dialog that
the applications Applescript dictionary can't be opened. I never had this
problem with previous versions of Chimera (0.5 and 0.6). I believe this means
that a file has been left out of the Navigator application package.

Comment 2

[Simon Fraser [no longer active]]

Mine.

Comment 3

[Simon Fraser [no longer active]]

This is a regression from adding a "Localized.rsrc" file to allow Shockwave
Director to work. It seems that if any resource files are present, Script Editor
looks for Carbon-style script terminology resources. Suckage.

Comment 4

[Clay Loveless]

This bug resurfaced in Camino 0.7.

Comment 5

[Simon Fraser [no longer active]]

Yeah, I'm gonna have to open the .rsrc dynamically after the app launches.

Comment 6

[Bill McGonigle (not currently reading bugmail; please contact directly)]

This appears to be true for Mozilla too - do you want a separate bug?

Comment 7

[Simon Fraser [no longer active]]

I filed bug 202340 to coner mozilla.

Comment 8

[Jon Stevens]

i'm curious what the status of this bug is. confirmed with a recent version of
camino.

Comment 9

[Chris Andrichak]

Yes this problem still exists with today's nightly.
And the same work around still works: remove the Localized.rsrc file from the Camino:Contents:
Resources:English.lproj:  folder.

Comment 10

[Simon Fraser [no longer active]]

I've discovered that the Director plugin doesn't need a 'vers' resource; it just
seems to need the application to have a "default" resource file (i.e. one opened
automatically by the OS). So it's hard to find a way to satisfy it, yet keep
Script Editor happy.

Comment 11

[Mike Pinkerton (not reading bugmail)]

doesn't seem like we're going to find a workaround for 0.9, pushing off to after
1.0.

Comment 12

[Simon Fraser [no longer active]]

Still an issue (note that Camino now uses a Camino.rsrc file, rather that
Localized.rsrc which the above comments describe).

Comment 13

[Wevah (Nate Weaver)]

We could use an 'aete' resource in the Camino.rsrc file, but this is kind of
ugly. I have tried it, though, and it works. Or at least, ScriptEditor will read
the scripting dictionary from it.

Comment 14

[Simon Fraser [no longer active]]

Yeah, we could, and I think we may even be able to build one using sdp from the
same xml file. But Camino is a Cocoa app and should use the New Way. I just want
to know why Directory needs a stupid resource file.

Comment 15

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Is there anyone at Macromedia who can answer comment 14?

Comment 16

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

This is really much worse than the current summary (and our sucky FAQ entry) implies.  Most of our AppleScript is essentially inoperative on 10.3 (and likely 10.2) with the .rsrc present.

I downloaded the latest Shockwave Director plugin and, after much tribulation, determined that it still suffers from this need for a stupid resource file.  

Is there anyone at Adobe we can bug about this?

Comment 17

[Stuart Morgan]

Attachment: workaround

I looked around a bit, and stumbled across OmniWeb's description of their workaround to this problem, which is to open a random resource file and put a reference to it in the magic location to make Shockwave happy. While trying to figure out how to implement that I came across WebKit's version, which seems to be based on the same thing. Since it's a previously described technique and a whopping 4 lines of code, I assume there aren't any license/copyright issues.

This will need a project change to remove the .r file and the script phase that turns it into the .rsrc in the bundle.

Comment 18

[Stuart Morgan]

Smokey, could you put together a project patch? If not, I can dig out my old laptop and do it.

Comment 19

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Attachment: Trunk project patch

You are my hero!  Please remember to update the Release Checklist file, too.

Comment 20

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Attachment: Branch project patch

Comment 21

[Mike Pinkerton (not reading bugmail)]

Comment on attachment 263083 [details] [diff] [review]
workaround

sr=pink

Comment 22

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Since 10.2 also suffers from this bug, is this a reasonable item to include in 1.0.5 before we EOL 10.2 support?

Comment 23

[Stuart Morgan]

Checked in on trunk and MOZILLA_1_8_BRANCH, along with removing the
corresponding line from the checklist file. We should make sure the release notes reflect this.

Flagging 1.0.5? so we don't forget to at least consider it; it seems like a
good idea to me as well.

Comment 24

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Approving for 1.0.5; whoever checks this in, please also update the the Release Checklist file on the 1.8.0, just in case there's a security firedrill or whatever post-1.0.5.

Comment 25

[Stuart Morgan]

Checked in on MOZILLA_1_8_0 branch with relnote fix and slight tweak to the patch to make it apply (the method I was calling from doesn't exist on 1_8_0, but I put in the same logical place in the flow).

Comment 26

[Stuart Morgan]

Attachment: 1_8_0 branch patch

As checked in.