On Jun 20, 2008, at 4:43 PM, Grant Limberg wrote:
Is there a way to create a new bundle from in Cocoa?
What I'd like to do is have a bundle in my app's Application Support
folder to store some data generated by the user in my app.
Since it's just data, I think you want a package rather
This might help:
http://www.cimgf.com/2008/05/13/from-hacker-to-microisv-custom-file-formats/
In essence you create a folder and set attributes on it as you
suspected. Though these are referred to as packages instead of
bundles. Take a look at NSFileManager. You can create a directory that
Initially I was storing the data in Core Data. In my app, the user
has the ability to attach an image to a record in Core Data.
Unfortunately, changing from a JPEG to NSData inflates a 1.5MB JPEG to
over 20 MB. In talking with some folks at the local Cocoaheads
meeting on wednesday, one
On Jun 20, 2008, at 3:28 PM, Grant Limberg wrote:
Initially I was storing the data in Core Data. In my app, the user
has the ability to attach an image to a record in Core Data.
Unfortunately, changing from a JPEG to NSData inflates a 1.5MB JPEG
to over 20 MB. In talking with some folks
On 2008 Jun, 20, at 15:28, Grant Limberg wrote:
Initially I was storing the data in Core Data. In my app, the user
has the ability to attach an image to a record in Core Data.
Unfortunately, changing from a JPEG to NSData inflates a 1.5MB JPEG
to over 20 MB.
I was planning on doing
As far as I know, you can't store a raw jpeg in Core Data directly
without turning it into an NSData object first which in turn
decompresses it.
Someone correct me if I'm wrong!
Grant Limberg
[EMAIL PROTECTED]
LinkedIn: http://www.linkedin.com/in/grantlimberg
http://www.glsoftware.net
On
On Jun 20, 2008, at 3:43 PM, Grant Limberg wrote:
As far as I know, you can't store a raw jpeg in Core Data directly
without turning it into an NSData object first which in turn
decompresses it.
It sounds quite possible that Core Data only support images in the
form of NSData. That
Currently, the user drags an existing image from their filesystem to
an NSImageView bound to an NSData attribute in the sqlite data store.
This causes the decompression from 1.5MB to 20MB. As you can see,
this isn't exactly efficient. Hence the question on package/bundle
creation. I'm
On Jun 20, 2008, at 4:00 PM, Grant Limberg wrote:
Currently, the user drags an existing image from their filesystem to
an NSImageView bound to an NSData attribute in the sqlite data
store. This causes the decompression from 1.5MB to 20MB. As you
can see, this isn't exactly efficient.
On 20 Jun '08, at 4:00 PM, Grant Limberg wrote:
Currently, the user drags an existing image from their filesystem to
an NSImageView bound to an NSData attribute in the sqlite data
store. This causes the decompression from 1.5MB to 20MB.
That's an issue with NSImageView — when an image is
10 matches
Mail list logo
