Hi everyone, Thanks both for the love and the frank constructive criticism. We can and should do a better job of communicating the roadmap and release timing to the broad GWT community. As Ian Petersen said, GWT contributors saw the 1.5 branch and (I think) had a pretty good sense for the progress on 1.5. However, it's easy to forget that the majority of GWT users are really just waiting for the release announcements rather than following svn check-ins.
Each release tries to balance adding important features and fixing bugs. Sometimes we tip the balance in favor of new features instead of fixing corner-case bugs because it is generally possible for people to understand and work around such bugs, whereas big features such as overlay types require tons of focus effort to spring into existence. Regarding layout bugs specifically, HTML isn't properly generalized, and it is hard to predict and account for the behavior of nesting any arbitrary widget in another. We focus testing effort on the UI use cases that seem most likely to actually occur in practice in real apps and much less time trying to ensure that every theoretical combination renders properly. That said, Joel Webber seems to be making progress on a new kind of dock panel that may actually really work sanely in every nesting case we know of. Keep your fingers crossed, and watch the incubator in the coming weeks. -- Bruce On Thu, Oct 9, 2008 at 10:19 AM, Ian Bambury <[EMAIL PROTECTED]> wrote: > I'd have to disagree: I don't think Google is any worse than the average, > but I don't think they are any better. > > I don't do anything very special or complicated with GWT so I wouldn't > expect to come across a great percentage of the bugs and problems there are > in there, but take the 1.5 *stable* release. > > * SplitPanels don't work in DisclosurePanels > > * SplitPanels don't work in StackPanels > > * getAttribute has been changed so it returns a zero-length string for a > missing custom attribute where every browser returns null in JavaScript. > This breaking change wasn't in the release notes and was added between the > last RC and the final release. > > * onHistoryChanged was removed in 1.5.1 without warning or > notification, then replaced in the final release but deprecated, even > though there is no direct replacement for the deprecated functionality. > > * RootPanel still caches requests and returns the old rootpanel under some > circumstances instead of what is actually in the DOM > > * setKeyCode still doesn't work in Firefox or Opero or Safari (maybe > Chrome, too, I haven't tried) and this was reported for version 1.1 in > September 2006. Currently it is accepted as a fault but not planned to be > fixed in any specific release > > I found these while writing a few sites which are basically doing not much > more than displaying text, so what else it there yet for me to find? > > My personal experience is that Google's *stable* releases are *not* of > a "much higher quality" than most other organisations but also that the RCs > aren't significantly worse than the stable ones. > > Ian > > http://examples.roughian.com > > > 2008/10/9 Arthur Kalmenson <[EMAIL PROTECTED]> > > >> > It isn't easy to plan ahead if you have a fixed schedule for your >> project. >> > There's no point in developing against a release candidate for the next >> > version of GWT if you have to go live in May next year and you don't >> even >> > know if the next stable version is coming out in the first or second >> half of >> > the year. >> >> This may be true for most organizations, but I don't think it applies >> to Google. As most of us know, Google's unstable beta releases are >> much higher quality then a lot of organizations' final releases that >> have been out there for several years. The real problem comes down to >> management accepting that argument. >> >> Regards, >> Arthur Kalmenson >> >> On Oct 8, 1:18 pm, "Ian Bambury" <[EMAIL PROTECTED]> wrote: >> > It isn't easy to plan ahead if you have a fixed schedule for your >> project. >> > There's no point in developing against a release candidate for the next >> > version of GWT if you have to go live in May next year and you don't >> even >> > know if the next stable version is coming out in the first or second >> half of >> > the year. >> > >> > Ian >> > >> > http://examples.roughian.com >> > >> > 2008/10/8 Ian Petersen [EMAIL PROTECTED] >> > >> > >> > >> > > I guess I was just taking issue with the claim that >> > > Google makes it impossible to plan ahead. >> >> >> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
