Last week I mentioned the effort to update Dasher 360 to use v4.2 of the Forge viewer (the most recent version, at the time of writing, and a fairly big jump from our previously-used version, v3.2.1). Here’s how Dasher 360 is now looking after these various changes:
In this post I’m going to give more details of what specifically was involved in refreshing Dasher 360 to the latest Forge viewer, in the hope it’ll help people make decisions around their own use of the viewer and hopw/when they migrate their applications.
Background
As we’ve developed Dasher 360, we’ve done our best to keep our code nicely modularised, even if the application is still tightly coupled with Forge. For instance, most of our features have been implemented as independent Forge viewer extensions that can be enabled or disabled depending on the needs of the project. There are inter-dependencies, of course, but we’ve done our best to keep these to a minimum. Architecturally-speaking, Dasher 360…