Difference between revisions of "Loading Order of Lua Files"
From GiderosMobile
m (Text replacement - "</source>" to "</syntaxhighlight>") |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 5: | Line 5: | ||
=== Description === | === Description === | ||
You can now implement Gideros Code Dependency by code instead of Gideros project setting. | You can now implement Gideros Code Dependency by code instead of Gideros project setting. | ||
| − | < | + | <syntaxhighlight lang="lua"> |
--!NEEDS:your_file.lua | --!NEEDS:your_file.lua | ||
| − | </ | + | </syntaxhighlight> |
'''PS: the path is relative to the file in which you call --!NEEDS:''' (unless your path begins with a /) | '''PS: the path is relative to the file in which you call --!NEEDS:''' (unless your path begins with a /) | ||
| Line 15: | Line 15: | ||
The other Gideros Code Dependency you can implement by code is the exclude file. To tell Gideros the file should not be executed/parsed right on start but will be loaded through a require or a loadfile command, you can write: | The other Gideros Code Dependency you can implement by code is the exclude file. To tell Gideros the file should not be executed/parsed right on start but will be loaded through a require or a loadfile command, you can write: | ||
| − | < | + | <syntaxhighlight lang="lua"> |
--!NOEXEC | --!NOEXEC | ||
| − | </ | + | </syntaxhighlight> |
You can also assign a name to library files: | You can also assign a name to library files: | ||
| − | < | + | <syntaxhighlight lang="lua"> |
--!LIBRARY:your_library_name | --!LIBRARY:your_library_name | ||
| − | </ | + | </syntaxhighlight> |
| Line 29: | Line 29: | ||
=== Examples === | === Examples === | ||
| − | < | + | <syntaxhighlight lang="lua"> |
--!NEEDS:../../tiled/tiled_ellipse.lua | --!NEEDS:../../tiled/tiled_ellipse.lua | ||
--!NEEDS:luashader/luashader.lua | --!NEEDS:luashader/luashader.lua | ||
| + | |||
--!LIBRARY:GiderosUI | --!LIBRARY:GiderosUI | ||
| + | ... | ||
| + | --!NEEDS:(GiderosUI)/uistyle.lua | ||
local function makeEffect(name,vshader,fshader) | local function makeEffect(name,vshader,fshader) | ||
... | ... | ||
end | end | ||
| − | </ | + | </syntaxhighlight> |
=== See also === | === See also === | ||
Latest revision as of 14:30, 13 July 2023
Supported platforms: 
Available since: Gideros 2020.5
Description
You can now implement Gideros Code Dependency by code instead of Gideros project setting.
--!NEEDS:your_file.lua
PS: the path is relative to the file in which you call --!NEEDS: (unless your path begins with a /)
This will tell Gideros to load your_file.lua before the file containing the above code.
The other Gideros Code Dependency you can implement by code is the exclude file. To tell Gideros the file should not be executed/parsed right on start but will be loaded through a require or a loadfile command, you can write:
--!NOEXEC
You can also assign a name to library files:
--!LIBRARY:your_library_name
This is very useful if you develop a Lua library that is meant to be used in several projects.
Examples
--!NEEDS:../../tiled/tiled_ellipse.lua
--!NEEDS:luashader/luashader.lua
--!LIBRARY:GiderosUI
...
--!NEEDS:(GiderosUI)/uistyle.lua
local function makeEffect(name,vshader,fshader)
...
end
See also
