Doesn't matter how you implement the view in your MVC. If you keep the concerns seperate (in MVC), you will get the benifits regardles of your implementation of the view part.
XML is a little more declarative, but otherwise doesn't matter. On Jan 13, 7:04 pm, Toby <[email protected]> wrote: > Ok, we've thought about MVC paradigms for our company, > but unless you really need to hide the code from some > "Designer" I can't see the benefits. > > I want the power of the computer language at hand to allow me > to create layouts dynamically. I've been scolded about > that by one most learned participant of this list. I don't see > why. I want to use the base language (here java) to > create layouts. Why on earth does Google go for what > I (Certainly Erroneously given the body of individuals > to which I am now speaking) perceive to be an obsolete > separation between Controller and View? > > Please enlighten me, you undisputed masters of this > newly found world of which I hope to convincingly call > myself a member in short. > > Thanks, > > Tobiah -- 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
