hvr@eng.sun.COM (Heather Rose) (08/14/90)
The XView source donation, for those who may not already know, includes the complete source for the XView toolkit, the OLWM window manager, a number sample XView applications, and a collection of commercial-quality Lucida bitmap fonts from Bigelow & Holmes. What Is XView: ------------- XView is an X toolkit based on the OPEN LOOK (tm) Graphical User Interface (GUI). XView's application programmer's interface (API) is very similar to the API of the SunView toolkit; in practice, most SunView applications can be converted to XView in a few days, although some will take longer. Since there are more than 2000 SunView applications, we expect that releasing XView will immediately create a large base of X11 applications. To futher assist in converting SunView applications, the R4 donation includes improved automated conversion tools and documentation. Additionally, XView provides both 2D and 3D-look OPEN LOOK graphical interfaces through the usage of a new OPEN LOOK graphics library (OLGX). Changes to XView for Release 2: ------------------------------ For more complete list see the <XVIEW>/doc/relnotes.text and <XVIEW>/doc/rtf.text files. - new 3D-style OPEN LOOK appearance using OLGX library - multi-screen support - multi-server support - C++ and ANSI-C language bindings - additional OPEN LOOK features - documentation on creating new XView packages - changes and enhancements to the XView API - bug fixes - simplified build environment for source What is OLWM: ------------ OLWM is an ICCCM-compliant window manager, also based on the OPEN LOOK GUI. OLWM is a "stand-alone" window manager, not dependent on any toolkit code. We hope that OLWM will become the standard example of an ICCCM-compliant window manager in X11 R4. Additionally, OLWM provides both 2D and 3D-look OPEN LOOK graphical interfaces through the usage of a new OPEN LOOK graphics library (OLGX). OLGX is written to the Xlib interface and does not use any toolkit. What Libraries are Included: --------------------------- - XView (XView user interface toolkit) - XVPS (NeWS/PostScript canvas package) - OLGX (OPEN LOOK Graphics for X) What XView Applications are Included: ------------------------------------ - clock - textedit (graphical file editor) - cmdtool/shelltool (a terminal emulator) - props (root properties program) - xvbench (useful for testing ports of XView) In addition, we are including a script that helps convert SunView programs to XView by flagging the application code that needs to be changed and another tool which helps convert SunView ".defaults" files into ".Xdefaults" resource files. What Contributed Clients are Included: ------------------------------------- The examples from the XView Programmer's Manual from O'Reilly. This includes over 70 simple example programs to show features in each of the XView packages and three examples of new XView subclasses. A perfdemo example which monitors performance on multiple hosts. This includes an example of creating a new XView panel item and how to use XView with Sun's Light Weight process (LWP) library. Examples using the new XView PostScript (XVPS) library extension to do NeWS/PostScript imaging in an XView canvas. What Fonts are Included: ----------------------- The Bigelow & Holmes Lucida bitmap fonts are a collection of different type styles and point sizes in the Lucida typeface. In addition, XView uses "glyph fonts" to accelerate the painting of some OPEN LOOK GUI graphical elements, and these fonts are also being made available. These glyph fonts are used extensively by OLGX to provide high performance when rendering 2D and 3D-look OPEN LOOK graphics. However, only OLWM will be able to provide the 3D-look in this update. Note that these glyph fonts *MUST* be added to your X11 R3 server in order to run XView applications. These fonts are standard with all R4 servers. XView Source: ------------ With licensed source products from Sun, source is usually not released until several months after a binary version of the product has shipped. The extra time is used to "clean up" the source for external consumption. In contrast, we are releasing XView and OLWM now, soon after the binary version of XView (XView 2.0) has shipped. We will continue to fix bugs and portability problems as we find them, and these changes will be made available periodically (this is just the first). We are releasing this FCS version of the source at this time to accellerate the number of ports of XView, and to encourage the notion that X toolkit source should be free. We will update this free source to track changes that Sun makes in XView, including bug fixes, performance improvements, and new features. Sun has selected the MIT X11 distribution as our XView source distribution channel. If you port XView to a new platform or make fixes to the library, please send your code diffs for inclusion in a future release to the bugs alias. As ports of XView become available for other platforms, we will incorporate this work and include it in future source donations. As the Kanji version of XView becomes available, we will also integrate this work and donate the sources as well. This initial release is to facilitate porting of XView to other platforms. Current ports in progress include the following platforms available from the listed vendors: Platform Vendor ------------------------------------------------ DEC Station Sun Microsystems HP 9000/300 Sun Microsystems IBM RIOS Sun Microsystems DOS Quarterdeck AUX ICS VMS TGV Some vendors will sell XView on a particular hardware or OS base; others will donate their changes back to Sun for inclusion with the publically available source. We encourage both uses of this source donation. XView Requirements: ------------------ XView requires the use of an ICCCM-compliant window manager. One such window manager is olwm, which supports the OPEN LOOK (TM) user interface. Further, XView requires full ICCCM support in Xlib. This is the standard in the X Window System Version 11, Release 4. In order to run under Release 3, you must define the PRE_R4_ICCCM compile-time flag (see config/XView.cf) and the set resource, xview.icccmcompliant, to False in the .Xdefaults file (see the xview man page). Building the Release: -------------------- To build XView, you only need the XView source release and installed X11 header files and libraries. All needed X11R4 configuration files are included in the XView source. More Information: ---------------- There is a second message which discusses how to report bugs, get more help and what documentation is available. Please direct comments or questions about this source donation to xpert@expo.lcs.mit.edu (or comp.windows.x). And thank you for your support, The XView Development Team Sun Microsystems, Inc.
hvr@eng.sun.COM (Heather Rose) (08/14/90)
More information on XView regarding bugs, help, and documentation Reporting Bugs -------------- When you find a bug in the operation of XView, we would like to hear about it so we can consider scheduling a fix in the next release. Often, you won't want or need the help of Sun's support services to report a bug. When that is the case, please follow the steps listed below. If you experience problems that require more direct support from Sun, please refer to the Getting Help section below. To help us process bug reports as quickly and smoothly as possible, please: 1) Use the template bug form in <XVIEW>/doc/bugs/bugform. 2) Send bugs via electronic mail to sun.com!xviewbugs. (Customers with software support contracts who are reporting problems against using the XView libraries or clients can also send email to sun!hotline or call Sun Microsystems directly, 1-800-USA-4SUN. The hotline service does not support building the XView library sources. The hotline service does provide personal feedback on problems reported.) Don't be concerned if you have difficulty determining the correct category for your bug report. We will review the report and see that it is correctly recorded. Known bugs are included in the directory <XVIEW>/doc/bugs. Getting Help ------------ Sun Microsystems provides support for customers who have software support contracts via a telephone support line and a special email alias. Support for customers without support contracts is provided only through an email alias. Contract customers can also send questions or bug reports via electronic mail to sun.com!hotline. Be sure to include your name, company, and phone number, along with the serial number and details of the problem. If possible, you should use the bug report form discussed above. Those who are not Sun customers or would like to participate in conversations with other people using XView, can take advantage of public news groups and email aliases. Existing groups are listed below: 1) openlook@unify.unify.com Unify is sponsoring an OPEN LOOK developers alias. This is for anyone using an OPEN LOOK toolkit such as XView. To join or leave this alias send a request to openlook-request@unify.unify.com or ...!unify!openlook-request. 2) xviewbug-trackers@sun.com This alias consists of people who would like to share information on bugs reported against XView. If you would like to share your bug report with this group, put this address on the Cc: line of your email message to the xviewbugs alias. To join of leave this alias send a request to sun.com!xviewbug-trackers-request. (If this address bounces, then try kimba.eng.sun.com!xviewbug-trackers-request.) 3) xpert@expo.lcs.mit.edu/comp.windows.x xpert@expo.lcs.mit.edu is the mailing list from which comp.windows.x was spawned. The two are gatewayed together so that messages sent via either channel will appear on both. Xpert is a general alias for all X Window System enthusiasts. To join or leave this alias send a request to xpert-request@expo.lcs.mit.edu or begin reading the net news group comp.windows.x. Note: These are all public aliases which are received by many companies and individuals around the world. It is important to conduct dealings on public aliases with discretion. XView Programmer's Documentation ---------------------------------- The documentation for this release of the XView source includes the following programmer's manuals: XView Reference Manual: Converting SunView Applications This manual contains complete instructions for converting SunView programs to XView. It provides an overview of the XView toolkit's architecture and design principles, and gives instructions for both minimal and full conversion to XView. This document will be of most use to programmers who are familiar with the SunView API. If you are not a SunView programmer, you should also read the SunView Programmer's Guide . This document is included in the <XVIEW>/doc/conversion directory. XView PostScript Interface Library This manual describes how to use the NeWS/PostScript interface library for XView. The library is called xvps and included with this source distribution. One must have OpenWindows to use this library. This document is included in the <XVIEW>/doc directory. Documentation may be purchased separately: XView Programming Manual (revised for version 2) This manual provides both a complete reference guide to the XView Toolkit and a basic introduction to developing applications with it. The examples from the book are included in <XVIEW>/contrib/examples. XView Programming Manual, O'Reilly & Associates, Inc. Address: 632 Petaluma Avenue, Sebastopol, CA 95472 email: uunet!ora!nuts, phone: 1-800-338-6887, 1-707-829-0515 fax: 1-707-829-0104 OPEN LOOK Graphical User Interface Functional Specification This manual specifies how the toolkit and new toolkit components should implement the OPEN LOOK graphical user interface. OPEN LOOK Graphical User Interface Functional Specification, Addison-Wesley Publishing Company, Inc., 1989 OPEN LOOK Graphical User Interface Application Style Guidelines This manual provides guidelines for developing an OPEN LOOK compliant application with any toolkit. It's a good resource for any developer adding a graphical user interface to their applications. OPEN LOOK Graphical User Interface Application Style Guidelines, Addison-Wesley Publishing Company, Inc., 1989 Also, one will want an Xlib reference manual as well. All of these books are available at technical book stores or may be ordered. If you have OpenWindows version 2 from Sun Microsystems, these books are included in the Developer's Documentation Set.
hvr@eng.sun.COM (Heather Rose) (08/14/90)
XView version 2.0 source release
xview2-announce announcement of XView sources
xview2-more follow up information for announcement
xview2-ftp this file
xview2.tar.Z.a[a-i] split compressed tar file pieces
FTP sites for XView source:
Location Machine Name ftp login ftp directory
---------------------------------------------------------------------
west coast xview.ucdavis.edu ftp pub/XView2.0/*
east coast expo.lcs.mit.edu ftp pub/contrib/xview*
When transfering a tar file via ftp, be sure to set binary mode first.
The split pieces are all less than 512k (524288 bytes) long and must
be transfered in image mode (use the ftp "binary" and "mget" commands).
If you are doing an "mget" you'll probably want to restart ftp with
the "-i" option to prevent it from asking you about every file.
Here are the sizes of those pieces:
527052 xview2.tar.Z.aa
624920 xview2.tar.Z.ab
467928 xview2.tar.Z.ac
446444 xview2.tar.Z.ad
475499 xview2.tar.Z.ae
523285 xview2.tar.Z.af
533217 xview2.tar.Z.ag
533981 xview2.tar.Z.ah
1469 xview2.tar.Z.ai
total size: 4133795 bytes
BSD checksums:
22395 515 xview2.tar.Z.aa
16674 611 xview2.tar.Z.ab
40901 457 xview2.tar.Z.ac
40217 436 xview2.tar.Z.ad
03253 465 xview2.tar.Z.ae
02130 512 xview2.tar.Z.af
29054 521 xview2.tar.Z.ag
50894 522 xview2.tar.Z.ah
10008 2 xview2.tar.Z.ai
System 5 style checksums:
% /usr/5bin/sum *.a*
3219 1030 xview2.tar.Z.aa
18489 1221 xview2.tar.Z.ab
32292 914 xview2.tar.Z.ac
30830 872 xview2.tar.Z.ad
33429 929 xview2.tar.Z.ae
53093 1023 xview2.tar.Z.af
2324 1042 xview2.tar.Z.ag
35743 1043 xview2.tar.Z.ah
24259 3 xview2.tar.Z.ai
To recreate the compressed tar file, can do the following:
% cat *.tar.Z.?? | uncompress | (cd /usr/local/src/xview; tar xvf - )
which create a directory called "fcs" in the directory /usr/local/src/xview.
Can rename this to anything you like. See the README file in that directory
on how to begin building the XView source.
Unpacked XView source requires approximately 12.5+ MB of disk space.rehmann@.iam.unibe.ch (Rene Rehmann) (08/15/90)
Compiling XView 2.0 source WARNING WARNING WARNING ======================= Before doing a "make World" be shure to "imake" the top-level Makefile. This is not remade and can lead to incorrect paths. This is especially dangerous when doing a make clean. Then the top-level Makefile makes a "rm -f -r $(BUILDINCTOP)" (why ??) which pointed in our case to the root directory. Normally (e.g. X11R4) when doing a "make World" the top-level Makefile is remade by imake which produces correct paths. -- Rene Rehmann, Dep. of Computer Science, ! rehmann@iam.unibe.ch or U. of Bern, Laenggassstrasse 51 ! rehmann%iam.unibe.ch@relay.cs.net CH-3011 Bern, Switzerland ! UUCP:uunet!mcsun!iam.unibe.ch!rehmann Phone: +41 31 65 89 64 or +41 31 65 86 81 Fax: +41 31 65 39 65