It's a difficult juggling act, balancing the need to have interfaces fir everything and the practical value in actually doing it. I recall rwading/listening to something Josh Bloch said about why there are not any read only collection interfaces Vs the way it was done and what we have today. Why do I bring this up - mainly because there are similarities in both cases. It's not always a good thing to have interfaces describing all contracts for a panel, just like perhaps it didn't make sense to have UnreadableList etc...
Unfortunately writing code is about these sorts of nuances - I like to think of them like the annoying mozzies one gets in the summer. Summer, the beach etc are all great ( like gwt) but sometimes there's a mozzie buzzing around. On 10/08/2009, at 12:14 AM, Ed <[email protected]> wrote: > > Hi Miroslav > Thanks for the feedback. > You make a good point there about the increase in the amount of > javascript due to the interface.. > I wasn't aware of that and would love to hear about this. > > It makes you wonder what is "better". I mean: using these interfaces > also safes code as I can re-use code that works agains different > implementations, I think it's better progamming, overcomes code > duplication and reduces bugs... But at the other end the amount of > code increases... > > > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
