[teklib-general] teklib: display_x11: re-interpretation of window min/max propert...

[Timm S. Mueller]

details:   http://hg.teklib.org/teklib/rev/63ae4159c90e
changeset: 179:63ae4159c90e
user:      Timm S. Mueller <tmueller at neoscientists.org>
date:      Sat Apr 12 15:06:02 2008 +0200
description:
display_x11: re-interpretation of window min/max properties is now correctly
handled in setattrs(); README improved

diffs (truncated from 194 to 100 lines):

diff -r fd8ff8efd925 -r 63ae4159c90e README
--- a/README	Wed Apr 09 12:38:50 2008 +0200
+++ b/README	Sat Apr 12 15:06:02 2008 +0200
@@ -1,32 +1,29 @@
 
 = About TEKlib =
 
-TEKlib is an open-source library project under the terms of the free
-MIT software license. By picking from its facilities, it can serve as
-a
+TEKlib is an open-source library under the terms of the free MIT
+software license. By picking from its facilities, it can serve as a
 
-	* middleware
+	* Middleware
 
-	* embedded operating system
+	* Embedded operating system
 
-	* virtual OS target for applications and libraries that would
+	* Virtual OS target for applications and libraries that would
 	have to be ported to many individual hosts
 
-	* component architecture and hosting environment that allows
-	plug-ins and their hosts to be written in a platform-independent
-	way
+	* Component architecture and hosting environment to allow plug-ins
+  and their hosts to be written in a platform-independent manner
 
-TEKlib is designed to be largely agnostic as to whether it runs in a
-shared or seperate address spaces. Its freestanding nature, small
-footprint and absence of global data recommend it as a layer for
-portability and code reuse in a wide range of environments; it can
-be used in userspace applications, kernel modules, plug-ins, in
-device drivers and on raw hardware.
+Its freestanding nature, small resource footprint and absence of
+global data recommend it as a layer for portability and code reuse in
+a wide range of environments; it can be used in userspace
+applications, kernel modules, plug-ins, device drivers and on raw
+hardware.
 
 == Features ==
 
-	* Recursive memory management: Allocators can be stacked on top
-	of each other and carry attributes for automatic cleanup and
+	* Recursive memory management: Allocators can be stacked on top of
+	each other and carry attributes for automatic cleanup and
 	thread-safety; special allocators can implement tighter packing,
 	custom allocation strategies, leak tracking, or operate in
 	user-supplied memory
@@ -34,46 +31,44 @@ device drivers and on raw hardware.
 	* TEKlib threads (''tasks'') are 'heavy-weight', or process-like.
 	They are equipped with means for local storage, individual file
 	descriptors, a reserved set of signals and endpoints for
-	communication. User signals can be synchronized on
-	individually, in sets or by using messages and I/O packets
+	communication. User signals can be synchronized on individually, in
+	sets or by using messages and I/O packets
 
-	* TEKlib provides strict asynchronoucy and atomicity throughout
-	its API; the core as a whole never blocks due to latency
-	inflicted by I/O, and it never imposes polling as an inevitable
-	mechanism
+	* TEKlib provides strict asynchronoucy and atomicity throughout its
+	API; the core as a whole never blocks due to latency inflicted by
+	I/O, and it never imposes polling as an inevitable mechanism
 
-	* The module interface is inherently thread-safe and provides
-	a referencing scheme for any number of tasks requesting a
-	component, library or device driver at the same time
+	* The module interface is inherently thread-safe and provides a
+	referencing scheme for any number of tasks requesting a component,
+	library or device driver at the same time
 
-	* Recursive mutexes and an extension thereof, ''atoms'',
-	allow for lookup by name, locking attempts and shared resource
-	arbitration
+	* Recursive mutexes and an extension thereof, ''atoms'', allow for
+	lookup by name, locking attempts and shared resource arbitration
 
 	* An asynchronous device driver interface can be utilized by
-	applications for overlapping I/O; using this interface, TEKlib
-	also implements a portable timer device
+	applications for overlapping I/O; using this interface, TEKlib also
+	implements a portable timer device
 
-	* File systems are an extension to device drivers. TEKlib
-	provides a file system namespace for any number of mountpoints
-	(''devices'') and logical roots (''assigns''). ''Handlers'' are
-	modules implementing roots in the file system; they can be
-	mounted explicitely or initialize themselves on demand. In
-	hosted scenarios, the file system is initially populated with
-	a default handler to occupy the root node, thus abstracting
-	from a host's native file system.
+	* File systems are an extension to device drivers. TEKlib provides
+	a file system namespace for any number of mountpoints (''devices'')
+	and logical roots (''assigns''). ''Handlers'' are modules
+	implementing roots in the file system; they can be mounted
+	explicitely or initialize themselves on demand. In hosted
+	scenarios, the file system is initially populated with a default