nuttx-apps

History

Gregory Nutt f730108adb Squashed commit of the following: apps/graphics/NxWidgets: Fix a possible deadlock condition when waiting for window geometry data that will never come. Fixed by re-requesting geometry data if we don't already have it. apps/graphics/twm4nx: Add some debug output. apps/graphics/twm4nx: Rethink how background events are handled. apps/grephics/twm4nx: Expermimental organization to capture background events.		2019-05-01 11:11:43 -06:00
..
src	Squashed commit of the following:	2019-05-01 11:11:43 -06:00
.gitignore	wm4Nx is a port of twm, Tab Window Manager (or Tom's Window Manager)	2019-04-25 16:54:17 -06:00
COPYING	wm4Nx is a port of twm, Tab Window Manager (or Tom's Window Manager)	2019-04-25 16:54:17 -06:00
Kconfig	apps/graphics/twm4nx: Add options to initialize the system via boardctl() and to bring up the network using the new apps/netutils/netinit. This latter is only necessary because VNC is being used to provide graphics.	2019-04-29 11:49:15 -06:00
Make.defs	wm4Nx is a port of twm, Tab Window Manager (or Tom's Window Manager)	2019-04-25 16:54:17 -06:00
Makefile	Squashed commit of the following:	2019-04-28 09:24:05 -06:00
README.txt	apps/graphics/twm4nx: Suppress input thread if using the VNC server. We don't need to catch input fromo keyboard and mouse devices in that case; those inputs will be injected into NX directly by the VNC server. Includes a couple of fixes from initial bringup attempts.	2019-04-28 12:47:49 -06:00
Twm4NX-Threading.pdf	apps/graphics/twm4nx: Suppress input thread if using the VNC server. We don't need to catch input fromo keyboard and mouse devices in that case; those inputs will be injected into NX directly by the VNC server. Includes a couple of fixes from initial bringup attempts.	2019-04-28 12:47:49 -06:00

README.txt

README
======

Twm4Nx is a port of twm, Tab Window Manager (or Tom's Window Manager)
version 1.0.10 to NuttX NX windows server.  No, a port is not the right
word.  It is a re-design of TWM from the inside out to work with the NuttX
NX server.  The name Twm4Nx reflects this legacy.  But Twm4Nx is more a
homage to TWM than a port of TWM.

The original TWM was based on X11 which provides a rich set of features.
TWM provided titlebars, shaped windows, several forms of icon management,
user-defined macro functions, click-to-type and pointer-driven keyboard
focus, graphic contexts, and user-specified key and pointer button bindings,
etc.

Twm4Nx, on the other hand is based on the NuttX NX server which provides
comparatively minimal support.  Additional drawing support comes from
the NuttX NxWidgets library (which necessitated the change to C++).

Twm4Nx is greatly stripped down and targeted on small embedded systems
with minimal resources.  For example, no assumption is made about the
availability of a file system; no .twmrc file is used.  Bitmaps are not
used (other than for fonts).

The TWM license is, I believe compatible with the BSD license used by NuttX.
The origin TWM license required notice of copyrights within each file and
a full copy of the original license which you can find in the COPYING file.
within this directory.

STATUS
======
  2019-04-28:  This port was brutal.  Much TWM logic was removed because it
    depended on X11 features (or just because I could not understand how to
    use it).  The replacement logic is only mostly in place but more
    needs to be done to have a complete system (hence, it is marked
    EXPERIMENTAL).  The kinds of things that need to done are:

    1. Update some logic that is only fragmentary for things like resizing.
       Resizing events should be be generated when user pulls to right,
       left, top, bottom, etc.  None of that is implemented.
    2. Left click on background should bring up a user provided main menu.
       Right click should bring up a window list (like the icon manager???)
    3. For TWM-like behavior, a window frame and toolbar should be highlighted
       when the window has focus.
    4. A right click on the toolbar should bring up a window-specific menu.