Re: Input for Upcoming Book
Re: Input for Upcoming Book
- Subject: Re: Input for Upcoming Book
- From: Steven Angier <email@hidden>
- Date: Mon, 20 Jan 2003 11:08:01 +1100
On 18/1/03 4:19 PM, "Paul Berkowitz" <email@hidden> wrote:
>
On 1/17/03 7:53 PM, "Steven Angier" <email@hidden> wrote:
>
>
> AppleScript Studio has some severe limitations -- the largest of which (to
>
> me) is the inability for the various scripts to share data. This effectively
>
> forces the entire project into one main project file, and the inevitable
>
> gigantic conditional statements make the event handlers cumbersome to work
>
> with.
>
>
Of course they can share data. There are examples to show how to do it,
>
where you load the other scripts as script objects. Bill Cheeseman published
>
a tutorial for this kind of set-up, which is excellent. What you can't do is
>
save persistent script properties between script runs. But the user default
>
methods are easy and work perfectly. You just have to learn them, which is
>
not hard, although a bit peculiar.
Perhaps I wasn't clear. I meant to say that the largest limitation of Studio
to me is the inability for the various scripts to share live data easily.
I consider inter-script communication by storing/loading data in scripts to
be less than ideal. I think that scripts within the same project should be
able to pass data around, sharing globals and functions.
Personally, I think FaceSpan had it spot-on with their model:
Controls could contain scripts whose parent was the window script, whose
parent was, in turn, the project script. FaceSpan also had the concept of a
Storage Item -- a sort of glob field which could hold just about anything,
including properties, functions, even entire scripts.
Steven Angier
Macscript.com
_______________________________________________
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.