Difference between revisions of "Loading Order of Lua Files"

From GiderosMobile
(added some more explanations)
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
 
<!-- GIDEROSOBJ:Loading Order of Lua Files -->
 
 
'''Supported platforms:''' [[File:Platform android.png]][[File:Platform ios.png]][[File:Platform mac.png]][[File:Platform pc.png]]<br/>
 
'''Supported platforms:''' [[File:Platform android.png]][[File:Platform ios.png]][[File:Platform mac.png]][[File:Platform pc.png]]<br/>
 
'''Available since:''' Gideros 2020.5<br/>
 
'''Available since:''' Gideros 2020.5<br/>
Line 11: Line 9:
 
</source>
 
</source>
  
'''PS: the path is relative to the file in which you call --!NEEDS:'''
+
'''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.
  
This will tell Gideros to load '''your_file.lua''' before the file containing the above code.
 
  
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:
 
<source lang="lua">
 
<source lang="lua">
 
--!NOEXEC
 
--!NOEXEC
 +
</source>
 +
 +
 +
You can also assign a name to library files:
 +
<source lang="lua">
 +
--!LIBRARY:your_library_name
 
</source>
 
</source>
  
Line 24: Line 28:
 
'''This is very useful if you develop a Lua library that is meant to be used in several projects.'''
 
'''This is very useful if you develop a Lua library that is meant to be used in several projects.'''
  
=== Example ===
+
=== Examples ===
 
<source lang="lua">
 
<source lang="lua">
 +
--!NEEDS:../../tiled/tiled_ellipse.lua
 
--!NEEDS:luashader/luashader.lua
 
--!NEEDS:luashader/luashader.lua
 +
 +
--!LIBRARY:GiderosUI
 +
...
 +
--!NEEDS:(GiderosUI)/uistyle.lua
  
 
local function makeEffect(name,vshader,fshader)
 
local function makeEffect(name,vshader,fshader)
Line 35: Line 44:
 
=== See also ===
 
=== See also ===
 
'''[[Require]]'''
 
'''[[Require]]'''
 
{|-
 
| style="width: 50%; vertical-align:top;"|
 
=== Methods ===
 
| style="width: 50%; vertical-align:top;"|
 
=== Events ===
 
=== Constants ===
 
|}
 
  
 
{{GIDEROS IMPORTANT LINKS}}
 
{{GIDEROS IMPORTANT LINKS}}

Revision as of 03:29, 21 March 2023

Supported platforms: Platform android.pngPlatform ios.pngPlatform mac.pngPlatform pc.png
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

Require