[timmerk]

I love it except for these two facts:

It has a script folder inside of it with all the AppleScripts. I think it should be inside the app inself, not just the package.

Those "compiled" scripts look way to easy to "decompile". Isn't there a run only feature like in script editor?

On another note, anyone know if sticking a scripting addition inside the package would be accessed by the script? Sort of like the merging a scription addition to the program like FaceSpan had.

[Tim Bumgarner]

Originally posted by timmerk:
<STRONG>I love it except for these two facts:

It has a script folder inside of it with all the AppleScripts. I think it should be inside the app inself, not just the package.

Those "compiled" scripts look way to easy to "decompile". Isn't there a run only feature like in script editor?

On another note, anyone know if sticking a scripting addition inside the package would be accessed by the script? Sort of like the merging a scription addition to the program like FaceSpan had.</STRONG>

There is a build style in each project, Development and Deployment. By default it is set to Deployment. (You can customize the toolbar to add the 'Build Styles' to your toolbar.) If you set the build style to 'Deployment' the scripts are compiled such that the script can't be decompiled. Similar to doing a 'Save as Run-Only' option in Script Editor.

The scripts are built into the application. Any native OS X application is basically a bundle (or app wrapper) with the following structure (given a Studio application called 'Quick Test'):

Quick Test.app
Contents
Info.plist
MacOS
Quick Test &lt;---- The Mach-O executable
pbdevelopment.plist
PkgInfo
Resources
English.lproj
InfoPList.strings
MainMenu.nib &lt;---- The user interface file
Scripts
Application.scpt

In the finder of course all you see is 'Quick Test'.

As the adding a scripting addition inside the application, there currently isn't support for that.

By the way there is a new mailing list for Studio. Go to http://www.lists.apple.com/mailman/l...escript-studio and sign up!

[Tim Bumgarner]

Originally posted by Tim Bumgarner:
<STRONG>

There is a build style in each project, Development and Deployment. By default it is set to Deployment. (You can customize the toolbar to add the 'Build Styles' to your toolbar.) If you set the build style to 'Deployment' the scripts are compiled such that the script can't be decompiled. Similar to doing a 'Save as Run-Only' option in Script Editor.

The scripts are built into the application. Any native OS X application is basically a bundle (or app wrapper) with the following structure (given a Studio application called 'Quick Test'):

Quick Test.app
Contents
Info.plist
MacOS
Quick Test &lt;---- The Mach-O executable
pbdevelopment.plist
PkgInfo
Resources
English.lproj
InfoPList.strings
MainMenu.nib &lt;---- The user interface file
Scripts
Application.scpt

In the finder of course all you see is 'Quick Test'.

As the adding a scripting addition inside the application, there currently isn't support for that.

By the way there is a new mailing list for Studio. Go to http://www.lists.apple.com/mailman/l...escript-studio and sign up!</STRONG>

Sorry, the tab's didn't show up correctly:

Quick Test.app
Contents
Info.plist
MacOS
Quick Test &lt;---- The Mach-O executable
pbdevelopment.plist
PkgInfo
Resources
English.lproj
InfoPList.strings
MainMenu.nib &lt;---- The user interface file
Scripts
Application.scpt

[Tim Bumgarner]

Originally posted by Tim Bumgarner:
<STRONG>

Sorry, the tab's didn't show up correctly:

Quick Test.app
Contents
Info.plist
MacOS
Quick Test &lt;---- The Mach-O executable
pbdevelopment.plist
PkgInfo
Resources
English.lproj
InfoPList.strings
MainMenu.nib &lt;---- The user interface file
Scripts
Application.scpt</STRONG>

Oh, I give up! ;-) I'm not sure how to get it to show the leading spaces/tabs, bug If you post a reply you'll see it correctly. Sorry about that...

[Mactoid]

Originally posted by Tim Bumgarner:
<STRONG>Oh, I give up! ;-) I'm not sure how to get it to show the leading spaces/tabs, bug If you post a reply you'll see it correctly. Sorry about that...</STRONG>

<BLOCKQUOTE><font size="1"face="Geneva, Verdana, Arial">code:</font><HR><pre><font size=1 face=courier>
try
the
code
tags

</font>[/code]

[swoodnj2]

Originally posted by timmerk:
<STRONG>I love it except for these two facts:

It has a script folder inside of it with all the AppleScripts. I think it should be inside the app inself, not just the package.

Those "compiled" scripts look way to easy to "decompile". Isn't there a run only feature like in script editor?

On another note, anyone know if sticking a scripting addition inside the package would be accessed by the script? Sort of like the merging a scription addition to the program like FaceSpan had.</STRONG>

Tim,

I think as somebody else mentioned you just need to change the target. Click on the "Target" tab (it's one of the vertical tabs) and change it from Development to Deployment.

Steve W

[timmerk]

Thanks everybody! I'm a lot more happy - 1 last thing, does it get faster when changed to Deployment? I'm asking because even some of Apple's own examples are dog slow. For example the Browser App and some others that have to do with files and parsing.

[timmerk]

Umm.. I just tested it out for myself with Apple's browser example - no speed increase, AND, here's the worst part, changing the build style from dev to deploy does nothing (well almost nothing) about changing the script to being hard to decompile.

Example from browser example:

This in the only line (line 28) that changes slightly out of all the compiled script:

(from dev build
aron&gt;ún&gt;&lt;caron&gt;&l t;caron&gt;n&gt;Ä&lt;caron&gt;úgt; Ô@lis;&lt;caron&gt;&lt;caron&gt;&a mp;lt;caron&gt;Ue;&lt;caron&gt;255.59

[timmerk]

Originally posted by timmerk:
<STRONG>Umm.. I just tested it out for myself with Apple's browser example - no speed increase, AND, here's the worst part, changing the build style from dev to deploy does nothing (well almost nothing) about changing the script to being hard to decompile.

Example from browser example:

This in the only line (line 28) that changes slightly out of all the compiled script:

(from dev build
U
Finder.app ü@on&gt;Ô?s‡¨ø&lt;caron&gt ;ÔpZ¸Ã‚s‡–ø&lt;caron&gt;MACS Xron&gt;&lt;caron&gt;X:System:Library: CoreServices:Finder.appa
Ö‡lt;caron&gt;MACSin der.app#pp&gt;»Écy: timmerk ]</STRONG>

any ideas what to do now?

[ 12-20-2001: Message edited by: timmerk ]