Geospatial Technology, Web Mapping and Spatial Services
August 15, 2011 Leave a Comment
I’m the first to admit I’m not a huge Flex supporter, but maybe this is interesting to all those who tell me Flex is where the magic is happening.
WebMapSolutions.com seems to be working with ArcGIS Flex 2.4 and Flex Builder 4.5 and ported them to AIR for mobile devices. For those organizations who are locked into Flex, this might be a simple solution to get their apps on mobile devices.
December 14, 2009 3 Comments
I’m sure everyone reading this blog knows my opinions about Flash and Silverlight. I’m of the mindset that I’d prefer HTML Javascript over either, but clearly like my opinion that 3D Globes would too hard for “ordinary people” to use; I’m in the minority. Given the huge adoption for both for mapping, an open source mapping framework usingActionScript 3 and Flex has appeared.
OpenScales, which has a LGPL license will allow those who want to build “rich” (rich is the keyword for any Flash or Silverlight app, if it ain’t rich, it ain’t a plugin) web mapping applications without need to license proprietary development frameworks. You can see from the demos that this ends up being very similar to other Flex based APIs.
On top of that, it supports WMS/WFS, OpenStreetMap, IGN, KML and direct image reading. You can also deploy on mobile using ActionScript 3 (Palm Pre support), web using wlex or on the desktop using Adobe Air.
OpenScales 1.1 was just released last week so the community seems strong and working toward increasing its functionality quickly. If you are working on Adobe web technology and want an open source mapping framework, you might want to check out OpenScales.
October 22, 2008 11 Comments
I was just talking to someone today about web applications for ArcGIS Server 9.3 and they were surprised that I was using the Web ADF to create an application after my post earlier this week on the JavaScript API. I feel like I need to clarify some things about that post. It wasn’t so much a desertion of the Web ADF, but point that one should be looking toward the JavaScript API (and I suppose the Flex API) for most mapping situation and use the Web ADF (Java and .NET) when it best makes sense. I’m using the Web ADF on this project because the requirements of the end user is best met with the Web ADF. The great thing about the JavaScript API, the Flex API, the .NET Web ADF, the Java Web ADF and even the JavaScript extenders for the JavaScript API is that they all can be called on if needed. Of course the Web ADF does have licensing issues that ESRI needs to address that limit its appeal even when it is the best choice for the solution.
ESRI has given their developers choices that we aren’t accustom to and in turn ESRI developers should be looking at the choices when making a decision of what SDK to use. Also just because you use the JavaScript API or the Flex API doesn’t mean you’ll end up with a great application. So much more goes into it and there isn’t any reason why the Java Web ADF can’t give you a great application anymore than the Flex API can.
Et tu, James?
October 20, 2008 45 Comments
OK, I’ll come clean. While Flex is a great tool, I can’t see how you’d not use the JavaScript API instead. Flex is still not available on every platform (I’m an iPhone elitist) and isn’t easily picked up by everyone. But more than one person said in last weeks thread on the JavaScript API that Flex was the way they are going. I’m curious is there a rising groundswell in Flex or are ESRI developers just an outlier to the overarching movement toward JavaScript? FlexBuilder 3 is at least $250 (Pro is almost $700) and I just can’t see people bothering to buy an
What part of the Flex API makes you choose it over the JavaScript API? If people are willing to block Flash, don’t you limit your marketplace by going that route over JavaScript?
Flex.....Savior of the Universe
