Hello, I've started digging in to ol-cesium while developing an Angular 5 application that uses openlayers and cesium. My assumption going in was that the ol-cesium project would be dependent on vanilla versions of openlayers and cesium and strictly export an 'ol-cesium' module that provides additional functionality on top of its dependent libraries. After looking over some of the source, it appears that ol-cesium actually bundles aspects of the openlayers project in with ol-cesium functionality and exports a custom ol module. If I am correct, I am curious about the motivation behind this decision instead of either keeping ol-cesium and openlayers distinct or pulling in the new functionality into mainline openlayers.
In the ideal case, I would like to be able to use ol-cesium along side my existing openlayers/cesium installations. If I had to downgrade/upgrade versions of either library, I would certainly understand. The necessity to use the custom exported ol module from ol-cesium means I need to refactor some of my application code because the closure compiler mangles the whole ol object, which I have already imported from openlayers. Any thoughts on this would be much appreciated. Thank you, Eric -- You received this message because you are subscribed to the Google Groups "OpenLayers Dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to openlayers-dev+unsubscr...@googlegroups.com. To post to this group, send email to openlayers-dev@googlegroups.com. Visit this group at https://groups.google.com/group/openlayers-dev. To view this discussion on the web visit https://groups.google.com/d/msgid/openlayers-dev/84bd7b06-3a34-480b-a9ed-271af46da9f2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
