Re: [android-developers] Re: Handling process killed by system

2013-06-24 Thread Benoit Vermont
while the stack of activity and bundles are saved. (If it's said anywhere, I still havent found it). I will rewrite everything for persistance, but still think it would be best if the documentation explained a bit more... -- Benoit Vermont 2013/6/23 Piren > Seems to me your mist

[android-developers] Re: Handling process killed by system

2013-06-21 Thread Benoit Vermont
The problem with parcelable and serializable it that it creates new instance of the object for each Activity that is launched. It means that, every time you leave an Activity, to go back for instance, you will have to write the modified object, and check the onActivityResult each time, to updat

[android-developers] Handling process killed by system

2013-06-21 Thread Benoit Vermont
Hi, I've been reading intensively the Android Application Framework FAQ (http://developer.android.com/guide/faq/framework.html) and it says that the system can kill process if needed to free memory. Well, fair enough, only it also destroys singletons and static instances. So when we launch the

[android-developers] 9Patch Resizer Tool : it's time to get lazy !

2012-06-04 Thread Benoit Vermont
This is not related as hacking an android device or anything, but I'm pretty sure I created a tool that's gonna appeal to a few Android developpers : a drag and drop utility that takes xhdpi .png files as input, and automatically generates ldpi, mdpi, hdpi files. What's more, it resize 9 patch