Ah, yes, that should work :) Cheers for your help. 2009/3/9 Thomas Broyer <[email protected]>: > > > > On 9 mar, 00:28, Darkflame <[email protected]> wrote: >> That seems like what I need thanks :) >> >> Dont suppose its possible to create an AbstractImagePrototype at run >> time? (say from an existing image or url) >> >> The widget I'm making needs to be updatable, and it would be handy if >> I could add to that List<AbstractImagePrototype> array. (rather then >> setting up a seperate array for runtime added images then using setURL >> with them). > > Nothing precludes making your own image-prototype "concrete" class > extending AbstractImagePrototype. > > Or if you don't want to implement the whole AbstractImagePrototype and > don't want to just "throw new NotImplementedException())", create an > interface with, say, an applyTo(Image):void method, a class > implementing this interface and deferring to an > AbstractImagePrototype's applyTo(Image):void, and another one just > calling Image::setUrl or Image::setUrlAndVisibleRect. > > >
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
