[OpenLayers-Users] Release?

[Christopher Schmidt]

On Thu, Jun 22, 2006 at 11:30:44AM -0600, Corey Puffalt wrote:
> Schuyler,
> 
> Thanks for your reply.
> 
> On 6/22/06, Schuyler Erle <sderle at metacarta.com> wrote:
> >
> >Actually IE6 compatibility is of enormous importance to us. Can you
> >give us a clear idea of the problems you are encountering?
> 
> 
> Good to hear that.  I have come across two issues.  I've just submitted
> tickets for both of them: #95 & #96.  The first one is that the MouseToolbar
> buttons don't change state visibly when the user clicks on them although
> they are otherwise functional.  The second one is a little more subtle (at
> least if you're using layers that render quickly):  I've found that under
> IE6 the map does not refresh until all the image tiles are loaded.  With a
> slow map server this makes a huge difference to the perceived responsiveness
> of the map.  I played with Google Maps for a while and it looks like they
> have found some way to work around this.

#95 is a duplicate of #82: "MouseToolbar icon img src doesn't change in
IE". Unfortunately, I'm not sure of the exact reason for this. I
essentially change the 'src' attribute for the image, and the image
itself doesn't update. I do see some hacks in ka-Map to get around this,
so I will try some of these.

I'm not sure if #96 is a result of something similar (it may be) or not.
Essentially, this performanec went into the pits when we added support
for transparent images -- I'm thinking that some of the changes here
might also be able to be pulled from ka-Map.

Thanks for bringing it up though. Most of us develop on Mac or Linux, so
IE doesn't get as much testing/love as it should. I've got a laptop here
now to do IE testing on, so I'll work on that in the relatively
short-term future: the performance bug is especially debilitating given
IE's position as the market share leader for browsers. 

However, if we get an API out, people can start developing against
Firefox and Safari, and then we can fix IE :) So that's our plan for the
moment, and I'll get on working out how to fix those IE bugs ASAP.

> Right now the release is *only* blocking on proper documentation of
> >the API. If you think the API docs can wait for the stable release,
> >I'll cut it now and finish the docs later. Although perhaps we should
> >clear up your browser compatibility issues first...
> >
> 
> I think complete API documentation can wait because you've got a nice set of
> examples showing how to use many of the features.  Since you're using a wiki
> the documentation can grow organically as time goes on anyways.


-- 
Christopher Schmidt
Web Developer