[tekui-devel] tekui: FloatText: added FontSpec and line breaks; Lissa: removed...

[Timm S. Mueller]

details:   http://hg.teklib.org/tekui/rev/13d30aa05a9f
changeset: 473:13d30aa05a9f
user:      Timm S. Mueller <tmueller at neoscientists.org>
date:      Thu May 08 19:06:01 2008 +0200
description:
FloatText: added FontSpec and line breaks; Lissa: removed maxsize; Makefile:
added installation of ListView class; README: minor improvements

diffs (truncated from 236 to 100 lines):

diff -r ee237fad244f -r 13d30aa05a9f README
--- a/README	Thu May 08 15:49:15 2008 +0200
+++ b/README	Thu May 08 19:06:01 2008 +0200
@@ -34,9 +34,9 @@ for desktop applications.
 
 Its main focus is on rapid development of custom-made devices and
 applications, often with a custom appearance and under
-resource-constrained conditions, such as for small devices with a
-display controller, or embedded into applications and libraries,
-like games and browser plug-ins.
+resource-constrained conditions, such as for embedded devices with a
+display controller, or integrated into applications, browser plug-ins
+and games.
 
 Being mostly written in the Lua scripting language (see
 [[http://www.lua.org/]]), it is easily extensible with new user
@@ -63,8 +63,8 @@ need of a GUI solution for their device 
 
 tekUI's development model is fairly simple; if you find this software
 useful, you have probably arranged to fit it to a certain device or
-application. Submit your additions and we will happily include them to
-the repository.
+application. Submit your additions and we will check them for
+inclusion to the source code repository.
 
 === 1.4. Commercial support and services ===
 
@@ -104,7 +104,9 @@ Lua. It is planned to additionally surro
 Lua. It is planned to additionally surround the toolkit with a C
 library, for making it fully generic. In this scenario, Lua would
 continue to play its role as the toolkit's notification and
-interconnection language.
+interconnection language. Note that the programming interface is
+nowhere complete and fully stable yet, so be prepared for structural
+and API changes.
 
 === 2.1. Selected features ===
 
@@ -129,8 +131,8 @@ applications can all share the same colo
 
 The current default theme tries to be as conservative and minimal as
 possible without looking too ugly. It is the only theme available at
-the moment. Custom themes can be created easily by modifying or
-deriving from the Theme class.
+the moment. Custom themes can be created by modifying or deriving
+from the Theme class.
 
 === 2.3. C library ===
 
@@ -140,29 +142,28 @@ the hassle of getting and installing the
 the hassle of getting and installing the software.
 
 The C library provides the host interface and a few
-performance-critical routines. Rendering and input management are
+performance-critical routines. Rendering and input handling are
 strictly isolated in the form of a '''virtual device driver''',
 which allows for easy exchangeability.
 
-Additionally, the C library provides facilities such as portable
-threads and a timer device. Depending on your application and its
-kind of deployment, the C library can be extended with more input
-drivers, a virtual filesystem, multimedia codecs, etc., and ported
-to any possible 32bit architecture (it can act as a small embedded
-operating system if necessary).
+Aside from the device driver interface, the C library provides
+OS-like facilities such as portable threads and a timer device.
+Depending on your application and its kind of deployment, it can
+be extended with more input drivers, a virtual filesystem,
+multimedia codecs etc., and be ported to any 32bit architecture,
+as it can act as a small embedded operating system if necessary.
 
 === 2.4. Lua, C and object model ===
 
-Layouting, rendering, input handlers, notifications and most user
-interface elements (besides the Window, Group and Application
-classes) are currently implemented in Lua, which is beneficial for
-prototyping custom classes - and generally in early stages of
-development. All classes can be ported to C later.
-
-Regardless whether classes are written in Lua or C, classes share a
+Regardless whether classes are written in Lua or C, they share a
 common, single-inheritance object model, which is determined by the
 Lua virtual machine and provides a referencing scheme and automatic
 memory management.
+
+Most user interface elements (besides the Window, Group and
+Application classes) are currently implemented in Lua, which is
+beneficial for creating custom classes - and generally in early
+stages of development.
 
 === 2.5. Documentation system ===
 
diff -r ee237fad244f -r 13d30aa05a9f bin/tekui.lua
--- a/bin/tekui.lua	Thu May 08 15:49:15 2008 +0200
+++ b/bin/tekui.lua	Thu May 08 19:06:01 2008 +0200
@@ -344,7 +344,7 @@ ui.application:new
 							AutoWidth = true,
 							KeepMinWidth = true,
 							Object = ui.FloatText:new {
-								Text = [[ Hello.  My Handle is The Cuisinart Blade, (I have since changed it) most people called me C.B., just as another nickname.  I got into computers because I always had a knack for Games, Programs, Etc... ]],