X-Git-Url: https://git.decadent.org.uk/gitweb/?a=blobdiff_plain;f=ionconf%2Fnode6.html;h=88aa9be89661e5a3719240a63cd598f2d4affce6;hb=28274d8cd79bfac0fec675582560463d4b2028f8;hp=17e8f34d6980950fb3a4ff4a8d13ce17a1511dd1;hpb=a35ba2541b8601953ae94f779a85ae70de19cd11;p=ion3-doc.git diff --git a/ionconf/node6.html b/ionconf/node6.html index 17e8f34..88aa9be 100644 --- a/ionconf/node6.html +++ b/ionconf/node6.html @@ -28,31 +28,31 @@ original version by: Nikos Drakos, CBLU, University of Leeds
@@ -61,20 +61,20 @@ original version by: Nikos Drakos, CBLU, University of Leeds SubsectionsThis chapter documents some additional features of the Ion configuration and scripting interface that can be used for more advanced scripting than -the basic configuration exlained in chapter 3. +the basic configuration explained in chapter 3.
@@ -101,16 +101,16 @@ the basic configuration exlained in chapter 3
Hooks are lists of functions to be called when a certain event occurs.
-There are two types of them; normal and ''alternative'' hooks. Normal
+There are two types of them; normal and ``alternative'' hooks. Normal
hooks do not return anything, but alt-hooks should return a boolean
-indicating whether it handled its assigned task succesfully. In the case
+indicating whether it handled its assigned task successfully. In the case
that true is returned, remaining handlers are not called.
Hook handlers are registered by first finding the hook
-with ioncore.get_hook and then calling WHook.add
-on the (succesfull) result with the handler as parameter. Similarly
-handlers are unregistered with WHook.remove. For example:
+with ioncore.get_hook and then calling WHook.add
+on the (successful) result with the handler as parameter. Similarly
+handlers are unregistered with WHook.remove. For example:
-Note that many of the hooks are called in ''protected mode'' and can not
+Note that many of the hooks are called in ``protected mode'' and can not
use any functions that modify Ion's internal state. TODO: More detailed
documentation when this is final.
@@ -142,7 +142,7 @@ documentation when this is final.
-All Ion objects are passed to Lua scriptss as 'userdatas', and you may
+All Ion objects are passed to Lua scripts as 'userdatas', and you may
safely store such object references for future use. The C-side object
may be destroyed while Lua still refers to the object. All exported
functions gracefully fail in such a case, but if you need to explicitly
@@ -219,8 +219,10 @@ and ioncore.x_get_text_p
-
@@ -228,11 +230,11 @@ All statusbar meters that do not monitor the internal state of Ion should
go in the separate ion-statusd program.
-Whenever the user requests a meter %foo or %foo_bar to be
-inserted in a statusbar, mod_statusbar asks ion-statusd to
-load statusd_foo.lua on its search path (same as that for Ion-side
+Whenever the user requests a meter `%foo' or `%foo_bar' to
+be inserted in a statusbar, mod_statusbar asks ion-statusd
+to load statusd_foo.lua on its search path (same as that for Ion-side
scripts). This script should then supply all meters with the initial part
-'foo'.
+`foo'.
To provide this value, the script should simply call statusd.inform
@@ -241,11 +243,11 @@ Additionally the script should provide a 'template' for the meter to
facilitate expected width calculation by mod_statusbar, and
may provide a 'hint' for colour-coding the value. The interpretation
of hints depends on the graphical style in use, and currently the
-stock styles support the normal, important and
-critical hints.
+stock styles support the `normal', `important' and
+`critical' hints.
-In our example of the 'foo monitor', at script init we might broadcast
+In our example of the 'foo monitor', at script initialisation we might broadcast
the template as follows:
@@ -319,31 +321,31 @@ local settings=table.join(statusd.get_config("foo"), defaults)
@@ -125,7 +125,7 @@ handlers do. The types of parameters for each hook are listed in
the hook reference, section 6.9.
-5.4 Writing ion-statusd monitors
+
+
+
+5.4 Writing ion-statusd monitors