Existing users, 
 Script Bundle Tool - 4.1.0Create AppleScript application bundles. |
|
||||||||||||||
|
|||||||||||||||
Feedback Summary:
| This Version: | |||||
| Overall Rating: | Not rated (0.0) | Features: | Not rated (0.0) | Support: | Not rated (0.0) |
| Ease of Use: | Not rated (0.0) | Quality / Stability: | Not rated (0.0) | Price: | Not rated (0.0) |
Key to Types of Feedback:
Reviews 
Troubleshooting 
Usage Tips 
Developer Notes 
Commentary 
Featured Reviews
All Feedback: 1 - 4 of 4
Oh, for heaven's sake, VT, fix the double-posting bug!!! - Version: 4.0.6, 11/21/2006 10:21PM PST
(2 of 2 users found this comment useful)
Krioni
Previewing a post should NOT result in it being posted twice. This happens way too often.
Script Editor bundles have bugs - Version: 4.0.6, 11/21/2006 10:19PM PST
(1 of 1 users found this comment useful)
Krioni
I don't remember what all of them are (used to program quite a bit in AppleScript, but have forgotten a lot since starting law school), but Script Editor introduces a few bugs when it creates bundles. One big annoying problem is that when you have a "bundle" applet and ask System Events for the currently running processes, the bundle is named "applet" - NOT the name you gave it. Non-bundled applets properly are referenced by the applet's name.
There are also issues dealing with this buggy behavior when you're trying to handle both Panther and Tiger, since System Events in Tiger has a new property for processes that you can use to work around the previously-mentioned bug.
Anyway, I'm assuming that's what the developer means, but don't have time to test it out. If you haven't come across the bugs, perhaps you don't need this.
Then again, Script Editor does not let you specify the short version, etc. of your applet bundle and this does. If you take a Script Editor-created bundle and modify the Info.plist by hand, then save again from Script Editor, I believe it wipes out those manual customizations.
Basically, it sounds like this Script Bundle Tool is very useful if its description is accurate. Too bad it didn't exist back when I was actually writing AppleScript programs often.
There are also issues dealing with this buggy behavior when you're trying to handle both Panther and Tiger, since System Events in Tiger has a new property for processes that you can use to work around the previously-mentioned bug.
Anyway, I'm assuming that's what the developer means, but don't have time to test it out. If you haven't come across the bugs, perhaps you don't need this.
Then again, Script Editor does not let you specify the short version, etc. of your applet bundle and this does. If you take a Script Editor-created bundle and modify the Info.plist by hand, then save again from Script Editor, I believe it wipes out those manual customizations.
Basically, it sounds like this Script Bundle Tool is very useful if its description is accurate. Too bad it didn't exist back when I was actually writing AppleScript programs often.
Script Editor bundles have bugs - Version: 4.0.6, 11/21/2006 10:19PM PST
Krioni
I don't remember what all of them are (used to program quite a bit in AppleScript, but have forgotten a lot since starting law school), but Script Editor introduces a few bugs when it creates bundles. One big annoying problem is that when you have a "bundle" applet and ask System Events for the currently running processes, the bundle is named "applet" - NOT the name you gave it. Non-bundled applets properly are referenced by the applet's name.
There are also issues dealing with this buggy behavior when you're trying to handle both Panther and Tiger, since System Events in Tiger has a new property for processes that you can use to work around the previously-mentioned bug.
Anyway, I'm assuming that's what the developer means, but don't have time to test it out. If you haven't come across the bugs, perhaps you don't need this.
Then again, Script Editor does not let you specify the short version, etc. of your applet bundle and this does. If you take a Script Editor-created bundle and modify the Info.plist by hand, then save again from Script Editor, I believe it wipes out those manual customizations.
Basically, it sounds like this Script Bundle Tool is very useful if its description is accurate. Too bad it didn't exist back when I was actually writing AppleScript programs often.
There are also issues dealing with this buggy behavior when you're trying to handle both Panther and Tiger, since System Events in Tiger has a new property for processes that you can use to work around the previously-mentioned bug.
Anyway, I'm assuming that's what the developer means, but don't have time to test it out. If you haven't come across the bugs, perhaps you don't need this.
Then again, Script Editor does not let you specify the short version, etc. of your applet bundle and this does. If you take a Script Editor-created bundle and modify the Info.plist by hand, then save again from Script Editor, I believe it wipes out those manual customizations.
Basically, it sounds like this Script Bundle Tool is very useful if its description is accurate. Too bad it didn't exist back when I was actually writing AppleScript programs often.
How does this differ from 'Save as Script Bundle' in Script Editor? - Version: 4.0.6, 11/19/2006 10:30AM PST
(0 of 1 users found this comment useful)
Brennan Young
Title asks it all. OK the price is right, but Script Editor does all this stuff automatically if you save as a Script Bundle (or Application Bundle). Just looking for the USP here.
