Closed vladkol closed 7 years ago
While we can rename, we need to find a name that is strongly associated with the Windows stack.
MixedReality is confusing, because it is a term that predates this internal rebranding and in use in the industry. It would confuse android and iOS users to find that "MixedRealty" is windows-only.
Fair. But HoloLens is confusing too, people may thing Urho is HoloLens-only. As an alternative, you may introduce MixedReality namespace branching it to MixedReality.Windows, MixedReality.GoogleDream, MixedReality.Oculus, MixedReality.OpenVR, etc. As a developer, I'd love to have a set of device-agnostic classes for VR app, HMD-driven camera, and controllers/hands. Everything else goes under vendor-specific namespaces.
@vladkol @migueldeicaza How about UrhoSharp.MixedReality.Windows
('HoloLens'->'MixedReality.Windows') ? Quite long but it's not confusing :)
@vladkol all basic/abstract stuff is available via PCL, even HoloApplication class and thus it can be used even in Android + Google Cardboard apps
Let us leave MixedReality entirely out of it.
I am open to ideas in a new realm.
Well, Unity folks went straight with VR, even though it includes AR and MR support too. Introducing new realms may be even more confusing.
I am in no rush to make the change, we can wait until the right name comes. In the meantime, I'll discuss with Egor offline. Keeping the issue open hoping that someone can shed some better light.
Ok, we came up with names.
StereoApplication
replaces HoloApplication
, and SharpReality
is the general namespace for apps that are used in the space.
Mono -> Stereo 👍 Love it!
Is there any support of Urho3D to Cardboard/Daydream ?
Platform grew across different devices (HoloLens, PC) and experiences (AR/VR/Mixed Reality). The umbrella term is Mixed Reality, so it makes sense to rename classes, namespaces and files.