IMO, this isn't feasible, because of what's probably the most common scenario for GWT projects:
* You want to create a great website (non-corporate), taking advantage of GWT, including its future improvements, and * you also have to support IE6. Most IE6 users have never encountered a website on the internet before, which doesn't work with their browser. All pages work - and if yours doesn't, it's very likely that they consider your site to be broken/very low quality. The percentage of IE6 users is still too high, so they can easily spoil your site's reputation. IOW, as developers, we have no choice. I hope, this will change soon - but trying to drive that change by restricting GWT to newer browsers would probably not lead us there (it would rather lead to a lower adoption of GWT). It would be a very different case, if Google Search wouldn't work with IE6 anymore... not that I recommend that Google (and Bing) should do that! Just my 2 cents Chris On Mar 18, 6:16 am, Nathan Wells <[email protected]> wrote: > Dropping IE6 support would be a really great way to fork the GWT > project. One would be focused on enterprise applications (w/ IE6 > support), while the other would be focused on the more traditional GWT- > ey things (like making things go really really fast). > > And when I say "really great way", I mean that in the sense that the > end of the world is described as "great" in the Bible. > > On Mar 17, 8:09 am, Rocky <[email protected]> wrote: > > > > > I think that users need to be pushed in this way in order to speed up > > upgrade process. > > > Also, I'm not saying that IE6 support should be retroactevly taken out > > from current GWT version. If you need to support IE6, you could still > > use excellent GWT 2.0. But you'll get no support for it. Since it's > > open-source project, you could still resolve problems with it, but you > > would be on your own. > > > I don't see what's annoying about asking developers (of the toolkit or > > of the applications based on toolkit) to stop supporting IE6. I'm sure > > that tookit's developers would love to stop bothering themselves with > > IE6's insufficiencies. I have looked at GWT's source code and there > > are A LOT of widgets where you have one implementation for IE6 and the > > other one for all the other browser. As time passes it would become > > more and more difficuilt to maintain all that different > > implementations. > > > On Mar 17, 2:48 pm, Pascal <[email protected]> wrote: > > > > I disagree completely. There are still a lot of people using IE6 in > > > the corporate world. One place where GWT really shines is to help > > > deliver rich in functionality, business-focused applications, given > > > the complexity management that java gives you.. Dropping support for > > > IE6 would be a major problem for a lot of developpers who use it to > > > target these users as telling them to upgrade from IE6 is at this > > > point still not an option. GIven the pressure is increasing on users > > > to upgrade, we'll get there but a lot of people still need this > > > support at this point and telling developpers to stop upgrading gwt > > > would be a real annoyance. > > > > Pascal > > > > On 17 mar, 08:23, Rade Martinoviæ <[email protected]> wrote: > > > > > The size of the population of IE6 users is the ONLY reason to keep IE6 > > > > support in GWT. > > > > If you're interested in IE6, you could always use old version of the > > > > toolkit. I'm saying that next major version of the toolkit, say GWT 3.0 > > > > should drop IE6 support completely. > > > > > Also, I'm saying since other Google teams are forcing its users to > > > > upgrade, > > > > maybe everyone should do it. > > > > -- > > > > ~~Rade~~ > > > > > 2010/3/17 Erron <[email protected]> > > > > > > -1 > > > > > > I'm sure I'm not the only one who still has clients that still use > > > > > IE6. The population of users still using IE6 is still too big to be > > > > > disregarded. > > > > > > On Mar 17, 7:45 am, Rocky <[email protected]> wrote: > > > > > > Since Google started advising its users to drop IE6, and will be > > > > > > dropping IE6 support from its applications such as GMail, when can > > > > > > we > > > > > > expect definite break with IE6 support in GWT? > > > > > > > What do you think about dropping IE6 support completely from GWT? It > > > > > > would make some big changes in code and many workarounds that are > > > > > > existent in current code would be gone, and code would be a lot > > > > > > cleaner? > > > > > > -- > > > > > 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]<google-web-toolkit%2Bunsubs > > > > > [email protected]> > > > > > . > > > > > 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 [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.
