Like in Java Swing applications, in Android apps everything is happening, when the system creates a thread of execution for the application, named genuinely “main thread”. Also, this thread is very important, because it’s in charge of dispatching events to the appropriate user interface widgets (like clicks and touches), including drawing events (exactly what we are looking for). It is also a thread in which your application interacts with components from the Android UI toolkit. When your application performing some intensive work, this single thread can yield poor performance (and be sure, it will happen), if you’re not properly handling such tasks. From the user’s perspective, the application appears to hang. Even worse, if the UI thread is blocked for more than a few seconds (about 5 seconds currently) a user is presented with the infamous “application not responding” (ANR) message dialog. So sad…
Custom Android View: the definition
The first question, that is rotating in my head is: why I should implement my own custom View and just not to use one of the standard View’s? Actually, there is not a problem. Most of the Android applications using standard View’s, LayoutGroup’s, only customizing its color schemes, Layout and another general based stuff, applied to every day Android development. So, how I can explain my or maybe your interest on customization? I’m very meticulous in choices, laboriously deciding what to do, what not and what to choose from. Here is my short opinion on these question:
Switching to Android
Recently I decided to switch on to another way, a way of new and very exciting capabilities → the Android world.
Really?! How so?? Are you a donkey??
I just realized for myself some of issues what do not let me sleep the last two weeks. I thought about future of Computer World and Computer Science. How that would be? From where it comes from? And with exactly, what technologies and what way it could be?
