เข้าสู่ระบบ สมัครสมาชิก

xview การใช้

ประโยคมือถือ
  • Sun continued to enhance its version to make its look and feel more consistent with XView.
  • "' XView "'is a widget toolkit from Sun Microsystems introduced in 1988.
  • Developers building OPEN LOOK applications could choose between two graphical programming libraries : the OPEN LOOK Intrinsics Toolkit ( OLIT ) or XView.
  • The last release supported the programming languages C + + ( Corba2 mapping ), ANSI C, Tk, XView ) operation.
  • OpenWindows comprised four components : the OPEN LOOK Window Manager ( olwm ), the DeskSet productivity tools, the XView and OLIT widget toolkits, and the underlying X11 / NeWS window server.
  • Support for running and displaying applications built with XView or OLIT remains in both Solaris 9 and Solaris 10, but the necessary libraries are no longer included in Solaris 11 and later releases.
  • With the release of Solaris 9 in 2002, the removal of OpenWindows support from Solaris finally began, as the OPEN LOOK DeskSet tools, OLIT and XView development tools, and olwm were removed.
  • Its interface, controls, and layouts are very close to that of the earlier SunView window system, making it easy to convert existing applications from SunView to X . Sun also produced the User Interface Toolkit ( UIT ), a C + + API to XView.
  • Speed problems plus the existence of programs that relied on the exact pixel results of X10 calls, and the obsolescence of X10, forced Sun to release an X11 / NeWS hybrid called " Motif, and XView used the same APIs as Sun's earlier SunView window system.
  • In an emulated user interface, the PIGUI's resultant code produces low-level calls and all the look-and-feel compliance is handled by the PIGUI software itself ( e . g ., for OpenWindows support, the software would NOT produce an XView program that must be compiled with the XView toolkit; the software would produce code that interfaces directly with Macintosh-style UI will look ( since the look-and-feel is part of the product ).
  • In an emulated user interface, the PIGUI's resultant code produces low-level calls and all the look-and-feel compliance is handled by the PIGUI software itself ( e . g ., for OpenWindows support, the software would NOT produce an XView program that must be compiled with the XView toolkit; the software would produce code that interfaces directly with Macintosh-style UI will look ( since the look-and-feel is part of the product ).