wm4Nx 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:
This port was brutal. Much TWM logic was removed because it depending on X11 features (or just because I could not understand how to use it). The logic is partial. A lot 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 how like resizing, and menus.
2. Integrate NxWidgets into the windows: The resize menu needs a CLabel, the menus are CListBox'es, but not completely integrated, the Icon Manager needs to be a button array.
3. Resit Icons. They are windows now, but need to be compound widgets lying on the background.
4. Widget events are only partially integrated. A lot more needs to be done. A partial change to thoe event system that hints at the redesign is in place but it is far from complete.
2019-04-26 00:54:17 +02:00
|
|
|
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.
|
2019-04-26 01:58:28 +02:00
|
|
|
|
|
|
|
|
STATUS
|
|
|
|
|
======
|
2019-04-28 20:47:49 +02:00
|
|
|
2019-04-28: This port was brutal. Much TWM logic was removed because it
|
2019-04-26 01:58:28 +02:00
|
|
|
depended on X11 features (or just because I could not understand how to
|
2019-04-27 20:05:18 +02:00
|
|
|
use it). The replacement logic is only mostly in place but more
|
2019-04-26 01:58:28 +02:00
|
|
|
needs to be done to have a complete system (hence, it is marked
|
|
|
|
|
EXPERIMENTAL). The kinds of things that need to done are:
|
|
|
|
|
|
2019-04-27 20:05:18 +02:00
|
|
|
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.
|
2019-04-28 20:47:49 +02:00
|
|
|
2. Left click on background should bring up a user provided main menu.
|
2019-04-27 20:05:18 +02:00
|
|
|
Right click should bring up a window list (like the icon manager???)
|
2019-04-28 20:47:49 +02:00
|
|
|
3. For TWM-like behavior, a window frame and toolbar should be highlighted
|
2019-04-27 20:05:18 +02:00
|
|
|
when the window has focus.
|
2019-04-28 20:47:49 +02:00
|
|
|
4. A right click on the toolbar should bring up a window-specific menu.
|
2019-05-03 00:40:10 +02:00
|
|
|
2019-05-02: Some testing progress. The system comes up, connects to and
|
|
|
|
|
initializes the VNC window. For some reason, the VNC client breaks the
|
|
|
|
|
connection. The server is no longer connected so Twm4Nx constipates and
|
|
|
|
|
and eventually hangs.
|
2019-04-26 01:58:28 +02:00
|
|
|
|