4 ms·
Depends on the use case, but generally right now it goes like this: if it can be done as a high-density Games/Games-like GUI or some kind of interactive media/c
by mmjaa 9y ago
Depends on the use case, but generally right now it goes like this: if it can be done as a high-density Games/Games-like GUI or some kind of interactive media/content display, which 99% of modern apps are: I use MOAI. If it has to be a Business GUI with normal looking things for whatever platform: Haxe. If its a quick tool for lab/workshop: libUI.
These approaches all have their pluses/minuses too, of course, but I have found that by exercising platform chops, the workload is minimal once the homework is done.
I find it utterly pleasant to code something up in Lua, ship the bins to the devices directly, and see the same thing on every machine. Even between libui and MOAI projects there are chances to share data - i.e. use a lab tool written in libUI to generate content consumed by the game engine...
Its like the web, only completely the opposite: you're not targeting someone else app (the web client), but rather running your own client (app).
- eli_gottlieb 9y agoI think I may have to learn Haxe. Which MOAI are you referring to? The library I found was a mobile-games engine.
- mmjaa 9y agoMOAI SDK: https://github.com/moai/moai-community https://github.com/moai/moai-community MOAI DEV: https://github.com/moai/moai-dev https://github.com/moai/moai-dev Warning: some effort is required, but .. once you get the hosts running on all platform targets (Win/MacOS/Linux/iOS/Android/&etc.), the true value shines and cross-platform nirvana can be attained. Bonus points for having Hanappe/Flower and/or whatever else involved as a 'higher layer' UI management abstraction on top of the GL pipeline ..