Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!exodus!snowking!tomj From: tomj@snowking.Eng.Sun.COM (Tom Jacobs) Newsgroups: comp.windows.x Subject: Re: SunView-XView Conversion ? Message-ID: <1990Oct15.143710@snowking.Eng.Sun.COM> Date: 15 Oct 90 21:37:10 GMT References: Sender: news@exodus.Eng.Sun.COM Reply-To: tomj@snowking.Eng.Sun.COM (Tom Jacobs) Distribution: comp Organization: Sun Microsystems, Inc. Lines: 101 In article , himsolt@trillian-gw.fmi.uni-passau.de (Michael Himsolt) writes: |> |> Hello, |> |> I am trying to convert a SunView application to XView, using XView 2.0 |> with X11R4. I wonder whether someone has experiences with |> SunView-XView conversion. |> |> I have some questions : |> |> - Sun claims easy conversion "within a view days". Any comments ? Experience has shown that conversion is heavily dependent upon how much pixrect/pixwin graphics your program does. We suggest that graphics programs take the extra time to convert their graphics logic to Xlib. To help with this, Appendix E of the Conversion Guide provides a pretty detailed logical conversion description. Programs that are don't use pixrect/pixwin have consistently been converted in only a few days. |> - My program involves both (a lot of) SunView windows and a built-in |> "graphic system" using Pixrect. What about XView performance under |> these circumstances ? The system must run on a SUN-3/50 with good |> performance (the SunView version had no problems). Whether you convert the graphics or not, it isn't clear that you'll ever get "as good" performance on X11 as you did in kernal-based SunView. However, converting from pixrect/pixwin to Xlib serves the additional benefit of allowing you to update you programs logic to be more maintainable over the longer term. Also, there are some displayability problems with pixwin emulation which conversion solves. |> I have started some work on porting and ran into the following |> problems : |> |> - I could not print the 'Book.ps' file distributed with XView |> (xview/doc/conversion/Book.ps) on our laserwriter. The laserwriter |> stopped at page 13; the next feature should have been a sample Open |> Look screen. Any ideas what has gone wrong ? A patch for this was sent out. Send a request to xviewbugs@sun.com and we'll resend the patch. |> - Pixrect support seems to be strange. Without linking -lpixrect, I |> get warnings that mem_create and pr_text are undefined, the other |> routines seem to be defined. [I tried to link -lpixrect, but then I |> got a runtime error that pr_vector is unsupported]. As stated above, |> the program is heavily based on PixRect, so I need it. Is there a |> reasonable PixRect support in XView ? You need to xv_mem_create and pw_text if you're not linking with libpixrect. This is the pixwin emulation mode. Sounds like you really need the doc. You might call Sun direct (800)USA-4-SUN and order the hardcopy manual (just to be sure) using the part number 800-4836-10. The charge is minimal and only covers material and shipping. |> - Sun seems to provide some PixWin-compatible procedures, but I could |> not find anything about that in the XView Programming manual. The "XView Version 2 Reference Manual: Converting SunView Applications" doc described is the correct place for pixwin compatibility. Sun "officially" suggests that you convert to Xlib graphics. |> All suggestions are welcome - thanks in advance |> |> -- Michael |> |> -- |> Michael Himsolt, Universitaet Passau, Innstrasse 33, D-8390 Passau, GERMANY |> himsolt@fmi.uni-passau.de graphed@fmi.uni-passau.de --- Tom Jacobs ARPA: tomj@Eng.Sun.com Windows & Graphics Software UUCP: sun!tomj Sun Microsystems, Inc.