Knowledge Folders: Recently changed documents for Satya Komatineni

With all the recent talk about Android KitKat, I thought I was late to the party. So I went looking today. Still there is not much in it. I took the opportunity anyway to quickly summarize the API changes that are probably worth noting for an Android developer. Here is that search trace below. You will high level features by each of the sub JellyBean releases and I have also listed all the changed/new APIs in a single list for all of 4.x releases so far at the end.

Creating the AVD and running your first app on the AVD

More documents like this are at: Android Avds, Install, Emulator

5-Dec-13

Creating the AVD and running your first app on the AVD

How to run android applications on a device from the eclipse ADB

More documents like this are at: Android Avds, Install, Emulator

5-Dec-13

How to run android applications on a device from the eclipse ADB

Android virtual devices or AVDs

More documents like this are at: Android Avds, Install, Emulator

5-Dec-13

Android virtual devices

Understanding Asynctask along with Progress Dialogs

More documents like this are at: Fragments and Dialogs

30-Nov-13

This topic covers the nuances of AsyncTask and progress dialogs in android. This is based on notes taken for ProAndroid 3 and 4 books.

Burlesque is a gorgeous film

Condensed or otherwise, Some Fragment Sample code

More documents like this are at: Fragments and Dialogs

28-Nov-13

Condensed or otherwise, Some Fragment Sample code

What I learned

Notes on ADOs (Activity Dependent Objects) and how they bolster activity life cycle

More documents like this are at: Fragments and Dialogs

25-Nov-13

I am not entirely happy how objects, especially worker objects, that are dependent on an activity needs to behave and the framework that is available for them to detect the activity availability.

Yes #Android #Fragments are good. yes #AndroidFragments are helpful. May be fragments will solve all of it. Even with fragments I believe there is a case to be made for something called "Activity Dependent Objects" or ADOs in Android.

These are some notes from my thought process here. Mainly as a reminders to myself so that when it is time for me to aggregate them into a framework I would have remembered them.

As I have worked with this idea in the last few months, I think it is mildly helpful. For me it clarified the lifecycle of fragments and activities really well.

The early illustrations below are mainly my brain gibberish and they coalesce more as you scroll down. Also the key conclusions are towards the end. If "Activity Dependent Objects" intrigues you read on.

ADO: Activity Dependent Object implementation

More documents like this are at: Fragments and Dialogs

25-Nov-13

ADO: Activity Dependent Object implementation

How to use a progress bar from an asynctask

More documents like this are at: Fragments and Dialogs

16-Nov-13

How to use a progress bar from an asynctask

Test Cases you should run for an asynctask

More documents like this are at: Fragments and Dialogs

16-Nov-13

It is not trivial to create an asynctask and monitor its progress on an activity's progress dialog.

The techniques you need to implement well include fragment dialogs, retained fragments, non-cancellable dialogs, or retained objects, that also can clean themselves up as various asynchronous events take place in the system.

With out a proper set of test cases it is very easy to miss the expected behavior.

Here is a list of test cases that I can think of in my limited research on this item.

Config changes research 2

More documents like this are at: Fragments and Dialogs

13-Nov-13

Config changes research 2

Advice to my younger self

More documents like this are at: Humanities Current

11-Nov-13

What ever you do,
Do it Sincerely!

Do it with one mind.
With Focus,
And God Willing,
With Rapture!

Seek Help!
Care to Ask!
For Did you not cry,
When you were hungry?