CN116185412B - Data management method and device, electronic equipment and storage medium - Google Patents
Data management method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN116185412B CN116185412B CN202310422251.8A CN202310422251A CN116185412B CN 116185412 B CN116185412 B CN 116185412B CN 202310422251 A CN202310422251 A CN 202310422251A CN 116185412 B CN116185412 B CN 116185412B
- Authority
- CN
- China
- Prior art keywords
- view
- data
- view window
- data document
- window
- 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
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Human Computer Interaction (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- User Interface Of Digital Computer (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The disclosure provides a data management method and device, electronic equipment and a storage medium, and relates to the technical field of data processing. The data management method comprises the following steps: acquiring at least one created data document; determining view management data corresponding to the data document; at least one view window corresponding to each data document is managed based on the view management data. According to the technical scheme, the management of at least one view window corresponding to the data document can be realized through the view management data, the management efficiency of the view window is improved, the management between the data document and the plurality of view windows is realized through the view management data, the decoupling of the data document and the view windows can be realized, and the management flexibility of the view window is improved.
Description
Technical Field
The present disclosure relates to the field of data processing technologies, and in particular, to a data management method, a data management apparatus, an electronic device, and a computer readable storage medium.
Background
With the rapid development of science and technology, more and more data need to be processed simultaneously, and one view window display data cannot meet the working requirements of people, so that a multi-window mode gradually becomes the choice of more and more data processing software.
MFC (Microsoft Foundation Classes) is a basic class library provided by a software development company, and an MFC contains a Document or View frame, so that a multi-window data management and presentation method can be realized, but the MFC is a class library specially designed for Windows and used for developing a graphical user interface, does not support cross-platform, completely depends on Windows sapi, and needs to forcedly use Document/View modes and templates (templates) by using MFC programming, so that management efficiency of View Windows in the multi-window mode is low, and management flexibility is poor.
It should be noted that the information disclosed in the above background section is only for enhancing understanding of the background of the present disclosure and thus may include information that does not constitute prior art known to those of ordinary skill in the art.
Disclosure of Invention
An object of the embodiments of the present disclosure is to provide a data management method, a data management device, an electronic device, and a computer readable storage medium, so as to effectively improve management efficiency of a view window, implement decoupling of a data document and the view window, and improve flexibility of view window management.
Other features and advantages of the present disclosure will be apparent from the following detailed description, or may be learned in part by the practice of the disclosure.
According to a first aspect of an embodiment of the present disclosure, there is provided a data management method, including:
acquiring at least one created data document;
determining view management data corresponding to the data document;
at least one view window corresponding to each data document is managed based on the view management data.
According to a second aspect of the embodiments of the present disclosure, there is provided a data management apparatus comprising:
a data document acquisition module for acquiring at least one created data document;
the view management data determining module is used for determining view management data corresponding to the data document;
and the view window management module is used for managing at least one view window corresponding to each data document based on the view management data.
According to a third aspect of embodiments of the present disclosure, there is provided an electronic device, comprising: a processor; and a memory having stored thereon computer readable instructions which when executed by the processor implement the data management method of the first aspect.
According to a fourth aspect of embodiments of the present disclosure, there is provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the data management method in the first aspect.
The technical scheme provided by the embodiment of the disclosure can comprise the following beneficial effects:
in the data management method in the example embodiment of the present disclosure, at least one data document created in advance may be acquired, view management data corresponding to the data document may be determined, and then at least one view window corresponding to each data document may be managed based on the view management data. On the one hand, the management of at least one View window corresponding to the data Document is realized through View management data, and compared with the fact that a Document/View mode and a template are required to be forcedly used in the related technology, the management efficiency of the View window can be effectively improved; on the other hand, the management between the data document and the plurality of view windows is realized through view management data, and compared with the related technology, the decoupling of the data document and the view windows can be realized, and the flexibility of view window management is improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
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. It will be apparent to those of ordinary skill in the art that the drawings in the following description are merely examples of the disclosure and that other drawings may be derived from them without undue effort.
FIG. 1 illustrates a schematic diagram of a system architecture of an exemplary application environment in which the data management methods and apparatus of embodiments of the present disclosure may be applied.
Fig. 2 schematically illustrates a flow diagram of a data management method according to some embodiments of the present disclosure.
FIG. 3 schematically illustrates a flow diagram for establishing a binding relationship between a data document and a view window, according to some embodiments of the present disclosure.
Fig. 4 schematically illustrates a flow diagram of presentation management of a view window according to some embodiments of the present disclosure.
Fig. 5 schematically illustrates a scene diagram of presentation management of a view window according to some embodiments of the present disclosure.
Fig. 6 schematically illustrates a schematic diagram of a data management apparatus according to some embodiments of the present disclosure.
Fig. 7 schematically illustrates a structural schematic diagram of a computer system of an electronic device according to some embodiments of the present disclosure.
Fig. 8 schematically illustrates a schematic diagram of a computer-readable storage medium according to some embodiments of the present disclosure.
In the drawings, the same or corresponding reference numerals indicate the same or corresponding parts.
Description of the embodiments
Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus a repetitive description thereof will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in software or in one or more hardware modules or integrated circuits or in different networks and/or processor devices and/or microcontroller devices.
FIG. 1 illustrates a schematic diagram of a system architecture of an exemplary application environment in which the data management methods and apparatus of embodiments of the present disclosure may be applied.
As shown in fig. 1, the system architecture 100 may include one or more of the terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 is used as a medium to provide communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others. The terminal devices 101, 102, 103 may be a variety of electronic devices having data processing capabilities including, but not limited to, desktop computers, portable computers, smart phones, tablet computers, and the like. It should be understood that the number of terminal devices, networks and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation. For example, the server 105 may be a server cluster formed by a plurality of servers.
The data management method provided by the embodiments of the present disclosure is generally performed in the terminal devices 101, 102, 103, and accordingly, the data management apparatus is generally provided in the terminal devices 101, 102, 103. However, it will be readily understood by those skilled in the art that the data management method provided in the embodiment of the present disclosure may be performed by the server 105, and accordingly, the data management device may be disposed in the server 105, which is not specifically limited in the present exemplary embodiment.
In the present exemplary embodiment, a data management method is provided first, and a data management method in the embodiment of the present disclosure will be described in detail below by taking a terminal device to execute the method as an example. Fig. 2 schematically illustrates a flow diagram of a data management method according to some embodiments of the present disclosure. Referring to fig. 2, the data management method may include the steps of:
step S210, obtaining at least one created data document;
step S220, determining view management data corresponding to the data document;
and step S230, at least one view window corresponding to each data document is managed based on the view management data.
According to the data management method in the present exemplary embodiment, on one hand, management of at least one View window corresponding to a data Document is implemented through View management data, and compared with the implementation of forcing use of Document/View modes and templates in the related art, management efficiency of the View window can be effectively improved; on the other hand, the management between the data document and the plurality of view windows is realized through view management data, and compared with the related technology, the decoupling of the data document and the view windows can be realized, and the flexibility of view window management is improved.
Next, a data management method in the present exemplary embodiment will be further described.
In step S210, the created at least one data document is acquired.
In an example embodiment, a data document refers to a document that contains critical data content in the associated software. The related software may be impeller machine design software or data analysis software, and the software type applied by the data management method in this example embodiment is not particularly limited.
Correspondingly, taking related software as impeller machinery design software as an example, the data content of the data document can be the data result of different stages of impeller machinery design needing to be presented; the data content of the data file can also be the data which has the same data in the design stage of the impeller machine but is displayed in different modes, such as the stress simulation results of the impeller machine displayed in a rectangular coordinate system, a cylindrical coordinate system, a three-dimensional cloud picture and the like; of course, the data content of the data document may also be multi-instance result display data, and the present exemplary embodiment does not make any particular limitation on the type of the data document.
In step S220, view management data corresponding to the data document is determined.
In an example embodiment, the view management data refers to data for managing association relationships between a data document and view windows in a multi-window mode, for example, the view management data may be a data document identifier, may also be a binding relationship between the data document and the view window, or may also be a view interface container, where a type of the view management data may be specifically set according to an actual application situation, and this example embodiment is not limited thereto.
The view management data may be recorded in a data document, may be recorded in a preset storage unit, or may be input by a user through a graphical user interface of related software, and the storage location or source of the view management data is not particularly limited in this example embodiment.
View management data corresponding to the data document can be determined according to the association relationship between the data document and the view management data, for example, the view management data corresponding to the data document can be determined through unique codes or hash values corresponding to the data document and the view management data respectively; the view management data corresponding to the data document may also be queried through the storage address corresponding to each of the data document and the view management data, and the pre-maintained storage address correspondence table, and the manner of determining the view management data corresponding to the data document is not particularly limited in this example embodiment.
In step S230, at least one view window corresponding to each data document is managed based on the view management data.
In an example embodiment, the view window refers to a window for displaying data content contained in the data document, at least one view window can be created on the image user interface according to different content or number of the data document, different view windows can display different data content, for example, for the data document containing data results of different stages of the impeller machine design, if three stages are provided, three view windows can be created to respectively display the data results of different stages; for the data file for displaying the stress simulation results of the impeller machine in three modes of a rectangular coordinate system, a cylindrical coordinate system and a three-dimensional cloud image, the stress simulation results of the impeller machine in the rectangular coordinate system, the cylindrical coordinate system and the three-dimensional cloud image can be respectively displayed through three view windows. One data document may correspond to multiple view windows, each of which uniquely binds one data document.
The at least one view window corresponding to each data document may be managed by view management data, for example, creation of the view window of the data document may be implemented by view management data, update of the view window of the updated data document may also be implemented by view management data, or, of course, management of the at least one view window corresponding to each data document may also be implemented by view management data in any other manner, which is not particularly limited in this example embodiment.
The view management data is used for realizing the management of at least one view window corresponding to the data document, so that the management efficiency of the view window can be effectively improved, the decoupling of the data document and the view window can be realized, and the management flexibility of the view window is improved.
Next, step S210 and step S230 will be described in detail.
In an example embodiment, the view management data may include a data document identification, which refers to information for uniquely identifying the corresponding data document, for example, the data document identification may be a data document number or a hash value corresponding to a sequence number of the data document, and the type of the data document identification is not particularly limited in this example embodiment. Through the data document identification, one data document can correspond to a plurality of view windows, and each view window is uniquely bound with one data document, so that the accuracy of a data structure can be effectively improved, and the management efficiency is improved.
Alternatively, the content of managing at least one view window corresponding to each data document based on the view management data in step S230 may be implemented by:
the view interface class corresponding to the data document can be called based on the data document identification, and at least one view window corresponding to each data document is created according to the view interface class, and each view window is derived from the view interface class. The View interface class (also can be considered as a View base class) refers to a View class provided by a QT application development framework in an MVC (Model-View-Controller) mode, and derived class objects of different data presentation modes, namely View windows, can be obtained by defining new attributes in the View interface class, and each View window corresponding to a data document is derived from the View interface class.
The view interface class container can be arranged in the data document, when the view window corresponding to the data document needs to be created, the view interface class corresponding to the data document can be called based on the data document identification, and further different attributes can be defined in the view interface class according to the data content in the data document, so that a plurality of different view windows are obtained.
For example, assuming that the data content of the data document records the stress simulation result of the impeller machine in three modes of rectangular coordinate system, cylindrical coordinate system and three-dimensional cloud image, the view interface class corresponding to the data document can be called in the view interface class container based on the data document identification, and then the attribute related to the rectangular coordinate system can be defined in the view interface class, so as to obtain the view window for displaying the stress simulation result of the impeller machine in the rectangular coordinate system; the attribute related to the cylindrical coordinate system can be defined in the view interface type, so that a view window for displaying the stress simulation result of the impeller machine by the cylindrical coordinate system is obtained; the three-dimensional cloud image related attributes can be defined in the view interface type, and a view window for displaying the stress simulation result of the impeller machine by the three-dimensional cloud image is obtained. Of course, it is to be understood that the present description is merely illustrative and that the present exemplary embodiment is not limited thereto.
Optionally, after at least one view window corresponding to the data document is created, a derivative class object pointer of the view interface class may be maintained in the data document record, so that the at least one view window corresponding to the data document may be quickly determined by the derivative class object pointer, and the derivative class object pointer may also be used as view management data of the data document.
And determining a corresponding view interface class through view management data corresponding to the data document, thereby creating at least one view window corresponding to the data document based on the view interface class, and realizing the positioning of the view window corresponding to the data document by maintaining a derivative class object pointer of the view interface class in the data document record, and effectively improving the management efficiency of the view window corresponding to the data document.
In an example embodiment, the view management data may include a binding relationship, where the binding relationship refers to data for indicating the association between the data document and the view window, and the step S230 may be implemented in the step in fig. 3, where at least one view window corresponding to each data document is managed based on the view management data, and referring to fig. 3, may specifically include:
Step S310, in response to an operation instruction for creating a first view window, determining whether an activated current data document exists;
step S320, if the current data document is determined to exist, acquiring an object interface of the current data document, and adding a first view window into the current data document through the object interface to establish a binding relationship;
step S330, if it is determined that the current data document does not exist, creating a new data document and a data document identifier corresponding to the new data document, and adding the first view window to the new data document through an object interface of the new data document to establish a binding relationship.
The first view window refers to a view window that needs to be newly created by a user, for example, the first view window may be a view window that displays a stress simulation result of the turbomachine in a rectangular coordinate system, and of course, may also be a view window that displays a data result of a certain stage of the turbomachine design, which is not limited in this example embodiment.
The operation instruction for creating the first view window can be generated by triggering the view window creation control provided by the software, the operation instruction for creating the first view window can be generated by triggering the combination shortcut key, and the operation instruction for creating the first view window can be generated by calling the view window creation interface through the voice assistant, and the triggering mode of the operation instruction for creating the first view window is not limited in any particular way in this example embodiment.
The current data document refers to a data document in an activated state when an operation instruction for creating the first view window is received, for example, the current data document may be a data document showing a stress simulation result of the turbomachine in a rectangular coordinate system manner, or may be a data document showing a data result of a certain stage of the turbomachine design, and the type of the current data document is not limited herein.
Judging whether an activated current data document exists or not when creating the view window, if the activated current data document exists, considering that a user wants to create the view window corresponding to the current data document, acquiring an object interface of the current data document, and adding a first view window into the current data document through the object interface to establish a binding relation between the current data document and the first view window; if the activated current data document does not exist, the user can be considered to want to create the data content which is never displayed at the moment, so that a new data document and a data document identification corresponding to the new data document can be created, and the first view window is added into the new data document through an object interface of the new data document so as to establish a binding relation between the new data document and the first view window.
When the activated current data document is determined to exist, if the fact that the user creates the first view window is detected, the created first view window can be directly bound with the current data document, and the creation efficiency of the first view window can be effectively increased; when the activated current data document does not exist, if the fact that the user creates the first view window is detected, the new data document and the data document identification corresponding to the new data document can be directly created, the first view window is bound with the new data document, the user only needs to add data content in the new data document, the data document does not need to be created again, and the creation efficiency of the view window can be further increased.
Optionally, the second view window may be activated in response to a triggering operation of selecting the second view window, and the target data document corresponding to the second view window may be determined according to the binding relationship, and placed in an activated state. The second view window refers to a view window selected by a user on a graphical user interface provided by software, and the target data document refers to a data document corresponding to the activated second view window.
By detecting the selection operation of the user on the second view window, the target data document corresponding to the second view window is set to be in an activated state in time based on the binding relation, so that the second view window is corresponding to the target data document, the setting change of the user on the second view window or the target data document is facilitated, and the management efficiency of the view window or the data document is effectively improved.
In an example embodiment, the view management data may include a view interface class container, and the content of managing at least one view window corresponding to each data document based on the view management data in step S230 may be implemented by:
and in response to the detection of the operation instruction for updating the data document, traversing the target call interface in the view interface class container, and determining a view window corresponding to the target call interface, so that the view window can be updated through the updated data document and the target call interface.
The target call interface is used for displaying data content in the data document to a corresponding view window.
The operation instruction for updating the data document can be generated by triggering the data document change control provided by the software, for example, the operation instruction for updating the data document can be generated by the data document change control such as the data document creation control, the data document binding control, the data document deletion control and the like, and of course, the operation instruction for updating the data document can also be generated by calling an adding interface, a deleting interface, a saving interface, a modifying interface or a unit conversion interface of the data content in the data document, and the generation mode of the operation instruction for updating the data document is not limited in any way.
After the operation instruction for updating the data document is monitored, the data content in the data document can be considered to be changed, and the corresponding view window is required to be updated at the moment, so that the target call interface in the view interface class container corresponding to the data document can be traversed, the target call interface is used for displaying the data content in the data document into the corresponding view window, the view window corresponding to the target call interface can be determined, and further the data content in the updated data document can be displayed into the corresponding view window through the target call interface, and the update of the view window corresponding to the updated data document is realized.
By setting the view interface type container, after the data document is updated, the corresponding target calling interface is timely called to update the view window, so that the consistency of the data content contained in the data document and the data content displayed by the view window can be ensured, the manual update is not needed, and the management efficiency of the view window is improved.
In an example embodiment, the presentation management of at least one view window may be implemented through the steps in fig. 4, and as shown with reference to fig. 4, may specifically include:
Step S410, in response to the moving operation of dragging the third view window, determining a fourth view window with a distance from the third view window being less than or equal to a distance threshold;
step S420, if it is determined that the third view window and the fourth view window belong to the same data document, the third view window is adsorbed to one side of the fourth view window to realize parallel display of multiple windows, or the display interface of the third view window is combined into the fourth view window to realize display of multiple display interfaces of the same window.
The third view window and the fourth view window refer to view windows displayed in a graphical user interface provided by running software, and the third view window and the fourth view window may be view windows corresponding to the same data document, for example, the third view window and the fourth view window may be view windows displaying a stress simulation result of the impeller machine in a rectangular coordinate system manner and view windows displaying a stress simulation result of the impeller machine in a cylindrical coordinate system manner, respectively; the third view window and the fourth view window may correspond to different data documents, for example, the third view window may be a view window that displays a stress simulation result of the turbomachine in a rectangular coordinate system, and the fourth view window may be a view window that displays a data result of a stage of the turbomachine design. The present exemplary embodiment does not make any particular limitation on the types of data contents presented by the third view window and the fourth view window.
When a moving operation for the third view window is detected, a fourth view window with a distance smaller than or equal to a distance threshold value from the third view window may be determined, if it is determined that the third view window and the fourth view window belong to the same data document, it may be considered that data contents in the third view window and the fourth view window need to be displayed in parallel, and therefore, the third view window may be adsorbed to one side of the fourth view window to implement multi-window parallel display, for example, the third view window may be adsorbed to one side closest to the third view window in the fourth view window, and the third view window may be adsorbed to one side specified in the fourth view window, which is not limited in this example embodiment.
Optionally, the display interface of the third view window may be combined into the fourth view window to implement the same-window multi-display interface display, for example, the display interface in the third view window may be displayed in the fourth view window, so that the data content in the third view window and the data content in the fourth view window are displayed in parallel in the same view window, and the same-window multi-display interface display is implemented.
When the moving operation of the view windows is detected, if the view windows belong to the same data document, the parallel display can be realized by adsorbing the view windows, or the display interfaces (data contents) in the view windows are displayed in the same view window, so that the parallel display of the same data contents is realized, the data browsing efficiency can be effectively improved, and meanwhile, when the view windows in the graphical user interface are more, the differentiated management of a plurality of view windows can be effectively realized, and the management efficiency of the view windows and the flexibility of the view window display are improved.
Optionally, with continued reference to fig. 4, when the third view window and the fourth view window belong to different data documents, presentation management of at least one view window may be achieved by:
step S430, if the third view window and the fourth view window are determined to belong to different data documents, determining a first data document corresponding to the third view window and determining a second data document corresponding to the fourth view window;
step S440, calculating the similarity between the data content contained in the first data document and the data content contained in the second data document;
And S450, when the similarity is greater than or equal to a similarity threshold, adsorbing the third view window to one side of the fourth view window to realize multi-window parallel display, or merging the display interface of the third view window into the fourth view window to realize the same-window multi-display interface display.
The similarity threshold is preset to measure similarity of data content between the data documents, for example, the similarity threshold may be 90% or 80%, and the similarity threshold may be specifically set in a user-defined manner according to actual situations, which is not limited in this example embodiment.
The data content contained in the first data document can be converted into word vectors, the data content contained in the second data document is converted into word vectors, and the similarity between the data content contained in the first data document and the data content contained in the second data document can be determined by calculating cosine distances between the word vectors; of course, keywords may be obtained by segmenting the data content included in the first data document, and keywords may be obtained by segmenting the data content included in the second data document, so that the overlapping rate between the keywords may be calculated to determine the similarity between the data content included in the first data document and the data content included in the second data document, and the method for determining the similarity in this example embodiment is not limited in any way.
When the similarity is determined to be greater than or equal to the similarity threshold, the data content displayed in the third view window and the fourth view window can be considered to be basically the same, and when the distance between the third view window dragged by the user and the fourth view window is smaller than or equal to the distance threshold, the user can be considered to need to compare the data in the two view windows, so that the third view window can be adsorbed to one side of the fourth view window to realize multi-window parallel display, or the display interface of the third view window is combined into the fourth view window to realize the same-window multi-display interface display.
When the moving operation of the view windows is detected, if the view windows belong to different data documents and the similarity of the data contents between the data documents is larger, the parallel display can be realized by adsorbing the view windows, or the display interfaces (data contents) in the view windows are displayed in the same view window, so that the parallel display of the same data contents can be realized, the data browsing efficiency can be effectively improved, and meanwhile, when the view windows in the graphical user interface are more, the differentiated management of a plurality of view windows can be effectively realized, and the management efficiency of the view windows and the flexibility of the view window display can be improved.
Fig. 5 schematically illustrates a scene diagram of presentation management of a view window according to some embodiments of the present disclosure.
Referring to fig. 5, a graphical user interface 501 may be provided by running software in which a view window 502 and a view window 503 may be presented. When a moving operation for the view window 503 is detected, a distance between the view window 503 and the view window 502 closest to the view window may be determined, and when the distance is smaller than or equal to a distance threshold, if it is determined that the view window 502 and the view window 503 belong to the same data document, or if the view window 502 and the view window 503 belong to different data documents, but a similarity between data contents in the view window 502 and the view window 503 is greater than or equal to a similarity threshold, it may be considered that a user needs to conduct parallel presentation on the view window 502 and the view window 503, and therefore, the view window 503 may be adsorbed to one side of the view window 502 to achieve multi-window parallel presentation, or a display interface of the view window 503 may be incorporated into the view window 502 to achieve same-window multi-display interface presentation.
It should be noted that although the steps of the methods of the present disclosure are illustrated in the accompanying drawings in a particular order, this does not require or imply that the steps must be performed in that particular order or that all of the illustrated steps be performed in order to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform, etc.
Further, in the present exemplary embodiment, there is also provided a data management apparatus. Referring to fig. 6, the data management apparatus 600 includes: a data document acquisition module 610, a view management data determination module 620, and a view window management module 630. Wherein:
the data document acquisition module 610 is configured to acquire at least one created data document;
the view management data determining module 620 is configured to determine view management data corresponding to the data document;
the view window management module 630 is configured to manage at least one view window corresponding to each of the data documents based on the view management data.
In an exemplary embodiment of the present disclosure, based on the foregoing, the view management data may include a data document identification, and the view window management module 630 may be configured to:
calling a view interface class corresponding to the data document based on the data document identification;
and creating at least one view window corresponding to each data document according to the view interface class, wherein the view window is derived from the view interface class.
In one exemplary embodiment of the present disclosure, based on the foregoing, the data document may record derived class object pointers that maintain the view interface class.
In an exemplary embodiment of the present disclosure, based on the foregoing scheme, the view management data includes a bindable relationship, and the view window management module 630 may be configured to:
determining whether an activated current data document exists or not in response to an operation instruction for creating the first view window;
if the current data document is determined to exist, acquiring an object interface of the current data document, and adding the first view window into the current data document through the object interface to establish a binding relationship;
if the current data document is determined not to exist, a new data document and a data document identifier corresponding to the new data document are created, and the first view window is added into the new data document through an object interface of the new data document so as to establish a binding relation.
In an exemplary embodiment of the present disclosure, based on the foregoing scheme, the data management apparatus 600 may further include an activation module, which may be used to:
activating a second view window in response to a trigger operation of selecting the second view window;
and determining a target data document corresponding to the second view window according to the binding relation, and setting the target data document to be in an activated state.
In an exemplary embodiment of the present disclosure, based on the foregoing, the view management data includes a view interface class container, and the view window management module 630 may be configured to:
responding to the detection of an operation instruction for updating the data document, traversing a target call interface in the view interface class container;
determining a view window corresponding to the target call interface;
and updating the view window through the updated data document and the target call interface.
In an exemplary embodiment of the present disclosure, based on the foregoing scheme, the data management apparatus 600 may further include a view window presentation management module, which may be used to:
in response to a movement operation of dragging the third view window, determining a fourth view window with a distance from the third view window being less than or equal to a distance threshold;
if the third view window and the fourth view window belong to the same data document, adsorbing the third view window to one side of the fourth view window to realize multi-window parallel display, or combining a display interface of the third view window into the fourth view window to realize same-window multi-display interface display.
In one exemplary embodiment of the present disclosure, based on the foregoing scheme, the view window presentation management module may be configured to:
if the third view window and the fourth view window belong to different data documents, determining a first data document corresponding to the third view window and determining a second data document corresponding to the fourth view window;
calculating the similarity between the data content contained in the first data document and the data content contained in the second data document;
and when the similarity is greater than or equal to a similarity threshold, adsorbing the third view window to one side of the fourth view window to realize multi-window parallel display, or merging a display interface of the third view window into the fourth view window to realize same-window multi-display interface display.
The specific details of each module of the data management device are described in detail in the corresponding data management method, so that the details are not repeated here.
It should be noted that although in the above detailed description several modules or units of the data management device are mentioned, this division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit in accordance with embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.
In addition, in an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above-described data management method is also provided.
Those skilled in the art will appreciate that the various aspects of the present disclosure may be implemented as a system, method, or program product. Accordingly, various aspects of the disclosure may be embodied in the following forms, namely: an entirely hardware embodiment, an entirely software embodiment (including firmware, micro-code, etc.) or an embodiment combining hardware and software aspects may be referred to herein as a "circuit," module "or" system.
An electronic device 700 according to such an embodiment of the present disclosure is described below with reference to fig. 7. The electronic device 700 shown in fig. 7 is merely an example and should not be construed as limiting the functionality and scope of use of the disclosed embodiments.
As shown in fig. 7, the electronic device 700 is embodied in the form of a general purpose computing device. Components of electronic device 700 may include, but are not limited to: the at least one processing unit 710, the at least one storage unit 720, a bus 730 connecting the different system components (including the storage unit 720 and the processing unit 710), and a display unit 740.
Wherein the storage unit stores program code that is executable by the processing unit 710 such that the processing unit 710 performs steps according to various exemplary embodiments of the present disclosure described in the above-described "exemplary methods" section of the present specification. For example, the processing unit 710 may perform step S210 as shown in fig. 2, acquiring the created at least one data document; step S220, determining view management data corresponding to the data document; and step S230, at least one view window corresponding to each data document is managed based on the view management data.
The memory unit 720 may include readable media in the form of volatile memory units, such as Random Access Memory (RAM) 721 and/or cache memory 722, and may further include Read Only Memory (ROM) 723.
The storage unit 720 may also include a program/utility 724 having a set (at least one) of program modules 725, such program modules 725 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.
The electronic device 700 may also communicate with one or more external devices 770 (e.g., keyboard, pointing device, bluetooth device, etc.), one or more devices that enable a user to interact with the electronic device 700, and/or any device (e.g., router, modem, etc.) that enables the electronic device 700 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 750. Also, electronic device 700 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN) and/or a public network, such as the Internet, through network adapter 760. As shown, network adapter 760 communicates with other modules of electronic device 700 over bus 730. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 700, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, and includes several instructions to cause a computing device (may be a personal computer, a server, a terminal device, or a network device, etc.) to perform the method according to the embodiments of the present disclosure.
In an exemplary embodiment of the present disclosure, a computer-readable storage medium having stored thereon a program product capable of implementing the method described above in the present specification is also provided. In some possible embodiments, the various aspects of the present disclosure may also be implemented in the form of a program product comprising program code for causing a terminal device to carry out the steps according to the various exemplary embodiments of the disclosure as described in the "exemplary methods" section of this specification, when the program product is run on the terminal device.
Referring to fig. 8, a program product 800 for implementing the above-described data management method according to an embodiment of the present disclosure is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present disclosure is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The computer readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).
Furthermore, the above-described figures are only schematic illustrations of processes included in the method according to the exemplary embodiments of the present disclosure, and are not intended to be limiting. It will be readily appreciated that the processes shown in the above figures do not indicate or limit the temporal order of these processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, for example, among a plurality of modules.
From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, and includes several instructions to cause a computing device (may be a personal computer, a server, a touch terminal, or a network device, etc.) to perform the method according to the embodiments of the present disclosure.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (9)
1. A method of data management, comprising:
acquiring at least one created data document;
determining view management data corresponding to the data document;
managing at least one view window corresponding to each data document based on the view management data;
wherein the view management data includes a data document identifier, and the managing at least one view window corresponding to each data document based on the view management data includes:
calling a view interface class corresponding to the data document based on the data document identification; the View interface class refers to a View class provided by the QT application development framework in an MVC mode;
and creating at least one view window corresponding to each data document according to the view interface class, wherein the view window is derived from the view interface class.
2. The method of claim 1, wherein the data document record maintains a derived class object pointer for the view interface class.
3. The method of claim 1, wherein the view management data includes a binding relationship, and wherein managing at least one view window corresponding to each of the data documents based on the view management data includes:
determining whether an activated current data document exists or not in response to an operation instruction for creating the first view window;
if the current data document is determined to exist, acquiring an object interface of the current data document, and adding the first view window into the current data document through the object interface to establish a binding relationship;
if the current data document is determined not to exist, a new data document and a data document identifier corresponding to the new data document are created, and the first view window is added into the new data document through an object interface of the new data document so as to establish a binding relation.
4. A method according to claim 3, characterized in that the method further comprises:
activating a second view window in response to a trigger operation of selecting the second view window;
and determining a target data document corresponding to the second view window according to the binding relation, and setting the target data document to be in an activated state.
5. The method of claim 1, wherein the view management data comprises a view interface class container, and wherein the managing at least one view window corresponding to each of the data documents based on the view management data comprises:
responding to the detection of an operation instruction for updating the data document, traversing a target call interface in the view interface class container;
determining a view window corresponding to the target call interface;
and updating the view window through the updated data document and the target call interface.
6. The method according to claim 1, wherein the method further comprises:
in response to a movement operation of dragging the third view window, determining a fourth view window with a distance from the third view window being less than or equal to a distance threshold;
if the third view window and the fourth view window belong to the same data document, adsorbing the third view window to one side of the fourth view window to realize multi-window parallel display, or combining a display interface of the third view window into the fourth view window to realize same-window multi-display interface display.
7. The method of claim 6, wherein the method further comprises:
if the third view window and the fourth view window belong to different data documents, determining a first data document corresponding to the third view window and determining a second data document corresponding to the fourth view window;
calculating the similarity between the data content contained in the first data document and the data content contained in the second data document;
and when the similarity is greater than or equal to a similarity threshold, adsorbing the third view window to one side of the fourth view window to realize multi-window parallel display, or merging a display interface of the third view window into the fourth view window to realize same-window multi-display interface display.
8. A data management apparatus, comprising:
a data document acquisition module for acquiring at least one created data document;
the view management data determining module is used for determining view management data corresponding to the data document;
the view window management module is used for managing at least one view window corresponding to each data document based on the view management data;
Wherein the view management data comprises a data document identification, the view window management module being configured to:
calling a view interface class corresponding to the data document based on the data document identification; the View interface class refers to a View class provided by the QT application development framework in an MVC mode;
and creating at least one view window corresponding to each data document according to the view interface class, wherein the view window is derived from the view interface class.
9. An electronic device, comprising:
a processor; and
a memory having stored thereon computer readable instructions which, when executed by the processor, implement the data management method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310422251.8A CN116185412B (en) | 2023-04-19 | 2023-04-19 | Data management method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310422251.8A CN116185412B (en) | 2023-04-19 | 2023-04-19 | Data management method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116185412A CN116185412A (en) | 2023-05-30 |
| CN116185412B true CN116185412B (en) | 2023-07-11 |
Family
ID=86444603
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310422251.8A Active CN116185412B (en) | 2023-04-19 | 2023-04-19 | Data management method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116185412B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101203848A (en) * | 2005-06-24 | 2008-06-18 | 佳思腾软件公司 | Document processing device and document processing method |
| CN110489725A (en) * | 2019-07-08 | 2019-11-22 | 浙江兴土桥梁临时钢结构工程有限公司 | Three-dimensional visualization method, device, computer equipment and its storage medium |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8566711B1 (en) * | 2005-11-14 | 2013-10-22 | Adobe Systems Incorporated | Document views |
| CN102200914B (en) * | 2011-06-24 | 2013-11-27 | 北京神州泰岳软件股份有限公司 | Method and equipment of realizing user interface on mobile terminal |
| CN111866403B (en) * | 2019-04-30 | 2022-11-22 | 腾讯科技（深圳）有限公司 | Video graphic content processing method, device, equipment and medium |
| CN115079873B (en) * | 2021-03-01 | 2024-03-26 | 北京字跳网络技术有限公司 | Information display method, information display device, electronic equipment and storage medium |
| CN115659909A (en) * | 2022-10-31 | 2023-01-31 | 北京字跳网络技术有限公司 | Method, apparatus, device and storage medium for presenting document |
-
2023
- 2023-04-19 CN CN202310422251.8A patent/CN116185412B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101203848A (en) * | 2005-06-24 | 2008-06-18 | 佳思腾软件公司 | Document processing device and document processing method |
| CN110489725A (en) * | 2019-07-08 | 2019-11-22 | 浙江兴土桥梁临时钢结构工程有限公司 | Three-dimensional visualization method, device, computer equipment and its storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116185412A (en) | 2023-05-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109992589B (en) | Method, device, server and medium for generating SQL (structured query language) statements based on visual page | |
| CN109634598B (en) | Page display method, device, equipment and storage medium | |
| CN110781658B (en) | Resume analysis method, resume analysis device, electronic equipment and storage medium | |
| CN113051514B (en) | Element positioning method and device, electronic equipment and storage medium | |
| CN113032083A (en) | Data display method, device, electronic equipment and medium | |
| CN113971037A (en) | Application processing method and device, electronic equipment and storage medium | |
| CN114461691A (en) | Control method and device of state machine, electronic equipment and storage medium | |
| CN109558408B (en) | Method and device for updating list, electronic equipment and readable storage medium | |
| CN116185412B (en) | Data management method and device, electronic equipment and storage medium | |
| CN114692055A (en) | Form processing method and device, storage medium and electronic equipment | |
| CN113110846A (en) | Method and device for acquiring environment variable | |
| CN113656041A (en) | Data processing method, device, equipment and storage medium | |
| CN113687880A (en) | Method, device, equipment and medium for calling component | |
| CN113760317A (en) | Page display method, device, equipment and storage medium | |
| CN114461127A (en) | Information display method, information display device, electronic equipment and computer readable storage medium | |
| CN112612991A (en) | Page display method and device, electronic equipment and storage medium | |
| US8775936B2 (en) | Displaying dynamic and shareable help data for images a distance from a pointed-to location | |
| CN111104409A (en) | Database processing method and device, storage medium and electronic equipment | |
| CN113835791B (en) | Method and apparatus for presenting hierarchical relationships of view components | |
| CN112445790B (en) | Report data storage method, device, equipment and medium | |
| CN111638903B (en) | Method and device for generating difference information of different software versions | |
| CN113821278B (en) | Calling image size method, device, electronic equipment and storage medium | |
| CN115658276B (en) | Service development method, device, electronic equipment and readable storage medium | |
| CN113760404A (en) | Page rollback method, device, equipment and storage medium | |
| CN107451273B (en) | Chart display method, medium, device and computing equipment |
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 |