aboutsummaryrefslogtreecommitdiffstatshomepage
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--ClientHamr/GuiLua/README13
1 files changed, 7 insertions, 6 deletions
diff --git a/ClientHamr/GuiLua/README b/ClientHamr/GuiLua/README
index a456cee..e586318 100644
--- a/ClientHamr/GuiLua/README
+++ b/ClientHamr/GuiLua/README
@@ -229,9 +229,10 @@ previous section is built on top of Thing. Things are stored in
229ThingSpace, which is a BonsaiTree of LeafLike Things. Java's version of 229ThingSpace, which is a BonsaiTree of LeafLike Things. Java's version of
230multiple inheritance was used. Commands are a Thing. 230multiple inheritance was used. Commands are a Thing.
231 231
232ThingSpace is per users session. classCache stores ... , command stores 232ThingSpace is per users session. classCache stores cached class
233commands, module stores loaded modules, param stores variables and their 233lookukps, command stores commands, module stores loaded modules, param
234values, widget stores widgets and their value / state. 234stores variables and their values, widget stores widgets and their value
235/ state.
235 236
236Skanglet is a generated mapping between actual methods / variables in a 237Skanglet is a generated mapping between actual methods / variables in a
237class, and skang. Each method or variable that ends up in the skanglet 238class, and skang. Each method or variable that ends up in the skanglet
@@ -261,14 +262,14 @@ called ends with "return someTable". See LuaLSL for an example. This
261package is actually run, so it can figure out what to put in the 262package is actually run, so it can figure out what to put in the
262returned table. So for instance it could use inlined methods and such - 263returned table. So for instance it could use inlined methods and such -
263 264
264local skang = require skang 265local skang = require('skang')
265local result = {}; 266local result = {};
266result.author = 'onefang' 267result.author = 'onefang'
267result.version = '0.72 alpha 2004-11-19 16:28:00' 268result.version = '0.72 alpha 2004-11-19 16:28:00'
268local foo 269local foo
269-- The first argument would be the name of a local variable / method. Which could be accessed via _G? 270-- The first argument would be the name of a local variable / method. Which could be accessed via _G?
270-- Not sure if we could use a global foo, AND use it directly. 271-- Not sure if we could use a global foo, AND use it directly.
271result.foo = skang.newParam(foo, "Required", "Shortcut", "Default", "Help text") 272result.foo = skang.newParam('foo', "Required", "Shortcut", "Default", "Help text")
272result.func = skang.newCommand('arg1_type,arg2_type', 'Help Text', function (arg1, arg2) 273result.func = skang.newCommand('arg1_type,arg2_type', 'Help Text', function (arg1, arg2)
273... 274...
274end) 275end)
@@ -307,7 +308,7 @@ based on name. Not even a way to get to the public Eo_Class_Description
307from the opaque Eo_Class. 308from the opaque Eo_Class.
308 309
309Eo_Class_Description is at least public. It includes 310Eo_Class_Description is at least public. It includes
310Eo_Op_Description's and Eo_Evenet_Description's. Eo_Op_ and Eo_Event_ 311Eo_Op_Description's and Eo_Event_Description's. Eo_Op_ and Eo_Event_
311include the name and documentation of the op / event. The macro used to 312include the name and documentation of the op / event. The macro used to
312generate Eo_Op_ does NOT pass the name, just the ID number as a string. 313generate Eo_Op_ does NOT pass the name, just the ID number as a string.
313There is also Eo_Op_Func_Description, which does not include a name, it 314There is also Eo_Op_Func_Description, which does not include a name, it