aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/docs
diff options
context:
space:
mode:
authorDavid Walter Seikel2015-07-09 04:13:13 +1000
committerDavid Walter Seikel2015-07-09 04:13:13 +1000
commit88a9790f848d15d4053288655057994e06d37224 (patch)
tree2e2a677b17380b25fc2a703e513f400e6bb4f000 /docs
parentDocument crazy idea I had for implementing Skang's _123 via metatables. (diff)
downloadSledjHamr-88a9790f848d15d4053288655057994e06d37224.zip
SledjHamr-88a9790f848d15d4053288655057994e06d37224.tar.gz
SledjHamr-88a9790f848d15d4053288655057994e06d37224.tar.bz2
SledjHamr-88a9790f848d15d4053288655057994e06d37224.tar.xz
Fix some typoes, and white space.
Diffstat (limited to '')
-rw-r--r--docs/ClientHamr/README.GuiLua18
1 files changed, 9 insertions, 9 deletions
diff --git a/docs/ClientHamr/README.GuiLua b/docs/ClientHamr/README.GuiLua
index 3d4bb1c..55c7fa4 100644
--- a/docs/ClientHamr/README.GuiLua
+++ b/docs/ClientHamr/README.GuiLua
@@ -5,7 +5,7 @@ similar names, it's not exactly the same. It's more accurate to say
5this is in the spirit of matrix-RAD. 5this is in the spirit of matrix-RAD.
6 6
7The ultimate goal is for the various ClientHamr parts to be able to 7The ultimate goal is for the various ClientHamr parts to be able to
8either host their own UI, or have it hosted in the in world 3D window. 8either host their own UI, or have it hosted in the in world 3D window.
9Matrix-RAD's ability to run either server or client side, with no change 9Matrix-RAD's ability to run either server or client side, with no change
10to the code, is great for this sort of thing. If I can manage the 10to the code, is great for this sort of thing. If I can manage the
11ability to "tear off" windows, in other words, pull them out of the 3D 11ability to "tear off" windows, in other words, pull them out of the 3D
@@ -34,7 +34,7 @@ access to the Edje Lua stuff I've already written, but drag it outside
34of an edje file. 34of an edje file.
35 35
36This pretty much means that GuiLua should be a shared library, coz in 36This pretty much means that GuiLua should be a shared library, coz in
37the ClientHamr use case, several programs are gonna be using it at once. 37the ClientHamr use case, several programs are gonna be using it at once.
38Should also be separate modules for development stuff like the skin 38Should also be separate modules for development stuff like the skin
39editor, which could be just another proggy using GuiLua. 39editor, which could be just another proggy using GuiLua.
40 40
@@ -56,7 +56,7 @@ probably can deal with that though, I'm not familiar enough with them to
56know. Eo on the other hand allegedly offers introspection, which was 56know. Eo on the other hand allegedly offers introspection, which was
57always the corner stone of matrix-RAD. So access to elementary widgets 57always the corner stone of matrix-RAD. So access to elementary widgets
58via Eo might be possible. That's kinda the entire hook I'm hoping will 58via Eo might be possible. That's kinda the entire hook I'm hoping will
59help to make matrix-RAD style stuff work as well as it did there. 59help to make matrix-RAD style stuff work as well as it did there.
60Apparently when they promised introspection with Eo, they meant compile 60Apparently when they promised introspection with Eo, they meant compile
61time, not run time. 61time, not run time.
62 62
@@ -75,7 +75,7 @@ interested parties -
75"First step is to write edje functions for generically bundling up one 75"First step is to write edje functions for generically bundling up one
76or more Lua tables into a message, sending that message, then unpacking 76or more Lua tables into a message, sending that message, then unpacking
77it again. This will be able to be done from edje, from C, and from Lua 77it again. This will be able to be done from edje, from C, and from Lua
78directly. Perhaps adding that as one more edje messege type. This is 78directly. Perhaps adding that as one more edje message type. This is
79for sending Lua tables between threads. A later addition will be to 79for sending Lua tables between threads. A later addition will be to
80send them through the 'net, probably as eet. 80send them through the 'net, probably as eet.
81 81
@@ -141,7 +141,7 @@ Skang notes
141----------- 141-----------
142 142
143So, what will this variation of skang look like? For a start, the 143So, what will this variation of skang look like? For a start, the
144syntax will have to be more Lua like, so that's a real basic change. 144syntax will have to be more Lua like, so that's a real basic change.
145Can't use a space as an argument separator, Lua allows only ',' and 145Can't use a space as an argument separator, Lua allows only ',' and
146';'. Strings can still use single or double quotes. 146';'. Strings can still use single or double quotes.
147 147
@@ -168,11 +168,11 @@ foo = widget.label(0, "otherWidget+0.1", 0.5, 0, 'Text goes here")
168While failing to fall asleep, I had another idea, though not sure how 168While failing to fall asleep, I had another idea, though not sure how
169feasible it is just yet. _123 could use a metatable thingy at the 169feasible it is just yet. _123 could use a metatable thingy at the
170lowest level, and just translates that to a value, the value being a 170lowest level, and just translates that to a value, the value being a
171number. Or something hand wavey like that. lol 171number. Or something hand wavy like that. lol
172 172
173In skang.lua _M is the modules table, and it's a local, it's also a 173In skang.lua _M is the modules table, and it's a local, it's also a
174proxy table. So _M's metatable's __index could check if it's a _123, 174proxy table. So _M's metatable's __index could check if it's a _123,
175then return the 123 as the value. As a bonus, we could do arithmatic 175then return the 123 as the value. As a bonus, we could do arithmetic
176via this metatable. 176via this metatable.
177 177
178"widget" would be a table with functions for dealing with widgets. It 178"widget" would be a table with functions for dealing with widgets. It
@@ -212,7 +212,7 @@ foo = 'bar' -- Using the metatable to override '=' to set the actual value of th
212bar = foo -- The reverse of the above. Though perhaps these can't be done? 212bar = foo -- The reverse of the above. Though perhaps these can't be done?
213foo = foo .. 'stuff' .. 'more stuff' .. 'another line of the dropdown or whatever' 213foo = foo .. 'stuff' .. 'more stuff' .. 'another line of the dropdown or whatever'
214 214
215OK, first two can't be done, metatable only overides that for table elements. The third one can only be (I might be wrong there) - 215OK, first two can't be done, metatable only overrides that for table elements. The third one can only be (I might be wrong there) -
216 216
217foo.value = 'stuff' .. 'more stuff' 217foo.value = 'stuff' .. 'more stuff'
218foo.value = foo.value .. 'another line of the dropdown or whatever' 218foo.value = foo.value .. 'another line of the dropdown or whatever'
@@ -240,7 +240,7 @@ local other = require('otherPackageName')
240skang.clear 240skang.clear
241skang.window(200, 200, "G'day planet.") 241skang.window(200, 200, "G'day planet.")
242quitter = widget.button('Quit', 0.5, 0.5, 0.5, 0.5) 242quitter = widget.button('Quit', 0.5, 0.5, 0.5, 0.5)
243quitter:action('quit') -- 'quit' is looked up in ThingSpcae.commands, and translated into the Lua 'skang.quit()'. 243quitter:action('quit') -- 'quit' is looked up in ThingSpace.commands, and translated into the Lua 'skang.quit()'.
244other.foo = 'stuff' 244other.foo = 'stuff'
245this.bar = other.foo 245this.bar = other.foo
246 246