diff options
Diffstat (limited to '')
-rw-r--r-- | ClientHamr/GuiLua/skang.lua | 52 |
1 files changed, 52 insertions, 0 deletions
diff --git a/ClientHamr/GuiLua/skang.lua b/ClientHamr/GuiLua/skang.lua index 25aedac..1b0a199 100644 --- a/ClientHamr/GuiLua/skang.lua +++ b/ClientHamr/GuiLua/skang.lua | |||
@@ -1,3 +1,55 @@ | |||
1 | -- TODO - This should be in C, but so far development has been quite rapid doing it in Lua. | ||
2 | --[[ | ||
3 | In here should live all the internals of matrix-RAD that don't | ||
4 | specifically relate to widgets. This would include the "window" though. | ||
5 | |||
6 | skang.module(Evas) | ||
7 | skang.module(Elementary) | ||
8 | skang.skang('some/skang/file.skang') | ||
9 | |||
10 | This package is also what "apps" that use the system should "inherit" | ||
11 | from, in the same way matrix-RAD apps did. Skang "apps" could be Lua | ||
12 | modules. They could also be C code, like the extantz modules are likely | ||
13 | to be. Skang "apps" would automatically be associated with skang files | ||
14 | of the same name. | ||
15 | |||
16 | For a .skang file, the skang command (written in C) would strip off the | ||
17 | first line, add the two implied lines, then run it as Lua. The | ||
18 | skang.load() command would do the same. So that skang C comand would | ||
19 | just pass the file name to skang.load() in this library. B-) | ||
20 | |||
21 | The old skang argument types are - | ||
22 | |||
23 | {"name", "java.lang.String"}, | ||
24 | {"action", "java.lang.String"}, | ||
25 | {"type", "java.lang.String"}, | ||
26 | {"data", "java.lang.String"}, | ||
27 | {"URL", "java.lang.String"}, | ||
28 | {"file", "java.lang.String"}, | ||
29 | {"method", "java.lang.String"}, | ||
30 | {"lx", "java.lang.String"}, | ||
31 | {"ly", "java.lang.String"}, | ||
32 | {"lw", "java.lang.String"}, | ||
33 | {"lh", "java.lang.String"}, | ||
34 | {"normal", "java.lang.String"}, | ||
35 | {"ghost", "java.lang.String"}, | ||
36 | {"active", "java.lang.String"}, | ||
37 | {"toggle", "java.lang.String"}, | ||
38 | {"boolean","java.lang.Boolean"}, | ||
39 | {"number", "java.lang.Integer"}, | ||
40 | {"int", "java.lang.Integer"}, | ||
41 | {"x", "java.lang.Integer"}, | ||
42 | {"y", "java.lang.Integer"}, | ||
43 | {"w", "java.lang.Integer"}, | ||
44 | {"h", "java.lang.Integer"}, | ||
45 | {"r", "java.lang.Integer"}, | ||
46 | {"g", "java.lang.Integer"}, | ||
47 | {"b", "java.lang.Integer"}, | ||
48 | {"alpha", "java.lang.Integer"}, | ||
49 | {"acl", "net.matrix_rad.security.ACL"}, | ||
50 | ]] | ||
51 | |||
52 | |||
1 | -- Trying to capture best practices here for creating modules, especially since module() is broken and deprecated. | 53 | -- Trying to capture best practices here for creating modules, especially since module() is broken and deprecated. |
2 | 54 | ||
3 | -- Wrapping the entire module in do .. end helps if people just join a bunch of modules together, which apparently is popular. | 55 | -- Wrapping the entire module in do .. end helps if people just join a bunch of modules together, which apparently is popular. |