Visual Component Framework - Design and Goals

Design and Goals

The framework is designed with several goals in mind. One is the ability to be ported to other platforms beyond Windows, such as Mac OS X, BeOS, or possibly even embedded operating systems like Windows CE.

The next goal is to provide solid support for dynamic programming such as that found in languages like Borland's Object Pascal, Java, or Objective-C. This included RTTI or reflection like classes that allow the developer to query all sorts of information about a given class instance at runtime.

Another goal was to design the UI classes so that visual programming or rapid application development was possible, similar to what is found in Delphi. This includes support for property editors, component editors, persistence of the UI state to and from an external text file, and making use of the dynamic features to create class instances on the fly and get and set the instance's registered properties.

In addition to this, the last goal was to provide support for a large number of common programming tasks when developing an application, particularly for larger scale applications. This includes support for various kinds of IO (in memory, file/disk, and so forth), thread support and various synchronization primitives like mutexs, semaphores, and conditions, Unicode string support, locale and internationalization support including localizing string resources, comprehensive resource support, and basic XML parsing. Graphics features include anti-aliased graphics using the Anti-Grain Graphics Library, full affine transformation support, images with direct access to the image's pixel bits. Additional application support features also include undo/redo classes, advanced support for Model View Controller.

As a general rule, the framework makes as much use as possible of the Standard Template Library, avoiding duplication of work on things like container classes, or string handling.

Where possible the framework builds on top of the native C++ RTTI support such as using dynamic cast and typeid, as opposed to simply re-implementing it.

Most OS objects, such as files, threads, graphics devices, and window controls (or widgets), and so on, are implemented using a thin layer that talks directly to the specific native object. UI controls are not emulated for the most part, instead the framework uses native widgets in most places. Direct access to the underlying OS "handle" is allowed in cases where platform specific functionality is needed, allowing the developer to easily call the platform's native APIs.

Read more about this topic:  Visual Component Framework

Famous quotes containing the words design and/or goals:

    Joe ... you remember I said you wouldn’t be cheated?... Nobody is really. Eventually all things work out. There’s a design in everything.
    Sidney Buchman (1902–1975)

    We should stop looking to law to provide the final answer.... Law cannot save us from ourselves.... We have to go out and try to accomplish our goals and resolve disagreements by doing what we think is right. That energy and resourcefulness, not millions of legal cubicles, is what was great about America. Let judgment and personal conviction be important again.
    Philip K. Howard, U.S. lawyer. The Death of Common Sense: How Law Is Suffocating America, pp. 186-87, Random House (1994)