Table of Contents for
OpenLayers 3 : Beginner's Guide

Version ebook / Retour

Cover image for bash Cookbook, 2nd Edition OpenLayers 3 : Beginner's Guide by Erik Hazzard Published by Packt Publishing, 2015
  1. Cover
  2. Table of Contents
  3. OpenLayers 3 Beginner's Guide
  4. OpenLayers 3 Beginner's Guide
  5. Credits
  6. About the Authors
  7. About the Reviewers
  8. www.PacktPub.com
  9. Preface
  10. What you need for this book
  11. Who this book is for
  12. Sections
  13. Time for action – heading
  14. Conventions
  15. Reader feedback
  16. Customer support
  17. 1. Getting Started with OpenLayers
  18. Advantages of using OpenLayers
  19. What, technically, is OpenLayers?
  20. Anatomy of a web mapping application
  21. Connecting to Google, Bing Maps, and other mapping APIs
  22. Time for action – downloading OpenLayers
  23. Time for action – creating your first map
  24. Where to go for help
  25. OpenLayers issues
  26. OpenLayers source code repository
  27. Getting live news from RSS and social networks
  28. Summary
  29. 2. Key Concepts in OpenLayers
  30. Time for action – creating a map
  31. Time for action – using the JavaScript console
  32. Time for action – overlaying information
  33. OpenLayers' super classes
  34. Key-Value Observing with the Object class
  35. Time for action – using bindTo
  36. Working with collections
  37. Summary
  38. 3. Charting the Map Class
  39. Time for action – creating a map
  40. Map renderers
  41. Time for action – rendering a masterpiece
  42. Map properties
  43. Time for action – target practice
  44. Map methods
  45. Time for action – creating animated maps
  46. Events
  47. Views
  48. Time for action – linking two views
  49. Summary
  50. 4. Interacting with Raster Data Source
  51. Layers in OpenLayers 3
  52. Common operations on layers
  53. Time for action – changing layer properties
  54. Tiled versus untiled layers
  55. Types of raster sources
  56. Tiled images' layers and their sources
  57. Time for action – creating a Stamen layer
  58. Time for action – creating a Bing Maps layer
  59. Time for action – creating tiles and adding Zoomify layer
  60. Image layers and their sources
  61. Using Spherical Mercator raster data with other layers
  62. Time For action – playing with various sources and layers together
  63. Time For action – applying Zoomify sample knowledge to a single raw image
  64. Summary
  65. 5. Using Vector Layers
  66. Time for action – creating a vector layer
  67. How the vector layer works
  68. The vector layer class
  69. Vector sources
  70. Time for action – using the cluster source
  71. Time for action – creating a loader function
  72. Time for action – working with the TileVector source
  73. Time for action – a drag and drop viewer for vector files
  74. Features and geometries
  75. Time for action – geometries in action
  76. Time for action – interacting with features
  77. Summary
  78. 6. Styling Vector Layers
  79. Time for action – basic styling
  80. The style class
  81. Time for action – using the icon style
  82. Have a go hero – using the circle style
  83. Multiple styles
  84. Time for action – using multiple styles
  85. Style functions
  86. Time for action – using properties to style features
  87. Interactive styles
  88. Time for action – creating interactive styles
  89. Summary
  90. 7. Wrapping Our Heads Around Projections
  91. Time for action – using different projection codes
  92. Time for action – determining coordinates
  93. OpenLayers projection class
  94. Transforming coordinates
  95. Time for action – coordinate transforms
  96. Time for action – setting up Proj4js.org
  97. Time for action – reprojecting extent
  98. Time for action – using custom projection with WMS sources
  99. Time for action – reprojecting geometries in vector layers
  100. Summary
  101. 8. Interacting with Your Map
  102. Time for action – converting your local or national authorities data into web mapping formats
  103. Time for action – testing the use cases for ol.interaction.Select
  104. Time for action – more options with ol.interaction.Select
  105. Introducing methods to get information from your map
  106. Time for action – understanding the forEachFeatureAtPixel method
  107. Time for action – understanding the getGetFeatureInfoUrl method
  108. Adding a pop-up on your map
  109. Time for action – introducing ol.Overlay with a static example
  110. Time for action – using ol.Overlay dynamically with layers information
  111. Time for action – using ol.interaction.Draw to share new information on the Web
  112. Time for action – using ol.interaction.Modify to update drawing
  113. Understanding interactions and their architecture
  114. Time for action – configuring default interactions
  115. Discovering the other interactions
  116. Time for action – using ol.interaction.DragRotateAndZoom
  117. Time for action – making rectangle export to GeoJSON with ol.interaction.DragBox
  118. Summary
  119. 9. Taking Control of Controls
  120. Adding controls to your map
  121. Time for action – starting with the default controls
  122. Controls overview
  123. Time for action – changing the default attribution styles
  124. Time for action – finding your mouse position
  125. Time for action – configuring ZoomToExtent and manipulate controls
  126. Creating a custom control
  127. Time for action – extending ol.control.Control to make your own control
  128. Summary
  129. 10. OpenLayers Goes Mobile
  130. Using a web server
  131. Time for action – go mobile!
  132. The Geolocation class
  133. Time for action – location, location, location
  134. The DeviceOrientation class
  135. Time for action – a sense of direction
  136. Debugging mobile web applications
  137. Debugging on iOS
  138. Debugging on Android
  139. Going offline
  140. Time for action – MANIFEST destiny
  141. Going native with web applications
  142. Time for action – track me
  143. Summary
  144. 11. Creating Web Map Apps
  145. Using geospatial data from Flickr
  146. Time for action – getting Flickr data
  147. A simple application
  148. Time for Action – adding data to your map
  149. Styling the features
  150. Time for action – creating a style function
  151. Creating a thumbnail style
  152. Time for action – switching to JSON data
  153. Time for action – creating a thumbnail style
  154. Turning our example into an application
  155. Time for action – adding the select interaction
  156. Time for action – handling selection events
  157. Time for action – displaying photo information
  158. Using real time data
  159. Time for action – getting dynamic data
  160. Wrapping up the application
  161. Time for action – adding dynamic tags to your map
  162. Deploying an application
  163. Creating custom builds
  164. Creating a combined build
  165. Time for action – creating a combined build
  166. Creating a separate build
  167. Time for action – creating a separate build
  168. Summary
  169. A. Object-oriented Programming – Introduction and Concepts
  170. Going further
  171. B. More details on Closure Tools and Code Optimization Techniques
  172. Introducing Closure Library, yet another JavaScript library
  173. Time for action – first steps with Closure Library
  174. Making custom build for optimizing performance
  175. Time for action – playing with Closure Compiler
  176. Applying your knowledge to the OpenLayers case
  177. Time for action - running official examples with the internal OpenLayers toolkit
  178. Time for action - building your custom OpenLayers library
  179. Syntax and styles
  180. Time for action – using Closure Linter to fix JavaScript
  181. Summary
  182. C. Squashing Bugs with Web Debuggers
  183. Time for action – opening Chrome Developer Tools
  184. Explaining Chrome Developer debugging controls
  185. Time for action – using DOM manipulation with OpenStreetMap map images
  186. Time for action – using breakpoints to explore your code
  187. Time for action – playing with zoom button and map copyrights
  188. Using the Console panel
  189. Time for action – executing code in the Console
  190. Time for action – creating object literals
  191. Time for action – interacting with a map
  192. Improving Chrome and Developer Tools with extensions
  193. Debugging in other browsers
  194. Summary
  195. D. Pop Quiz Answers
  196. Chapter 5, Using Vector Layers
  197. Chapter 7, Wrapping Our Heads Around Projections
  198. Chapter 8, Interacting with Your Map
  199. Chapter 9, Taking Control of Controls
  200. Chapter 10, OpenLayers Goes Mobile
  201. Appendix B, More details on Closure Tools and Code Optimization Techniques
  202. Appendix C, Squashing Bugs with Web Debuggers
  203. Index

