On Fri, Dec 17, 2010 at 6:34 AM, Rob Ross <[email protected]> wrote:
> To me this just looks like MVC in the large. You have one data model, but > multiple views for different purposes. I'm not sure why you would call that > "fragmentation". > > If I have some model data and I display it in one widget as a pie chart, > and another as a line graph, have I fragmented my application code? > The point I was originally trying to make was that it was cool that Android was attempting to handle much of the phone/tablet form factor differences automatically, for example in the common master-detail case. Combined with the already existing automatic UI resource selection, that could be extremely useful. For example, not only could the master-detail be displayed in two columns if on a tablet, but the way the detail is displayed could be defined in two different XML files and automatically chosen depending on whether the app is running on a phone or a tablet. That gets rid of tedious if/else, at least for simple cases. In the long run, having fragmentation built-in as a fundamental assumption from the beginning might turn out to be an advantage. Moandji -- You received this message because you are subscribed to the Google Groups "The Java Posse" 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/javaposse?hl=en.
