5 ms·
plenty of games come to iOS before macOS now. Marzipan means (I think?) you get a lot of the the basics: get a window, setup a gl/metal context, start drawing.
by olliej 8y ago
plenty of games come to iOS before macOS now.
Marzipan means (I think?) you get a lot of the the basics: get a window, setup a gl/metal context, start drawing. That's more or less the entirety of a game's output.
Input then means adding a mouse/keyboard path in addition to touch events and it seems like that's something that should be easy :D
Honestly the effort to setup a GL (and I assume metal) view is kind of annoying on macOS.
- saagarjha 8y agoMarzipan bridges almost every iOS framework (notably UIKit) to macOS. Games tend to not link against these.
- olliej 8y agoSorry, what I was trying to say is that basically all games want to do is get pixels to the screen - they're aren't really using the OS to do anything else: no system UI, etc
- saagarjha 8y agoThat's my point as well: you don't really need Marzipan for this. Putting pixels on the screen using OpenGL is already pretty easy for pretty much every platform.
- olliej 8y agoHaha I’m not saying you need this, I suspect for many devs using marzipan and adding mouse+keyboard handlers is probably less work than setting up a real Mac app. But for games I’m not super concerned as they’re not generally heavy on the OS UI.
- valleyer 8y ago> Marzipan means (I think?) you get a lot of the the basics: get a window, setup a gl/metal context, start drawing. That's more or less the entirety of a game's output. There's a template in Xcode to set all of this up for Metal. It takes about five clicks. For OpenGL, it's as simple as adding an NSOpenGLView to a nib.
- olliej 8y agoBut compare to just recompiling your IOS app to marzipan - you no longer need to have separate paths to initialize the gl context - all you need is the different event handlers. I like to imagine that a point+click name wouldn’t even need that.
- w0utert 8y agoYou're really grossly overstating the effort to port a typical full-screen OpenGL/Metal application over from iOS to macOS or vice versa. It's literally a 1-hour job at most to get a drawing context initialized and up and running even when starting from scratch. Any experencied dev who has done it before just re-uses what's already there and will be done in 10 minutes tops. Obviously you're not even 1% of the way of 'porting your iOS game to macOS' after that, the remaining 99% will be in re-implementing a mouse-based UI, and dealing with the fact that your running on hardware with completely different capabilities and performance profiles. Marzipan will not be able to help with any of that.
- babuskov 8y ago> That's more or less the entirety of a game's output. Output is only a very small subset of a game. You need stuff like UI layout or Scene graph with transitions, tweening, texture atlases handling, animation, etc. A good game engine like Unity or libGDX provides all that without a game programmer having to reinvent the wheel. See for example a list of classes the libGDX API provides: https://libgdx.badlogicgames.com/ci/nightlies/docs/api/ https://libgdx.badlogicgames.com/ci/nightlies/docs/api/