Updated interim codebase for Sprint 1

Completed work on following functionalities:
1. UI for  smart phones, tablets and desktop browsers
2. Basemap switcher – Allows to select basemap
3. Zoom Controls
4. Home button – return to initial extent configured for the application
/ webmap
5. Legend panel on bottom left
6. UI for Unified Search
7. UI for 511 panel - We will implement the recent UI changes to 511
info panel in the next sprint
8. UI for Get Directions – Enter two addresses; draw route on map and
show driving directions
9. Geolocation – Drop push pin
10. UI for Sharing
Updated interim codebase for Sprint 2

Completed work on following:
1. Modified workflow on application start
a. Display 511 information upon starting application
b. Direction panel UI will be enabled only when “showdirection/routing”
flag is set true in configuration
2. Unified search
a. Search for an address/county or Route Name/Route ID/Mile post using a
single search box
b. UI for Unified search
c. Autocomplete Implementation
d. Configure and implement default value for search
e. Use of Configurable locators for address/county search
f. Show results in results panel grouped by addresses/county or Route
/Mile post
g. Display search result with custom scroll bar in result panel
3. Incorporated feedback received during previous demo
a. Make the text "511 Information" (in "511 Information" panel)
configurable
b. Lower height of Search Results panel and expand while searching for
an address
V 0.3 – Interim codebase for Sprint 3

Implemented following functionalities:

1. Populate ‘Legend’ based on configured layers with ‘Previous’ and
‘Next’ buttons
2. UI for ‘Directions’ panel
3. Show generated route on map
4. Show driving directions for generated route
V 0.4 – Interim codebase for Sprint 4

Implemented following functionalities
1. Routing
a. User  will enter source and destination address
b. To add one or more than one destination address user may click on
‘Add Destination’
c. User will have the facility to swap source and destination addresses
d. User will have facility to delete a destination point when more than
two destinations are provided
e. User can dynamically drag start and end points to generate a new
route
f. Routing settings should be configurable
2. Re-Route
a. User will be able to reroute using ‘Re-route’ button if incidents are
found on the route – development in progress
b. While re-routing, barriers are consider within 5 times of mile buffer
distance
3. Refresh 511 panel to display incidents in proximity to route
4. Incorporated following feedback
a. Reduce load time for 511 Information panel
b. Route color and buffer colors are configurable
c. Change Legend display based on extent change
Merge branch 'CT_Development' into develop
Merge remote-tracking branch 'origin/master' into develop
Updated to JSAPI 3.8
Fixed typos
Commented out problem widget and feature service
Added placeholder strings for languages

and added English file to for fine-tuning English without having to resubmit entire language suite to translators
Moved charset instruction to front of file
Removed empty link instruction that was blocking W3C validation
Removed instruction that was preventing language files to be read

and fixed switched language files
Extracted shared library
Made distinction between import of app-specific nls & shared nls
Split internationalizable terms between app-specific & shared nls

and added tooltips to header widgets
Merge branch 'shared_library' into develop
Simplified URL
Added proxy
Switched to new routing service