[go: up one dir, main page]

CN119903262B - CAD front-end and back-end interaction method and system based on service message transfer mechanism - Google Patents

CAD front-end and back-end interaction method and system based on service message transfer mechanism

Info

Publication number
CN119903262B
CN119903262B CN202510400957.3A CN202510400957A CN119903262B CN 119903262 B CN119903262 B CN 119903262B CN 202510400957 A CN202510400957 A CN 202510400957A CN 119903262 B CN119903262 B CN 119903262B
Authority
CN
China
Prior art keywords
tool
message
tool setting
cad
class
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202510400957.3A
Other languages
Chinese (zh)
Other versions
CN119903262A (en
Inventor
王志宁
高建朋
周雅丽
徐震
袁建平
郑波
杨帆
杨礼国
陈鑫
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Zhejiang East China Engineering Digital Technology Co ltd
PowerChina Huadong Engineering Corp Ltd
Original Assignee
Zhejiang East China Engineering Digital Technology Co ltd
PowerChina Huadong Engineering Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Zhejiang East China Engineering Digital Technology Co ltd, PowerChina Huadong Engineering Corp Ltd filed Critical Zhejiang East China Engineering Digital Technology Co ltd
Priority to CN202510400957.3A priority Critical patent/CN119903262B/en
Publication of CN119903262A publication Critical patent/CN119903262A/en
Application granted granted Critical
Publication of CN119903262B publication Critical patent/CN119903262B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/958Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
    • G06F16/986Document structures and storage, e.g. HTML extensions
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F30/00Computer-aided design [CAD]
    • G06F30/10Geometric CAD
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/30Creation or generation of source code
    • G06F8/36Software reuse
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/451Execution arrangements for user interfaces

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Geometry (AREA)
  • Computer Hardware Design (AREA)
  • Evolutionary Computation (AREA)
  • Pure & Applied Mathematics (AREA)
  • Mathematical Optimization (AREA)
  • Human Computer Interaction (AREA)
  • Mathematical Analysis (AREA)
  • Computational Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The invention provides a CAD front-end and back-end interaction method and system based on a service message transmission mechanism, wherein the method comprises the following steps of S1, when a system is initialized, starting a process corresponding to a front-end type according to the front-end type, loading all tools, registering a public message processing class object, starting a message manager and a tool setting manager, registering an extended message processing class object and a tool setting view corresponding to the front-end type, and starting a tool setting view manager corresponding to the front-end type, and S2, responding to user operation, transmitting and processing messages between the front-end and a cloud CAD service, and executing modeling operation. According to the scheme, front-end and back-end separation is achieved by considering coexistence of the middle end and the cloud of the CAD platform, a set of codes is achieved in a unified frame to support multi-front-end operation, and interactive engineering modeling design under the environment of multiple front-ends is achieved.

Description

CAD front-end and back-end interaction method and system based on service message transfer mechanism
Technical Field
The disclosure relates to the technical field of engineering digitization, in particular to a CAD front-end and back-end interaction method and system based on a service message transmission mechanism.
Background
CAD (Computer AIDED DESIGN) is used as a core digitizing tool of modern engineering design, and provides full-flow support for geometric modeling, parameter analysis, scheme optimization, drawing generation and the like for designers through deep fusion of Computer graphics and numerical computing technology.
CAD is an important technical means in the field of modern engineering design, and currently mainstream CAD software, such as AutoCAD, revit, microstation, CATIA, is heavy desktop software, and needs a computer with stronger performance and a software installation package with larger volume, so that along with the improvement of the requirement on the design work efficiency, the defects of high requirement on the performance of a client computer, inconvenient use, difficult collaboration, difficult management of data, complicated software upgrading and the like are gradually revealed, and for these problems, some solutions of cloud CAD are also derived.
However, at the present stage, the client CAD software is still mainstream, and at the same time, the cloud CAD platform is being accepted by designers. However, the existing CAD platform architecture has the problems that (1) the front end and the rear end of the existing CAD software are in high-level coupling, so that code maintenance is difficult, function expansion is limited, and (2) the existing CAD software is difficult to adapt to various front end types such as a Web end, a desktop end and the like at the same time.
Disclosure of Invention
The invention provides a CAD front-end and back-end interaction method and system based on a service message transmission mechanism, which can realize front-end and back-end decoupling in CAD platform end and cloud coexistence application, and support multi-front-end operation through one set of codes, so that interactive engineering modeling design is realized in a multi-front-end environment.
In a first aspect, the present disclosure provides a CAD front-end and back-end interaction method based on a service messaging mechanism, including:
Step S1, when the system is initialized, starting a process corresponding to the front-end type according to the front-end type, wherein the process comprises loading all tools, registering a public message processing class object, starting a message manager and a tool setting manager, registering an extended message processing class object and a tool setting view corresponding to the front-end type, and starting a tool setting view manager corresponding to the front-end type;
the public message processing class comprises a command message processing class, an extension message processing class comprises a Web end tool setting view message processing class and a desktop end tool setting view message processing class;
Step S2, responding to user operation, transmitting and processing information between the front end and the cloud CAD service, and executing modeling operation, wherein the modeling operation comprises starting a tool;
The user starts the tool through the front end, the front end triggers the command message, the command message is sent to the cloud CAD service, the cloud CAD service receives the command message, the message is distributed to the command message processing object through the message manager for processing, the command in the message is operated, and a specific tool is started;
When constructing a specific tool, creating or inquiring a tool setting data class object of the specific tool by calling a method for acquiring tool setting data of a tool setting manager, and taking charge of maintaining the tool setting data class object;
In the specific tool loading process, creating a tool setting view message corresponding to the front end type, and transmitting the tool setting view message corresponding to the front end type to the front end by a tool setting view message processing class object corresponding to the front end type;
The tool setting view manager corresponding to the front end type receives the tool setting view message, inquires the corresponding view and displays the view.
In some embodiments, the front-end type is a Web end, the tool setting view message is formatted by a Web end tool setting view message processing class object, the tool setting view message is sent to the front-end through a data channel, the Web end tool setting view manager receives and parses the formatted tool setting view message, and when the front-end type is a desktop end, the front-end message transfer is realized by the desktop end tool setting view message processing class object through in-process communication and memory sharing.
In some embodiments, the common message handling classes further include a mouse message handling class and a keyboard message handling class;
step S2, responding to user operation, transmitting and processing information between the front end and the cloud CAD service, and executing modeling operation, and further comprising a running tool;
wherein, the running tool comprises the following steps:
After the tool is started, the system enters a tool state and carries out a tool operation process through user interaction, and the method specifically comprises the steps of receiving mouse information input by a user, processing and responding by a mouse information processing class object, receiving keyboard information input by the user, processing and responding by the keyboard information processing class object, and transmitting a response result to the specific tool;
The specific tool draws the model by monitoring the mouse message and the keyboard message and setting the data class object according to the tool of the specific tool.
In some embodiments, the command message includes instructions to turn on/off the specified tool through a menu and toolbar component in the UI interface.
In some embodiments, in step S1, the extended message handling class further comprises a tool setting data change message handling class;
in step S2, after the tool is started, the system enters a tool state, and performs a tool operation process through user interaction, and further includes:
When a user performs model drawing operation through mouse operation and keyboard operation and the cloud CAD service triggers the tool setting data class object attribute value to change, the tool setting data corresponding to the front end type changes the message processing class object, sends the variable quantity to the tool setting view corresponding to the front end type, and updates the tool setting view corresponding to the front end type.
In some embodiments, in step S2, after the tool is started, the system enters a tool state, performs a tool running process through user interaction, and further includes:
When a user carries out tool setting data class object attribute value modification operation on the tool setting view corresponding to the front end type, the tool setting view corresponding to the front end type sends the variable quantity to a cloud CAD service, the tool setting data corresponding to the front end type changes message processing class object processing, and the tool setting data class object of the corresponding tool is updated;
the specific tool sets the attribute value of the data class object according to the modified tool, and draws the model.
In some embodiments, between the front end and the cloud CAD service, the current end type is a Web end, the Web end tool setting data change message processing class object sequences the variable quantity and then sends the variable quantity to the Web end tool setting view through a data channel, and updates the view;
when the front-end type is a desktop end, the desktop end tool setting data change message processing class object and the desktop end tool setting view realize front-end and back-end data synchronization through in-process communication and memory sharing.
In some embodiments, the tool setting data class inherits an observable object base class, wherein the observable object base class is an implementation class of a message interface and is used for monitoring attribute value changes of sub-class objects of the observable object base class, and when one end operation of the front end or cloud CAD service causes the attribute value changes of the sub-class objects, an observable object message is triggered to inform the other end, so that the front end and cloud CAD service data synchronization is realized.
In some embodiments, the Web-side or desktop-side tool set data change message handling class relies on observable object messages to enable the transfer and synchronization of changes in the front-end and cloud CAD service tool set data class object attribute values.
In a second aspect, the present disclosure provides a service messaging mechanism based CAD front-end and back-end interaction system for executing the service messaging mechanism based CAD front-end and back-end interaction method, the system comprising:
the initialization module is used for starting a process corresponding to the front-end type according to the front-end type when the system is initialized, and comprises loading all tools, registering common message processing class objects, starting a message manager and a tool setting manager, registering an extended message processing class object and a tool setting view corresponding to the front-end type, and starting a tool setting view manager corresponding to the front-end type.
And the system operation module is used for responding to the user operation, transmitting and processing the message between the front end and the cloud CAD service and executing the modeling operation.
The beneficial effects of this disclosure lie in, compare with prior art, this disclosure has following advantage:
1) According to the technical scheme, SAAS is applied to the CAD desktop end by comprehensively considering the coexistence of the middle end and the cloud of the CAD platform, front-end and back-end separation is achieved, public classes and specific classes aiming at different front ends are created in a unified frame, and one set of codes supports multi-front-end operation. Specifically, the same set of codes is adopted by the webpage end (Web end) application and the desktop end application, and the system judges the front end type during initialization and dynamically loads the corresponding implementation mode. On the one hand, the method can reduce repeated codes to the greatest extent, improves the high availability and reusability of system codes, and on the other hand, can realize multi-terminal adaptation, perfectly integrate webpage end (Web end) application and desktop end application, ensure that one set of codes supports multi-front end operation, thereby realizing interactive engineering modeling design under a multi-front end environment.
2) By defining various message classes and message processing classes and creating tool setting data classes and specific tool classes, efficient processing and delivery of different types of messages and data between front and back ends is ensured. Through the classification and specialized processing mechanism, the front end and the back end can realize efficient communication and operation under various interaction scenes.
3) In the scheme, the front end and the rear end realize data synchronization based on observable objects, the data change of any one end can trigger the synchronization of the other end in real time, the risk of inconsistent manual coding and data is reduced, and meanwhile, the interface (View) and the service logic are thoroughly decoupled, so that a technical foundation is provided for a multi-front-end fusion framework, and the platform can be flexibly adapted to various front-end applications.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure.
Fig. 1 is a schematic flow diagram of a CAD front-end and back-end interaction method based on a service message delivery mechanism according to an embodiment of the present disclosure;
FIG. 2 is a schematic diagram of a UI interface for CAD front-end and back-end interactions based on a service messaging mechanism provided by embodiments of the present disclosure;
Fig. 3 is a schematic diagram of a multi-front-end implementation framework of a CAD front-end and back-end interaction method based on a service messaging mechanism according to an embodiment of the present disclosure;
fig. 4 is a schematic diagram of a multi-front-end implementation framework of a CAD front-end and back-end interaction method based on a service messaging mechanism according to an embodiment of the present disclosure.
Specific embodiments of the present disclosure have been shown by way of the above drawings and will be described in more detail below. These drawings and the written description are not intended to limit the scope of the disclosed concepts in any way, but rather to illustrate the disclosed concepts to those skilled in the art by reference to specific embodiments.
Detailed Description
The disclosure is further described below with reference to the drawings. The following examples are only for more clearly illustrating the technical aspects of the present disclosure, and are not intended to limit the scope of the present disclosure.
It should be noted that, the order of steps of the present disclosure is merely exemplary, and the order may be adjusted according to the need when actually performed, or some steps may be performed in parallel, and the order between steps does not constitute a limitation of the present disclosure unless the execution of a step explicitly depends on the result of the previous step.
Example 1
As shown in fig. 1, this embodiment provides a CAD front-end and back-end interaction method based on a service message delivery mechanism, which includes:
step S1, when the system is initialized, starting a process corresponding to the front-end type according to the front-end type, wherein the process comprises loading all tools, registering a public message processing class object, starting a message manager and a tool setting manager, registering an extended message processing class object and a tool setting view corresponding to the front-end type, and starting a tool setting view manager corresponding to the front-end type.
The front-end type comprises a Web end and a desktop end.
Specifically, the desktop end includes wpf front ends, winforms front ends, QT front ends, and the like.
Optionally, the front end type is a Web end, and in the step S1, when the system is initialized, a process corresponding to the front end type is started according to the front end type, and the method further includes creating a data channel.
The method comprises the steps of creating a public message processing class object, a Web end extension message processing class object, a desktop end extension message processing class object and a message manager in a cloud CAD service by a tool setting manager;
The Web end tool setup view, the desktop end tool setup view, the Web end tool setup view manager, and the desktop end tool setup view manager are created at the front end of the system.
The common message handling class includes a command message handling class.
A command message handling class that, upon triggering a command operation, invokes a system method to execute the command, depending on the command message.
As one example, in a CAD platform, a UI interface includes several UI function components configured in zones, including a drawing area (workspace), a tool setting panel component, a resident command interaction component, an attribute panel component, a message display component, and a menu and toolbar component, among others. As shown in FIG. 2, the system is divided into A, B, C, D, E, F areas, wherein area A is a menu and toolbar component, area B is an attribute panel component, area C is a tool setting view component, area D is a drawing area (working area), area E is a message display component, and area F is a resident command interaction component.
The command message includes a start/stop designation tool instruction through a menu and toolbar component (region a) in the UI interface, and may also include other modeling commands or auxiliary modeling commands. The command message includes a command string, specifically, the command message mainly includes modeling commands such as creation, modification, editing, deletion, query, etc. of model elements, and auxiliary modeling commands such as view control, capturing, accurate drawing, etc.
For example, a user activates a tool through a front end, the front end triggers a command message, sends the command message to a back end, the back end receives the command message, processes the command message by a command message processing class object, obtains command content, runs a command in the message, and activates a specific tool. In this embodiment, the extended message processing classes include a Web end tool setup view message processing class and a desktop end tool setup view message processing class.
The Web end tool sets view message processing class, a data channel object is aggregated, and when the tool sets view to be displayed/closed, the tool sets view message is sent to the Web front end through the data channel;
The desktop end tool sets a view message processing class, and when the tool set view needs to be displayed/closed, the tool set view message is transmitted to the desktop front end through in-process communication and memory sharing;
the tool setting view message is used for informing the front end to execute operations including displaying the view and closing the view.
Optionally, the Web end tool setting view is an example of a Web end tool setting view class, and the Web end tool setting view class inherits from a Web end tool setting view base class, wherein the Web end tool setting view base class provides a basic display/closing method, aggregates data channels and observable object messages, binds tool setting data class objects to views, and when the attribute value of the tool setting data class object changes, the Web end tool setting view base class sequences the change amount and sends the change amount to the cloud CAD service through the data channels.
Because the Web end tool setting view class inherits from the Web end tool setting view base class, the Web end tool setting view class is used for providing a basic display/closing method, data channels and observable object messages are aggregated, tool setting data class objects are bound to views, when the attribute values of the tool setting data class objects change, the Web end tool setting view class sequences the variable quantity and sends the variable quantity to the cloud CAD service through the data channels depending on the observable object messages.
Optionally, the desktop end tool setting view is an example of a desktop end tool setting view class, and the desktop end tool setting view class inherits from a desktop end tool setting view base class, wherein the desktop end tool setting view base class provides a basic display/closing method, aggregates observable object messages, binds tool setting data class objects to views, and synchronizes the variable amount to a cloud CAD service through in-process communication and memory sharing after serialization of the variable amount when the tool setting data class object attribute value changes.
The desktop end tool setting view class inherits from the desktop end tool setting view base class, so that a basic display/closing method is provided, observable object information is aggregated, tool setting data class objects are bound to views, when the tool setting data class object attribute values change, the desktop end tool setting view class sequences the variable quantity and synchronizes with memory sharing to cloud CAD service through in-process communication.
It will be appreciated that the tool setting view refers to the interface for displaying tool setting data, generally indicated by the area C in fig. 2, for displaying and interacting with tool setting data, each time a tool is activated. Tool setting data, such as a line drawing tool, including selecting whether to designate a length, a length value input, whether to designate an angle, an angle value input, may display the length and angle values of a current freely drawn line segment when the length and angle are not designated, and may also receive user operations to designate the current length and angle.
Specifically, tool setting data classes, including tool setting data for specifying various inputs of tool operating parameters, such as whether orthogonal, whether length, whether width, height are specified, when a user performs two-dimensional free modeling and parametric modeling in a CAD platform.
As shown in fig. 4, the tool setting data class inherits the observable object base class, which is a data base class of all the data base classes needing front-end and back-end data synchronization operation in the framework, and is an implementation class of a message interface, and can monitor the attribute value change of a sub-class object (such as a tool setting data class object), when one end operation of the front-end or cloud CAD service causes the attribute value change of the sub-class object, an observable object message is triggered to notify the other end, so that the front-end and cloud CAD service data synchronization is realized.
It can be understood that, since the tool setting data class inherits the observable object base class, when the attribute value of the tool setting data class object changes, an observable object message is triggered, and when one end of the front end or cloud CAD service operates to cause data change, the other end is notified through the observable object message, so that the front end and cloud CAD service data synchronization is realized. The tool refers to various interactable tools for creating/editing models, and can be used for freely modeling in a drawing area (D area) through a mouse and a keyboard, and can be used for carrying out data interaction through a tool setting view component (area C) so as to carry out parameterized modeling. The tools include, for example, line drawing tools, rectangular tools, spline curve tools, and the like.
"Tool state" refers to the overall state of the system during the period from the start of the tool to the end of the tool, the tool is generally a state machine, the overall state of the system during the operation of the tool is divided into a plurality of sub-states, and the sub-states are driven to be switched from the start to the end of the operation of the tool through user interaction (such as mouse key operation) or parameterized input (such as tool setting data). When the next tool is started, the system enters the next tool state.
Optionally, the tool class inherits a tool base class, and the tool base class is a base class for realizing interactive two-dimensional and three-dimensional modeling, and comprises a tool setting data class object, a plurality of mouse-key interaction methods and the like.
Since the tool class inherits from the tool base class, it also includes a tool set data class object and is responsible for maintaining that object, i.e., aggregating the tool set data class objects. I.e. when the front end changes (user inputs) the property value of the object, the tool draws a corresponding model according to the modified property value of the object, and when the front end does not change (user does not input), the tool completes the modeling operation according to the property value of the instance.
Optionally, the common message handling class further includes a mouse message handling class and a keyboard message handling class.
In particular, the mouse message handling class relies on mouse messages for responsive handling of mouse inputs in the front-end interface.
The keyboard message handling class relies on the keyboard message for responsive handling of keyboard inputs in the front-end interface.
In this embodiment, all messages are one instance of a message class, which is an implementation of a message interface.
In this embodiment, the mouse message and the keyboard message refer to a mouse key operation in the drawing area (area D) in a tool state after the tool is started, and the view operation (translation/rotation/zoom, etc.), the model element pickup, the point coordinates acquisition, etc. are completed. That is, in the area D, the mouse message and the keyboard message are transmitted to the back end, and the response processing is performed by the mouse message processing class object and the keyboard message processing class object, respectively.
And mouse and keyboard events in other areas of the UI interface are processed by the front end and are not transferred to the back end. For example, when the user clicks the drawing button, the front end processes the click event, interprets the action of clicking the drawing button as starting the drawing tool, constructs a command for starting the drawing tool, and transmits the command to the back end, and the back end starts the drawing tool according to the command. After that, the user inputs parameters on the drawing tool setting view that the front end has acquired the keyboard input, the tool setting data variable is sent to the back end, and the tool setting data is changed to the message processing class object for processing. That is, unlike the "mouse message and keyboard message" in this embodiment, mouse-keyboard events in other areas of the UI interface can be considered global, requiring cooperation of the mouse and keyboard for each interactive tool.
Optionally, in the cloud CAD service, the message manager is configured to manage all the messages and the message processing class objects, and maintain a relationship between a message type and a corresponding message processing class object, and mainly includes a registration message processing method, a cancellation message processing method, a triggering message method, and the like. When the trigger message method is invoked, the message is forwarded to a specific process in the message handling class object.
The tool setting manager is used for maintaining the relation between the tool and the tool setting data class object, and depends on the tool setting view message and the message manager, and comprises a method for acquiring the tool setting data and a method for displaying/closing the tool setting view.
The method for acquiring the tool setting data acquires a current tool setting data class object according to the current tool type and the tool setting data type, the tool setting data class object is in a single instance mode, and a single instance state is maintained by a tool setting manager, namely, the tool setting data class object is created only when the method for acquiring the tool setting data is called for the first time, and a new tool setting data class object is not generated after the later call, so that the response efficiency of a system is improved, and the consistency and the global accessibility of tool setting data are ensured.
The method for displaying/closing the tool setting view is to trigger a tool setting view message through a message manager, call a Web end or desktop end tool setting view message processing class object to transmit the tool setting view message to the front end, and realize the operation of displaying/closing the view.
Optionally, in the front end, a tool setting view manager is used for managing tool setting views of all tools of the system and maintaining the relation between tool setting data class objects and specific tool setting views, wherein the tool setting view manager comprises a Web end tool setting view manager and a desktop end tool setting view manager.
And step S2, responding to user operation, transmitting and processing information between the front end and the cloud CAD service, and executing modeling operation.
It should be noted that, because the front end and the back end of the desktop software are only logically separated, the data can still be accessed in the memory, and the front end and the back end of the Web application are physically separated, the front end and the back end data can only be transmitted through the network, and a special data channel needs to be established, so in the multi-front-end implementation, the implementation of the desktop and the Web is mainly different in the data transmission mode.
Based on this, in this embodiment, the multi-front-end framework determines the running logic of the whole program, which is mainly different in the processing method of the message processing class.
Specifically, in response to user operation, the step S2 is to transmit and process messages between the front end and the cloud CAD service, and execute modeling operation, and comprises 1) starting a tool.
1) A start tool comprising the steps of:
step S2.1, a user starts a tool through a front end, the front end triggers a command message, the command message is sent to a cloud CAD service, the cloud CAD service receives the command message, the message is distributed to a command message processing class object through a message manager for processing, a command in the message is operated, and a tool class instance is constructed, namely a specific tool is started;
S2.2, when a specific tool is constructed, creating or inquiring a tool setting data class object of the specific tool by calling a tool setting data acquisition method of a tool setting manager, and taking charge of maintaining the tool setting data class object;
Step S2.3, in the specific tool loading process, creating a tool setting view message corresponding to the front end type, and transmitting the tool setting view message corresponding to the front end type to the front end by a tool setting view message processing class object corresponding to the front end type;
and S2.4, the tool setting view manager corresponding to the front end type receives the tool setting view message, inquires the corresponding view and displays the view.
The method comprises the steps that a tool setting view message is formatted by a Web end tool setting view message processing class object, the tool setting view message is sent to the front end through a data channel, and a Web end tool setting view manager receives and analyzes the formatted tool setting view message.
When the front-end type is a desktop end, the desktop end tool sets a view message processing class object to realize front-end and back-end message transmission through in-process communication and memory sharing.
As an alternative embodiment, the system's startup tool when the front end is the Web end is implemented as follows:
The user starts the tool through the front end, the front end triggers the command message, the command message is sent to the cloud CAD service module through the data channel, the cloud CAD service receives the command message, the message is distributed to the command message processing class object through the message manager for processing, the command in the message is obtained and operated, a tool class instance is constructed, and a specific tool is started;
When a specific tool is constructed, creating or inquiring a tool setting data class object of the current tool by calling a tool setting data acquisition method of a tool setting manager, and taking charge of maintaining the tool setting data class object;
In the specific tool loading process, a display tool setting view method of a tool setting manager is called, tool setting view information is created, a trigger message event method of the message manager is called according to the object, information is distributed, a Web end tool setting view information processing class object formats the tool setting view information, and the tool setting view information is transmitted to the Web front end through a data channel;
The Web end tool setting view manager receives and analyzes the formatted tool setting view message, and queries and displays the corresponding view according to the tool setting data type and the tool setting view which are registered and bound during initialization.
The starting tool of the system when the front end is the desktop end is realized as follows:
The user starts the tool through the front end, the front end triggers the command message, the command message is sent to the cloud CAD service module, the cloud CAD service receives the command message, the message is distributed to the command message processing class object through the message manager for processing, the command in the message is obtained and operated, a tool class instance is constructed, and a specific tool is started;
When a specific tool is constructed, creating or inquiring a tool setting data class object of the current tool by calling a tool setting data acquisition method of a tool setting manager, and taking charge of maintaining the tool setting data class object;
In the specific tool loading process, a display tool setting view method of a tool setting manager is called, tool setting view information is created, a trigger message event method of the message manager is called according to the object, information is distributed, and a desktop end tool setting view information processing class object sends the tool setting view information to the front end;
The desktop end tool setting view manager receives the tool setting view message, and queries and displays the corresponding view according to the type of the tool setting data registered and bound and the tool setting view corresponding to the desktop end during initialization.
The message processing class object corresponding to the desktop end realizes front-end and back-end message transmission through in-process communication and memory sharing.
Optionally, step S2, in response to user operation, transmits and processes messages between the front end and the cloud CAD service, and performs modeling operation, and further comprises 2) running a tool.
2) The running tool comprises the following steps that after the tool is started, the system enters a tool state, and the running process of the tool is carried out through user interaction, and the running tool specifically comprises the following steps:
Step S2.5, when the tool is operated, receiving a mouse message input by a user, processing the mouse message by a mouse message processing class object, responding to the mouse message (including the movement of the mouse, the key, the roller and other messages);
And S2.6, the specific tool draws the model by monitoring the mouse message and the keyboard message and setting the data class object according to the tool of the specific tool.
Example 2
The present embodiment further defines steps S1-S2 based on the method described in embodiment 1, and the specific scheme is as follows:
in step S1, the extended message handling class further includes a tool setting data change message handling class. That is, when the system is initialized, the process corresponding to the front-end type is started according to the front-end type, and the method further comprises the step of registering the tool setting data corresponding to the front-end type to change the message processing class.
It should be noted that, in this embodiment, the tool setting data change message processing class is only effective in the tool state after the tool is started, and its functions include responding to the user's modification operation to the tool setting data class object in the tool setting view component (region C) of the front end UI interface, and synchronizing these changes into the tool setting view when the cloud CAD service operation causes the tool setting data class object attribute value to change.
The Web end tool setting data change message processing class is used for transmitting the change quantity to the Web end tool setting view through a data channel and updating the Web end tool setting view after the Web end tool setting data change message processing class object sequences the change quantity when the cloud CAD service operation causes the change of the attribute value of the tool setting data class object;
When a user carries out tool setting data class object attribute value modification operation on a Web end tool setting view, the Web end tool setting view sequences the variable quantity and then sends the variable quantity to a cloud CAD service through a data channel, the Web end tool setting data change message processing class object processes, and the tool setting data class object of the corresponding tool is analyzed and updated;
the Web end tool sets the data change message processing class, realizes the transmission and synchronization of the attribute value variation of the front end tool and the rear end tool set data class object according to the observable object message, and aggregates one data channel object.
The desktop end tool setting data change message processing class is used for sending the variable quantity to the desktop end tool setting view by the desktop end tool setting data change message processing class object when the cloud CAD service operation causes the change of the attribute value of the tool setting data class object, and updating the desktop end tool setting view;
When a user carries out tool setting data class object attribute value modification operation on a desktop end tool setting view, the desktop end tool setting view sends the variable quantity to a cloud CAD service, the desktop end tool setting data change message processing class object processes, and the tool setting data class object of the corresponding tool is analyzed and updated;
The desktop end tool setting data change message processing class realizes the transmission and synchronization of the variable quantity of the attribute value of the front end tool setting data class object according to the observable object message, and realizes the front end and back end data transmission through in-process communication and memory sharing.
In step S2, 2) running the tool, comprising the steps of:
After the tool is started, the system enters a tool state, and the tool operation process is carried out through user interaction, which specifically comprises the following steps:
Step S2.5, when the tool is operated, receiving a mouse message input by a user, processing the mouse message by a mouse message processing class object, responding to the mouse message (including the movement of the mouse, the key, the roller and other messages);
S2.6, a specific tool monitors a mouse message and a keyboard message, sets a data class object according to the tool of the specific tool, and draws a model;
Step S2.7, when a user performs model drawing operation through mouse operation and keyboard operation, when the cloud CAD service triggers the change of the attribute value of the tool setting data class object, the tool setting data corresponding to the front end type changes the message processing class object to send the variable quantity to the tool setting view corresponding to the front end type, and the tool setting view corresponding to the front end type is updated;
Further optionally, after the step S2.7, the method may further include the following steps:
Step S2.8, when a user carries out tool setting data class object attribute value modification operation on the tool setting view corresponding to the front end type, the tool setting view corresponding to the front end type sends the variable quantity to the cloud CAD service, the tool setting data corresponding to the front end type changes message processing class object processing, and the tool setting data class object of the corresponding tool is updated;
and S2.9, setting the attribute value of the data class object by the specific tool according to the modified tool, and drawing the model.
The method comprises the steps of providing a cloud CAD service, wherein the type of the front end is a Web end, and a Web end tool setting data change message processing class object is used for serializing a variable quantity, then sending the variable quantity to a Web end tool setting view through a data channel and updating the view;
when the front-end type is a desktop end, the desktop end tool setting data change message processing class object and the desktop end tool setting view realize front-end and back-end data synchronization through in-process communication and memory sharing.
The Web-side or desktop-side tool setting data change message processing class relies on observable object messages to achieve the above-described transfer and synchronization of the front-end and back-end tool setting data class object attribute value variation.
Therefore, in the embodiment, the front end and the rear end realize data synchronization based on the observable objects, the data change of any one end can trigger the synchronization of the other end in real time, the risk of inconsistent manual coding and data is reduced, and meanwhile, the interface (View) and the service logic are thoroughly decoupled, so that a technical foundation is provided for the multi-front-end fusion framework, and the platform can be flexibly adapted to various front-end applications.
Example 3
The present embodiment further defines step S2 on the basis of the methods described in embodiments 1-2, and the specific scheme is as follows:
Optionally, step S2, in response to user operation, communicates and processes messages between the front end and the cloud CAD service, performing modeling operations, and further includes 3) switching tools after starting the tools or running the tools.
3) After starting the tool or running the tool, switching the tool, comprising the steps of:
Step S2.10, a user starts a new tool through the front end, the front end triggers a command message, the command message is sent to the cloud CAD service, the cloud CAD service receives the command message, the message is distributed to a command message processing class object through a message manager for processing, a command in the message object is operated, and the current tool is ended;
S2.11, calling a closing tool setting view method of a tool setting manager, creating a tool setting view message, calling a trigger message event method of a message manager according to the object, distributing the message, and transmitting the tool setting view message to the front end by a tool setting view message processing class object corresponding to the front end type;
step S2.12, the tool setting view manager corresponding to the front end type receives the tool setting view message, inquires the corresponding view according to the tool setting data type and the tool setting view which are registered and bound during initialization, and closes the view;
Step S2.13, running the command in the command message, starting a new tool, and running the starting tool, i.e. returning to step S2.1.
The method comprises the steps that a current end type is a Web end, a tool setting view message processing class object formats a tool setting view message, the tool setting view message is sent to the front end through a data channel, and a Web end tool setting view manager receives and analyzes the formatted tool setting view message.
When the front-end type is a desktop end, the message processing class object corresponding to the desktop end realizes front-end and back-end message synchronization through in-process communication and memory sharing.
Specifically, the formatting of the message may be transmitted using a data format such as JSON or XML, and the serialization and deserialization of the message may use standard serialization libraries, such as Jackson or Python's jackle library of Java, etc.
In the above-described embodiments, as shown in fig. 3 and 4, the message processing classes (including the common message processing class and the extended message processing class) are one implementation of a message processing interface for performing response and processing of specific messages. I.e. the message handling interface defines the type of all message handling classes within the framework of the present embodiment, which are one implementation of the interface, including but not limited to message interfaces, serialized message interface strings, and other various forms of messages.
It should be noted that, for the embodiment of the present disclosure, in the running process of the system, after the cloud CAD service receives the message, the message manager distributes the message to the corresponding message processing object for processing, so whether the above steps are explicit or not, the cloud CAD service distributes the message to the corresponding message processing object for processing after receiving the message.
In an alternative embodiment, the extended message processing classes further include a Web-side prompt message processing class and a Web-side set view size message processing class, a desktop-side prompt message processing class and a desktop-side set view size message processing class, and the like.
The Web end prompts the message processing class, has aggregated a data channel, when invoking and prompting the message method in the tool class, prompt the message processing class to sequence the message, send and prompt the message to the Web front end through the data channel, the Web front end synchronizes the interface data according to the message content;
Specifically, the prompt information message refers to a message for feeding back an operation state, error information, warning or advice to the user, such as an operation success/failure prompt, progress information, warning prompt, and the like, in the CAD platform.
The Web end set view size message processing class comprises an encoder object and a view object, when the current end view changes, the Web end set view size message processing class triggers to set the view size message, and the Web end set view size message processing class sets the size of the encoder and the size of the view according to the message content.
The desktop side prompts information message processing class, when the tool class invokes the prompt information method, the front end is informed to synchronize interface data according to the information content;
The desktop end sets a view size message processing class which comprises a view object, when the front end view changes, a view size setting message is triggered, and the view size setting message processing class sets the size of a view according to the message content.
Therefore, in the scheme of the disclosure, by defining various message classes and message processing classes and creating tool setting data classes and specific tool classes, efficient processing and transmission of different types of messages and data between front and rear ends are ensured. Through the classification and specialized processing mechanism, the front end and the back end can realize efficient communication and operation under various interaction scenes.
Example 4
The method of embodiment 1-3 further defines step S1, where the specific scheme is that, optionally, step S1 specifically includes:
step S1.1, when the system is initialized, responding to the starting of the system, determining a front end type, and if the front end type is a Web end, turning to step S1.2, and if the front end type is a desktop end, turning to step S1.3;
Step S1.2, starting a Web end process, comprising the steps of creating a data channel, loading all tools, registering common message processing class and Web end extension message processing class objects, calling a registration message processing method of a message manager, respectively registering and binding the common message processing class objects and the Web end extension message processing class objects with corresponding message types, calling a Web end tool setting view manager, and binding tool setting data types with tool setting views corresponding to a Web end.
Step S1.3, starting a desktop process, comprising loading all tools and registering common message processing class and desktop end extension message processing class objects, calling a registration message processing method of a message manager, respectively registering and binding the common message processing class objects and the desktop end extension message processing class objects with corresponding message types, and calling a desktop end tool setting view manager to bind tool setting data types with tool setting views corresponding to the desktop end.
Example 5
The present embodiment provides a service messaging mechanism based CAD front-end and back-end interaction system for executing the service messaging mechanism based CAD front-end and back-end interaction method as described in embodiments 1-4, the system comprising:
the initialization module is used for starting a process corresponding to the front-end type according to the front-end type when the system is initialized, and comprises loading all tools, registering common message processing class objects, starting a message manager and a tool setting manager, registering an extended message processing class object and a tool setting view corresponding to the front-end type, and starting a tool setting view manager corresponding to the front-end type.
And the system operation module is used for responding to the user operation, transmitting and processing the message between the front end and the cloud CAD service and executing the modeling operation.
Therefore, in the above embodiment, by comprehensively considering the coexistence of the middle end and the cloud of the CAD platform, the SAAS is applied to the CAD desktop end, so as to realize front-end and back-end separation, and create a common class and specific classes for different front ends in a unified frame, so as to realize that one set of codes supports multi-front-end operation. Specifically, the same set of codes is adopted by the webpage end (Web end) application and the desktop end application, and the system judges the front end type during initialization and dynamically loads the corresponding implementation mode. On the one hand, the method can reduce repeated codes to the greatest extent, improves the high availability and reusability of system codes, and on the other hand, can realize multi-terminal adaptation, perfectly integrate webpage end (Web end) application and desktop end application, ensure that one set of codes supports multi-front end operation, thereby realizing interactive engineering modeling design under a multi-front end environment.
The apparatus embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
From the above description of the embodiments, it will be apparent to those skilled in the art that the embodiments may be implemented by means of software plus necessary general hardware platforms, or of course may be implemented by means of hardware. Based on this understanding, the foregoing technical solution may be embodied essentially or in a part contributing to the prior art in the form of a software product, which may be stored in a computer readable storage medium, such as ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method described in the respective embodiments or some parts of the embodiments.
It should be understood that the foregoing embodiments are merely illustrative of the technical solutions of the present disclosure and not limiting thereof, and that although the present disclosure has been described in detail with reference to the foregoing embodiments, it should be understood by those skilled in the art that modifications may be made to the technical solutions described in the foregoing embodiments or equivalents may be substituted for some of the technical features thereof, and that these modifications or substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present disclosure in essence of the corresponding technical solutions.

