Current idea: restructure the VR2gather repository to be somewhat similar in structure to the https://github.com/cwi-dis/cwipc_unity repository, with two things at the toplevel:
The package, called something like nl.cwi.dis.vr2gather,
The sample application, possibly called VR2Gather, possibly VRTApp, which hard-links to the package (and its samples).
For an external application (like mediascape or so) the global structure would become the reverse from what it is now: A repo VRTApp-xxxxx which would simply include the nl.cwi.dis.vr2gahter package by git URL through the Unity Package manager. No more branches in VR2Gather, much cleaner structure.
We have to do this, and we have to do this now.
Current idea: restructure the VR2gather repository to be somewhat similar in structure to the https://github.com/cwi-dis/cwipc_unity repository, with two things at the toplevel:
nl.cwi.dis.vr2gather
,VR2Gather
, possiblyVRTApp
, which hard-links to the package (and its samples).For an external application (like mediascape or so) the global structure would become the reverse from what it is now: A repo
VRTApp-xxxxx
which would simply include thenl.cwi.dis.vr2gahter
package by git URL through the Unity Package manager. No more branches in VR2Gather, much cleaner structure.