1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
|
GuiLua is basically a redo of my ancient Java based matrix-RAD system,
but using Lua and EFL. The ultimate goal is for the various ClientHamr
parts to be able to either host their own UI, or have it hosted in the
in world 3D window. Matrix-RAD's ability to run either server or client
side, with no change to the code, is great for this sort of thing. If I
can manage the ability to "tear off" windows, in other words, pull them
out of the 3D window to be real windows, then that's something people
have been asking for from LL forever.
Stdin/out might be good to use. Extantz starts up "client" programs,
with a "use stdin/out" argument, the clients pass skang commands (open
this internal window with these widgets) to extantz through their
stdout, extantz passes skang commands (these values where set by these
widgets) back through their stdin. With no "use stdin/out" argument,
the programs host their own UI. Perhaps extantz can just pass the UI
skang stuff back to the client, which will mean "draw your own window",
to support the "tear off" feature. If I remember skang had suitable
serialization stuff to support this. Lua does anyway. B-)
Naturally, like matrix-RAD, all this UI stuff can happen across a socket
as well as through stdin/out. Should be transparent to the user proggy.
I can redesign skang to be more Lua like, to take advantage of Lua's
meta language capabilities. Since no one used skang anyway, I can get
away with this. Also should add a Lua friendly wrapper around nails, so
that addons for Extantz can be supplied entirely as Lua scripts. In
other words, LuaSL scripts. On top of all that, should also allow
access to the Edje Lua stuff I've already written, but drag it outside
of an edje file.
This pretty much means that GuiLua should be a shared library, coz in
the ClientHamr use case, several programs are gonna be using it at once.
Should also be separate modules for development stuff like the skin
editor, which could be just another proggy using GuiLua.
Initially GuiLua can wrap elementary / evas, with the goal of wrapping
NAWS, just like matrix-RAD was originally planned. Then I can put off
writing NAWS for another decade. lol
Design notes
------------
Edje Lua does not wrap elementary widgets, and is not likely to due to
elementary being compiled after edje. Smart objects and swallows
probably can deal with that though, I'm not familiar enough with them to
know. Eo on the other hand allegedly offers introspection, which was
always the corner stone of matrix-RAD. So access to elementary widgets
via Eo might be possible. That's kinda the entire hook I'm hoping will
help to make matrix-RAD style stuff work as well as it did there.
Edje Lua is restricted to scripts in edje files, AND sandboxed to those
edje files as well. We want to step outside that sandbox, and run stand
alone Lua scripts, as well as GuiLua / LuaSL scripts internal to
extantz. Some merging of LUaSL and Edje Lua, leaving room for GuiLua,
would be great, but I might have to convince Raster. Note that the
socket idea wont work in sandboxed edje Lua scripts, unless the socket
is in C code, that uses edje messages as the internal transport.
Just so it's easier to find, I'll repeat a bit from the Enlightenment
mailing list here, the result of discussions with raster and other
interested parties -
"First step is to write edje functions for generically bundling up one
or more Lua tables into a message, sending that message, then unpacking
it again. This will be able to be done from edje, from C, and from Lua
directly. Perhaps adding that as one more edje messege type. This is
for sending Lua tables between threads. A later addition will be to
send them through the 'net, probably as eet.
Host apps can register arbitrary functions with edje Lua, using a more
generic version of the code I already wrote for letting edje register
lua functions. These host functions are by default not thread safe.
Edje puts a wrapper function around the host app, and registers that
wrapper function with Lua. The wrapper function, when called from Lua,
does this -
ecore_thread_main_loop_begin();
call the host app callback();
ecore_thread_main_loop_end();
The first alternative, which the host app must request, is for the
wrapper function to use the table message functions to marshal the
arguments, send it to the main thread, wait for the response (or do
something else), then unmarshal the result before sending it back to
Lua.
The second alternative, which the host app must REALLY request, is for
the host app to say "I'm REALLY going out of my way to be threadsafe,
just call me direct". No edje wrapper function, BUT the host app still
has to use edje to register this function.
The first two might be done this way -
host_cb = edje_lua2_functions_add(...);
edje_lua2_function_marshal_set(host_cb, function);
The last one could be -
host_cb = edje_lua2_threadsafe_function_add(...);
Note the difference between _functions_ and _function_. The first call
registers an entire metatable full of functions, in the same way that
edje does for it's functions. These are the default sort of
functions. The second call references one of those previously
registered functions, and makes it marshal arguments and results. The
third one registers a single function, but it could be added to an
existing metatable registered by the first function."
and -
"We are actually half way there. Anticipating that there would be way
more edje and evas stuff to add to the edje Lua API in the future, I
created generic wrapper functions to make that easier. Implementing
this would mean exposing those static functions, and writing more of
these generic wrapper stuff.
Lua already provides a mechanism for this sort of thing, but we
currently sandbox that out. We can provide a very limited version of
the package module, that only lets the Lua script load modules that the
host app explicitly provides. This keeps edje Lua in it's strictly
sandboxed state."
Raster also wants to thread lots of edje, likely including having edje
Lua scripts as threads, much like I'm doing with LuaSL already. Plus
LuaJIT SPEEEEED!!. B-)
skang vs edje vs LL shit
------------------------
EDJE
Verbose, complex.
Used to place and decorate widget parts.
Can be used to place entire widgets through externals and swallows.
Basic parts relative to each other.
Signals and messages.
Embryo scripts.
Lua scripts (sandboxed).
SKANG
Tight, simple.
Used to place widgets, and describe actions.
Can include some really basic scripting.
Widgets in a fixed position, but included stuff for relative placement in the TODO.
Automated associations between widget name and variable (and method?) via introspection.
Actions.
Looks (could easily be extended to edje groups).
Extensible.
Can be used to pass values around.
LL SHIT
Verbose, even worse, XML, more crap than is needed.
Menus.
Windows with widgets relative to each other.
Basically nested rectangles.
Manual association of widgets to methods.
Can include tool tip string, enabled, visible, hover cursor, bounding rectangle?, mouse opaque?, tab groups, font (name, size, style, and alignment).
More stuff, typically hidden in the OO somewhere. sigh
Generally uses fixed image and colour names, which skins overide.
Skins can also overide the XML files.
Translations provide override XML files that need only override the text bits.
old notes
---------
See if it's possible to disable the Emerald/Phoenix/Firestorm LSL bridge
when connecting to OpenSim. Actually, they finally came to their senses
and support OpenSim now, so that should be sorted already.
|
