I think MVVM is more suitable for Android. That is widely use in WPF. On Sun, Jan 15, 2012 at 8:35 PM, sell.bergstr <sell.bergst...@googlemail.com > wrote:
> I dont think its worth speding too many thought on "MVC" at all. IMO, > that term in itself is not well defined at all, its just one more of > those terms that are fashionable in the software dev community for a > certain time frame. I remember when it was first coined - that was > back in the days of ObjectWorks Smalltalk (Smalltalk being an object- > oriented programming language), somwhere in the late 80ies or early > 90ies, but it meant something quite different (some detail of the > ObjectWorks UI library) from what people think of when hearing it > today. Later, it was applied to Java Servlet programming in a way that > made me shudder all over (think Struts). > > A better way is to simply follow the ideal of separation of concerns. > Every component of the system should know and do just one well-defined > thing. Strong cohesion, weak coupling. Never copy code, avoid > redundancies like hell. > > My2cts > chris > > -- > 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 > -- Regards, Michael Leung http://www.itblogs.info - My IT Blog http://diary.skynovel.info - My Blog http://www.michaelleung.info - My Homepage -- 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
