Re: Build Settings for Release: App/Library is bloated

You're welcome. It seems to me that storing your dictionary in a trie is a good idea anyway. Tries are compact and very fast for many kinds of string matching queries. Incidentally, here's an excellent implementation of tries, by the great OMNI folks: OFTrie - Implementation of the popula

Re: Build Settings for Release: App/Library is bloated

Thanks Wagner. I'm actually just needing to verify if a word is in the dictionary, but maybe this is still a good choice? If I don't need to search for shared prefixes would I be better off using sqlite so i don't have to load it all into memory? On Sun, Apr 12, 2009 at 2:34 PM, WT wrote: > I

Re: Build Settings for Release: App/Library is bloated

I you're trying to search for shared prefixes, you might want to store your data in a data structure better suited for such tasks, such as a Trie . Tries are fast and compact. Implementing a Trie isn't very difficult and, since it's such a commonly used da

Re: Build Settings for Release: App/Library is bloated

And BTW, my app is back down to 3.4MB after removing those classes and adding the dictionary in as a text file! That issue is now solved -- now I just need to figure out how to go about this approach :) awesome, thanks. On Sun, Apr 12, 2009 at 2:19 PM, Miles wrote: > > OK, it's gradually makin

Re: Build Settings for Release: App/Library is bloated

OK, it's gradually making sense, but i still have some questions. I started trying to do something like this a while back -- storing it all in one file, then loading it, but I think after that is where I went wrong. I created an array out of the contents and used it searched it way. I then decided

Re: Build Settings for Release: App/Library is bloated

On Sun, Apr 12, 2009 at 1:19 PM, Miles wrote: > In the meantime if you have a good link handy about how to do this I would > appreciate it. If you put something in the Resources directory of the app bundle, you can use NSBundle's -pathForResource:ofType: and related methods to get their paths. S

Re: Build Settings for Release: App/Library is bloated

Thanks a lot, guys. I wasn't aware of this option, but I am going to look into it right now. In the meantime if you have a good link handy about how to do this I would appreciate it. Thanks again, and if there are any other suggestions I'm welcoming those as well. On Sun, Apr 12, 2009 at 1:1

Re: Build Settings for Release: App/Library is bloated

On Sun, Apr 12, 2009 at 12:11 PM, Miles wrote: > I'm having similar issues in the application itself, but I'm currently > working on the static library so those are the numbers I have handy. Does > that add up? Is there something else I'm missing? 12MB seems pretty > ridiculous for this. In addit

Re: Build Settings for Release: App/Library is bloated

Thanks for the response. Under my release configuration where I'm currently building it just shows 'Standard (iPhone OS: armv6)' under 'Architectures', and 'Build Active Architecture Only' is checked. On Sun, Apr 12, 2009 at 1:08 PM, Dave Keck wrote: > You might be compiling for four archite

Re: Build Settings for Release: App/Library is bloated

You might be compiling for four architectures - PPC 32/64, Intel 32/64. Compiling for each of these can of course greatly increase your app's size, since you're essentially combining four versions of your app into one binary file. Check your release target to see what architectures it's compiling f

Re: Build Settings for Release: App/Library is bloated

Yes, the size is in the executable which is about 8MB. It doesn't feel like this app should be that big considering the size of the files, but again I don't really know what all goes into making an app grow like this during compile. Any thoughts? On Sun, Apr 12, 2009 at 12:42 PM, I. Savant wrote

Re: Build Settings for Release: App/Library is bloated

On Apr 12, 2009, at 3:11 PM, Miles wrote: My .app file and library file have both quickly grown to be 13MB in disk size and I'm having a hard time figuring out why. The .app bundle usually contains more than just your code. Have you examined it to see where the size is? Is it the executa

Build Settings for Release: App/Library is bloated

My .app file and library file have both quickly grown to be 13MB in disk size and I'm having a hard time figuring out why. I've been reading about build settings and anything else I can get my hands on but I can't seem to make significant improvements. I don't know a ton about what happens in the c