Claims (10)

1.一种基于服务消息传递机制的CAD前后端交互方法,其特征在于,包括:1. A CAD front-end and back-end interaction method based on a service message transmission mechanism, characterized by comprising: 步骤S1:系统初始化时,根据前端类型,启动该前端类型对应的进程,包括:加载所有工具,注册公共消息处理类对象,启动消息管理器及工具设置管理器,注册该前端类型对应的扩展消息处理类对象、工具设置视图,并启动该前端类型对应的工具设置视图管理器;Step S1: When the system is initialized, according to the front-end type, the process corresponding to the front-end type is started, including: loading all tools, registering public message processing class objects, starting the message manager and tool setting manager, registering the extended message processing class objects and tool setting views corresponding to the front-end type, and starting the tool setting view manager corresponding to the front-end type; 其中,前端类型包括Web端和桌面端;公共消息处理类包括命令消息处理类;扩展消息处理类包括Web端工具设置视图消息处理类和桌面端工具设置视图消息处理类;Among them, the front-end types include Web and desktop; the public message processing class includes the command message processing class; the extended message processing class includes the Web tool setting view message processing class and the desktop tool setting view message processing class; 步骤S2:响应用户操作,在前端与云端CAD服务之间传递并处理消息,执行建模操作,包括:启动工具;Step S2: responding to user operations, transmitting and processing messages between the front end and the cloud CAD service, and performing modeling operations, including: starting the tool; 其中,启动工具,包括如下步骤:用户通过前端启动工具,前端触发命令消息,将命令消息发送到云端CAD服务,云端CAD服务接收到命令消息,通过消息管理器将该消息分发到命令消息处理类对象进行处理,运行消息中的命令,启动一个具体工具;Among them, starting the tool includes the following steps: the user starts the tool through the front end, the front end triggers a command message, sends the command message to the cloud CAD service, the cloud CAD service receives the command message, distributes the message to the command message processing class object for processing through the message manager, runs the command in the message, and starts a specific tool; 构造具体工具时,通过调用工具设置管理器的获取工具设置数据方法,创建或查询具体工具的工具设置数据类对象,并负责维护该工具设置数据类对象;When constructing a specific tool, the tool setting data class object of the specific tool is created or queried by calling the Get Tool Setting Data method of the Tool Setting Manager, and the tool setting data class object is maintained; 具体工具装载过程中,创建该前端类型对应的工具设置视图消息,由该前端类型对应的工具设置视图消息处理类对象将该前端类型对应的工具设置视图消息发送到前端;During the specific tool loading process, a tool setting view message corresponding to the front-end type is created, and the tool setting view message processing class object corresponding to the front-end type sends the tool setting view message corresponding to the front-end type to the front-end; 前端类型对应的工具设置视图管理器接收工具设置视图消息,查询到对应的视图,并显示;The tool setting view manager corresponding to the front-end type receives the tool setting view message, queries the corresponding view, and displays it; 工具设置数据类继承可观测对象基类,所述可观测对象基类是所有需要前后端数据同步操作的数据基础类,是消息接口的实现类,用于实现前端和云端CAD服务数据同步。The tool setting data class inherits the observable object base class, which is the data foundation class for all front-end and back-end data synchronization operations. It is the implementation class of the message interface and is used to realize data synchronization between the front-end and cloud CAD services. 2.根据权利要求1所述的基于服务消息传递机制的CAD前后端交互方法,其特征在于,当前端类型是Web端,由Web端工具设置视图消息处理类对象将工具设置视图消息格式化,通过数据通道发送到前端,Web端工具设置视图管理器接收并解析格式化的工具设置视图消息;当前端类型是桌面端,由桌面端工具设置视图消息处理类对象通过进程内通信与内存共享实现前后端消息传递。2. According to the CAD front-end and back-end interaction method based on the service message transmission mechanism described in claim 1, it is characterized in that, when the current end type is the Web end, the Web end tool setting view message processing class object formats the tool setting view message and sends it to the front end through the data channel, and the Web end tool setting view manager receives and parses the formatted tool setting view message; when the current end type is the desktop end, the desktop end tool setting view message processing class object realizes the front-end and back-end message transmission through in-process communication and memory sharing. 3.根据权利要求2所述的基于服务消息传递机制的CAD前后端交互方法,其特征在于,公共消息处理类还包括鼠标消息处理类和键盘消息处理类;步骤S2:响应用户操作,在前端与云端CAD服务之间传递并处理消息,执行建模操作,还包括:运行工具;3. The CAD front-end and back-end interaction method based on the service message transmission mechanism according to claim 2 is characterized in that the public message processing class also includes a mouse message processing class and a keyboard message processing class; step S2: responding to user operations, transmitting and processing messages between the front end and the cloud CAD service, and performing modeling operations, and also includes: running tools; 其中,运行工具,包括如下步骤:Running the tool includes the following steps: 在启动工具之后,系统进入工具状态,通过用户交互进行工具运行过程,具体包括:运行工具时,接收用户输入的鼠标消息,由鼠标消息处理类对象处理并响应;接收用户输入的键盘消息,由键盘消息处理类对象处理并响应,并将响应结果传递至具体工具;After starting the tool, the system enters the tool state and performs the tool operation process through user interaction, which specifically includes: when running the tool, receiving the mouse message input by the user, which is processed and responded by the mouse message processing class object; receiving the keyboard message input by the user, which is processed and responded by the keyboard message processing class object, and the response result is passed to the specific tool; 具体工具通过对鼠标消息、键盘消息的监听,并根据该具体工具的工具设置数据类对象,绘制模型。The specific tool draws the model by monitoring the mouse messages and keyboard messages and setting the data class object according to the tool of the specific tool. 4.根据权利要求1所述的基于服务消息传递机制的CAD前后端交互方法,其特征在于,命令消息包括通过UI界面中的菜单和工具条组件启动/关闭指定工具的指令。4. According to the CAD front-end and back-end interaction method based on the service message transmission mechanism of claim 1, it is characterized in that the command message includes instructions for starting/closing specified tools through menus and toolbar components in the UI interface. 5.根据权利要求3所述的基于服务消息传递机制的CAD前后端交互方法,其特征在于,在步骤S1中,所述扩展消息处理类还包括工具设置数据改变消息处理类;5. The CAD front-end and back-end interaction method based on the service message transmission mechanism according to claim 3 is characterized in that, in step S1, the extended message processing class also includes a tool setting data change message processing class; 在步骤S2中,在启动工具之后,系统进入工具状态,通过用户交互进行工具运行过程,还包括:In step S2, after starting the tool, the system enters the tool state, and the tool operation process is performed through user interaction, which also includes: 当用户通过鼠标操作和键盘操作进行模型绘制操作,在云端CAD服务触发工具设置数据类对象属性值改变时,该前端类型对应的工具设置数据改变消息处理类对象将变化量发送到该前端类型对应的工具设置视图,并更新该前端类型对应的工具设置视图。When the user performs model drawing operations through mouse and keyboard operations, and the cloud CAD service triggers a change in the attribute value of the tool setting data class object, the tool setting data change message processing class object corresponding to the front-end type sends the change to the tool setting view corresponding to the front-end type, and updates the tool setting view corresponding to the front-end type. 6.根据权利要求5所述的基于服务消息传递机制的CAD前后端交互方法,其特征在于,在步骤S2中,在启动工具之后,系统进入工具状态,通过用户交互进行工具运行过程,还包括:6. The CAD front-end and back-end interaction method based on the service message transmission mechanism according to claim 5 is characterized in that in step S2, after starting the tool, the system enters the tool state and performs the tool operation process through user interaction, and further comprises: 当用户在该前端类型对应的工具设置视图进行工具设置数据类对象属性值修改操作,该前端类型对应的工具设置视图将变化量发送到云端CAD服务,由该前端类型对应的工具设置数据改变消息处理类对象处理,更新对应工具的工具设置数据类对象;When the user performs a tool setting data class object attribute value modification operation in the tool setting view corresponding to the front-end type, the tool setting view corresponding to the front-end type sends the change amount to the cloud CAD service, which is processed by the tool setting data change message processing class object corresponding to the front-end type to update the tool setting data class object of the corresponding tool; 具体工具根据修改后的工具设置数据类对象属性值,绘制模型。The specific tool sets the data class object attribute value according to the modified tool and draws the model. 7.根据权利要求6所述的基于服务消息传递机制的CAD前后端交互方法,其特征在于,其中,在前端与云端CAD服务之间,当前端类型是Web端,Web端工具设置数据改变消息处理类对象将变化量序列化后通过数据通道发送到Web端工具设置视图,并更新视图;Web端工具设置视图将变化量序列化后通过数据通道发送到云端CAD服务,由Web端工具设置数据改变消息处理类对象处理,通过反序列化解析变化量,更新工具设置数据类对象;7. The CAD front-end and back-end interaction method based on the service message transmission mechanism according to claim 6 is characterized in that, between the front-end and the cloud CAD service, when the front-end type is the Web end, the Web end tool setting data change message processing class object serializes the change amount and sends it to the Web end tool setting view through the data channel, and updates the view; the Web end tool setting view serializes the change amount and sends it to the cloud CAD service through the data channel, and is processed by the Web end tool setting data change message processing class object, and the change amount is parsed by deserialization, and the tool setting data class object is updated; 当前端类型是桌面端,桌面端工具设置数据改变消息处理类对象和桌面端工具设置视图通过进程内通信与内存共享实现前后端数据同步。When the front-end type is desktop, the desktop tool setting data change message processing class object and the desktop tool setting view realize front-end and back-end data synchronization through in-process communication and memory sharing. 8.根据权利要求5-7中任一项所述的基于服务消息传递机制的CAD前后端交互方法,其特征在于,工具设置数据类继承可观测对象基类,所述可观测对象基类是消息接口的实现类,用于监听其子类对象的属性值变化,在前端或云端CAD服务的其中一端操作引起子类对象的属性值变化时,触发可观测对象消息,通知另一端,实现前端和云端CAD服务数据同步。8. The CAD front-end and back-end interaction method based on the service message transmission mechanism according to any one of claims 5-7 is characterized in that the tool setting data class inherits the observable object base class, and the observable object base class is the implementation class of the message interface, which is used to monitor the attribute value changes of its subclass objects. When the operation at one end of the front-end or cloud-based CAD service causes the attribute value of the subclass object to change, the observable object message is triggered to notify the other end, thereby realizing the synchronization of the front-end and cloud-based CAD service data. 9.根据权利要求8所述的基于服务消息传递机制的CAD前后端交互方法,其特征在于,Web端或桌面端工具设置数据改变消息处理类依赖于可观测对象消息实现前端与云端CAD服务工具设置数据类对象属性值变化量的传送与同步。9. According to the CAD front-end and back-end interaction method based on the service message transmission mechanism of claim 8, it is characterized in that the Web-end or desktop-end tool setting data change message processing class relies on observable object messages to realize the transmission and synchronization of the change in the attribute value of the data class object set by the front-end and the cloud-based CAD service tool. 10.一种基于服务消息传递机制的CAD前后端交互系统,用于执行如权利要求1-9中任一项所述的基于服务消息传递机制的CAD前后端交互方法,其特征在于,所述系统包括:10. A CAD front-end and back-end interaction system based on a service message transmission mechanism, used to execute the CAD front-end and back-end interaction method based on a service message transmission mechanism as claimed in any one of claims 1 to 9, characterized in that the system comprises: 初始化模块,用于系统初始化时,根据前端类型,启动该前端类型对应的进程,包括:加载所有工具,注册公共消息处理类对象,启动消息管理器及工具设置管理器,注册该前端类型对应的扩展消息处理类对象、工具设置视图,并启动该前端类型对应的工具设置视图管理器;The initialization module is used to start the process corresponding to the front-end type according to the front-end type when the system is initialized, including: loading all tools, registering public message processing class objects, starting the message manager and tool setting manager, registering the extended message processing class objects and tool setting views corresponding to the front-end type, and starting the tool setting view manager corresponding to the front-end type; 系统运行模块,用于响应用户操作,在前端与云端CAD服务之间传递并处理消息,执行建模操作。The system operation module is used to respond to user operations, transmit and process messages between the front end and the cloud CAD service, and perform modeling operations.
CN202510400957.3A 2025-04-01 2025-04-01 CAD front-end and back-end interaction method and system based on service message transfer mechanism Active CN119903262B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202510400957.3A CN119903262B (en) 2025-04-01 2025-04-01 CAD front-end and back-end interaction method and system based on service message transfer mechanism

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202510400957.3A CN119903262B (en) 2025-04-01 2025-04-01 CAD front-end and back-end interaction method and system based on service message transfer mechanism

