Visual Inheritance

Alchemy CATALYST supports visual inheritance as implemented within the Microsoft .NET Framework Version 1.1, 2.0 and 3.0. This allows developers of .NET applications to reuse winforms or controls, previously defined in an application, to make up new ‘inherited’ winforms or controls.

This can lead to dependencies within your .NET application and other external files such as 3rd party controls. When Catalyst is parsing .NET binary files, other assembly files that are referenced within that binary file may be needed to complete the parsing process successfully.

In the case of inherited winforms and user controls that exist in external assemblies, Alchemy CATALYST uses the .NET Framework to resolve the vast majority of these dependencies and references. This information is stored in the Global Assembly Cache (GAC).  Using this information Alchemy CATALYST can locate and load these external assemblies as appropriate.  See Customising .NET Component for more information.

Viewing Relationships between Inherited Forms

Use the Inheritance View in the Project Navigator to view the relationships between inherited objects. For more information on this please refer to Overview: Dialog Editor.

In the example above, the Project Your project is where you manage and organize all the files that are to be localised. Navigator displays an inheritance tree for the winform Microsoft name for a .NET Dialog Panel Generic name given to dialog boxes. A Dialog Panel is an internal CATALYST object that is used to represent dialogs from multiple development platforms. (ie .NET Windows, Desktop Dialog boxes, SmartPhone Canvas Areas, ASP+ Pages, XLIFF Frames, Oracle Forms. etc.).Dialog Panel . in the Dialog Editor. This is a hierarchical list of sub-forms which are combined together using visual inheritance Introduced by Microsoft and Borland. It allows developers to create complex UI elements using previously defined Winforms or objects. to make this final form.