Difference between revisions of "Why use Gideros?"
From GiderosMobile
(Created page with "Here there should be a list of reason to use Gideros.") |
|||
| Line 1: | Line 1: | ||
| − | + | '''As of 2019, Gideros just out of the box has pretty much everything that can be needed for creating even top tier mobile games:''' | |
| + | *GLSL Shaders | ||
| + | *Physics (LiquidFun) | ||
| + | *Meshes | ||
| + | *Particles | ||
| + | *Texturepacks | ||
| + | *Tilemaps | ||
| + | *Blend modes | ||
| + | *Stencil | ||
| + | *IAP/Ads | ||
| + | *JSON | ||
| + | *Skeletal animations (Spine/Dragonbones) | ||
| + | *Sockets & real-time multiplayer (PhotonCloud/Noobhub) | ||
| + | |||
| + | |||
| + | '''Besides that, few more advantages can be mentioned:''' | ||
| + | ===Instant on-device testing=== | ||
| + | ===True Multithreading=== | ||
| + | ===Built-in Profiler=== | ||
| + | ===Built-in Debugger=== | ||
| + | ===[[Lua_enhancements|Various Lua enhancements]]=== | ||
| + | For example classic 'getDistance' function performs 5x faster with Gideros' mutation operators then with vanilla Lua code. | ||
| + | ===Unique async calls system=== | ||
| + | Besides regular enterframe callbacks, we can write a program "sequentially", like we would have written for the Commodore 64 or DOS PC, ie assuming our program has complete control of the computer. | ||
Revision as of 06:16, 11 January 2019
As of 2019, Gideros just out of the box has pretty much everything that can be needed for creating even top tier mobile games:
- GLSL Shaders
- Physics (LiquidFun)
- Meshes
- Particles
- Texturepacks
- Tilemaps
- Blend modes
- Stencil
- IAP/Ads
- JSON
- Skeletal animations (Spine/Dragonbones)
- Sockets & real-time multiplayer (PhotonCloud/Noobhub)
Besides that, few more advantages can be mentioned:
Instant on-device testing
True Multithreading
Built-in Profiler
Built-in Debugger
Various Lua enhancements
For example classic 'getDistance' function performs 5x faster with Gideros' mutation operators then with vanilla Lua code.
Unique async calls system
Besides regular enterframe callbacks, we can write a program "sequentially", like we would have written for the Commodore 64 or DOS PC, ie assuming our program has complete control of the computer.
