Vikas wrote: > 2.) The bus framework looks really appealing, and design-wise it > actually decouples activity and background tasks and still gives a > callback functionality on to activity in a cleaner way. But as you > said, it is still going a major revamp so does not look completely > ready yet?
The API isn't frozen, it needs a ton more testing, I need to sit down and be absolutely sure I don't introduce long-term leaks, etc. There's a reason I describe it as a 0.1 edition... ;-) > Could you guys shed your opinion on this if the approach taken in the > above article makes sense or does it also suffer from any major > drawbacks.(I was thinking of just replacing their "DataFetcherThread" > class with Async Task). Mr. Burke is first-rate. The biggest difference in his approach versus mine is that I was concerned about covering the case where the thread wraps up its work in mid-transition, or other cases where important things happen between onDestroy() of the first activity and onCreate() of the second activity (e.g., incoming sensor data). That's why I wanted to allow event receivers to indicate that events should get queued up where needed, yet not assume a queuing approach across the board. On the flip side, it makes my implementation more complicated. :-( > "Phew!!!! only if google had taken some other approach instead of > automatically destroying activities. We just finished a succesful huge > project using blackberry apis and never had to worry on this type of > issue about orientation effects or phone call receive[Again I am > trying my level best to be positive with android framework here, > because I really want to like it.)].. Blackberry, AFAIK, doesn't allow background threads or much in the way of multitasking. You want that power, you gotta pay the price. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Need help for your Android OSS project? http://wiki.andmob.org/hado --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