Publications (2)

Publication Number Publication Date
CN119903262A CN119903262A (en) 2025-04-29
CN119903262B true CN119903262B (en) 2025-07-15

Family

ID=95472538

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202510400957.3A Active CN119903262B (en) 2025-04-01 2025-04-01 CAD front-end and back-end interaction method and system based on service message transfer mechanism

Country Status (1)

Country Link
CN (1) CN119903262B (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105049420A (en) * 2015-06-23 2015-11-11 天津大学 Security protocol formal verification method using expanded UML model as framework
CN115665120A (en) * 2022-12-28 2023-01-31 浙江华东工程数字技术有限公司 Cloud CAD processing method and system, computer equipment and storage medium

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103631663A (en) * 2013-12-05 2014-03-12 用友软件股份有限公司 Rich client platform dynamic behavior device and rich client platform dynamic behavior method
CN109067911B (en) * 2018-09-14 2022-01-21 国云科技股份有限公司 Message sending implementation method based on multi-cloud platform sending conditions
CN110275700A (en) * 2019-06-17 2019-09-24 河南大学 An electron-based cross-platform desktop application development framework and method
US11237881B2 (en) * 2019-09-17 2022-02-01 Kyndryl, Inc. Message connector as a service to migrate streaming applications into cloud nativity
CN116415321B (en) * 2022-12-28 2024-06-21 浙江华东工程数字技术有限公司 Cloud CAD processing system and construction method thereof
CN118041932A (en) * 2024-02-20 2024-05-14 厦门稿定股份有限公司 Method, device, equipment and medium for keeping consistency of event communication at multiple ends
CN117997890A (en) * 2024-03-19 2024-05-07 武汉云阁科技有限公司 Cloud operating system and electronic equipment based on Web
CN118502991B (en) * 2024-07-17 2024-12-24 北京圜晖科技有限公司 A communication method, computing device and storage medium between CAD front end and back end

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105049420A (en) * 2015-06-23 2015-11-11 天津大学 Security protocol formal verification method using expanded UML model as framework
CN115665120A (en) * 2022-12-28 2023-01-31 浙江华东工程数字技术有限公司 Cloud CAD processing method and system, computer equipment and storage medium

Also Published As

Publication number Publication date
CN119903262A (en) 2025-04-29

Similar Documents

Publication Publication Date Title
JP3341893B2 (en) Concurrent framework system
JP3602532B2 (en) Concurrent processor with incremental command object
JP3839468B2 (en) International data processing system
JP4842305B2 (en) Computing system and method for implicitly committing non-saved data for world wide web applications
US7366723B2 (en) Visual query modeling for configurable patterns
DE69734545T2 (en) Method and device for improving the portability of an object-oriented interface between different environments
JP4117132B2 (en) Object-oriented notification framework system, method for executing the same, and method for managing the same
US7953767B2 (en) Developing applications using configurable patterns
EP0667972B1 (en) Collaborative work system
US9659012B2 (en) Debugging framework for distributed ETL process with multi-language support
JP3793226B2 (en) Atomic command system
CN104866585B (en) A kind of experiment test flight data total system
US20030101291A1 (en) Application programming interface for provision of DICOM services
JP2005505050A (en) Method, apparatus and system for performing view caching in a framework for supporting web-based applications
CA2627270A1 (en) System and method for displaying data on a thin client
US20120102414A1 (en) Distributed controller of a user interface framework for web applications
JP2005528667A (en) Method, apparatus and system for implementing a framework for supporting web-based applications
JP2007095090A (en) Method and device for menu item display
CN113934832A (en) Session-based interactive processing method, apparatus, device, medium and program product
CN116415321B (en) Cloud CAD processing system and construction method thereof
CN101561850A (en) System for comprehensively processing massive multi-channel nerve information and control method thereof
CN119903262B (en) CAD front-end and back-end interaction method and system based on service message transfer mechanism
CN111596957A (en) Configuration and application method of Revit model interface plug-in and interface plug-in
CN113806596A (en) Operation data management method and related device
JP2005292982A (en) Data processing system design apparatus and computer program therefor

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant