I come to praise the Web ADF, not to bury it
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?
Et tu, James?
Adding touch control to OpenLayers
whit has written a blog post on what he’s been working on getting OpenLayers to work with Mobile Safari on the iPhone (and iTouch).
A major part of my recent investigations for mobile and opengeo have focused on getting OpenLayers to do a basic version of it’s thing on the iphone.? I’ve had limited success, but maybe these demos will help someone else get a little further or perhaps help crystallize a more effective approach than mine, since I’m pretty green with OL.
He’s also created a couple demos for the iPhone/iTouch using some of the touch controls. The bottom line is that moving from mouse control to finger touch is as hard as you’d expect. I think it is great to see OpenLayers take on this effort because being able to move mapping to mobile devices will be key with the iPhone and Android taking off here in the next year.
OpenLayers iPhone Support
Adding touch control to OpenLayers
whit has written a blog post on what he’s been working on getting OpenLayers to work with Mobile Safari on the iPhone (and iTouch).
A major part of my recent investigations for mobile and opengeo have focused on getting OpenLayers to do a basic version of it’s thing on the iphone.? I’ve had limited success, but maybe these demos will help someone else get a little further or perhaps help crystallize a more effective approach than mine, since I’m pretty green with OL.
He’s also created a couple demos for the iPhone/iTouch using some of the touch controls. The bottom line is that moving from mouse control to finger touch is as hard as you’d expect. I think it is great to see OpenLayers take on this effort because being able to move mapping to mobile devices will be key with the iPhone and Android taking off here in the next year.
OpenLayers iPhone Support
MapQuest for iPhone — Interesting if there is an API
I see that MapQuest now has an optimized iPhone site (HT APB) for all those people who still use MapQuest (though I’d guess most iPhone users would just assume use the built in Google Maps app). Since MapQuest is not using the iPhone App SDK I wonder if there is an API available for developers to create iPhone mapping applications using the MapQuest API for the iPhone? MapQuest’s API has been hit hard by Google and Microsoft and I would think a smartphone API (Android and iPhone both use WebKit) would help them get out of their niche.
Damn! We’re in a tight spot!
Damn! Were in a tight spot!
MapQuest for iPhone — Interesting if there is an API
I see that MapQuest now has an optimized iPhone site (HT APB) for all those people who still use MapQuest (though I’d guess most iPhone users would just assume use the built in Google Maps app). Since MapQuest is not using the iPhone App SDK I wonder if there is an API available for developers to create iPhone mapping applications using the MapQuest API for the iPhone? MapQuest’s API has been hit hard by Google and Microsoft and I would think a smartphone API (Android and iPhone both use WebKit) would help them get out of their niche.
Damn! We’re in a tight spot!
Damn! Were in a tight spot!
The ESRI Flex API vs the JavaScript API
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
Flex…..Savior of the Universe