Mail glue and making glue on x

[Brian Ablaza]

There is a trick (which I used today for the Image Capture scripting 
addition), and it seems to work.

There is a brief thread in the discussion group. Do a search on 
Google for "commercial aete os x" and it should be the first hit. 
This is the salient message, which I will recap below.

http://frontier.userland.com/discuss/msgReader$10545

Here's the basic approach:

1) Find out the application signature for your app. The Mail app is 
'emal', but what if I didn't know that? The signature is in the 
pkgInfo for the app. Using a text editor that can see "hidden" files 
(I used BBEdit), or using a command line editor (like pico), navigate 
to the app and "open" it (it's really a folder). Inside, open the 
Contents folder, then the pkgInfo file. It will say, "APPLemal" for 
Mail: the application signature is "emal".

2) In Frontier, create this script:

result = AppleEvent('[app signature]', 'ascr', 'gdte')
file.new("[path to writable folder]:appAETE.rsrc")
rez.putResource ("[path to writable folder]:appAETE.rsrc", 'aete', 0, @result)

where "app signature" is the signature you got from the pkgInfo file, 
and "path to writable folder" is a path to a folder you have 
privileges for. If you try to write to the top-level directory, 
you'll get a permissions error (probably).

3) Fix the commercial suite. Jump to "commercial.enterAppName". Find 
the statement, "If promptForFile". Below that, where it says, "if not 
file.getFileDialog()", the file type is set to 'APPL'. This won't 
work, since you are trying to import from a resource file, not an 
app. So change 'APPL' to 0 to have Frontier show you all files, not 
just apps. If you try to import the aete's manually using "Import 
'aete info..." from the Glue menu, you'll have to perform a similar 
fix.

4) From the Glue menu, choose, "Enter your App's name...". When 
asked, "Where is [app name]?", navigate to the rsrc file you created 
in step 2. Answer yes to everything else.

5) Fix the glue table. Open up the glue table you just made ("Open 
Table & Menu" from the Glue menu). Open the appInfo table. The path 
will be wrong, since it is the path to the resource file, not the 
app. You can either correct the filespec, or just delete it. When you 
call any script in the table, you will be prompted to find the 
application. Navigate to the correct app this time and Frontier will 
fill in the correct path. Th app ids are wrong as well. You probably 
have "????" instead of a creator code. I don't know if it matters, 
but change this to the application signature you determined in step 
1. The id appears in two places: in the appInfo table and in the glue 
table proper.

Good luck. Let us know what happens.





>Does any one have a glue table for mail.app on MacOS X or is there a 
>version of Commercial Developers Suite that has been updated?
>
>Sam D
>=======
>See a new experiment: a dad and his two girls
>http://scidzone.editthispage.com
>join, see and share......
>=======


-- 
Brian Ablaza
Chief Technology Officer
Star Interactive

856.488.2015
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.userland.com/pipermail/frontier-users/attachments/20021007/a2a3b8ed/attachment-0002.htm