Book Image

Building Web and Mobile ArcGIS Server Applications with JavaScript ??? Second Edition - Second Edition

By : Eric Pimpler, Mark Lewin
Book Image

Building Web and Mobile ArcGIS Server Applications with JavaScript ??? Second Edition - Second Edition

By: Eric Pimpler, Mark Lewin

Overview of this book

The ArcGIS API for JavaScript enables you to quickly build web and mobile mapping applications that include sophisticated GIS capabilities, yet are easy and intuitive for the user. Aimed at both new and experienced web developers, this practical guide gives you everything you need to get started with the API. After a brief introduction to HTML/CSS/JavaScript, you'll embed maps in a web page, add the tiled, dynamic, and streaming data layers that your users will interact with, and mark up the map with graphics. You will learn how to quickly incorporate a broad range of useful user interface elements and GIS functionality to your application with minimal effort using prebuilt widgets. As the book progresses, you will discover and use the task framework to query layers with spatial and attribute criteria, search for and identify features on the map, geocode addresses, perform network analysis and routing, and add custom geoprocessing operations. Along the way, we cover exciting new features such as the client-side geometry engine, learn how to integrate content from ArcGIS.com, and use your new skills to build mobile web mapping applications. We conclude with a look at version 4 of the ArcGIS API for JavaScript (which is being developed in parallel with version 3.x) and what it means for you as a developer.
Table of Contents (21 chapters)
Title Page
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Customer Feedback
Preface

Chapter 14. Looking Ahead - Version 4 of the ArcGIS API for JavaScript

Version 4 of the ArcGIS API for JavaScript is a radical reimagining of the API by Esri in order to achieve a number of aims. Why start over? Basically, because the API has grown greatly in capability and therefore in complexity. Esri has been under pressure to add more and more features and, as with any development project that outlives its original scope, the API has become a mass of complex and often contradicting classes, methods, and workflows.

If you have been reading this book thinking Oh great! I've just spent hours of my life learning about v3, when v4 is out already and it's totally different! then rest assured. Although it's undoubtedly possible that Esri will, at some point, pull the plug on v3.x and pressure developers to go and learn v4, that time is not now. The reason is that there is plenty of stuff that v4 can't do yet that v3 can, and does, very well. So, for now, and for an indeterminate period in the...