ol-ishare (or oli for short) is a new embedded map JavaScript client using the latest OpenLayers library which was itself designed from the outset for use on mobile devices.
Using ol-ishare we have produced an embedded map component that is similar in functionality to iShare Lite maps, along with the new Spotlight map creator and a rewrite of Logger.
Release
The official latest release version is at: https://ol-ishare.services.astuntechnology.com/v1/apps/spotlight/index.html for embedding, downloading resources, etc.. This uses the v1 branch.
Examples
A number of examples of using ol-ishare can be found here:
https://ol-ishare.services.astuntechnology.com/v1/examples/index.html
A significant benefit of ol-ishare is that we have structured the JavaScript code in such a way (using UMD bundles) so as to make it far easier for other developers to work with and develop custom solutions by themselves - or for Astun to build and maintain customer specific embedded map components containing bespoke functionality.
Documentation
API documentation can be found in each branch, e.g. https://ol-ishare.services.astuntechnology.com/main/apidoc/
Branches
The current principal branches are:
'v1'
Where the latest v1.x.y release will always be available.
'main'
https://ol-ishare.services.astuntechnology.com/main/
Where other branches are consolidated and tested before progressing to a release candidate. Minor bugfixes are allowed but any changes to capability or significant work required for a fix should be reviewed via the pull request process and so require use of feature & bugfix branches (temporary or otherwise).
Other notable branches
'v1-beta' - Archive of code used by customer feedback beta. (https://ol-ishare.services.astuntechnology.com/v1-beta/apps/spotlight/index.html )
Feature & bugfix branches
We create new branches for any significant new features or major bugfixes. These then go through a Pull Request and code review before being merged into the main branch. These are made available on ol-ishare.services.astuntechnology.com URLs through the same build process that outputs main etc. but there is no guarantee that these URLs will persist beyond the point at which the branches get merged.