Explaining Chrome Developer debugging controls

In this section, we will see each button in the Chrome Developer Developer Tools to review the available functions you can perform with the debugger.

Explaining Chrome Developer debugging controls
  • The Page Inspector(1) icon: This icon, a magnifying glass, is the HTML Inspector. When you click on it, the mouse cursor will identify HTML elements on the web page. So, when the mouse hovers over anything on a website, the element will be outlined in blue and the HTML panel will open up and show you the element your mouse is over.
  • The Toogle Device mode(2) icon: This is when you need to test different mobile screen resolutions or you want to use simulation for Geolocation. It's a component in the Google Developer Tools that have changed several times. So, we prefer to redirect you to official doc https://developer.chrome.com/devtools/docs/device-mode as it may change again.
  • It's the various panels (3) we will review just after all the tool bar options reviews.
  • The Console(4) icon: This icon is a way to display the console, a tool for exploring JavaScript. You click on it to display a new window below the bottom row. When activated, the grey icon changes to blue. We will explore it further when describing the console panel. Just before this icon, you will see errors and warnings appear if there are any in the web page you are browsing.
  • The Settings(5) icon: this icon displays a new panel with three vertical tabs. The first one is dedicated to the General settings. The second is Workspace. Its goal is to make the editing done in the Sources panel persistent. The last, Shortcuts, is the reminder of all shortcuts needed to be efficient when using the debugger. It contains more or less the information available in the shortcuts web page provided some pages before.
  • The Attached/detached debugger(6) icon: This enables you to display the debugger with fullscreen web page with a separated window or with the debugger view integrated in the current page (aligned to bottom or right). To switch between those modes, click or click and hold access the several options.
  • Cross(7): This enables you to close the browser debugger.

