-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal for the OPPO vendor extension #146
Conversation
An issue (number 1963) has been filed to correspond to this pull request in the internal Khronos GitLab (Khronos members only: KHR:openxr/openxr#1963 ), to facilitate working group processes. This GitHub pull request will continue to be the main site of discussion. |
There are people on the working group who are concerned with your suggested naming (of the component with just We are also making sure that interaction profiles added in vendor extensions (the actual profile path itself) is also decorated with your vendor ID, so that we can remove it to perform any renames needed when/if it is promoted to KHR or core. Also, in the 1.0.27 release we introduced describing interaction profiles additionally in the XML. The spec text is not (yet) generated from that part of the XML, but please add it since tooling is being worked on that uses it. (There is some checking of those entries in (It is OK to force-push over your old branch, you do not need to open a new MR if you rebase or amend commits) |
@rpavlik Thanks for the comments. I updated the pull request with decorated controller name and xml entries. Please check and let me know if there is anything else needed. Thanks |
specification/sources/chapters/extensions/oppo/oppo_controller_interaction.adoc
Outdated
Show resolved
Hide resolved
specification/sources/chapters/extensions/oppo/oppo_controller_interaction.adoc
Show resolved
Hide resolved
specification/sources/chapters/extensions/oppo/oppo_controller_interaction.adoc
Outdated
Show resolved
Hide resolved
specification/sources/chapters/extensions/oppo/oppo_controller_interaction.adoc
Outdated
Show resolved
Hide resolved
@rpavlik Thanks a lot for the detailed review and suggestions. I accepted all suggestions and added some description about the heartrate sensor. Please check and let me know if there is anything to be updated. Thanks a lot |
specification/sources/chapters/extensions/oppo/oppo_controller_interaction.adoc
Outdated
Show resolved
Hide resolved
specification/sources/chapters/extensions/oppo/oppo_controller_interaction.adoc
Show resolved
Hide resolved
specification/sources/chapters/extensions/oppo/oppo_controller_interaction.adoc
Outdated
Show resolved
Hide resolved
@rpavlik I justed modified then entries per your suggestion. If you could help review again and let me know if there is anything else to be updated, it would be greatly appreciated. Thanks |
@rpavlik I'm wondering if there is any update on this PR. Please let us know if there is anything we should do to move this forward. thanks a lot. |
* Decorated name for controller and adding xml entry * Add description about heartbeat on controller * Add /input/thumbstick path * Remove battery path * Add reference to interaction profile in extension * Apply PrettyRegistryXML * Accept suggestions Co-authored-by: Ryan A. Pavlik <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like I missed one correction. I squashed your existing commits into a single one, and added an XML formatting cleanup. Once the license header is added, I can merge this.
specification/sources/chapters/extensions/oppo/oppo_controller_interaction.adoc
Outdated
Show resolved
Hide resolved
…_interaction.adoc Co-authored-by: Ryan A. Pavlik <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
Released and published in 1.0.28! |
Recreate pull request for OPPO vendor extension proposal to rebase commits to latest releases / staging.
The original pull request was in #144
@rpavlik @Wallbraker It seems like there is a new release last week and I rebase the unmerged part of work from pr144 to here. Let me know if there is something I could do to move this forward.
Thanks a lot.