Giving Smile a test run
Giving Smile a test run
- Subject: Giving Smile a test run
- From: Jeff Porten <email@hidden>
- Date: Thu, 18 Aug 2005 20:51:25 -0400
So I'm messing around with Smile for what I think is the first time,
and I'm not entirely grokking it. So I thought I'd toss around a few
questions for other folks who went from Ye Olde Script Editor to this
thingamajig.
1) I'm gathering that the script windows are what I'm used to to SE.
Workspaces are for code testing. When you're banging out code, where
do you usually go?
2) If you use the custom Smile commands, what happens if you open a
saved script in SE? Do you have to manually strip out the commands
that won't work, or is there some voodoo that takes care of this?
3) Does anyone have any suggestions for when to use one editor over
the other (if you switch back and forth)?
4) For all those nifty UI commands, what exactly does one have to
ship? Does a self-contained app store all the code it needs? And
for someone who hasn't learned either yet, how does the learning
curve for Smile compare to AppleScript Studio?
Note: not trying to start any kind of flames against either app; just
trying to figure out the tools.
Best,
Jeff
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden