<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Taking OpenLayers to the next level?</title>
	<atom:link href="http://blog.xebia.com/2009/10/23/taking-openlayers-to-the-next-level/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.xebia.com/2009/10/23/taking-openlayers-to-the-next-level/</link>
	<description></description>
	<lastBuildDate>Mon, 26 Jul 2010 20:40:47 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Schuyler Erle</title>
		<link>http://blog.xebia.com/2009/10/23/taking-openlayers-to-the-next-level/comment-page-1/#comment-92959</link>
		<dc:creator>Schuyler Erle</dc:creator>
		<pubDate>Mon, 26 Oct 2009 18:34:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xebia.com/2009/10/23/taking-openlayers-to-the-next-level/#comment-92959</guid>
		<description>Depends on how you add the features. If you&#039;re just creating new layers, no worries. If you need to change the API fundamentally, that&#039;ll require a new major version of the OpenLayers.

To be fair, I think we should start thinking about what OpenLayers 3.0 might look like. OL currently has a bunch of warts and legacy code from as far back as 2007, retained for compatibility reasons. A version 3.0 would let us clean out the cruft while planning for new features.</description>
		<content:encoded><![CDATA[<p>Depends on how you add the features. If you&#8217;re just creating new layers, no worries. If you need to change the API fundamentally, that&#8217;ll require a new major version of the OpenLayers.</p>
<p>To be fair, I think we should start thinking about what OpenLayers 3.0 might look like. OL currently has a bunch of warts and legacy code from as far back as 2007, retained for compatibility reasons. A version 3.0 would let us clean out the cruft while planning for new features.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
