david@lta.com (David B. Lewis) (02/19/91)
This appeared on comp.newprod. Has anybody seen this? Does the "behavior" below extend to the programmatic interface? Just BTW, has anybody else looked at reimplementing Mwm without using Xm? |> NEW SOFTWARE SUITE FOR NCD X TERMINAL FAMILY INCLUDES LOCAL WINDOW |> MANAGER, ENHANCED SECURITUY, REMOTE RESET |> |> DALLAS, January 22, 1991 -- Network Computing Devices, Inc., |> has developed a window manager with the appearance and behavior of |> OSF/MOTIF that runs locally on its X terminals -- rather than on a |> host computer across the network -- saving network resources and |> allowing X terminals to be used with hosts that do not support the X |> Window System. |> |> The new NCDwm window manager is part of NCDware 2.3, the |> latest release of software for the firm's X terminal family, which |> also includes improved security features and a remote reset |> capability. |> |> |> Local Window Manager a Tenth the Size of OSF/MOTIF Window Manager |> |> The X terminal-resident NCDwm window manager is identical in |> functionality to the OSF/MOTIF window manager, defining the appearance |> and behavior of windows (e.g., how to open and close them, their |> borders, icons and menus), and managing mouse-driven events, such as |> moving and resizing windows. However, it uses only 100 kilobytes of |> memory space -- about one-tenth the one megabyte consumed by OSF/MOTIF |> running on a networked host computer. [rest omitted] -- David B. Lewis Lewis, Trachtenberg & Associates (LTA) Note new address!: david@lta.com +1 617 225 0366
adrian@ORA.COM (Adrian Nye) (02/21/91)
> Just BTW, has anybody else looked at reimplementing Mwm without using Xm?
Quarterdeck Office Systems wrote a window manager for their
PC implementation of X. They didn't even use Xlib! They
implemented the protocol directly from assembly language
and so the window manager was ~30K in size! That was because
memory is really critical on PCs.
I don't remember if their WM was an Mwm lookalike.