[tekui-devel] tekui: Frame: renamed BorderHook to BorderObject, implemented 'b...
Timm S. Mueller
tmueller at schulze-mueller.de
Wed Aug 27 00:49:21 CEST 2008
details: http://hg.teklib.org/tekui/rev/5fc5280440ef
changeset: 7:5fc5280440ef
user: Timm S. Mueller <tmueller at schulze-mueller.de>
date: Wed Aug 27 00:48:45 2008 +0200
description:
Frame: renamed BorderHook to BorderObject, implemented 'border-class'
property, improved documentation; ListGadget, ScollGroup, Canvas: resolved
inconsistencies in the connect() and setup() procedure; ListGadget: Now using
the 'default' border class for the cursor by default, renamed CursorHook to
CursorObject, fixed various refreshing problems; Default border: changed
precedence of sub borders (which is now documented in the Frame class);
README: minor corrections; documentation regenerated
diffs (truncated from 1194 to 100 lines):
diff -r eb291b7e8b75 -r 5fc5280440ef README
--- a/README Wed Aug 20 16:49:39 2008 +0200
+++ b/README Wed Aug 27 00:48:45 2008 +0200
@@ -474,16 +474,14 @@ be useful:
* Application classes are created in the same way, but they are
located in the application's local program directory (also under
- {{tek/ui/class}}). They would also allow an application to be
- shipped with modified versions of the standard classes, as the
- application's local directory will be searched for classes first.
+ {{tek/ui/class}}).
* Another scope is inside the source code of an existing application
or module. We might call this the 'ad-hoc' style, as new classes are
often created out of a spontaneous need.
-For the ad-hoc style, it is not necessary to create a new source.
-For example, to derive a button class from the Text class:
+For the ad-hoc style, it is not necessary to create a new source
+file. For example, to derive a button class from the Text class:
local Button = ui.Text:newClass { _NAME = "_button" }
@@ -491,7 +489,7 @@ names should be prefixed with an undersc
names should be prefixed with an underscore to distinguish them
from global classes.
-From this point, the new class can be overridden, e.g. for
+From this point, the new class can be extended, e.g. for
initializations which turn a Text into a Button:
function Button.init(self)
@@ -501,7 +499,7 @@ initializations which turn a Text into a
end
As shown in the example, we also passed the call on to our
-superclass, which we expect to perform the missing initializations.
+super class, which we expect to perform the missing initializations.
Finally, a new object from our new class can be created:
@@ -530,7 +528,7 @@ See also the module's documentation for
==( proxied : 5.2. Proxied object model )==
If you plan on extending existing classes or develop your own, you
-should set the following configurable parameters in
+are advised to set the following configurable parameters in
[[tek.class][manual.html#tek.class]], the base class of all tekUI
classes:
@@ -624,7 +622,7 @@ The template for a definition is this:
DEFINITION::
-The function template:
+And the function template:
ret1, ret2, ... = function(arg1, arg2, ...): ...
diff -r eb291b7e8b75 -r 5fc5280440ef bin/dynamic.lua
--- a/bin/dynamic.lua Wed Aug 20 16:49:39 2008 +0200
+++ b/bin/dynamic.lua Wed Aug 27 00:48:45 2008 +0200
@@ -141,6 +141,7 @@ ui.application:new
ui.Slider:new
{
Border = { 2, 2, 2, 2 },
+ Style = "border-rim-width: 1; border-focus-width: 1;",
Width = "free",
Value = 2,
Min = 0,
diff -r eb291b7e8b75 -r 5fc5280440ef doc/index.html
--- a/doc/index.html Wed Aug 20 16:49:39 2008 +0200
+++ b/doc/index.html Wed Aug 27 00:48:45 2008 +0200
@@ -733,9 +733,7 @@ app:run()
<li>
Application classes are created in the same way, but they are
located in the application's local program directory (also under
- <code>tek/ui/class</code>). They would also allow an application to be
- shipped with modified versions of the standard classes, as the
- application's local directory will be searched for classes first.
+ <code>tek/ui/class</code>).
</li>
<li>
Another scope is inside the source code of an existing application
@@ -745,8 +743,8 @@ app:run()
</ul>
</blockquote>
<p>
- For the ad-hoc style, it is not necessary to create a new source.
- For example, to derive a button class from the Text class:
+ For the ad-hoc style, it is not necessary to create a new source
+ file. For example, to derive a button class from the Text class:
</p>
<pre>
local Button = ui.Text:newClass { _NAME = "_button" }
@@ -757,7 +755,7 @@ local Button = ui.Text:newClass { _NAME
from global classes.
</p>
<p>
- From this point, the new class can be overridden, e.g. for
More information about the tekui-devel
mailing list