use handler.
--
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
I was wondering about this as well; I figured the Google team would
have incorporated a GWT EventBus into Android, as it works very well
in the GWT framework.
On Jul 5, 2:58 am, Nikolay Elenkov nikolay.elen...@gmail.com wrote:
On Tue, Jul 5, 2011 at 1:46 PM, doles sachin.d...@gmail.com wrote:
On Jul 4, 11:27 pm, Sachin Dole sachin.d...@gmail.com wrote:
I can see how the async task
mechanism can be used in lieu of the event/eventhandler mechanism, but thats
not apples to apples. make sense?
Android/JavaScript is also not an apples to apples comparison, but it
kind of sounds like you
Yes, I am familiar with that mechanism. However, that is not like the
event/eventhandler mechanism that is available in javascript/gwt. In the
asynctask mechanism, the asynctask#postExecute runs on the UI thread and the
asynctask needs to passed in a view if a specific view needs to be updated.
Yes, I am familiar with that mechanism. However, that is not like the
event/eventhandler mechanism that is available in javascript/gwt. In the
asynctask mechanism, the asynctask#postExecute runs on the UI thread and the
asynctask needs to passed in a view if a specific view needs to be updated.
It's so simple:
There r two best ways:
1. Create a class extending AsyncTask and overrides it's doBackgroud() and
and on postExecute() methods
and write your code of fetching data from server in doBackground() mtd
and onPostExecute() write ur code of db updation and start a new activity;
6 matches
Mail list logo
