bryces@mrloog.LA.TEK.COM (Bryce G. Schroeder) (04/27/89)
I am posting this to the net to see if anyone else has a similar situation. Also someone may benefit from my findings. The following are results from tests conducted on a Vaxstation II GPX, with 7M memory, and an RD54 hard disk. Swap space was set at default of 16.7M. Comparisons were draw between UWS1.3 and UWS2.0 Two different test cases were analyzed: 1) Running Decwindows (dxwm) under the session manager. 2) Running Ultrix Window Manager (uwm) under the session manager. The third case of running the X server alone is not possible. With release 11 of X windows the login window is not supported. Some of the test results are subjective, where ever possible empirical data has been used to support conclusions. Running under dxwm * dxterm uses excessive amounts of swap space and takes too long to generate new windows. The session manager uses 2+ Megabytes of swap space. Each successive Decwindow uses 1 MB. This rapidly uses up available swap space, causing contention for swap space between Decwindows and applications. Under UWS1.3 the X server and uwm used approx. 1MB, and each successive xterm uses 350KB of swap space. Window creation was immediate. Deficiencies in Decwindows (UWS2.0) page 2 Running under dxwm * Could not iconify dxterm windows to bitmaps. Bitmap iconification does not appear to be supported, there was no manual reference as to feature deletion. * No .uwmrc file to easily add menus. There appears to be no support for interpretive window control. The method now in place is to write XUI calls in C. While the method much more complex, it is well documented. * Could not program function keys to strings. * When using xterm windows, keys had different functions than in dxterm windows. Example: backspace key in xterm windows would not back over characters on screen. * Documentation for window management was incomplete or nonexistent. Example: programming keys, Xdefaults files, keymaps, character fonts for uwm, dxwm, xterm, dxterm. * Documentation for Xstartup file was incomplete or nonexistent. Had trouble with things started with Xstartup not have characteristics of my .login (xsh.c). * UE (unix browser) window would close if you viewed certain files. Deficiencies in Decwindows (UWS2.0) page 3 Running under uwm (Ultrix Window Manager) * xterm had no title bar. * Could not program function keys to strings. * Documentation unclear on Xdefaults files and how to iconify to bitmap files. * UE (unix browser) window would close if you viewed certain files. * Documentation on how to get Vaxstation to use uwm is incomplete or nonexistent. Conclusion: We find this environment(UWS2.0 Decwindows) inflexible, cumbersome, and slow. It does have several excellent features but these are by far out-weighed by the limitations imposed by the environment. It appears that DEC's thrust with Decwindows is to present a generic non-configurable interface. This interface does not meet the needs of our engineering environment. It is our belief that we will be ahead to continue using the present release (UWS1.3). + Bryce G. Schroeder + Tektronix, Inc + + + Network Admin LA + P.O. Box 4600 M/S 92-101 + bryces@mrloog.la.tek.com+ + (503) 629-1391 + Beaverton., OR 97075 + +