On Thu, Apr 10, 2008 at 09:24:56AM -0700, Anselm Hook wrote: > > > So what are our dream features from a js web map API? > > Not to change scope of the question but can't we do better? Isn't > there any way to get beyond Javascript, the DOM, HTML and the like? > We are locked away from hardware resources that already exist on these > machines; persistence, math, rasterization...
That depends. Do you care about hitting users *today*, or 3-5 years from now? If the answer is the former, then you have to target what currently exists: in the same way that OpenLayers has wasted a ton of effort duplicating our vector support for IE, despite the fact that everything else now supports SVG. If you want to do something in a browser that isn't currently supported, you need to be looking at 3-5 years minimum for mainstream acceptance: 1 year to get it in the pipeline for the next release of current browsers, and another two years to let it propogate its way through the installed userbase. And that's only if you can achieve acceptance in all the major browsers: and IE is still one of those, regardless of the specific issues associated with it. Regards, -- Christopher Schmidt MetaCarta _______________________________________________ Geowanking mailing list [email protected] http://lists.burri.to/mailman/listinfo/geowanking
