Forced to use Applescript

RCS rcs at rcsprogramming.com
Thu Feb 6 14:35:01 EST 2003


What started this 'copying files' rant for me was the fact that I MUST use
AppleScript to copy 'Application' files on the Mac...here's why (and tell me
if I am wrong):

*Note: When I say copying an Application file, I mean the data and resource
fork, and doing a copyResource if you have to, as well as type and creator.

Copying any 'Application' file using either 'open/write/close as binFile' or
'URL binFile:' will trash the custom icon property. And you cannot set that
with MetaCard. You can set some flags, but not that one...
Test: Copy your stand-alone that has your custom icon.


You cannot copy Application' files in OSX  using ANY MetaCard
method...MetaCard sees '.app' files as folders. That is also why you cannot
create an 'alias' to an 'Application' file (i.e .app package) using 'create
alias' in MetaCard.

Test:  Do a "put files" on a directory in OSX that has files (both documents
and Application files) and folders...you won't see any '.app' files like
'iTunes'. But you will if you do a 'put folders'.


  Windows works fine...it took me a few hours. I have a really high speed
interface that I am proud of. As far as OS9 and OSX...I have been grappling
with this AppleScript BS for a few days now, and the final result stnks. I
have an Apple dialog that pops up for every file and folder I am copying.
Lame...

  The only thing that didn't work using native MetaCard routines in OSX was
copying the 'Mach-O' resource from an '.app' package. There was some kind of
corruption going on, and I couldn't track it down any further than to the
Metacard engine itself.

This is all using MetaCard 2.4.3 by the way.
OSX 10.1.5
OS 9.2.1
Windows 98SE


JR




More information about the metacard mailing list