I’d recommend cramfs as it is a real filesystem that is optimised to be
expanded in-memory.
On Apr 9, 2014, at 14:42, Charles Srstka wrote:
> On Apr 9, 2014, at 12:32 AM, John Joyce
> wrote:
>
>> Sure. Core Data would work just as well as binary blobs.
>> Base64 would work in plists / xml /
On Apr 9, 2014, at 2:20 AM, Maxthon Chan wrote:
> I’d recommend cramfs as it is a real filesystem that is optimised to be
> expanded in-memory.
Not complicated enough. I'd recommend encrypting the whole thing with an
AES-256 key which is encrypted using elliptical-curve cryptography, and stuff
LOL
I actually used cramfs once in a game carried the rules database. The rules are
so complicated so I tried to make it smaller without sacrificing the efficiency
of the game code. Ended up using cramfs for that.
On Apr 9, 2014, at 15:49, Charles Srstka wrote:
> On Apr 9, 2014, at 2:20 AM, M
On 09 Apr 2014, at 07:22, dangerwillrobinsondan...@gmail.com wrote:
> Base64 encode images into one file. It could even be an SQLite db file.
I’d recommend against base64-encoding possibly large binary data like image
files. base64 makes it balloon in size. It’s fine for storing small binary bi
cramps features decompression in-memory in place and to avoid copying data you
can put uncompressed TIFF in it. cramfs decompresses into NSData objects
in-place and can be taken up directly by NSImage/UIImage/CGImage/CIImage
object. cramfs variant that is based on zlib makes that image a equival
Hi,
in trying to find the source of a memory leak I think to have in my project, I
ended up creating a plain SpriteKit project from template and did the following:
- (IBAction)test:(id)sender
{
if (self.skView.scene.children.count>0){
[self.skView.scene removeAllChildren];
} else
On Apr 8, 2014, at 10:07 PM, Rick Mann wrote:
> Well, if I were to do this, one of the reasons would be to create a text
> representation that could be easily diffed. I took a look at Core Data's XML
> format, and while necessarily verbose, it would work pretty well, until the
> schema change
On Apr 8, 2014, at 10:32 PM, John Joyce
wrote:
> Base64 would work in plists / xml / keyed archives / yaml / json whatever.
> Serializing a dictionary or custom object would make it really simple and
> easy to manage.
> As a text file, you could compress the heck out of it if needed to reduce
On Apr 9, 2014, at 3:45 AM, Alexander Reichstadt wrote:
> This code is bound to a menu item method test. When looking at memory in
> Xcode I would expect for it before adding any children to be identical to
> after removing all children. But memory steadily increases.
Try using Instruments, s
On Mon, 7 Apr 2014 07:01:19 -0700, Jerry Krinock said:
>Cocoa Bindings are useful to magically keep visible user interface
>elements in sync with data, although the magic comes with some pain,
>sometimes quite considerable. But menus only appear when the user
>clicks on them and disappear when th
On 9 Apr 2014, at 9:58 AM, Jens Alfke wrote:
> Frankly, I don’t even know what that memory-usage graph in Xcode’s debugger
> pane is showing. I’ve found that “memory usage” is a slippery concept in a
> modern OS, and unless you know exactly what you’re looking at, it’s easy to
> draw the wrong
Say I have an array of Person object with a name property. Is there a
difference between :
namesArray = [personsArray valueForKeyPath:@"@unionOfObjects.name"];
and
namesArray = [personsArray valueForKeyPath:@"name"];
On a small test I can just see that the concrete NSArray class returned are
On Apr 9, 2014, at 07:49 , Jens Alfke wrote:
> You can always write some code to export the database to XML for such
> purposes.
> But for regular storage, SQLite, or even a binary-format flat file, is going
> to be a lot more efficient than XML. (Assuming you have a large data set.)
Oh, I ab
I have a dialog which has an NSBox. Inside the NSBox are two
(separate, but conceptually linked) sets of radio buttons. These are
just NSButtons with radio style---I haven't (at least intentionally)
embedded them into an NSMatrix. However, when I select one of
the buttons from one set, it reset
On Apr 8, 2014, at 4:20 PM, Jens Alfke wrote:
>
> I’m not a big fan of Core Data, but if you’ve worked with it before I suspect
> you’ll find it more efficient to use it for this than to roll your own.
Even if you haven't worked with it before, it'll still probably wind up being
more efficient
On 10 Apr 2014, at 7:06 am, Tom Doan wrote:
> have a dialog which has an NSBox. Inside the NSBox are two
> (separate, but conceptually linked) sets of radio buttons. These are
> just NSButtons with radio style---I haven't (at least intentionally)
> embedded them into an NSMatrix. However, wh
Hi all,
Does anyone have a handy guide or pointer to the relevant docs which show all
the various meanings of highlight, state, appearance and button type. There are
so many combinations, and the class reference doesn't really explain it very
well (or at all). Some buttons appear to care about
(Sent from the road)
> On Apr 9, 2014, at 10:17 PM, Graham Cox wrote:
>
> Hi all,
>
> Does anyone have a handy guide or pointer to the relevant docs which show all
> the various meanings of highlight, state, appearance and button type. There
> are so many combinations, and the class referenc
Thanks Kyle - looks just the job.
--Graham
On 10 Apr 2014, at 3:57 pm, Kyle Sluder wrote:
>
> (Sent from the road)
>
>> On Apr 9, 2014, at 10:17 PM, Graham Cox wrote:
>>
>> Hi all,
>>
>> Does anyone have a handy guide or pointer to the relevant docs which show
>> all the various meanings
19 matches
Mail list logo
