On Mon, Dec 1, 2008 at 11:02 PM, Michael Ash <[EMAIL PROTECTED]> wrote:
> On Mon, Dec 1, 2008 at 11:04 PM, Stephen J. Butler
> <[EMAIL PROTECTED]> wrote:
>> Really, don't encode it in your binary. Especially bad idea on an
>> embedded platform like the iPhone because they you're carrying around
>>
On Mon, Dec 1, 2008 at 11:04 PM, Stephen J. Butler
<[EMAIL PROTECTED]> wrote:
> Really, don't encode it in your binary. Especially bad idea on an
> embedded platform like the iPhone because they you're carrying around
> the image data in memory whether you're currently using the image or
> not. It'
On Mon, Dec 1, 2008 at 9:46 PM, Dave DeLong <[EMAIL PROTECTED]> wrote:
> I've got some NSData objects that I'd like to hard code into a file (they're
> encoded images for some example factory methods). The reason I need to hard
> code them is that I need to be able to reconstruct these images on b
On Dec 1, 2008, at 10:46 PM, Dave DeLong wrote:
I've got some NSData objects that I'd like to hard code into a file
(they're encoded images for some example factory methods). The
reason I need to hard code them is that I need to be able to
reconstruct these images on both the Mac and the i
Hey everyone,
I've got some NSData objects that I'd like to hard code into a file
(they're encoded images for some example factory methods). The reason
I need to hard code them is that I need to be able to reconstruct
these images on both the Mac and the iPhone, and I thought that
gettin
