Olivier, The way I'd do it if I were you (and the way I've done many custom controls) is use create your class and have it extend Composite. In your class, you would have your ScrollPanel and VerticalPanel. Then, expose whatever add, remove, iterator methods you want and have them relay to your VerticalPanel, bypassing your ScrollPanel.
HTH, Chad On Mar 31, 1:55 pm, Vhann3000 <[email protected]> wrote: > On 31 mar, 14:30, Ben Imp <[email protected]> wrote:> Correct. You weren't > abusing the iterator itself, you were abusing > > the iterator method, which other things used. > > > You can still extend ScrollPanel, but just add your own bit of > > interface on top of it. Like this bit of pseudocode. > > Ok, thanks for the help. > > > This is all a very view-centric way of doing it, however. I might > > suggest reading up on the MVP pattern, which would help abstract away > > the details of the panels entirely. > > I see. Thanks again, off to reading on MVP I guess. > > Regards, > Olivier -- 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.
