Plug-in software designing method based on document tree and message pump

Abstract

The invention discloses a plug-in software designing method based on a document tree and a message pump. The method comprises the following steps of: splitting software into a plurality of plug-ins according to functions, wherein each plug-in corresponds to one or more functional modules and is divided into a model layer, a view layer and a control layer; and extracting data and documents in the model layers of all the plug-ins to form a management document with a tree structure. By the method, communication between the modules is quickened and simplified, and extensibility and maintainability of a system are improved. On the aspect of view management of the plug-ins, views are uniformly managed by adopting a framework container; and by the method, as long as the document data of a new plug-in are derived from the same base class, the document can be connected to the document tree, so that extension of the software functions is facilitated.

Description

technical field [0001] The invention relates to the field of computer software design, in particular to an enhanced management method for software reuse on a computer. Background technique [0002] With the industrialization of software, software reuse has evolved from a general-purpose class library to a domain-oriented application framework. The application framework emphasizes the reusability of software design and the scalability of the system, so as to shorten the development cycle of large-scale application software systems and improve the development quality. In the face of this development trend, a brand-new, open, and highly scalable architecture system is ready to emerge, that is, plug-in software design, which divides software by functional blocks. [0003] Interactive software usually adopts the layered approach of MVC (Model)-View (view)-Controller (controller) in software architecture design, and Event (event) causes Controller to change Model or View, or both...

AI Technical Summary

Problems solved by technology

[0008] 1. There are some advantages in adopting flat management documents, but it depends too much on specific classes, it is not easy to abstract a unified document interface, and the scalability is poor; for example, in the above example, the root node of a certain software is not Solution but Others, then a lot of software changes are required;

[0009] 2. Failure to separate document management from document data (such as name, description information), which violates the Single Responsibility Principle (SRP) of the software;

[0010] 3. For data with a hierarchical relationship (such as folders in the project and folders in the folders), it cannot be reflected in the data structure;

[0011] 4. This flat management is not convenient for files to be split when loading and merged when saving;

[0012] 5. The tree structure is less efficient when traversing locally

[0016] 1. Views are divided into two categories, which are managed by a unified platform (DefaultWorkbench). It is difficult to expand special views other than panel and document views, and does not meet the Open-Closed Principle (OCP);

[0017] 2. The framework and documents are glued together, which is not easy for software maintenance and expansion

Images