Re: Permissions in an app bundle

FROM : Nir Soffer
DATE : Wed Jul 05 17:13:54 2006

Quoting Tage Borg <<email_removed>>:

>
> On 2006-07-05, at 11:42, Nir Soffer wrote:
>
> > I pack a directory structure in my app bundle, which used to create 
> > new "documents" by copying the a template directory and adding 
> > content. I prefer to have the directory in the bundle and not in 
> > application support folder, to allow drag and drop install.
>
> Let me just ask, in case you haven't considered this alternative: 
> Have you thought about letting your application copy the template 
> directory to an application support folder on first execution? This 
> way you can have drag and drop installation and also have (1) the 
> templates outside the bundle and (2) code already in place for 
> handling drag and drop installation of more templates. Drag and drop 
> uninstallation won't be there, of course, but still...


I considered this, and I see several problems:
1. If the user delete the template, the app will not work.
2. A user may not have permissions to copy to /Library, I will have to handle
this by authorization or fallback to the user Library, then search for templates
on both directories, handle the case where there are multiple copies etc.
3. I leave junk on /Library or user Library folders when uninstalling

The best solution seems to be to keep the template in the app bundle. The
template is not visible to the user, and I don't need to support more templates
installed by the user.

The simplest thing - no code required - is to make the template writable in the
bundle.


--
Best regards,

Nir Soffer