It is much easier to maintain XML layouts. XML layout is less wordy than Java, too (amount of text in XML file versus amount of text in Java file accomplishing the same).
This is especially true if you have different layouts for one activity, depending on the phone's orientation, screen size, etc. You get a lot of help from the Resource Manager when you use XML (versus Java). But if you *have to* create layouts dynamically (e.g. layout-info comes from a server), you're left with using mostly Java code. On Jan 13, 10: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
