It took three weeks to write a flex-based Web process designer prototype system to the company. Since it is a prototype system, there must be a lot of nuances that are not perfect, but as part of future product components, its pre-Research and architecture components are still very good.
Flex itself provides good graphical support, but to achieve the separation of model and view, command processing and other basic things, this cannot be compared with eclipse GEF.
First, we had to simulate GEF and provide a model-editpart MVC Architecture and command Framework framework at the underlying layer. Once these two basic frameworks are built, the response and processing between "model", "View", and "action" can be well solved, as well as graphic display and rendering.
We have time to change the course. Let's share with you the ideas and implementation of this architecture. Let's show it first:
Drag-and-drop operations are not complex. The key is how to resolve the ing and response between the model and view. In addition, the activity icons and types in the pallete must be easily scalable.
All models must implement the toxml and fromxml interfaces, so that the ing between objects and XML can be easily realized. Of course, the model itself also needs to introduce some listener mechanisms so that views and other editing components can respond to changes after the model is changed.
Attribute panel was originally designed as "dynamic configuration-based loading". I did not expect that flex itself was not ideal for the dynamic loading class, resulting in poor implementation of this module.