pmprog
DNF (Did Not Finish)
- Joined
- Apr 25, 2011
- Messages
- 4,150
I understand what you're saying, but surely if the developer writes their own "DownloadAndConvert" function, that will be compiled within their app, so that's not something you need to implement. However, if that calls Java.Network.Http.Download and Java.Graphics.Bitmaps.Load (Namespaces are made up, as I don't know the libraries), then you'd only have to implement them once, and any other games that download, or load bitmaps will call the same Java functions?- To call library functions that only exist in Java (getting information about the device perhaps)
- To call functions from a third party SDK, where said SDK only exists for Java (loads of examples of this, like Scoreloop, Flurry, luckily these two specific examples can mainly be stubbed out)
- To avoid having to write lots of native code (for example: from Java it is pretty easy to download a file and convert it to a .PNG, it would be a lot more work from C/C++ so a developer may write a 'DownloadAndConvert' Java function, which subsequently would need to be added to an apkenv module)
As it is down to each developer to choose what functions to write in Java, there isn't a simple 'one API fits all' that can be implemented into a module and make all games work. There will probably be a lot of similar things being done on the Java, but even if it is identical, the function name/parameters may well be different, so some amount of work is still required.
So then, if they use a Java wrapper for SDL for example, well, surely that would require a module for the SDL wrapper, and that would be reusable across multiple applications that use Java/SDL
Or am I still missing something?