[tekui-devel] tekui: Markup:new() now initializes all used variables; README: ...

Timm S. Mueller tmueller at neoscientists.org
Thu May 15 00:08:40 CEST 2008


details:   http://hg.teklib.org/tekui/rev/38a0f2bee225
changeset: 501:38a0f2bee225
user:      Timm S. Mueller <tmueller at neoscientists.org>
date:      Wed May 14 14:11:56 2008 +0200
description:
Markup:new() now initializes all used variables; README: improved

diffs (truncated from 264 to 100 lines):

diff -r 333aad91026c -r 38a0f2bee225 README
--- a/README	Wed May 14 13:44:04 2008 +0200
+++ b/README	Wed May 14 14:11:56 2008 +0200
@@ -10,7 +10,7 @@
 
  - 2. [[#overview : Technical overview]]
   - 2.1. Selected features
-  - 2.2. Kinds of deployment
+  - 2.2. Development plans and deployment
   - 2.3. Themes
   - 2.4. C library
   - 2.5. Lua, C and object model
@@ -117,7 +117,7 @@ stable yet, so be prepared for structura
  * Works with stock (double precision), single precision and
  integer versions of the Lua VM
 
-=== 2.2. Kinds of deployment ===
+=== 2.2. Development plans and deployment ===
 
 The only language currently supported for writing applications in is
 Lua. So, in its present state, the framework revolves around the Lua
@@ -131,7 +131,7 @@ Our next development target is to fold t
 (including the interpreter, C library and some core classes) into a
 fully self-contained C library, which allows to spawn asynchronous
 "GUI tasklets" communicating with the main program via a pipe or
-socket using a highlevel application protocol. From this, we envision
+socket using an application-level protocol. From this, we envision
 the following benefits:
 
  * GUIs integrate smoothly even into I/O-burdened applications
@@ -141,11 +141,10 @@ the following benefits:
  * Faulty GUI application code, as it is written in a safe language,
  cannot crash the server, even if the device is without MMU
 
-This is why GUI creation is designed to be largely descriptive and
-data centric - no functions/lambdas are required to get a basic
-interface up and working. In this scenario, Lua would continue to
-play its role as the toolkit's notification and interconnection
-language.
+GUI creation is designed to be largely descriptive and data centric -
+no functions/lambdas are required to get a basic interface up and
+working. For the remaining functionality, Lua would continue to play
+its role as the toolkit's notification and interconnection language.
 
 === 2.3. Themes ===
 
diff -r 333aad91026c -r 38a0f2bee225 doc/readme.html
--- a/doc/readme.html	Wed May 14 13:44:04 2008 +0200
+++ b/doc/readme.html	Wed May 14 14:11:56 2008 +0200
@@ -42,7 +42,7 @@
 								2.1. Selected features
 							</li>
 							<li style="list-style-type: none">
-								2.2. Kinds of deployment
+								2.2. Development plans and deployment
 							</li>
 							<li style="list-style-type: none">
 								2.3. Themes
@@ -227,7 +227,7 @@
 				</ul>
 			</blockquote>
 			<h3>
-				2.2. Kinds of deployment
+				2.2. Development plans and deployment
 			</h3>
 			<p>
 				The only language currently supported for writing applications in is
@@ -243,7 +243,7 @@
 				(including the interpreter, C library and some core classes) into a
 				fully self-contained C library, which allows to spawn asynchronous
 				&quot;GUI tasklets&quot; communicating with the main program via a pipe or
-				socket using a highlevel application protocol. From this, we envision
+				socket using an application-level protocol. From this, we envision
 				the following benefits:
 			</p>
 			<blockquote>
@@ -263,11 +263,10 @@
 				</ul>
 			</blockquote>
 			<p>
-				This is why GUI creation is designed to be largely descriptive and
-				data centric - no functions/lambdas are required to get a basic
-				interface up and working. In this scenario, Lua would continue to
-				play its role as the toolkit's notification and interconnection
-				language.
+				GUI creation is designed to be largely descriptive and data centric -
+				no functions/lambdas are required to get a basic interface up and
+				working. For the remaining functionality, Lua would continue to play
+				its role as the toolkit's notification and interconnection language.
 			</p>
 			<h3>
 				2.3. Themes
diff -r 333aad91026c -r 38a0f2bee225 tek/class/markup.lua
--- a/tek/class/markup.lua	Wed May 14 13:44:04 2008 +0200
+++ b/tek/class/markup.lua	Wed May 14 14:11:56 2008 +0200
@@ -205,7 +205,7 @@ local ipairs = ipairs
 
 module("tek.class.markup", tek.class)
 
-_VERSION = "Markup 2.5"


More information about the tekui-devel mailing list