Open nlsdvl opened 1 year ago
rt-xr-maf-plugin
is really just a build artifact of rt-xr-maf-native
and there is no plan to add extra code or features there.
I propose to remove it. continuous delivery of rt-xr-maf-native
and updated documentation should reduce the friction for new developpers.
cc @Etiennefaivredarcier @aaronmontilla
I agree on this, the number of repositories need to be reduced to invite new developers to test the tools
I completely agree with you, it was difficult for me to understand what each repository was used for. Reducing the number of repositories will make the first steps more intuitive for beginners.
Progress on continous delivery for the media pipeline dependencies here: https://github.com/5G-MAG/rt-xr-maf-native/pull/6
The unity player implementation currently comes as a set of 4 repos:
rt-xr-unity
: reference player - unity projectrt-xr-gltfast
: a fork of glTFast - unity pluginrt-xr-maf-plugin
: maf library & media pipelines - unity plugin.rt-xr-maf-native
: maf library & media pipelines - C++ librariesThis configuration makes the project more complex to maintain and reason about than it has to be.
Having fewer repos would make it easier:
rt-xr-maf-plugin
was initially intended to contain the maf implementation for unity. It currently only contains build artifacts and dependencies fromrt-xr-maf-native
. If media player code wrapping the MAF API for Unity is not maintained in this repo, it could be removed.The project needs to be organized with the following in mind: