So... Is there any better way of blocking all these Composite methods other than kludgy myWidget @Override?
On Thu, May 21, 2009 at 6:23 PM, Ian Bambury <ianbamb...@gmail.com> wrote: > You are creating a composite widget which is going to be a UIObject so it > has UIObject methods. > But if you make a composite with three labels, then you probably don't want > (and it wouldn't be easy) to expose the setText method for all three. > Ian > > http://examples.roughian.com > > > 2009/5/21 alan m <alan.jame...@gmail.com> >> >> Hi, >> >> I see how Composite is useful in theory for custom widgets, to wrap >> rather than extend specific widgets & prevent exposing all their >> methods; but I have found that Composite itself has a LOT of methods >> exposed, particularly the UIObject position/dimension/etc setters >> which I had wanted hidden in the first place! It defeats the purpose >> of using it for me - to provide component/view developers with my >> widgets that have only my methods exposed (only mine - bwa-ha-ha-ha!). >> >> Am I missing something here? Is there any better way of blocking all >> these Composite methods other than kludgy myWidget @Override? >> >> Thanks, >> Alan >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
