Re: Script in Script Editor MUCH faster than compiled app -- why?
Re: Script in Script Editor MUCH faster than compiled app -- why?
- Subject: Re: Script in Script Editor MUCH faster than compiled app -- why?
- From: Paul Berkowitz <email@hidden>
- Date: Tue, 29 Apr 2003 11:00:06 -0700
On 4/29/03 10:21 AM, "Jeff Porten" <email@hidden> wrote:
>
I've got a script running which:
>
>
1) creates a Finder list of files in a given folder (numbering in the
>
thousands)
>
2) opens each file for access sequentially
>
3) reads the file into a variable
>
4) and if the text contains a given string, adds this text to a
>
FileMaker Pro database (in a nested tell)
>
>
All working just fine. The thing I don't get: it's MUCH faster when
>
I've got the script open in Script Editor, than when I save it as a
>
compiled app and launch it. Makes no sense to me. Why is this
>
happening?
Maybe Script Editor is better at demanding memory and/or CPU allocation from
the system than an applet is designed to do? (Incidentally, I've never seen
"compiled app" as a term anywhere. If you're talking about a "complied
script" run by the Jaguar script menu, that's _really inefficient_ and slow
since it calls on System Events to do the work, then has to send AppleEvents
from System Events to the other apps. If you mean "saved as an application"
then say so. "compiled application" is confusing since we don't know what
you mean.) It could be that applets (script applications) have been designed
to be less demanding than other apps, if such a thing is possible, or just
are inefficient.
This is assuming you're in OS X. In OS 9, just give the applet more memory
and hope for the best.
--
Paul Berkowitz
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.