Features
  • Xponent uses a Design Repository - a database of design information.

  • Xponent provides standard object types and models for business application functions.

  • The easy-to-use development environment has a painter, attribute editors, and a code editor.

  • Design analysis shows where and how tables, fields, and code elements are used.

  • Each object inherits standard capabilities for security, context-sensitive help, and printing.

  • The Xponent Builder generates optimized code to run against various databases.

  • Xponent provides links to applications like imaging, word processing, and spreadsheets.


    		•
    Objects, Models, and Templates
    Xponent's set of object types are the building blocks for database applications: entries, outputs, queries for database access, and jobs for multi-step tasks.

    These object types all have a clear, hierarchical structure. Objects have different object models and, at a lower level, object attributes to define different behaviors.

    An Xponent developer usually begins with a template using a particular object model and set of attributes, with perhaps a set of buttons and some standard code.
    The Design Environment
    The Xponent Design Environment is a powerful, flexible, easy-to-use workspace. It uses a graphical painter and several attribute editors for quick design.

    Xponent attribute editors go beyond the attributes in most development tools. Xponent attributes specify not only window or component size, position, and so forth, but also actual object behavior.

    Developers can work on multiple objects at once and have immediate access to tools for dictionary queries, design analysis, object status and messages.

    Xponent developers use a code editor to write Progress code at pre-defined event points. Because Xponent takes care of routine behavior like record management, window control, online help context, and printing, Xponent developers use code only for specific application functionality.

    Xponent developers rely on a clear object structure with well-defined event points and internal procedures. They use a set of system variables, preprocessor arguments, and built-in functions to keep their code maintainable. The clear structure and set of standard techniques is shared among all Xponent developers - they all talk the same language.

    Design Analysis
    Because Xponent uses a design repository, design information is readily available for review and analysis. First, Xponent objects have names like 'Work Order Tasks' instead of unintelligible procedure ID's. All development is maintained as catalogued objects, with statuses, change information, and clear internal structure.

    Developers can print Technical Documentation on any object—at several levels of detail. Even when objects become complex, their structure is always readily apparent. Developers have instant access to 'where used' information for tables, fields, searches, and code queries.

    Xponent Configuration Management uses the design repository to provide an additional management capability with design history, configurations, additional analysis tools, and deployment packaging.

    Application Architecture
    Xponent goes beyond object design to provide a true application architecture. Xponent's object structures are designed for a persistent, messaging environment where several windows are active at once and exchange information. Xponent runtime services such as online help, security, printing, and task management are fully integrated into the application environment.

    The Xponent Object Controller registers all objects as they are instantiated and maintains information about them. Applications and objects route messages via this central controller for a comprehensive architecture.