RemObjects HydraHydra is an application framework that allows developers to create modular applications that can mix managed (.NET) and unmanaged (native Delphi) code in the same project, creating a seamless user experience while combining the best technologies available from either platform. |
Hydra is an application framework that allows developers to create modular applications that can mix managed (.NET) and unmanaged (native Delphi) code in the same project, creating a seamless user experience while combining the best technologies available from either platform. Hydra 3.0 builds on the tradition of our Hydra framework for Delphi to bridge the gap between the worlds of unmanaged Delphi code and the new Microsoft .NET platform. Today, many Delphi developers consider migrating to the .NET platform, either to make use of its advanced development capabilities or to leverage new technologies such as the Windows Presentation Foundation or LINQ. At the same time, they are hesitant to leave behind the existing investment in their extensive Delphi code base. Hydra 3.0 – provided in one SKU for both Delphi and .NET – enables you to keep your investment in your existing Delphi/Win32 code base, while at the same time opening your applications to managed plugins. This allows new development to happen in .NET, for example using C# or Oxygene/Prism, or any other languages available for .NET. At the same time, the existing code can be kept and maintained in Delphi/Win32, and both parts can contribute to what appears to the end user as a single, unified application. This makes it possible to employ new and emerging .NET technologies within your existing Delphi/Win32 based frame. For example, you might decide to implement fancy diagrams using the hardware-accelerated Windows Presentation Foundation (WPF) introduced in .NET 3.0 (as in the example shown on the left), or to use technologies such as LINQ to access and manage data. Hydra is also helpful in migrating applications to .NET altogether, in a step-by-step fashion. Developers can start by modularizing their existing Win32 code base, and extend it with .NET code or port selective modules over to .NET, where it makes most sense (for example those modules that still see most active development and would benefit most from using new, .NET based development technologies). Over time, they can elect to port and replace the remaining modules (and even the host application) over time and at their own pace. They can keep working on the project in mixed-mode, or eventually to a fully managed solution, once all parts are ported.
|