Dear cocoa-dev,
So I'm wondering how in the maze of sandboxed apps how to get my app to work
properly. What it does is wrap around pdf files so that they can be combined,
separated; etc. It doesn't actually change the original pdfs, just remembers
their locations, reads them in and then writes
If I understand you correctly, this sounds like the use case for
security-scoped bookmarks:
http://developer.apple.com/library/mac/documentation/Security/Conceptual/AppSandboxDesignGuide/AppSandboxInDepth/AppSandboxInDepth.html#//apple_ref/doc/uid/TP40011183-CH3-SW16
(Sent from my iPhone.)
--
From what I have read in the docs, accessing files outside of the approved
areas/domains (music, photos, documents(?) ) will ALWAYS require user
interaction.
Apple is really screwing us in this one.
I hope that Conrad is right with his suggestion.
On Jun 23, 2012, at 12:17 PM, Matthew
I think the temp.security thing will work, but I'm wondering what happens if a
user replaces a file in the directory by one with the same name; does the os
know it's not the original file?
On Jun 23, 2012, at 9:53 AM, Alex Zavatone wrote:
From what I have read in the docs, accessing files
On Jun 23, 2012, at 12:09 PM, Matthew Weinstein mwein...@kent.edu wrote:
I think the temp.security thing will work, but I'm wondering what happens if
a user replaces a file in the directory by one with the same name; does the
os know it's not the original file?
Security scoped bookmarks are
The whole idea of the app is so that users can automate the combining of
different PDFs; users should be able to swap out different pdfs and then the
program will recombine them. The program remembers (saves in a wrapper) the
pdfs that have been combined. Sort of defeats the purpose if the
On Jun 23, 2012, at 1:16 PM, Matthew Weinstein mwein...@kent.edu wrote:
The whole idea of the app is so that users can automate the combining of
different PDFs; users should be able to swap out different pdfs and then the
program will recombine them. The program remembers (saves in a
Unfortunately that undoes the automation idea. The time saving here is that by
just re-saving the pdf, the app when the document is opened recombines it based
upon the rules that the user set up. Basically you're forcing the user to
recreate the sequence of files each time anew.
On Jun 23,
So if I understand your pattern, you are managing a single product PDF which
is constructed by your app based upon metadata which describes the specific
component PDFs etc that the user has chosen. Those component PDFs reside
elsewhere than within your app space, correct?
On 2012-06-23, at
Yup! They are contributed by the user, but they stay in the user space; they
are read-only. I create a pdfdocument with them and then borrow pages to
resequence them (based on a table the user keeps) and spit out a new pdf. The
automatic part is that the user can tell the program what to do
I think I see a second problem coming down the pike. the users can add pdfs to
the wrapper file through a typical open file or through drag and drop. I get
that the NSOpen... allows me to expand entitlements. But does drag and drop? Is
there a way to get a bookmark and ask for ongoing
On Jun 23, 2012, at 1:26 PM, Matthew Weinstein mwein...@kent.edu wrote:
Unfortunately that undoes the automation idea. The time saving here is that
by just re-saving the pdf, the app when the document is opened recombines it
based upon the rules that the user set up. Basically you're
On Jun 23, 2012, at 2:02 PM, Matthew Weinstein mwein...@kent.edu wrote:
I think I see a second problem coming down the pike. the users can add pdfs
to the wrapper file through a typical open file or through drag and drop. I
get that the NSOpen... allows me to expand entitlements. But does
13 matches
Mail list logo
