On Thu, Nov 4, 2010 at 7:12 PM, Streets Of Boston <flyingdutc...@gmail.com> wrote: > When i wrote my image editor, i put the 'gallery/pick-list of images' > activity (and other activities) into one process and the actual > 'editor' activity in another. I needed to squeeze every bit of memory > out of a process to make have a chance at having enough memory when > editing full-sized images. > > It did work for me :-).
Ah, now that's one scenario where multiple processes can benefit the developer: more heap space. I had not considered that, and it's a good point. My hope is that relatively few apps will need to do that -- image manipulation certainly is a likely category. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android 2.2 Programming Books: http://commonsware.com/books -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
