Release 10.1A: OpenEdge Development:
Progress Dynamics Web Development Guide

> ## Client logic

> Client logic is implemented through the client logic API. The client logic API is a collection of functions that extend the visual class, and a programming standard that supports easier development of client-side user interface logic in containers, browses, viewers, and other visual objects.

> The client logic API essentially supports widget manipulation in containers, browses, viewers, and visual objects in both static and dynamic objects. For example, you might want to enable some fields in a dynamic viewer based upon the value of another field. The API, in particular, makes it much easier to associate code with one browse or viewer and have that code manipulate widgets in a different browse or viewer (as long as both are in the same container).

> You can use the client logic API in static object code or in custom super procedures for dynamic objects.

> Note that an application for both the GUI and DHTML clients must maintain two versions of client logic, one written in 4GL for GUI rendering and another written in JavaScript for Web browser rendering. This chapter describes the client logic API for DHTML applications. For information on the 4GL applications, see OpenEdge Development: Progress Dynamics Basic Development .

> A JavaScript file named install_dir`\tty\dynamics\ry\dhtml\rylogic.js` implements the API. The default HTML file contains a reference to `rylogic.js`. The Logic object is the internal definition of this file. As with other JavaScript objects supplied with Progress Dynamics, you can extend the Logic object in your own JavaScript file.

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095