Yes, thanks for your answer, I could of course patch the GWT jar but I would prefer to just use the API as is. I am not saying that it is not doable, just saying that with a little bit of cooperation from GWT team, the developers would not have to patch classes just to avoid too restricted visibility.
On Aug 26, 11:54 am, Thomas Broyer <[EMAIL PROTECTED]> wrote: > On Aug 26, 7:11 pm, danael <[EMAIL PROTECTED]> wrote: > > > > > "... just simply take the HorizontalSplitPanel.java original class > > file form svn and remake it to your needs ?" > > If I wanted to maintain my own API, I would not be using somebody > > else's, would I? I want to use standard GWT components and, at the > > same time, I want to be able to subclass them to add some extra > > functionality when I need it. As mentioned, previously, branching our > > own code for a component is not the way to go, it is the best way to > > run into cross browser bugs and maintenance issues along the way. > > How about just maintaining a patch to GWT? Whenever you want to update > GWT, apply your patch to the new JAR (or compile/package from source) > and see if your subclasses still compile and run as expected. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
