Skip to content
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

Add Oculus Platform SDK bindings #169

Closed
Spasi opened this issue Mar 28, 2016 · 3 comments
Closed

Add Oculus Platform SDK bindings #169

Spasi opened this issue Mar 28, 2016 · 3 comments

Comments

@Spasi
Copy link
Member

Spasi commented Mar 28, 2016

https://developer.oculus.com/documentation/platform/latest/concepts/developer-intro/

@Spasi Spasi added this to the 3.0.x milestone Mar 28, 2016
@huhlig
Copy link

huhlig commented Mar 28, 2016

This seems very out of scope for lwjgl. If included it seems like it should be a separate subproject.

The Oculus Platform is designed to provide you with the infrastructure you need, so you can focus on creating a great game or experience. The Oculus Platform currently provides the following features:

Friend Management—to enable social functionality and increase engagement, this enables players to add friends and find friends that are currently online.
Rooms—your app can create rooms where players gather or you can enable players to create them.
Achievements—you can create trophies, badges, awards, medals, or challenges in your app and Oculus will manage it.
Leaderboards—if your app or experience is competitive, you can create leaderboards to track the top players.
Matchmaking—if players can't find a match, you can help them find available games. The platform supports both standard and skill-based pools.
In-App Purchases—enables you to monetize your games and experiences.
Peer-to-Peer Networking—enables players to communicate directly.

@octylFractal
Copy link
Contributor

I agree with @huhlig about making this a subproject. I think that if LWJGL starts including a lot of bindings then #100 should become a much higher priority.

@ShadowLordAlpha
Copy link

I wouldn't mind having libraries like this though #100 should really be finished first and maybe with it add a set of libraries that are less used and have less work put into them and are not part of the main jar but can be added if they are wanted by the user.

@Spasi Spasi removed this from the 3.?.? milestone Nov 20, 2021
@Spasi Spasi closed this as completed Nov 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants