XVT's WYSIWYG GUI Layout provides common representation of events, windows, fonts, graphics, and many other control/interface features. Instead of calling the functions available on each individual native window system, the application makes calls to the XVT Universal API Library. The XVT API then calls the native API, for all 14 supported Platform/OS's (Windows, Mac, Unix, Linux)
The XVT interface is identical on each supported window system. Because the XVT interface is an abstraction of existing programming interfaces, it is easy use, but still provides similar functionality to that available in the native window systems.
The port of an XVT application requires moving all source files (C++), header files, resource files and help files to the target platform, recompile the C++ files with a native C++ compiler (not provided by XVT), recompile the resource file using XVT curl compiler into a native resource file, compile the native resource file with the native resource compiler (not provided by XVT, either by compiler manufacture on PCs, or by native toolkit libraries for Motif), and link the object files using the native linker.
XVT front end tools work on portable binary projects that can be moved from platform to platform. With XVT, identical application source code runs on all platforms and runs natively on each. Rather than rewriting an entire application from scratch for each new windowing environment, developers can create and maintain one set of source code and address multiple environments. For this reason, XVT offers a tremendous savings in development time and costs for cross platform applications. The portability can open new markets and allow proprietary software to endure platform changes.
XVT applications obey appropriate user interface guidelines for each system. It is transparent to the end user that XVT was used in development; XVT applications appear and act as if they were coded specifically for the particular window