Proposed Message Standardisation
#9
Another solution comes to mind, it would be less complicated for Lua devs, but it might get a bit involved for the C++ devs.
If there was a possibility for a plugin to load a specified Lua file from another plugin, we could just put all those messaging functions along with the config into a single Lua file inside Core and then have each plugin load that file by name ("../Core/Messaging.lua"). No need for the GetPlugin() / Call(FnName, ...) trickery, Lua could call those functions directly.
Reply
Thanks given by:


Messages In This Thread
Proposed Message Standardisation - by tigerw - 08-08-2013, 02:45 AM
RE: Proposed Message Standardisation - by bearbin - 08-08-2013, 02:47 AM
RE: Proposed Message Standardisation - by tigerw - 08-08-2013, 03:11 AM
RE: Proposed Message Standardisation - by tigerw - 08-08-2013, 03:22 AM
RE: Proposed Message Standardisation - by xoft - 08-08-2013, 06:36 AM
RE: Proposed Message Standardisation - by bearbin - 08-08-2013, 06:47 AM
RE: Proposed Message Standardisation - by xoft - 08-08-2013, 06:52 AM
RE: Proposed Message Standardisation - by xoft - 02-06-2014, 09:06 PM
RE: Proposed Message Standardisation - by tigerw - 02-07-2014, 04:33 AM
RE: Proposed Message Standardisation - by bearbin - 02-07-2014, 05:30 AM
RE: Proposed Message Standardisation - by xoft - 02-07-2014, 07:24 AM
RE: Proposed Message Standardisation - by xoft - 02-07-2014, 07:56 AM
RE: Proposed Message Standardisation - by xoft - 02-07-2014, 08:44 PM
RE: Proposed Message Standardisation - by xoft - 02-08-2014, 12:27 AM
RE: Proposed Message Standardisation - by tigerw - 02-08-2014, 04:14 AM
RE: Proposed Message Standardisation - by bearbin - 02-08-2014, 04:40 AM
RE: Proposed Message Standardisation - by tigerw - 02-08-2014, 07:10 AM
RE: Proposed Message Standardisation - by tigerw - 02-08-2014, 08:04 AM
RE: Proposed Message Standardisation - by xoft - 02-08-2014, 08:37 AM
RE: Proposed Message Standardisation - by tigerw - 02-09-2014, 07:09 AM



Users browsing this thread: 5 Guest(s)