Dynamics4.NET is the fastest way to migrate your Dynamics or ADM2 application to OpenEdge GUI for .NET. Gain advantage of the competitive user interface of OpenEdge 10.2 without affecting your business logic and with minimum changes to your development process. A unique possibility to protect your investment in your Dynamics development.
Consultingwerk Ltd. has developed the alternative rendering engine for Progress Dynamics (OpenEdge Studio Framework) based applications. This rendering engine is based on OpenEdge GUI for .NET and offers a high level of compatibility with existing Dynamics applications. With Dynamics4.NET we are focusing on the migration and maintenance of existing Dynamics applications well as new development.
• Protect investment made in Dynamics development
• Improve competitiveness with a state of the art user interface
• ADM2 based rendering engine, offering maximum compatibility with existing Dynamics applications
• Migration to OpenEdge GUI for .NET by changing attributes in the repository using migration utilities instead of manually changing UI design, rewriting code or even change the framework foundation
• "Mix and match" operation with the classic Dynamics rendering engine, including links between .NET and Progress UI based windows
• Container support: Dynamic object controller, folder window, treeview container and dynamic SmartFrame
• MDI container support (optional), MDI Menu controller
• SmartObject support: DynBrowser, DynViewer, DynToolbar, …
• SmartDataField support: DynLookup, DynCombo, …
• Dynamic rendering or static code generation (PGEN)
• Implementation of the client logic API provides abstract access to .NET controls from client side logic procedures and reduces code changes
• Compatibility layer eases migration of custom code that does not use the client logic API
• Progress Dynamics Managers opened up object oriented programming
The rendering engine enhances the appearance of a Dynamics application with a modern .NET based user interface. Dockable panes, MDI support, graphical toolbar objects, Ribbon and explorer bars are provided to improve the presentation layer. Infragistics controls enhance the user experience when working in input forms (e.g. calendar or calculator controls). Multiline layout, card views, etc. enhance the visual appearance of browsers in the application. Modern control sets like calendars or graphs can be utilized to display and edit data in a more natural and advanced way. Drag and drop can be used for filtering data or as an event to your business logic to update information as required.
The .NET resizing supports the usage on screens of virtually any resolution. The resizing is controlled using native .NET WinForms resizing attributes stored in the Dynamics repository (Dock, Anchor) and are supported by literally every .NET control. .NET controls enable a much faster rendering process and smoother and faster resizing than the previously used Progress widgets.
Customizing, translation and security are supported by the Dynamics4.NET rendering engine as they are supported by the standard rendering engine.
The rendering engine is based on the most recent release of Progress Dynamics. Compatibility is achieved by making required changes only to the repository manager and related Dynamics components. The visible components of the ADM2 and rendering objects are rewritten using a compatibility layer. An alternative set of rendering objects uses standard repository definitions and creates.NET controls. The compatibility layer is built with ABL classes and custom .NET controls that close the functional gap between .NET controls and ABL widgets. Standard Dynamics components like the filter screen, the message dialog or the login prompt are rewritten using the same method. The client logic API and the compatibility layer support developers of client logic by only requiring the minimum set of changes to existing code. Business logic is not affected by the changes at all.
Dynamics manager access has been OO enabled. Thus the usage of the manager’s functionality is simplified even when designing additional static components using the Visual Designer of OpenEdge 10.2.
Our SmartComponent Library framework integrates seamless into Dynamics4.NET. SmartComponent Library Forms can be started from menu controllers and toolbars and fields can be secured using the Dynamics security manager.
Migration of existing applications requires changing the rendering engine for each affected object by changing the object type (i.e. from DynObjc to DynObjc.NET, DynView to DynView.NET). This change can be done manually using standard Dynamics tools or automated for a complete container or a set of containers using our migration utilities. These tools also support the creation of copies of nested objects used in instances. This is very useful when a viewer is used in a container that is already migrated and in a container that has not (yet) been migrated. Dynamics4.NET is flexible enough to leverage customizations to an existing Dynamics and ADM2 environment.
An initial migration should be done together with our consultants in a 5 day workshop. This workshop covers training and the migration of (parts of) your application. Customized .NET features will be added to enhance the user experience even more.
Ready for OpenEdge 11
Dynamics4.NET is currently shipped and supported on OpenEdge 10.2B. However our development team has already ensured compatibility with the upcoming major release. With the commercial availability of OpenEdge 11 our customers will instantly be able to use the new core features such as Multi-Tenancy which we will be supporting thought enhancements to the Dynamics Session- and Security-Manager. The use of the new core language objects for communicating with the OpenEdge BPM/Savvion is available through the SmartBPMAdapter add-on. New functionality is available to our customers with updating to the latest framework version. Our tools are tested using the latest OpenEdge UltraControls (Infragistics Controls) to ensure that your application supports the look and feel of Microsoft Office 2010. We will be supporting the latest additions to the ABL programming language as soon as they are available.