Well, I don't disagree with you. I just found this discussion, where Sumit responds to these concerns (a few months ago, even). I suppose that starring the issue he mentions is probably your best course of action.
Nathan Wells On Tue, Dec 8, 2009 at 2:48 PM, lemaiol <lema...@gmail.com> wrote: > Hi Nathan, > > That is exactly the thing. GWT is much more than widgets and the > provided ones should be the building blocks to extend. That is the > message that comes from the team behind GWT. The problem I see is that > some widgets are not designed to be easily extended and therefore they > are not good building blocks. This leads to the integration of > heavyweight third-party widget libraries (even for simple things) or, > in the other hand, to the development of custom widgets to avoid this > overhead. I expected that, with the new versions, this situation would > change integrating most of the widgets of the incubator refined to fit > the widget "framework" over which to build the new widgets. > > Cheers, > Alberto > > On Dec 8, 2:18 pm, Nathan Wells <nwwe...@gmail.com> wrote: > > "Creating and maintaining custom widgets is discouraged" > > > > Really? I had the opposite impression. I understand why it might be > > discouraged, but from everything I've heard the GWTers tend to assume > > that they are only providing basic building blocks in the widgets > > package. I could be wrong (and I would like to be; maintaining custom > > widgets _is_ a pain), so if you have any references indicating > > otherwise, let me know! > > > > On Dec 7, 2:34 pm, lemaiol <lema...@gmail.com> wrote: > > > > > I have recently started having a look at the GWT 2.0 RC2 version and > > > found me once again frustrated trying to extend the SplitLayoutPanel. > > > In version 1.4 we needed to do the same with the splitter panels and > > > we thought that some of the reasons not to build more easy to extend > > > Splitter panels (had to copy over a lot of code) had to do with the > > > implementation substitution performed by the compiler. > > > In this case, I miss setting the splitter position programmatically > > > (or associated widget size) and setting the maximum splitter size > > > (minimum is already possible to be set) in the SplitLayoutPanel. With > > > the current implementation (a really simple one) the changes are not > > > complicated. The only problem is, that as the widget is implemented, > > > it is not possible to extend it properly. > > > > > Could somebody give some input on this? Why the SplitLayoutPanel is a > > > basic part of the new layout system but does not allow extension > > > easily? Creating and maintaining custom widgets is discouraged and a > > > pain but the actual widgets are sometimes not designed even for > > > trivial extension. > > > > > Feedback really appreciated, > > > Alberto > > -- > > 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-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > > -- 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-tool...@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.
