<?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: Google Abandons Maps for Adobe Flash/Air	</title>
	<atom:link href="https://www.selikoff.net/2011/09/21/google-abandons-maps-for-adobe-flashair/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.selikoff.net/2011/09/21/google-abandons-maps-for-adobe-flashair/</link>
	<description>Java/J2EE Software Development and Technology Discussion Blog</description>
	<lastBuildDate>Thu, 12 Mar 2015 06:45:30 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		By: james		</title>
		<link>https://www.selikoff.net/2011/09/21/google-abandons-maps-for-adobe-flashair/comment-page-1/#comment-151066</link>

		<dc:creator><![CDATA[james]]></dc:creator>
		<pubDate>Thu, 12 Mar 2015 06:45:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.selikoff.net/?p=3897#comment-151066</guid>

					<description><![CDATA[Hi Wonder,  how people easily say about some technology that its gone!..  Its a 4 year old article saying adobe AIR is dead. Yet we are building everyday adobe AIR apps.  We built multi-million dollar cross platform apps with adobe AIR just last year i.e 2014.  Every other app in google store is built with AIR. Who wants to ruin months developing in native codes for both platforms individually.  If any part or component is not supported in AIR then it can easily be incorporated using native extensions of adobe AIR.  So, nutshell its far from over. I see atleast a decade more of mobile apps development with adobe AIR if not less..]]></description>
			<content:encoded><![CDATA[<p>Hi Wonder,  how people easily say about some technology that its gone!..  Its a 4 year old article saying adobe AIR is dead. Yet we are building everyday adobe AIR apps.  We built multi-million dollar cross platform apps with adobe AIR just last year i.e 2014.  Every other app in google store is built with AIR. Who wants to ruin months developing in native codes for both platforms individually.  If any part or component is not supported in AIR then it can easily be incorporated using native extensions of adobe AIR.  So, nutshell its far from over. I see atleast a decade more of mobile apps development with adobe AIR if not less..</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Grit		</title>
		<link>https://www.selikoff.net/2011/09/21/google-abandons-maps-for-adobe-flashair/comment-page-1/#comment-5096</link>

		<dc:creator><![CDATA[Grit]]></dc:creator>
		<pubDate>Wed, 18 Jul 2012 19:54:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.selikoff.net/?p=3897#comment-5096</guid>

					<description><![CDATA[Well... Articles like this also don&#039;t help adobe&#039;s poor coverage on the flash&#039;s future. This all can be solved. Air and flash now have native extensions, also providing google map support like this one here: 

http://code.google.com/p/air-maps-ane/ 

I&#039;m still working with flash+air, the new  openGL support + native extensions make it one of the most powerful development platforms in delivering fast cross mobile apps]]></description>
			<content:encoded><![CDATA[<p>Well&#8230; Articles like this also don&#8217;t help adobe&#8217;s poor coverage on the flash&#8217;s future. This all can be solved. Air and flash now have native extensions, also providing google map support like this one here: </p>
<p><a href="http://code.google.com/p/air-maps-ane/" rel="nofollow ugc">http://code.google.com/p/air-maps-ane/</a> </p>
<p>I&#8217;m still working with flash+air, the new  openGL support + native extensions make it one of the most powerful development platforms in delivering fast cross mobile apps</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Michael		</title>
		<link>https://www.selikoff.net/2011/09/21/google-abandons-maps-for-adobe-flashair/comment-page-1/#comment-4945</link>

		<dc:creator><![CDATA[Michael]]></dc:creator>
		<pubDate>Wed, 11 Apr 2012 21:34:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.selikoff.net/?p=3897#comment-4945</guid>

					<description><![CDATA[Interesting article. thanks for the headsup Mike! i&#039;ve definately taken a look at the mapquest API. Since the AIR mobile isn&#039;t any different from AS3 api&#039;s, it sucks that AS3 support is falling away because of Adobe&#039;s decision. too bad really.]]></description>
			<content:encoded><![CDATA[<p>Interesting article. thanks for the headsup Mike! i&#8217;ve definately taken a look at the mapquest API. Since the AIR mobile isn&#8217;t any different from AS3 api&#8217;s, it sucks that AS3 support is falling away because of Adobe&#8217;s decision. too bad really.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Mike		</title>
		<link>https://www.selikoff.net/2011/09/21/google-abandons-maps-for-adobe-flashair/comment-page-1/#comment-4762</link>

		<dc:creator><![CDATA[Mike]]></dc:creator>
		<pubDate>Sun, 25 Sep 2011 13:36:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.selikoff.net/?p=3897#comment-4762</guid>

					<description><![CDATA[When searching for a map API, take a look at the MapQuest developer area.  They have a Flex/AIR/Actionscript API that is quick and easy to use.  I delved into the Google API and quickly discovered it wouldn&#039;t work.  But no problem, I still have maps in my app.  Just because Google doesn&#039;t offer it doesn&#039;t mean it&#039;s not available someplace else!]]></description>
			<content:encoded><![CDATA[<p>When searching for a map API, take a look at the MapQuest developer area.  They have a Flex/AIR/Actionscript API that is quick and easy to use.  I delved into the Google API and quickly discovered it wouldn&#8217;t work.  But no problem, I still have maps in my app.  Just because Google doesn&#8217;t offer it doesn&#8217;t mean it&#8217;s not available someplace else!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: David O'Meara		</title>
		<link>https://www.selikoff.net/2011/09/21/google-abandons-maps-for-adobe-flashair/comment-page-1/#comment-4761</link>

		<dc:creator><![CDATA[David O'Meara]]></dc:creator>
		<pubDate>Sun, 25 Sep 2011 12:20:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.selikoff.net/?p=3897#comment-4761</guid>

					<description><![CDATA[Nice article, Scott :)]]></description>
			<content:encoded><![CDATA[<p>Nice article, Scott 🙂</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Darren		</title>
		<link>https://www.selikoff.net/2011/09/21/google-abandons-maps-for-adobe-flashair/comment-page-1/#comment-4758</link>

		<dc:creator><![CDATA[Darren]]></dc:creator>
		<pubDate>Fri, 23 Sep 2011 00:16:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.selikoff.net/?p=3897#comment-4758</guid>

					<description><![CDATA[One workaround is to show content using the Javascript Maps API over part of your Flash content using an iFrame shim. I agree that the whole Spark/Halo thing is erratic but if you can make do with the Spark components, having the option to reach desktop, iOS and Android with practically the same codebase is a bonus. And good frameworks like Robotlegs do make the Flex coding experience worthwhile.]]></description>
			<content:encoded><![CDATA[<p>One workaround is to show content using the Javascript Maps API over part of your Flash content using an iFrame shim. I agree that the whole Spark/Halo thing is erratic but if you can make do with the Spark components, having the option to reach desktop, iOS and Android with practically the same codebase is a bonus. And good frameworks like Robotlegs do make the Flex coding experience worthwhile.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
