In article ,
William wrote:
> I'm stuck in another area of my app where I'm not making much progress,
> so I wanted to step out of it for a bit and work on how to bundle my
> application for a release.
>
> I will have my app, a *.dylib, and a directory of example files to read
> and write to as a sort of working dir. Can anyone point me to something
> about how to package up something like this?
I assume you have read
<http://developer.apple.com/tools/installerpolicy.html>
The dynamic library should be stored inside the app's package (there are
exceptions, but 99.9% of apps do not fall in that category)
The example files are a different issue. At first sight, example files
should be visible in the Finder, requiring installation outside the
application bundle.
I would advise some rethinking here. Two options are:
- do not ship example files; ship templates instead
- ship examples inside the application bundle (for an example, see
/Applications/Utilities/Grapher.app)
I think both approaches are better than using a secondary install
location. Which is best for you depends on whether you can show off your
application features in templates that really look like templates. If
you do imitate Grapher, do not make the same mistake they did, and do
not attempt to save the examples inside the application bundle.
Reinder
>> Stay informed about: release packaging