Panels

The top row set of controls is called panels; each panel provides a different type of function. The panels act like tabs (the two terms can be used interchangeably), but Chrome Developer Tools refers to them as panels in the documentation. Let's go over each panel, since they are, essentially, what makes up Chrome DevTools. We will not go over these panels from left to right, but instead we will look at the most important ones for beginners first.

The Elements panel

The Elements panel provides not just a display of the HTML source code, but also the ability to quickly edit any HTML element and its associated style. It allows users to add, remove, and move HTML elements, edit HTML attributes, and change nearly anything about the page without having to save any files. It also can track when attributes or elements are created, changed, or removed. This helps to make web development much easier and faster.

How it works

Chrome DevTools automatically builds a tree structure from HTML code, giving the ability to expand and hide each HTML tag. It is important to note that the code you see in the HTML panel is a generated HTML code—the code in the panel may not be exactly the same as the page's source code (because the browser is interpreting the HTML to be able to show a page content).

Here is what the Elements tab looks like when Chrome DevTools is opened while viewing a web page:

How it works

On the left-hand side, Chrome DevTools shows the HTML of the page. It's possible to right-click on any tag and do various things—such as copying the HTML to the clipboard, deleting the element, changing the tag attributes, and more.

On the right-hand side, the associated style information for the selected element is displayed. Properties can be added or modified and will instantly appear on the page, like in the preceding capture image example (at http://www.w3.org/Style/Examples/011/firstcss.en.html), with the div element with id attribute value to language . Looking at the CSS on the right-hand side, there is a definition for the language id but only font-size and font-style properties are defined. We also see that some other styles are coming from the body element parent. The <div> tag inherits from body the color #333333 or the font-family properties.

Note

If you are unfamiliar with HTML or CSS, the WebPlatform site is a great resource. For more information on HTML, visit http://docs.webplatform.org/wiki/html, and for CSS, visit http://docs.webplatform..

What does this mean? Well, Chrome DevTools lists all inherited style information, and parent element styles propagate down to all their child elements (each child has all its parent's styles, unless the child overrides a style, which doesn't happen in this example).

By double-clicking on pretty much anything in the HTML or CSS list, you can quickly change values and names. Any change you make will immediately show up on the page, which makes it very easy to change style in real time and see how the page is affected without having to edit and save any files.

When you're playing with CSS, you can disable a property with a left click on the left part of the CSS property. You can try this on font-size to see visual change. For CSS, when the code really inherits from a lot of properties, we advise you to go to sub-panel Computed on the right part of Elements panel. You get the summary overview for each property. Play around with it a bit—if you mess anything up, you can just reload the page in Chrome.

When editing pages with Google Chrome Developer Tools, any changes you make will disappear when you refresh the page. You are not editing the actual web server's files with Google Chrome Developer Tools—instead, you are editing a copy that is on your computer that only you can see when you make changes to it. So, if you make changes and want them to be saved, you'll have to edit your actual source code.

Tip

In fact, one way to directly edit and save content within Google Chrome Developer Tools is to rely on the Workspace ability we already have evocated when clicking in the Settings icon. Check out the official Chrome Developer browser documentation at https://developer.chrome.com/devtools/docs/workspaces.

Until now, we focused on the right part of panel elements. Let's see how to manipulate and inspect DOM elements in the left Elements window.