As long as you update your patched code with the newer version every time you upgrade you GWT version, it should be no problem.
The main issue is that you cannot extend the DefaultCalendarView directly and the we need to use this kind of hack. On Aug 8, 3:53 pm, "[email protected]" <[email protected]> wrote: > On Aug 5, 9:43 am, ctasada <[email protected]> wrote: > > > I did it in my code without too much problems, but I agree with you > > that's quite annoying. > > > Steps: > > 1.- Create a new package in your code: > > com.google.gwt.user.datepicker.client > > > Copy the DefaultCalendarView.java from the GWT repository (I'm not > > sure which version I used, but was the one from 2.0) > > Are you sure that the behaviour of the GWT compiler is well-defined > for cases where you've selectively monkey-patched part of a GWT > package in local code, and are relying the source from gwt-user.jar > for the rest of the package? I guess it's working for the moment, but > is that kind of behavior expected to work in future versions of the > compiler? Any GWT compiler devs care to comment? -- 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.
