Show HN: A UIKit Game Engine
github.com
github.com
Re-uploaded the GIF file for him, hopefully this one loads for you.
My problems are admittedly very niche, and I will get to see everything when I'm at work tomorrow (if my VPN was working, I could see them now...drats). Thanks for the try though!
BTW, nytimes.com and other whistle-blowers also get blocked.
I'm obviously careful about this, there are good alternatives that work (for now) in china, e.g. Skydive rather than Dropbox. But even I have to we YouTube for video uploads.
There are 2 other videos where hopefully you can see this happening. Or, better yet, you can try it running it yourself on Windows or Mac.
SDL[1] on Windows for instance, falls back to GDL when proper DirectX support isn't available. GDI is what most GUI apps use to draw their elements on Windows. It is akin to UIKit on iOS. But GDI is horribly slow as all the computation is done on the CPU.
In fact, realizing this fact, Microsoft has recently developed Direct2D, which does the computation on the GPU and which regular GUI apps can use to achieve better performance. (BTW, I believe Direct2D is somewhat similar to Cairo 2D.)
[1] Simple DirectMedia Layer -- used by plenty of games to achieve cross-platform compatibility. Most games in the Humble Indie Bundle use this.
UIKit is fantastic for normal UI's and the 'general case' but almost certainly isnt optimised for doing efficient drawing of a large number of sprites / tiles (trading efficiency for flexibility).
Couple years ago I actually wrote my own API compatible version of UIKit but backed by OpenGL , and then extended support for these type of cases. As it was basically a drop in replacement I was able to confirm UIKit (at least at the time) was not very clever or fast when it came to a large view hierarchy. So my fraemwork was optimising for large batch drawing from a single texture mostly which is what you really want in the OP's case.
I should release it one day as open source.. though is all OpenGL 1 so a little outdated on iOS these days.
You definitely should! :-D
You can worry about porting/updating it later. You might even get help in doing so, once you open-source it.
I started with processing TMX files and Texture Packer files, just to see if I could get UIKit to load them. Once I had that working, I added virtual controls, basic dialog, and basic game state.
The performance aspect is just not there. Once you get to a game with a large number of sprites and animations, animations will jitter and glitch. You're really going to be stretching what Core Animation can handle.
What I usually recommend these days is to use Cocos2d for your main game view, but using UIKit for the rest of the interface (menus, score screens, etc.).
With a UIKit engine, you don't have to deal with OpenGL and UIKit fighting for performance.