osaxen loaded into memory
osaxen loaded into memory
- Subject: osaxen loaded into memory
- From: JJ <email@hidden>
- Date: Fri, 06 Jul 2001 15:08:03 +0200
I was re-studying "Jon's Commands" (up to six hours!) and readed the
documentation from 2.1.2 version about command "load embedded scripting
additions".
(Jon Pugh)
+In the case where a scripting addition is installed in the system and
the same one (or a different version of the same one) is in the applet,
the one installed in the application by this command will be used,
solely because it is in the application's event handler table, which is
searched before the system's table where all the other scripting
additions are.
;This command should only be called once because it loads the 'osax'
resources into memory, detaches them and installs them in the event
handler table. It does not keep any reference to those memory blocks, so
they are not reclaimed until the application quits. Calling this
multiple times will install multiple copies and use a potentially
significant amount of memory. ;
So, I understand:
1. Build the following aplet and then copy into it resources (from
"password" osaxen):
- "osax", the code.
- "DITL" & "DLOG", needed by "osax"
to display the password interface.
2. Kill coercions:
Copy "password" osaxen to desktop, delete the original & empty trash
3. Run aplet:
-- START SCRIPT --
load embedded scripting additions
--> loads embedded "osax" rsrc into memory and install it
user password
--> display correctly the password interface
--> uninstall "osax" rsrc
-- END SCRIPT --
So, have we these loading-osax types?:
1. "Always-running" (busy files). At my computer:
> AppleScript Formatting
> RegEx Commands
> Standard Additions
> Satimage
2. Persistent coercions: (loaded into memory but not installed until
they are required/called?)
3. Punctual coercions: (the ones generated by, i. e., Jon's Commands?)
?
JJ