解决方案的人需要IE7 / IE8支持在未来的GWT版本 [英] Solutions for people needing IE7/IE8 support in future GWT releases

问题描述

谷歌在5月宣布，他们将删除GWT 2.6（今年12月）的IE6 / IE7支持，并删除GWT 3.0中的IE8支持。

这个选择的原因，我支持它，我不在这里争论。努力保持最新的人不希望有一个缓慢的GWT，因为没有人。

我们选择GWT技术的主要原因是它为我们处理浏览器的问题。我正在工作的公司需要有我们的应用程序运行在IE下降到IE7。我们不得不努力，让他们放弃IE6。最近几个月，员工刚刚将浏览器迁移到IE8。

恐怕我们会永远停留在2.5.1。

IE迁移是一个广泛的主题，但狭窄的答案（是/否）对我来说是足够好的！我可能不会理解有关GWT内部机制的细节。

第一个问题： ？含义窗口小部件不适用于这些浏览器，或者我应该说'停止'，这意味着旧的小部件仍然可以工作，但修补，新的功能将无法处理旧版本的IE？

第二&第三个问题：

• 您是否听说过某些社区/组愿意编写支持IE6 / 7 / 8或者由于2.6版本中的GWT基本层发生变化而不可能这样做？

如果这是不可能的：第四个问题。

解决方案如果您不得不开始一个应用程序运行在IE7 / div>

1. 我们最终决定在2.6中禁用 ie6 排列，并且只在3.0中删除它。这意味着你可以重新启用支持IE，IE6和IE7的GWT 2.6中的怪异模式。在GWT 3.0中，支持将被删除，即支持 ie6 排列的类将被删除，我们将开始做那些在那些浏览器中不能工作的东西




2. 从3.0开始，支持那些古老的浏览器变得越来越困难，因为没有什么可以做容易（没有什么可以使它变硬，这只是我们不再在乎他们）。为了保持简单，我会说在GWT 3.0中支持IE6 / 7是不可能的，因为基本的支持（DOM级别）将被删除，其他的东西被重构（如果 ie6 permutation是唯一一个具有特定实现的实例，很可能会删除实现插入的 hook ，以使代码更简单，更易于阅读和维护） 。
   
   我不知道我们将如何处理IE8的情况;可能与IE6 / 7相同：默认情况下在3.0中禁用，然后在下一个版本中完全删除。




3. 否。




4. 我会使用2.6然后（然后开始寻找另一份工作;-)）

Google announced in May that they would remove IE6/IE7 support in GWT 2.6 (coming December this year) and remove IE8 support in GWT 3.0.

I understand the reasons of this choice, I support it, and I'm not here to argue about it. People that make the effort to stay up-to-date don't want to have a slow GWT because of people who don't.

The main reason we chose GWT technology is because it handles browser quirks for us. The company I'm working at need to have our app running on IE down to IE7. We had to fight hard to have them drop IE6. Last months, employees just migrated their browsers to IE8.

I'm afraid we'll be stuck with the 2.5.1 forever.

IE migration is a broad topic but narrow answers (yes/no) are good enough for me! I probably won't understand details about the inner mechanisms of GWT anyway.

First question: is the word 'remove' appropriate ? Meaning widget won't work with those browsers, or should I say 'stop', meaning that old widgets will still work but patched and new functionalities won't cope with older versions of IE ?

Second & third question:

• did you heard about some communities/groups willing to write widget libraries that support IE6/7/8 or will it be impossible to do so due to changes in GWT basic layers coming in the 2.6 release ?
• did you heard about communities/groups that are ready to patch the 2.5.1 and keep it alive for another few years ?

If this is not possible: fourth question. If you had to start a new application that should run on IE7/8 would you use GWT 2.5.1 ?

解决方案

1. We finally decided to disable the ie6 permutation in 2.6 by default, and only remove it in 3.0. That means you'll be able to re-enable support for quirks mode in IE, IE6 and IE7 in GWT 2.6. In GWT 3.0, support will be removed though, i.e. classes that support the ie6 permutation will be deleted, and we'll start doing things that won't work in those browsers with no hook to workaround them.

2. Starting with 3.0, it'll become harder and harder to keep supporting those antique browsers, because nothing will be made to make it easy (nothing will be made to make it hard either, it's just that "we'll no longer care about them"). To keep things simple, I'd say it'll be impossible to support IE6/7 in GWT 3.0, because basic support (DOM-level) will have been removed and other things refactored (if the ie6 permutation was the only one with a specific implementation, it's likely that the hook where that implementation is plugged in will be removed, to make the code simpler and easier to read and maintain).
   I don't know yet how we'll handle the IE8 case; probably the same as IE6/7: disable by default in 3.0 then remove completely in the next release.

3. No.

4. I'd use 2.6 then (then start looking for another job ;-) )

这篇关于解决方案的人需要IE7 / IE8支持在未来的GWT版本的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！