------------------------------------------------------------------------------- MIT X windows VS. Sun X View & Openlook Pluses for MIT X: - Smaller server - Full source available free - Support via the net - Runs on more than Suns - Up to date Pluses for Sun X: - PostScript interpreter in the server - Takes advantage of hardware accelerators - Possible warm fuzzy feeling from running vendor-supplied stuff - requires unusual fonts to run. Minuses for MIT X: - You need enough disk space to build the distribution Minuses for Sun X: - Server is (comparatively) big and slow - Source costs many $ - What support is available costs many $ - Tends to be about a release behind the times My recommendation is not to run OpenWindows. Use the straight MIT X if you don't need the extra OpenWindows stuff. You'll see a massive improvement. We had a Sparcstation 2 (16 MB) that ran as a server and development machine for about 10 people, and it was fine until someone ran OW on the console. Then we would run out of memory, hit massive IO blocks as everything swapped, and only return to normal once OL was stopped. Upgrading to 32MB will help but it would be better still, if you don't need NEWS and other bangs and whistles OW gives you, then use MIT's straight X11R[45]. --- guy@Auspex.COM (Guy Harris) I strongly second this notion. I spent a bit o' time installing R5, right off of export.lcs.mit.edu, and although it took MUCH longer than just talking OW from the CD, the performance is, oh, about four times better. OW is slow, big, and old (based on R4). As such, it just doesn't cut it for anything new/internationalized/non-English (i.e., Japanese, etc.), and should be NOT EVEN BE CONTEMPLATED by anyone who cares about performance. --- ross@minnie.mit.edu (Ross Levinsky) The biggest problem is memory. As some people may have guessed, adding Display Postscript and Sunview to the already rather large X11 makes it larger. It was noted somewhere that OW 3.0 has a "-nosunview" flag - it may not be documented - that speeds it up somewhat if you don't plan to run SunView clients atop it; one thing it may do is disable those checks. ------------------------------------------------------------------------------- Clipboard and Xview > > xselection CLIPBOARD foobar > > should put the string "foobar" into the CLIPBOARD so I can then paste > it with the Paste key. Unfortunately I find that if I hit the Paste key > over a textedit or cmdtool window, only the first character ("f" in > this case) is pasted. However if I hit Paste in a shelltool window > the entire string is pasted, as desired. > Apparently xview expects that the CLIPBOARD will respond to a request of type LENGTH as well as STRING. xselection doesn't stick around to do this. ------------------------------------------------------------------------------- Translation interface for OpenLook Cut and Paste *Text.translations: #override \n\ L6: extend-start() extend-end(PRIMARY, CLIPBOARD, CUT_BUFFER0 )\n\ L8: insert-selection(CLIPBOARD) \n\ L10: extend-start() extend-end(PRIMARY, CLIPBOARD, CUT_BUFFER0 )\n\ L10: kill-selection() *XmText*translations: #override \n\ L6: copy-primary() copy-clipboard() \n\ L8: paste-clipboard() XTerm*VT100.Translations: #override \n\ L6: start-extend() select-end(PRIMARY, CLIPBOARD, CUT_BUFFER0)\n\ L8: insert-selection(CLIPBOARD) \n\ L10: start-extend() select-end(PRIMARY, CLIPBOARD, CUT_BUFFER0) NOTE: for the MIT server on Sun Consoles "Lx" (where x is a number) may have to be changed to "Fy" (where y is also a number) and y = 10 + x NOTE: in openlook all cut and pasting is performed by Left-Function Keys ------------------------------------------------------------------------------- See Extra Font Aliases for Open Windows in hints.Fonts -------------------------------------------------------------------------------