Difference between revisions of "Why use Gideros?"
From GiderosMobile
m (→Description: replaced __TOC__ with __NOTOC__) |
|||
| Line 1: | Line 1: | ||
| − | '''As of 2019, Gideros just out of the box has pretty much everything | + | __NOTOC__ |
| + | |||
| + | '''As of 2019, Gideros, just out of the box, has pretty much everything you need to create apps and games for desktop and mobile:''' | ||
| + | |||
*GLSL Shaders | *GLSL Shaders | ||
*Physics (LiquidFun) | *Physics (LiquidFun) | ||
| Line 13: | Line 16: | ||
*Sockets & real-time multiplayer (PhotonCloud/Noobhub) | *Sockets & real-time multiplayer (PhotonCloud/Noobhub) | ||
*plenty of other plugins built-in | *plenty of other plugins built-in | ||
| + | <br/> | ||
| + | '''Besides that, few more advantages can be mentioned:''' | ||
| − | |||
===Instant on-device testing=== | ===Instant on-device testing=== | ||
| + | |||
===[[Threads|True Multithreading]]=== | ===[[Threads|True Multithreading]]=== | ||
| + | |||
===[[Lua_enhancements|Various Lua enhancements]]=== | ===[[Lua_enhancements|Various Lua enhancements]]=== | ||
For example classic 'getDistance' function performs 5x faster with Gideros' mutation operators then with vanilla Lua code. | For example classic 'getDistance' function performs 5x faster with Gideros' mutation operators then with vanilla Lua code. | ||
| + | |||
===Facebook Instant Games support=== | ===Facebook Instant Games support=== | ||
| + | |||
===Unique async calls system=== | ===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. | 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. | ||
| + | |||
===Built-in Profiler=== | ===Built-in Profiler=== | ||
| + | |||
===Built-in Debugger=== | ===Built-in Debugger=== | ||
| + | |||
===Full assets encryption=== | ===Full assets encryption=== | ||
| + | |||
===Offline builds=== | ===Offline builds=== | ||
You don't have to expose your code and assets to any server and don't depend on internet connection. | You don't have to expose your code and assets to any server and don't depend on internet connection. | ||
| − | ===Fully open-source | + | |
| + | ===Fully free and open-source=== | ||
Revision as of 08:02, 24 May 2019
As of 2019, Gideros, just out of the box, has pretty much everything you need to create apps and games for desktop and mobile:
- GLSL Shaders
- Physics (LiquidFun)
- Meshes
- Particles
- Texturepacks
- Tilemaps
- Blend modes
- Stencil
- IAP/Ads
- JSON
- Skeletal animations (Spine/Dragonbones)
- Sockets & real-time multiplayer (PhotonCloud/Noobhub)
- plenty of other plugins built-in
Besides that, few more advantages can be mentioned:
Instant on-device testing
True Multithreading
Various Lua enhancements
For example classic 'getDistance' function performs 5x faster with Gideros' mutation operators then with vanilla Lua code.
Facebook Instant Games support
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.
Built-in Profiler
Built-in Debugger
Full assets encryption
Offline builds
You don't have to expose your code and assets to any server and don't depend on internet connection.
