aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/ClientHamr/GuiLua/README
diff options
context:
space:
mode:
authorDavid Walter Seikel2013-02-02 21:22:58 +1000
committerDavid Walter Seikel2013-02-02 21:22:58 +1000
commit7d48bd9a65bc5fe92ede80ea7fc49e7526d07c7a (patch)
tree10f5afed6d45ceb28bbd08d97151141c6b60eff9 /ClientHamr/GuiLua/README
parentAdded GuiLua stub. (diff)
downloadSledjHamr-7d48bd9a65bc5fe92ede80ea7fc49e7526d07c7a.zip
SledjHamr-7d48bd9a65bc5fe92ede80ea7fc49e7526d07c7a.tar.gz
SledjHamr-7d48bd9a65bc5fe92ede80ea7fc49e7526d07c7a.tar.bz2
SledjHamr-7d48bd9a65bc5fe92ede80ea7fc49e7526d07c7a.tar.xz
Rearrange ClientHamr README's into better bits.
Diffstat (limited to 'ClientHamr/GuiLua/README')
-rw-r--r--ClientHamr/GuiLua/README60
1 files changed, 58 insertions, 2 deletions
diff --git a/ClientHamr/GuiLua/README b/ClientHamr/GuiLua/README
index 70f67b8..8c798c7 100644
--- a/ClientHamr/GuiLua/README
+++ b/ClientHamr/GuiLua/README
@@ -1,2 +1,58 @@
1GuiLua is basically a redo of my ancient Java based matrix-RAD system to 1GuiLua is basically a redo of my ancient Java based matrix-RAD system,
2Lua and EFL. 2but using Lua and EFL. The ultimate goal is for the various ClientHamr
3parts to be able to either host their own UI, or have it hosted in the
4in world 3D window. Matrix-RAD's ability to run either server or client
5side, with no change to the code, is great for this sort of thing. If I
6can manage the ability to "tear off" windows, in other words, pull them
7out of the 3D window to be real windows, then that's something people
8have been asking for from LL forever.
9
10
11old notes
12---------
13
14Might be good to allow Lua scripting. One way of dealing with viewer
15prefs perhaps? Certainly think about Lua for the UI, and a built in
16editor, etc. ala skang. All the fancy stuff like development and such
17should be kept in some sort of module, so as not to bloat the main
18proggy. See if it's possible to disable the Emerald/Phoenix/Firestorm
19LSL bridge when connecting to OpenSim. See if we can do it from Lua,
20with some sort of generic Lua system for munging things.
21
22
23skang vs edje vs LL shit
24------------------------
25
26EDJE
27Verbose, complex.
28Used to place and decorate widget parts.
29Can be used to place entire widgets through externals and swallows.
30Basic parts relative to each other.
31Signals and messages.
32Embryo scripts.
33Lua scripts (sandboxed).
34
35
36SKANG
37Tight, simple.
38Used to place widgets, and describe actions.
39Can include some really basic scripting.
40Widgets in a fixed position, but included stuff for relative placement in the TODO.
41Automated associations between widget name and variable (and method?) via introspection.
42Actions.
43Looks (could easily be extended to edje groups).
44Extensible.
45Can be used to pass values around.
46
47
48LL SHIT
49Verbose, even worse, XML, more crap than is needed.
50Menus.
51Windows with widgets relative to each other.
52 Basically nested rectangles.
53Manual association of widgets to methods.
54Can include tool tip string, enabled, visible, hover cursor, bounding rectangle?, mouse opaque?, tab groups, font (name, size, style, and alignment).
55 More stuff, typically hidden in the OO somewhere. sigh
56Generally uses fixed image and colour names, which skins overide.
57Skins can also overide the XML files.
58Translations provide override XML files that need only override the text bits.