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? Rob On Dec 16, 2010, at 9:10 PM, Casper Bang wrote: > > Can we thus infer, that you are not convinced by Java's deeply rooted > philosophy of "write once, run anywhere" ...for UI-kits anyway? > > > On Dec 16, 5:38 pm, "Joe Nuxoll (Java Posse)" <[email protected]> > wrote: >> On Dec 13, 7:25 pm, Karsten Silz <[email protected]> wrote: >> >>> On Dec 14, 3:44 am, Cédric Beust ♔ <[email protected]> wrote: >> >>>> The bottom line remains that you need to write two different versions of >>>> your code for the iPhone and the iPad. >> >>> Agreed. I think it's because its a different device, you think it's >>> because iOS fragmentation. I rest my case. :-) >> >> I rest my case with Karsten's case. The good news is that you get to >> use all the same code for the underlying data structures. Only the UI >> code is different for each - because a good user experience means >> thinking differently about the interface for each device. Ideally, the >> two versions should "feel" similar, but when you look closely they'll >> be quite different. -- 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.
