MACSCRPT Archives

November 2009

MACSCRPT@LISTSERV.DARTMOUTH.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Paul Skinner <[log in to unmask]>
Reply To:
Macintosh Scripting Systems <[log in to unmask]>
Date:
Tue, 17 Nov 2009 13:25:57 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (32 lines)
Jon,

	I love Script Debugger, but I found Script Debugger's Library  
function to be somewhat unwieldy. Scripts loaded as libraries cannot  
contain a run handler, the loaded objects are completely invisible in- 
editor and it seems to have a small but noticeable runtime overhead  
that I can't understand.

	Do you personally use SD's library or any other library loading  
function regularly?

Thanks,
Paul Skinner


On Nov 16, 2009, at 10:16 PM, Jon Pugh wrote:

> At 5:42 PM -0800 11/16/09, Stan Cleveland wrote:
>> There may be other library systems that I've either forgotten about  
>> or of
>> which I'm unaware. Please forgive my inadvertent omissions.
>
> Script Debugger has had a library system built in for years now.
>
> It uses a similar system to Paul's suggestion, loading the library  
> into the script's context (instead of the parent), so everything is  
> just accessible with no work or cruft in the script.  Script  
> Debugger provides a library selection sheet which allows easy  
> library selection and management.
>
> Jon

ATOM RSS1 RSS2