Dmitry, Ok, I see what you're trying to get at (across several threads and forums!), but let me suggest an alternative approach to trying to get another container class added to GWT. This seems to be meeting resistance - and rightly so, given the lightweight philosophy of GWT. Make the normal stuff easy - and the expert cases possible.
I'm assuming the code is pretty small for the class, so of course it's no big deal to just have it in your own code. The real issue is the private status of certain methods/members in the GWT UI class hierarchy. Perhaps a more fruitful approach would be to propose a set of methods/members that you feel should be made protected instead of private - I've been frustrated by this myself trying to override various specifics without having to rewrite large portions of a particular UI class. I think this would be much easier to make happen, would benefit a larger audience, and would enable people to extend their own widgets in whatever manner they feel is best. So is there a set of methods and/or members in the UI class hierarchy that, made protected, would allow you to accomplish your goals? jk --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
