|
 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's then call the native API, for all 14 Platofrm/OS's we support. Platform independent C/C++.
The XVT interface is identical on each window system that we support. Because the XVT interface is an abstraction of existing programming interfaces, it is easy use, but it still provides similar functionality to that available in the native window systems.  To build an application with XVT, a programmer writes his own source code and resources making calls to the XVT software. The implementation of the XVT software calls native windowing system functions. This source is compiled and linked with XVT libraries as well as native GUI libraries. To port, the developer moves his source code and resource files to a new platform, recompiles, and links with the XVT and native libraries for that platform. Porting XVT Applications: Write Once, Build Everywhere The port of an XVT application requires moving all source files (C or C++), header files, resource files and help files to the target platform, recompile the C/C++ files with a native C/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 you can move from platform to platform. With XVT, identical application source code runs on all platforms and looks native 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. 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 system. |
|
Last Updated ( Monday, 15 September 2008 )
|
|
|
 Event Tags
Event tags correspond to the events in the XVT API: events that are generated by user actions (for example, mouse clicks) or by the window system (for example, update events). Special Tags Special tags do not correspond to events but rather serve as convenient places to add functions and variable declarations to the framework code. Availability The following table describes which tags are available for each type of user-interface object: the application itself, windows, dialogs, controls, menubars, and menu items:
(image enlarged in full article) |
|
Last Updated ( Friday, 11 July 2008 )
|
|
Read more...
|
|
|
Portable GUI
XVT-Design is a graphical, interactive design tool and application generator. With the C code generated by DSC, you can expect native platform performance. DSC is not an emulator, and it doesn't require a runtime component. DSC guides you through the development process from defining the architecture to laying out the interface to building the final application. Using the DSC libraries, you simply compile on all the platforms you need. With DSC, you can: - Quickly lay out the user interface - no need to calculate and program the screen coordinates
- Customize screen layouts for different monitors
- Automatically preserve and regenerate the modifications you make to the C code
- Achieve native language performance without learning proprietary languages or different toolkits
- Integrate existing or third-party development tools
(image enlarged in full article) |
|
Last Updated ( Monday, 13 April 2009 )
|
|
Read more...
|
|
|
XVT-Design is a graphical, interactive design tool and application generator. It simplifies the design and implementation of graphical-user-interface (GUI) based applications in three major ways: - XVT-Design lets you create the user-interface objects of your application (windows, controls, menus, and so on) graphically and interactively, rather than by programming manually.
- XVT-Design provides a TestMode that lets you preview your application’s user interface without separate compilation and linking steps. You can use XVT-Design to build and refine application prototypes rapidly without writing any code.
- XVT-Design generates event handlers and other source code for your application’s user interface. Instead of rewriting“generic” user-interface code by hand for each new application, you can use XVT-Design to create this code automatically.
|
|
Last Updated ( Monday, 15 September 2008 )
|
|
Read more...
|
|
|
GUI Objects
A graphical user interface (GUI) has four main types of graphical components: windows, dialogs, controls, and menus. You can lay out all these GUI objects with XVT-Design. XVT-Design also constructs the C-language source code to manage the objects.
Portable Resources
XVT-Design transforms your WYSIWYG layout of GUI objects into a portable resource language called URL. Since the URL code is portable (platform independent), you need only use XVT-Design to generate it once. You can compile the URL code to any supported native resource format. XVT's curl compiler translates URL resource specifications into the native resource language. The native resources are bound to the executable program, either by loading the resources directly into the executable image or by creating a resource file with a canonical name. (Native environments use differing methods to bind resources.) Universal Resource Language (URL) file
This file defines the external resources of the project. You can inspect these files, or change their names, by choosing Generate Application from the File menu. Note: The project file does not display when you choose Generate Application. The prefix of the project filename matches the name of the project, but you can configure its suffix in XVT-Design's configuration file. |
|
Last Updated ( Monday, 15 September 2008 )
|
|
Read more...
|
|
|
