In our last post, we talked about some of the high level reasons for the improvements we’re rolling out in the new VenueOps: performance and mobile. In this post, we’re going to dig a bit deeper into the release.
For the last three years, VenueOps has been using AngularJS. AngularJS has served us well, but this framework will no longer be developed or supported. Keeping an unsupported framework in our application is not a good idea for many reasons (security being one of them). Upgrading to Angular 2+ was going to involve a complete rewrite, so we took the opportunity to look at other available frameworks and to see which one, in our opinion, had the best patterns and practices. We also wanted to be sure to choose a framework which can support a graphics-heavy program—like our calendar—for the foreseeable future. We chose to go with Vue, a framework we felt was faster, cleaner, and more performant.
While updating the framework, we took the opportunity to internationalize VenueOps. Previously, all of the headers, labels, captions, etc. were written into the front-end code. Since we were going to have to rewrite all of that code, now was a perfect opportunity to change from hard-coded English labels to variables which would call the correct label from a language file. Doing this now had the added advantage of only having to retest the entire front end once, saving us significant time.
The building blocks are in place so that translating VenueOps from English is now possible, and we’re currently working with clients and partners in other parts of the world on these language translations.
To complete the scope of work for this release, we took a long, hard look at VenueOps itself. Were there any changes needed which would save us time to do now? And after three years of adding features, there was certainly some cleanup we could do! The two sections we took the time to reorganize were Sys Admin and Company Settings (be sure to check out the webinar on December 10 to see these changes).
We also kept an eye on the feedback we have been collecting from our users. We implemented close to two dozen enhancements which made sense to do now, rather than later (we’ll have those listed in the release notes).
Additionally, we worked to make the entire user experience more consistent—from using the same download icon throughout to always placing the Remove option in the edit slider. Our goal is to make VenueOps as intuitive and user-friendly as possible, even though it is complex, enterprise-level software.