SproutCore supported IE6/7 in the past and it will support IE7 again very soon. It only broke temporarily as I added some major new features earlier this year, such as incremental rendering, and I have not had the time yet to finish bringing IE7 back into line. Going forward I do not expect to go so long with IE7 non functional.
IE6 is something I am considering leaving behind because the browser is both (a) lacking in too many features and (b) too slow to be very useful for building full client-side apps. I could be convinced otherwise though, especially if people were motivated to pitch in.
On Jun 17, 2008, at 10:32 AM, vemon...@gmail.com wrote:
> > I know we all want it dead, but any plans on IE6 Support?
I second that motion - I would love to see the end of IE6 support,
especially in the corporate world who still distribute this version
among end users.
But since that is not happening anytime soon, what sort of help do you
require Peter
to keep IE6 support alive?
On Jun 17, 3:16 pm, Peter Bergström <pberg...@apple.com> wrote:
> IE6 is something I am considering leaving behind because the browser
> is both (a) lacking in too many features and (b) too slow to be very
> useful for building full client-side apps. I could be convinced
> otherwise though, especially if people were motivated to pitch in.
I loathe IE6. However, realistically, if you want to make *any*
inroads into enterprise or corporate sites, IE6 is still needed.
On the plus side, IE6 is loads better than IE5.5. *shudder*.
True. Well SproutCore did support IE6/7 until a few months ago. IE7 is nearly done. IE6 will be right behind... :-)
Actually, most of the JS will just work for IE6 today. It is the SproutCore theme (the purple buttons and controls, etc. -- which are optional) that needs the most work for IE6.
-Charles
On Jun 17, 2008, at 11:49 PM, Christian Höltje wrote:
> On Jun 17, 3:16 pm, Peter Bergström <pberg...@apple.com> wrote: >> IE6 is something I am considering leaving behind because the browser >> is both (a) lacking in too many features and (b) too slow to be very >> useful for building full client-side apps. I could be convinced >> otherwise though, especially if people were motivated to pitch in.
> I loathe IE6. However, realistically, if you want to make *any* > inroads into enterprise or corporate sites, IE6 is still needed.
> On the plus side, IE6 is loads better than IE5.5. *shudder*.
> True. Well SproutCore did support IE6/7 until a few months ago. IE7
> is nearly done. IE6 will be right behind... :-)
> Actually, most of the JS will just work for IE6 today. It is the
> SproutCore theme (the purple buttons and controls, etc. -- which are
> optional) that needs the most work for IE6.
> -Charles
> On Jun 17, 2008, at 11:49 PM, Christian Höltje wrote:
> > On Jun 17, 3:16 pm, Peter Bergström <pberg...@apple.com> wrote:
> >> IE6 is something I am considering leaving behind because the browser
> >> is both (a) lacking in too many features and (b) too slow to be very
> >> useful for building full client-side apps. I could be convinced
> >> otherwise though, especially if people were motivated to pitch in.
> > I loathe IE6. However, realistically, if you want to make *any*
> > inroads into enterprise or corporate sites, IE6 is still needed.
> > On the plus side, IE6 is loads better than IE5.5. *shudder*.
> I loathe IE6. However, realistically, if you want to make *any* > inroads into enterprise or corporate sites, IE6 is still needed.
If people keep breaking their backs over making stuff work in IE6, then what incentive do corporate and enterprise groups have to move away from IE6?
If your app is great and users (not IT guys) want it, then maybe they'll switch to a better browser. Perhaps there is something to the "if you build it, they will come" mantra.
Just my ideological two cents...
On Jun 18, 2008, at 10:21 AM, Levi McCallum wrote:
> On Jun 18, 1:36 am, Charles Jolley <char...@sproutit.com> wrote: >> True. Well SproutCore did support IE6/7 until a few months ago. IE7 >> is nearly done. IE6 will be right behind... :-)
>> Actually, most of the JS will just work for IE6 today. It is the >> SproutCore theme (the purple buttons and controls, etc. -- which are >> optional) that needs the most work for IE6.
>> -Charles
>> On Jun 17, 2008, at 11:49 PM, Christian Höltje wrote:
>>> On Jun 17, 3:16 pm, Peter Bergström <pberg...@apple.com> wrote: >>>> IE6 is something I am considering leaving behind because the >>>> browser >>>> is both (a) lacking in too many features and (b) too slow to be >>>> very >>>> useful for building full client-side apps. I could be convinced >>>> otherwise though, especially if people were motivated to pitch in.
>>> I loathe IE6. However, realistically, if you want to make *any* >>> inroads into enterprise or corporate sites, IE6 is still needed.
>>> On the plus side, IE6 is loads better than IE5.5. *shudder*.
On Jun 18, 2008, at 7:59 AM, Andrew Sardone wrote:
> If people keep breaking their backs over making stuff work in IE6, > then what incentive do corporate and enterprise groups have to move > away from IE6?
Agreed. IE6 also has significant security issues that you'd think enterprise IT managers would want to avoid.
On Jun 18, 10:59 am, Andrew Sardone <andrew.sard...@gmail.com> wrote:
> > I loathe IE6. However, realistically, if you want to make *any*
> > inroads into enterprise or corporate sites, IE6 is still needed.
> If people keep breaking their backs over making stuff work in IE6,
> then what incentive do corporate and enterprise groups have to move
> away from IE6?
> If your app is great and users (not IT guys) want it, then maybe
> they'll switch to a better browser. Perhaps there is something to the
> "if you build it, they will come" mantra.
> Just my ideological two cents...
The problem is that it won't convince management in these huge IT
shops to switch. With the current dissatisfaction with the latest
Microsoft products combined with the natural reluctance to change
something that works, enterprises aren't likely to upgrade soon.
> On Jun 18, 10:59 am, Andrew Sardone <andrew.sard...@gmail.com> wrote: >>> I loathe IE6. However, realistically, if you want to make *any* >>> inroads into enterprise or corporate sites, IE6 is still needed.
>> If people keep breaking their backs over making stuff work in IE6, >> then what incentive do corporate and enterprise groups have to move >> away from IE6?
>> If your app is great and users (not IT guys) want it, then maybe >> they'll switch to a better browser. Perhaps there is something to the >> "if you build it, they will come" mantra.
>> Just my ideological two cents...
> The problem is that it won't convince management in these huge IT > shops to switch. With the current dissatisfaction with the latest > Microsoft products combined with the natural reluctance to change > something that works, enterprises aren't likely to upgrade soon.
The problem in my opinion is that IT folks are amazingly risk averse. They'd rather keep IE6 which works with their corporate apps and breaks half the websites out there, than upgrade to IE7/8 and break the corporate apps...and possibly 2000 desktops in the process. :-)
Our web-based products will continue to be supported on IE6 because our corporate customers require it. Heck, we only discontinued IE5.5 support a year ago.
>> I loathe IE6. However, realistically, if you want to make *any* >> inroads into enterprise or corporate sites, IE6 is still needed.
> If people keep breaking their backs over making stuff work in IE6, > then what incentive do corporate and enterprise groups have to move > away from IE6?
> If your app is great and users (not IT guys) want it, then maybe > they'll switch to a better browser. Perhaps there is something to the > "if you build it, they will come" mantra.
> Just my ideological two cents...
> On Jun 18, 2008, at 10:21 AM, Levi McCallum wrote:
>> Wow, this good news to my ears.
>> Thanks, Charles.
>> On Jun 18, 1:36 am, Charles Jolley <char...@sproutit.com> wrote: >>> True. Well SproutCore did support IE6/7 until a few months ago. IE7 >>> is nearly done. IE6 will be right behind... :-)
>>> Actually, most of the JS will just work for IE6 today. It is the >>> SproutCore theme (the purple buttons and controls, etc. -- which are >>> optional) that needs the most work for IE6.
>>> -Charles
>>> On Jun 17, 2008, at 11:49 PM, Christian Höltje wrote:
>>>> On Jun 17, 3:16 pm, Peter Bergström <pberg...@apple.com> wrote: >>>>> IE6 is something I am considering leaving behind because the >>>>> browser >>>>> is both (a) lacking in too many features and (b) too slow to be >>>>> very >>>>> useful for building full client-side apps. I could be convinced >>>>> otherwise though, especially if people were motivated to pitch in.
>>>> I loathe IE6. However, realistically, if you want to make *any* >>>> inroads into enterprise or corporate sites, IE6 is still needed.
>>>> On the plus side, IE6 is loads better than IE5.5. *shudder*.
