Mixedrealitytoolkit-unity: Iteration Plan for January 2019

Created on 18 Jan 2019  路  8Comments  路  Source: microsoft/MixedRealityToolkit-Unity

This is our plan for January. The goal is to complete MRTK v2 and release Beta2. The definition of complete is:

  • [x] No remaining breaking changes
  • [x] Feature Complete compared to HTK (except for controller rendering)
  • [x] Substantial feedback from Beta1 addressed

Planned Work

  • [x] Update inconsistent naming of core system implementations #3115 @davidkline-ms
  • [x] Update Unity requirement to 2018.3 #3306 @davidkline-ms
  • [x] move input system to core #3328 @davidkline-ms
  • [x] Moving spatial awareness system to core #3327 @davidkline-ms
  • [x] Tree layout and assembly restructure to align with packaging #3341 @davidkline-ms
  • [x] Refactor Controller Mapping Profile to accept individual controller scriptable objects. #3074
  • [x] Create separate OpenVR provider assembly #3358 (blocked by #3074)
  • [x] Create separate WindowsMixedReality provider assembly #3357 (blocked by #3074)
  • [x] Spatial awareness interfaces changes #3326 @davidkline-ms && @radicalad
  • [x] Remove requirement for IMixedRealityInputHandler to be an IMixedRealityInputHandler #3295 @davidkline-ms
  • [x] Add Attribute to make sure we can migrate to data provider in V3 #3387 @davidkline-ms

Most helpful comment

iteration complete. all mrtk_approved changes made and merged

All 8 comments

reordered the planned work list (rough priority order). will work with @chbecker-ms and @Yoyozilla to finalize the list

add provider assembly work (#3356, #3357, #3358) which is currently blocked by #3074

moved #3233 to MRTK v3 backlog

Moving the following to v3. We will have a migration path for v2 profiles.

  • [ ] "Device" to "DataProvider" and give each system it's own registry #3170 @davidkline-ms

    • [ ] Implement data provider pattern for input #3330 @davidkline-ms

    • [ ] Implement data provider pattern for spatial awareness #3329 @davidkline-ms

Or potentially the Feb iteration plan #3352

Moving

  • [ ] Controller visualization for Windows Mixed Reality #3331 @davidkline-ms && @keveleigh
  • [ ] Controller visualization for OpenVR #3332 @davidkline-ms && @keveleigh

To February iteration (#3352)

3074, #3357, #3358, #3295 and #3387 are fixed pending PR approval.

will not be feature complete until Feb iteration is complete (controller model support)

iteration complete. all mrtk_approved changes made and merged

Was this page helpful?
0 / 5 - 0 ratings