Migrating to MRTK2: Missing Singleton and 3DTextPrefab
Learn about migrating to MRTK2 in this short post.
Join the DZone community and get the full member experience.Join For Free
If you are migrating from the HoloToolkit to Mixed Reality Toolkit 2 'cold turkey,' as I am doing for my AMS HoloATC app, a lot of things break, as I already said in the first post of this series. For things that you can tap, you can simply change the implementing interface from
IManipulationHandler to a couple of other interface and change the signature a bit — that's not complex, only tedious, depending on how much you have used it.
What I found really hard was the removal of the Singleton class and the 3DTextFab. I used both quite extensively. The first one I needed for like data access classes as the concept of services that was introduced in the Mixed Reality Toolkit 2 was not yet available, and the other... well basically all my texts were 3DTextPrefabs so any kind of user feedback in text format was gone. Because so much breaks at the same time, it's very hard to step by step rebuilding your app to a working condition. Basically you have to change everything before something starts to work again. Since I was still learning by doing, there was no way to test if I was doing things more or less right. I got stuck and took a radical approach.
I have created a little Unity Package that contains the things that made it hard for me to get a step-by-step migration to the MRTK2 and christened it the
HoloToolkitCompatiblityPack. It contains minimal amount of scripts and meta files to have Singleton and 3DTextFab working inside an MRTK2 built app. As I will be migrating more apps, I will probably update the package with other classes that I need. You can find the package file here and the project here. If you take your existing HoloToolkit based app, yank out the HoloToolkit, replace it by the MRTK2, then import the
HoloToolkitCompatiblityPack package, you at least have to fix a few less things to at least get your app to a minimal state of function again.
Yes, of course you can use the
HoloToolkitCompatiblityPack in your production app, and ship a kind of Frankenbuild using both MRTK2 and this. Do let yourself be tempted to do that. See this package as a kind of scaffolding, or a temporary beam to hold up the roof while you are replacing a bearing wall. For 3DTextFab I tend to turn a blind eye, but please don't use Singleton again. Convert those classes into services one by one. Then remove the Singleton from the
HoloToolkitCompatiblityPack to make sure everything works without. This is for migration purposes only.
Take the high road, not the low technical debt road.
Making this package helped me forward with the migration quite a lot. I hope it helps other too. I'd love to hear some feedback on this.
Published at DZone with permission of Joost van Schaik, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.