Re: Using Zip executable in Cocoa Application
Re: Using Zip executable in Cocoa Application
- Subject: Re: Using Zip executable in Cocoa Application
- From: Philip Dow <email@hidden>
- Date: Sun, 18 Dec 2005 22:41:31 +0100
Starting to get off topic, but to underscore why it may be important
for a document to be edited only via the creating application: smart
folders in a source list.
A user edits entries in a journal by way of a journaling application.
As the entries change, the application checks those changes against
smart folders that have already been setup. At launch, the
application does not rescan the content and metadata of every entry
to re-read them into the appropriate smart folders. Imagine doing
that for 50,000+ entries at every launch. Instead, the smart folders
are updated only as the user edits the data in the application
itself. If the user edits the data outside the application, the smart
folders will no longer be able to keep track of their content.
By the way, thanks for the info on actually calling zip from within
cocoa, or anything by way of nstask. It's very timely information for
me.
-Phil
On Dec 18, 2005, at 9:27 PM, Dan Saul wrote:
Well if the user wants to why stop them? Putting useless restrictions
only hampers the potential uses people could come up with.
On 18/12/05, Rick Langschultz <email@hidden> wrote:
Actually I don't want the user to know that there are XML files in
that directory. It is an open document format however it will not be
feasible for the user to edit the XML data. Also the contents will be
in zip format which may or may not be password protected. I do
believe iWork 2005 uses a form of the tar.gz file format to archive
an xml file format inside as well as images, and thumbnails.
I have a piece of software that uses Sleepycats DBXML for its
processing. There is a server, and a client which doesn't have to
connect to the server to provide database updates. These xml files
are cracked open and then distributed to a directory, indexed, and
then the user can query, select, etc. All in xml formatting. But the
zip file allows them to move around with the files and not stay on
one machine.
There will be a windows, linux, and apple version of this software so
zlib is going to be a better choice for the application.
Thank you all for the ideas and feedback...
Rick
On Dec 18, 2005, at 11:13 AM, Scott Ribe wrote:
The Applications folder is not
one of those places that you can assume that you can write to, and
it's not reasonable to expect the user to change access for you if
you can't write there.
I think by "Applications suite folder" he meant the folder he would
install
in /Applications, not /Applications itself. Whether or not that is
writable
to all users could be under the control of an installer.
Whether or not to use an Applications Support folder, depends on
whether or
not it is reasonable for the user to expect the data to follow the
application suite with a Finder copy.
--
Scott Ribe
email@hidden
http://www.killerbytes.com/
(303) 665-7007 voice
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40cox.net
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40gmail.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden