URL: GameFramework

Commit: dc1ea7ccced00c834437a3f347b5dd72549bf36f

Modifications:

• Add necessary game objects and components in GameFramework.unity.
  • Tick procedures on Procedure Component but still select Procedure Launch with which to run the project.
  • Select Package mode on Resource Component so it won't check for resource update/download.
• Git ignore AssetBundleBuilder.xml since its output directory field depends on your own folder structure.

URL: Tolua

Commit: ea55728d57473bcf1a36e818f9e81bb1be0a0f25

Modifications:

• Exclude LuaJit for now.
• Remove the examples.
• Copy Unity 5.x meta files to the right locations.
• Change path constants in CustomSettings.cs and LuaConst.cs. (See comments like // UGF)
• Add label 'LuaScript' for lua files so that they could be built into assetbundles. (Could be done by the editor script AssetLabelEnsurer.cs.

• LuaComponent extends GameFrameworkComponent and provides features of loading and running Lua scripts.
• CustomLuaLoader hacks ToLua's file reading mechanism so that asset bundles built by Game Framework will work.

• Assets/Scripts/ProcedureXXX.cs
• Assets/LuaScripts/XXX.lua

If you tick Editor resource mode on the Base Component of Game Framework, CustomLuaLoader reads the Lua files on the disk. Otherwise, the project, when launched, first loads the asset bundles that contain Lua scripts so that CustomLuaLoader gets the script contents later from the loaded (and hence cached) texts.

Currently .lua files will be recoginized by Unity as default assets, rather than text assets, so that you cannot load them directly from some asset bundle. So AssetBundleBuilder.cs add .bytes extension to the file names before building asset bundles and revert them afterwards.