Ok, nice first answer. The question is not stupid, because an Activity mix life cycle and view, so implementing MVC is not so obvious. And to make simple, your activity manage lifeCycle and delegate GUI to your GUI package. In that package you do usual MVC. In fact you implement usual layers separation (Model, View, BuisnessService, Service (i mean android service), DAO (that contains usual DAO and your Content providers) and you also have the Communication layer and the transversal one), as usual in Java. You just need to manage your models' life cycle according to your activity life cycle. And it should work.
On Jan 13, 6:21 am, TreKing <treking...@gmail.com> wrote: > On Thu, Jan 12, 2012 at 10:46 PM, Sree <sreelathapavul...@gmail.com> wrote: > > I want some information about MVC Architecture > > http://www.justfuckinggoogleit.com/ > > ------------------------------------------------------------------------------------------------- > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > transit tracking app for Android-powered devices -- 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 options, visit this group at http://groups.google.com/group/android-developers?hl=en
