Model-View-Controller Framework

Summary

This section covers high-level documentation for the generated .NET solution, which is architected using the Model-View-Controller design approach. The key advantages of the MVC approach include:

•	Supports an event-driven approach to host applications, which may implement thousands of function points that cannot be duplicated or anticipated in the UI layer

•	Insulates UI developers from data access issues

•	Provides clean code update patterns for migrating selected tasks or subtasks from screen-based access to superior alternatives

Controlling Properties

UIProject.AllScreensNavigation, UIProject.DateFormat, UIProject.HomeScreenName, UIProject.PooledSessionSupport, UIProject.ScreenBackwardKeyScreenBackwardKey, UIProject.ScreenCancelKey, UIProject.ScreenClearKey, UIProject.ScreenExitKey, UIProject.ScreenEnterKey, UIProject.ScreenForwardKey, UIProject.ScreenSelectionKey, ScreenDef.NavigationType, ScreenDef.IgnoreNavigationFields, ScreenDef.ExitKey, Field.NavigationUse, Field.NavigationJumpField

Details

The following diagram provides a high-level view of the key classes involved in the implementation of the E-Migration UI Framework.

Mouse-over popups are provided for each block in the diagram--please mouse-over the diagram to better understand the relationship between the elements.

MVC

Bottom of page