I'd do it the second way, for reasons Olivier pointed out. On Jun 17, 3:08 am, Olivier Monaco <[email protected]> wrote: > Hi, > > Depending on the "size" of object2, I will use a dedicated presenter > or not. Commonly, I like to have a dedicated one so I can easily reuse > it, extends it... and, more important, I have more encapsulation, > reducing the complexity of my code. > > Olivier > > On 16 juin, 17:20, Bilousme <[email protected]> wrote: > > > > > Hello all, > > > I need some help to check if my design I choose is correct. > > Imagine I have a data model like that : > > - An object1 containing a list of many object2 > > > Imagine now I want that my screen displays info of object1 and the > > list of object2 inside a tabpanel. When you click on a tab, you > > display the info of the selected object2. > > > What is the best way to implement that ? > > 1) only one couple of presenter/view for object1 and this couple > > manages the display of object2 in each tab > > 2) one presenter/view object for object1 and one presenter/view for > > each instance of object2 ? > > > in other words, do I have one couple of presenter/view by object > > model ?
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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/google-web-toolkit?hl=en.
