Understanding action paradigm

One of the most encountered problems in any application development process is overriding components default behavior, especially those where the source code is not available. In several integrations of previous versions of the visualizer and the diagrammer, this aspect is recurrent. We have considered such requests and have conceived a system that gives developers total control on the internal behavior of the visualizer and the diagrammer. This system has several features and purposes:

The main aim of the action paradigm is to make the Visualizer and the Diagrammer more flexible since the user can override the default existing actions or add his own actions. This "action" based architecture makes the visualizer an open system that can be enriched with many plugins. The main principle of this architecture is to develop independent actions that implement the IAction interface. Then, the user should register his action on the main Visualizer.as class so that it can be handled by the component. The different status value, that will be discussed on the next section, add more flexibility to the system.

To get more details about how to add new actions you can refer to the Injecting custom actions section.