Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!sdrc!evgabb From: evgabb@sdrc.UUCP (Rob Gabbard) Newsgroups: comp.sys.hp Subject: Re: TPS on HP [was: Re: hp-ux 7.0 recall?] Summary: Use the sox11 driver Message-ID: <1158@sdrc.UUCP> Date: 26 Feb 90 13:51:56 GMT References: <1395@io.UUCP> <1320033@hp-ptp.HP.COM> Organization: SDRC, Cincinnati Lines: 25 In article <1320033@hp-ptp.HP.COM>, davew@hp-ptp.HP.COM (Dave_Waller) writes: > However, TPS under X-windows *is* using Starbase compatibility mode, > therefore when running TPS under X, the window cannot be sent to a remote Why not use the Starbase sox11 (Starbase-on-X11) driver as an option to the user ? You could have the regular Starbase-X11 merge driver which uses a native driver on that host (hp98731, hp98550, etc.) and then have an option that uses the sox11 driver when it gopen's. That way the user could have the option of running quicker locally or slower over the network and you could maintain one set of code based on Starbase. I assume Interleaf makes mostly just 2D Starbase calls and doesn't use double buffering, Z-buffering, etc. I've found that the user will appreciate it more if you enable an option and alert him to its drawbacks than just saying "All thats a nice feature but it would be too slow". I'm not criticizing Interleaf here, I really like their product, just pointing out an available option to the aforementioned problem. -- ________ _________ _______ ________ / _______| | ____ \ | ___ \ / _______| Rob Gabbard (uunet!sdrc!evgabb) | |______ | | \ \ | | \ | | / Technical Development Engineer \_______ \ | | | | | |___/ / | | Structural Dynamics Research Corp. ______| | | |____/ / | ____ \ | \_______ #include |________/ |________/ |_| |_| \________|