What differentiates the DataFace product from other frameworks?
- SMART-CLIENT TECHNOLOGY
- Compared with browser-based applications: response times are better; only data moves across the network; servers are almost stateless; multiple servers are easily combinable; audit logs are easily activated locally; security is better.
- AN EASILY-UNDERSTOOD APPLICATION DEFINITION LANGUAGE
- Instead of obscure scripting languages spread across huge numbers of web pages, everything you want is contained in a simple XML file with many attributes that you can adjust to control the appearance of the application.
- DYNAMIC FORMS ARCHITECTURE
- Screens are built up in 7 layers. There are standard default components for each layer. Alternative components exist for each layer, and implementors can replace DataFace components with their own, writing to the same published interfaces.
- CUSTOMIZATION THROUGH EVENT PROCEDURES
- The event model is extremely familiar to all .NET programmers. The DataFace runtime raises events in just the same way. Every event includes a microhelp explanation and can be canceled one time or suppressed permanently.
- VALIDATION DERIVED FROM CHECK CONSTRAINTS
- The AppManager retrieves all validation rules from the database and the runtime executes them locally on the workstation. Additional validation can be written as JavaScript, regular expressions, built-in DataFace functions, event procedures, or custom procedures.
- A POWERFUL SQL CATALOG MECHANISM
- The DataFace SQL catalog extends the concept of parameterized queries to provide enhanced specialization of SELECT statements or stored procedure calls. Implementors have complete flexibility to add to the catalog or to disregard it.
- AN EDITING MECHANISM FOR COMPLEX DATA
- As well as the familiar concepts of parsing, validating, and formatting, the DataFace runtime's flow control includes a "selector" operation for data which cannot easily be typed into a text box. Selectors are built into the system for editing long text, simple xml, foreign keys, codes, and displaying photos and web pages. Implementors can add custom selectors, observing the published interface contract.
