OUYA Development Kit for ZGE
Posted: Sun Apr 13, 2014 4:50 pm
I'm pleased to announce that ZGE supports now also OUYA In-App Purchasing (IAP) and OUYA Storage functionality. Everything this is implemented in the ZgeOuya library which represents a facade to the OUYA Development Kit (ODK). The ZgeOuya is implemented as a native library written in C++ accompanied with a Java code used to interface ODK. This "architecture" allows more flexible maintenance and enables smaller changes when ODK will change in future.
The project is maintained at the Google Code page http://code.google.com/p/zgeouya. You can find the description of how to use ZgeOuya library in ZGE projects, source code and also relevant links there. The compiled version of the ZgeOuya library, demo projects and tools can be found at the download page.
The current version contains all the necessary parts of IAP but also something more, e.g. textual descriptions of the available products I used for testing, but are not really necessary for game development.
My future plans:
1. Add OUYA-related libraries (ZgeOuya and Android gamepad) to the "Add from library..." context menu in ZGE.
2. Optionally: create a new ZApplication.AndroidSdk option for OUYA which would extend the "4.1 (API Level 16)" by ZgeOuya.java file.
3. Allow to load the game signing key (key.der file) as file. So the developer will just copy the key.der file to some location; e.g., assets folder or res/raw folder.
4. Simplify the API by removing unnecessary parameters. For instance, if a game knows about its products, it is not necessary to load the product info from the server, because is the purchase is being done the OUYA dialog shows all the necessary information anyway (name, description, price).
Please note that you can use these features only if you are registered OUYA developer; i.e., you have UUID, access to defining products, games, etc.
If you do not want to sell your applications, you do not need this library; just compile your OUYA applications with ZApplication.AndroidSdk option set to "4.1 (API Level 16)" and use the "Android gamepad" library which provides you codes for OUYA controller buttons and axes. See this topic for more information about supporting game pads for Android (including OUYA Controller) in ZGE.
The project is maintained at the Google Code page http://code.google.com/p/zgeouya. You can find the description of how to use ZgeOuya library in ZGE projects, source code and also relevant links there. The compiled version of the ZgeOuya library, demo projects and tools can be found at the download page.
The current version contains all the necessary parts of IAP but also something more, e.g. textual descriptions of the available products I used for testing, but are not really necessary for game development.
My future plans:
1. Add OUYA-related libraries (ZgeOuya and Android gamepad) to the "Add from library..." context menu in ZGE.
2. Optionally: create a new ZApplication.AndroidSdk option for OUYA which would extend the "4.1 (API Level 16)" by ZgeOuya.java file.
3. Allow to load the game signing key (key.der file) as file. So the developer will just copy the key.der file to some location; e.g., assets folder or res/raw folder.
4. Simplify the API by removing unnecessary parameters. For instance, if a game knows about its products, it is not necessary to load the product info from the server, because is the purchase is being done the OUYA dialog shows all the necessary information anyway (name, description, price).
Please note that you can use these features only if you are registered OUYA developer; i.e., you have UUID, access to defining products, games, etc.
If you do not want to sell your applications, you do not need this library; just compile your OUYA applications with ZApplication.AndroidSdk option set to "4.1 (API Level 16)" and use the "Android gamepad" library which provides you codes for OUYA controller buttons and axes. See this topic for more information about supporting game pads for Android (including OUYA Controller) in ZGE.