CN112162793A - Method, storage medium, electronic device and system for separating structured view services - Google Patents
Method, storage medium, electronic device and system for separating structured view services Download PDFInfo
- Publication number
- CN112162793A CN112162793A CN202011062895.3A CN202011062895A CN112162793A CN 112162793 A CN112162793 A CN 112162793A CN 202011062895 A CN202011062895 A CN 202011062895A CN 112162793 A CN112162793 A CN 112162793A
- Authority
- CN
- China
- Prior art keywords
- plug
- view
- data
- structured
- structured view
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements 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/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/52—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow
- G06F21/54—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow by adding security routines or objects to programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G06F8/656—Updates while running
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements 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/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44568—Immediately runnable code
- G06F9/44578—Preparing or optimising for loading
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a method, a storage medium, electronic equipment and a system for separating structured view services, and relates to the field of application development of internet mobile terminals. The method comprises the following steps: defining an extension class of the structured view, which is configured with a host initiated plug-in method; defining an implementation protocol of the plug-in, and configuring a plug-in starting implementation method; when the structured view starts the plug-in, the main part starts all the related plug-ins by calling the plug-in starting method of the main part, in the starting process, a corresponding view copy is created for each plug-in, and the entrustment and the data source of the original structured view are assigned as the main part example; meanwhile, the plug-in starting implementation method of the relevant plug-in is called back, the relevant plug-ins are enabled to have respective view copies in the calling back process, and the view copies can play back all operations, except for setting delegation and data sources, of the plug-ins in the original structured view. The invention can achieve the purposes of separating service logic, reducing coupling and reducing maintenance cost.
Description
Technical Field
The invention relates to the field of application development of an internet mobile terminal, in particular to a method, a storage medium, electronic equipment and a system for separating structured view services.
Background
In application software development, the use of a structured view is often involved, and the structured view is a very common interaction mode, and comprises an abstract view such as a list view, a grid view, a paging view and the like. However, during the development and use of the structured view, there are usually multi-service logics, and these multi-service logics are coupled in the same entrusted class and the same data source, so that these two classes are very redundant, complex, and difficult to maintain.
Therefore, how to overcome the disadvantage that the multiple services are logically coupled in the same entrusted and same data source class in the prior art is a problem that needs to be solved by those skilled in the art.
Disclosure of Invention
The present invention is directed to overcome the above-mentioned drawbacks of the background art, and provides a method, a storage medium, an electronic device, and a system for separating structured view services, so that service logics of a delegation and a data source are distributed in different classes, and views can be accurately communicated and organized, thereby achieving the purposes of separating service logics, reducing coupling, and reducing maintenance cost.
To achieve the above object, in a first aspect, an embodiment of the present invention provides a method for separating a structured view service, including:
defining an extension class of the structured view, which is configured with a host initiated plug-in method; defining an implementation protocol of the plug-in, and configuring a plug-in starting implementation method;
when the plug-in is started by the structured view, the main part of the structured view starts all related plug-ins by calling the plug-in starting method of the main part; in the starting process, a plug-in class related to a main part is found by instantiating the structured view main part, the plug-in class is instantiated, and a corresponding view copy is created for each plug-in according to the main part instance and the plug-in instance; assigning the entrustment and the data source of the original structured view as a master instance;
meanwhile, the plug-in starting implementation method of the relevant plug-in is called back; in the callback process, the view copy instance corresponding to the plug-in is transmitted to the plug-in starting implementation method as an entry, so that the relevant plug-ins have respective view copies, and the view copies can play back all operations, except for setting delegation and data sources, of the plug-ins in the original structured view.
As a preferred embodiment, when the structured view master is instantiated, the customized structured view master class is instantiated to obtain the corresponding instance of the structured view master.
As a preferred embodiment, the method for implementing plug-in startup by using view copy instances corresponding to plug-ins as entries is introduced into the plug-in startup implementation method, so that the relevant plug-ins have respective view copies, and includes the following operations:
defining the access parameters of the plug-in startup implementation method to comprise a main part identifier hostIdentifier and a structured view tableView;
when the plug-in starting implementation method of the related plug-in is called back, the import parameter hostIdentifier is assigned to be a specific instance of the main part identifier, and the import parameter tableView is assigned to be a view copy instance corresponding to the plug-in.
As a preferred embodiment, the extension class of the structured view is further configured with:
a data set variable for returning a unified data set for the structured view;
and the plug-in data starting updating method and the plug-in data ending updating method are used for wrapping all operation processes of the data set variables.
As a preferred embodiment, the method further comprises the steps of:
when a plug-in needs to add data to a data set variable of an original structured view, calling the plug-in data to start an updating method; the method comprises the steps of initializing a data set as a data copy of the plug-in, traversing data set variables and judging: if the data source of the current data packet is from the plug-in, solving the data in the data packet and putting the data in the data copy of the plug-in; otherwise, adding meaningless data as position occupying data to the data copy of the plug-in;
when the plug-in adds data to the data copy, calling the plug-in data ending updating method; the method removes all data packets belonging to the plug-in the data set variable; then, traversing the data copy of the plug-in and judging: and if the current data is nonsensical data, inserting the data packet into the current data set variable, wherein the position of the data packet is the same as that of the data in the data copy.
As a preferred embodiment, the method further comprises a rendering process of the structured view:
when the structured view starts to be rendered, a view data source protocol method or a view entrusting protocol method of a data source example is called back one by one through data in a data set variable, and a main part example corresponding to the data source can distribute all call backs to the data source in a specified plug-in example as required; the data source instance of the plug-in for placing the data receives the call-back and returns the service Cell of the call-back;
and forwarding all the view data source protocol methods and the view delegation protocol methods according to the mode so as to complete the rendering of the whole structured view and the event callback.
As a preferred embodiment, the extension class of the structured view is further configured with: a method for refreshing all plug-ins associated with the master, and a method for uninstalling all plug-ins associated with the master; the implementation protocol is also configured with: methods for implementing plug-in refreshes, and methods for implementing plug-in uninstallations.
In a second aspect, an embodiment of the present invention provides a system for separating structured view services, including:
a definition module for defining an extension class of the structured view, configured with a master startup plug-in method; defining an implementation protocol of the plug-in, and configuring a plug-in starting implementation method;
the first starting module is used for controlling the main part of the structured view to start all related plug-ins by calling the main part starting plug-in method when the plug-ins are started by the structured view; in the starting process, a plug-in class related to a main part is found by instantiating the structured view main part, the plug-in class is instantiated, and a corresponding view copy is created for each plug-in according to the main part instance and the plug-in instance; assigning the entrustment and the data source of the original structured view as a master instance;
the second starting module is used for calling back the plug-in starting implementation method of the relevant plug-in when the first starting module finishes the operation; in the callback process, the view copy instance corresponding to the plug-in is transmitted to the plug-in starting implementation method as an entry, so that the relevant plug-ins have respective view copies, and the view copies can play back all operations, except for setting delegation and data sources, of the plug-ins in the original structured view.
In a third aspect, an embodiment of the present invention further provides a storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the method in the first aspect.
In a fourth aspect, an embodiment of the present invention further provides an electronic device, which includes a memory and a processor, where the memory stores a computer program running on the processor, and the processor executes the computer program to implement the method in the first aspect.
The invention has the beneficial effects that:
(1) in the invention, only the master has a real structural view, each plug-in related to the master can only operate a respective unique view copy, but the operation of each related plug-in on the view copy can be played back in the real structural view, so that independent operation can be realized in a development level without mutual interference; and the main part instance takes over the real entrustment and the data source, and intercepts the operation of setting the entrustment and the data source on the plug-in side, so that the business logics of the entrustment and the data source can be distributed in different classes, the views can be accurately communicated and organized, and the purposes of separating the business logics, reducing the coupling and reducing the maintenance cost are achieved.
(2) In the invention, when each plug-in adds data, each plug-in can only operate the respective data copy, and the data copies of the plug-ins are mutually independent, so that the plug-in cannot acquire the data added into the data set by other plug-ins, the possibility of mutual modification of the data among the plug-ins is also avoided, and the purpose of protecting the data is achieved. In addition, when the data in each data copy is written back to the data set of the original structured view, the data is inserted according to the same position in each plug-in data copy, so that the coverage between the previous data and the next data is avoided, and the integrity and the accuracy of the data are ensured.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings corresponding to the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a flow chart of a method for structured view service separation in an embodiment of the present invention;
fig. 2 is a block diagram of a system for separating structured view services according to an embodiment of the present invention.
In the figure: 10-a definition module, 20-a first starting module, 30-a second starting module.
Detailed Description
First, explanation is made on related technical terms appearing in the embodiments of the present invention:
(1) and (3) structuring view: the system comprises an abstract view control used in software, a display control module and a display control module, wherein the abstract view control is used for completing the style display, control and update of a certain specific type and is provided with a fixed external interface, a call-back and an event; common structured views include list views, grid views, paginated views, and the like.
(2) Service elements: the addition, control, callback, monitoring and the like of a certain view are all called service elements, and if the elements belong to the service A, the service A is called to have the service elements in the view.
(3) A main part: the business module which is actually initialized and operated to show a certain structured view is the actual owner of the structured view.
(4) Plug-in components: the method refers to that in a certain structural view, except for the main business element, all business modules to which other business elements exist in the structural view belong are plug-ins.
(5) View copy: refers to a copy provided for a certain structured view, which is not the view itself, but all operations and monitoring on the view copy can be played back in the original structured view, and the view copy can make necessary modification and interception on the operations, etc.
(6) Data copy: if the view has a data set of the view, when the plug-in B acquires the data set, a copy of the data set is obtained, the data copy only contains data related to the plug-in B, and if the data is strongly bound with the position relation, the positions of the data of the non plug-in B are filled with meaningless values.
It can be understood that, in the prior art, during the development and use of the structured view, the logic of multiple services is coupled in the same entrusted class and the same data source class, so that the two classes are very redundant, complex and difficult to maintain. For example, there is a master C and a plug-in D, E, F … … associated with the master C in a structured view; then in order to enable the host C and the plug-ins D, E, F, etc. to normally implement the functions of adding, controlling, calling back, listening, etc. to the view, the business logic of the host C and the plug-ins D, E, F must be coupled in the same entrusting and same data source class related to the structured view, so that when the structured view is used, the corresponding plug-ins can be normally called. While the business logic of these plug-ins D, E, F also couple in the same delegated, same data source class associated with the structured view when plug-ins D, E, F are also present in another structured view. Thus, these two classes are very redundant, complex, and difficult to maintain.
The invention aims to provide a method, a storage medium, electronic equipment and a system for separating structured view services, so that service logics of entrusts and data sources are distributed in different classes, and the views can be accurately communicated and organized, thereby achieving the purposes of separating the service logics, reducing coupling and lowering maintenance cost.
In order to achieve the technical effects, the main design idea of the invention is as follows:
defining an extension class of the structured view, which is configured with a host initiated plug-in method; defining an implementation protocol of the plug-in, and configuring a plug-in starting implementation method;
when the plug-in is started by the structured view, the main part of the structured view starts all related plug-ins by calling the plug-in starting method of the main part; in the starting process, a plug-in class related to a main part is found by instantiating the structured view main part, the plug-in class is instantiated, and a corresponding view copy is created for each plug-in according to the main part instance and the plug-in instance; assigning the entrustment and the data source of the original structured view as a master instance;
meanwhile, the plug-in starting implementation method of the relevant plug-in is called back; in the callback process, the view copy instance corresponding to the plug-in is transmitted to the plug-in starting implementation method as an entry, so that the relevant plug-ins have respective view copies, and the view copies can play back all operations, except for setting delegation and data sources, of the plug-ins in the original structured view.
In summary, in the scheme, only the master has a real structured view, each related plug-in has a respective independent view copy, and operations on the view copies can be played back in the real structured view, so that the independent operations can be realized in a development level without interference, the master takes over real delegation and data sources, and the operation of setting delegation and data sources is intercepted on the plug-in side, so that business logics of the delegation and data sources can be distributed in different classes, and the views can be accurately communicated and organized, thereby achieving the purposes of separating the business logics, reducing coupling and reducing maintenance cost.
In order to make the technical problems, technical solutions and advantages of the present invention more apparent, the technical solutions of the present invention will be described in detail with reference to the accompanying drawings and specific embodiments.
However, it should be noted that: the examples to be described next are only some specific examples, and are not intended to limit the embodiments of the present invention necessarily to the following specific steps, values, conditions, data, orders, and the like. Those skilled in the art can, upon reading this specification, utilize the concepts of the present invention to construct more embodiments than those specifically described herein.
Example one
Referring to fig. 1, the present embodiment provides a method for separating a structured view service, which includes the following steps:
s1, defining an extension class of the structured view, wherein the extension class is configured with a main component starting plug-in method for starting all plug-ins related to the main component; defining the implementation protocol of the plug-in, configuring a plug-in starting implementation method for realizing the starting of each plug-in.
It can be understood that, in order to implement the present solution, an extension class needs to be defined for the structured view first, and the core method needed to be used is disclosed. Similarly, we also need to define the implementation protocol of the plug-in, which includes the lifecycle callback of the plug-in, corresponding to the method in the extended class of the structured view. In the embodiment of the present invention, in the extended class of the structured view, a host startup plug-in method for starting all plug-ins related to the host is configured, for example, a plghost _ load method. In the implementation protocol of the plug-in, a plug-in startup implementation method for implementing startup of each plug-in is configured, and may be a plg _ load method, for example. The plug-in starting implementation method corresponds to the plug-in starting method of the main part. When the main plugin is started, all plugin classes corresponding to the main plugin can be found according to the method in the plugin protocol, and the plugin classes are instantiated. Moreover, because the plug-in class (not an instance) is registered in a static set for storage in the plug-in protocol, the plug-in class accesses the service in a registration mode and is independent from other services, and the coupling is reduced to a certain extent.
S2, when the plug-in is started by the structured view, the main part of the structured view starts all the related plug-ins by calling the method of starting the plug-in by the main part; in the starting process, a plug-in class related to a main part is found by instantiating the structured view main part, the plug-in class is instantiated, and a corresponding view copy is created for each plug-in according to the main part instance and the plug-in instance; assigning a delegation (delete) and a data source (dataSource) of the original structured view as a master instance;
meanwhile, the plug-in starting implementation method of the relevant plug-in is called back; in the callback process, a view copy instance corresponding to the plug-in is transmitted to the plug-in starting implementation method as an entry, so that the relevant plug-ins have respective view copies, and the view copies can play back all operations, except for a setting delegation (delete) and a data source (data source), performed by the plug-ins in the original structured view.
It is understood that in the present embodiment, when the plug-in is launched by the structured view, two major processes are experienced:
(1) the main part of the structured view starts the process of all the related plug-ins by calling the main part starting plug-in method. During this boot process, two things are done, one is: finding and instantiating a plug-in class related to the main part by instantiating the structured view main part, and creating and storing a corresponding view copy for each plug-in according to the two instances so as to enable the corresponding view copy to be used in the subsequent plug-in callback process; second, let the master instance take over the real delegation and data source. Specifically, as an optional implementation manner, in this embodiment, when instantiating the structured view master, the customized structured view master class is instantiated to obtain an instance of the corresponding structured view master. For example, the structured view master class can be customized as UITableViewHost, and the specific definition can be as follows:
in actual application, when the main component of the structured view starts all related plug-ins by calling the main component starting plug-in method, the UITableViewHost instance AHost is initialized and is associated with the original structured view (namely, the real view source) through the system obj _ setAssassailateObject method, all the created view copy instances are saved in the variable keys, the delegate (delete) and the data source (data source) of the original structured view are assigned to be self (namely, AHost), and the delegate (delete) and the data source (data source) of the original structured view are respectively saved in the sourceDelegate and sourceDataSource. Let AHost take over the delete and dataSource of the real view for later callback and event distribution, and the corresponding content will be described in detail later, and will not be described herein again.
(2) The plug-in of the relevant plug-in starts the process that the implementation method is called back. In the callback process, the view copy instance corresponding to the plug-in needs to be transmitted to the plug-in startup implementation method as an entry, so that the relevant plug-ins have respective view copies. Specifically, as an optional implementation manner, in this embodiment, the view copy instance corresponding to the plug-in is imported as an entry into the plug-in startup implementation method, so that the relevant plug-ins have respective view copies, specifically including the following operations:
step 1, defining the access parameter of the plug-in starting implementation method to comprise a main part identifier hostIdentifier and a structured view tableView. For example, a plug-in may be defined to initiate a run-in class of the implementation, such as PluginArg, which may include:
and 2, when the plug-in starting implementation method of the related plug-in is called back, assigning the entry-entry identifier as a specific example of the main part identifier, and assigning the entry-entry tableView as a view copy example corresponding to the plug-in.
In this embodiment, the parameter is represented by { hostdidentifier ═ myhostdidentifier; tableView ═ FakeOf (a, B); and assigning the import reference hostIdentifier as a specific instance of the master identifier, and assigning the import reference tableView as a view copy instance corresponding to the plug-in. Wherein, the real class of fakeof (a) is UITableViewFake, and is a view copy class of the structured view, which is defined as follows:
Class UITableViewFake(source:UITableView,plugin:Object<Plugin>):Proxy；
at instantiation, the add-in is the structured view and the add-in instance itself that accepts the add-in, and a different list view copy is provided for each different add-in (i.e., each associated add-in has a respective view copy); and this class will hold the delegates and data sources belonging to its own instance. Examples are as follows:
Class UITableViewFake(source:UITableView,plugin:Object<Plugin>):Proxy{
delete Object < UITableViewDelegate >; // saving delegation belonging to its own instance
Object < UITableViewDataSource >; v/saving data sources belonging to its own instance
}
It can be seen that, in the plug-in startup implementation method on the plug-in side, the plug-in may directly treat tableView (i.e., a view copy instance) as a real structured view, and the view copy may play back all operations (except for setting a delegate and a data source) performed by the plug-in the real structured view (source), so that each plug-in is equivalent to having a real structured view.
As can be seen from the operations of the above steps S1-S2, when the main part of the structured view starts all related plug-ins by calling the main part plug-in starting method, a corresponding view copy is created and stored for each plug-in related to the main part, and the main part instance is made to take over the real entrustment and data source; meanwhile, when the plug-in at the plug-in side starts the realization method to call back, the plug-in directly treats the corresponding view copy instance as a real structured view, and all operations (except setting a delegation and a data source) performed by the plug-in on the view copy are played back in the real structured view. Because only the main part has a real structural view, each related plug-in has a respective independent view copy, and the respective operations on the view copies can be played back in the real structural view, so that the independent operations can be realized in a development level without mutual interference, the main part instance takes over the real entrustment and the data source, and the operation for setting the entrustment and the data source is intercepted on the plug-in side, thereby enabling the business logics of the entrustment and the data source to be distributed in different classes, accurately communicating and organizing the view, separating the business logics, reducing coupling and reducing maintenance cost.
Further, in order to meet the requirement of practical application, as an optional implementation, the extension class of the structured view is further configured with: a method for refreshing all plug-ins associated with the master (e.g., plghost _ refresh method), and a method for uninstalling all plug-ins associated with the master (e.g., plghost _ unload method). Correspondingly, the implementation protocol is further configured with: a method for implementing refreshing of each plug-in (such as a plg _ refresh method), and a method for implementing uninstalling of each plug-in (such as a plg _ unload method). For example, the implementation protocol of the defined plug-in may be as follows:
it can be understood that, in practical applications, the specific implementation manner of the refresh plug-in and the specific implementation manner of the uninstall plug-in are processed according to the same idea as the implementation manner of the start plug-in this embodiment. The method names of the main part during calling and the method names of the related plug-in callback are different, and the internal implementation logic of the main part is the same as that of the starting plug-in. For example, when a structured view refreshes a plug-in, the main part of the structured view refreshes all relevant plug-ins by calling the plghost _ refresh method; and the plg refresh method of the associated plug-in will be recalled. When the plug-in is unloaded from the structured view, the main part of the structured view refreshes all relevant plug-ins by calling a plghost _ unload method; and the plg _ unload method of the relevant plug-in will be recalled.
Still further, as a preferred embodiment, the extension class of the structured view is further configured with: a data set variable for returning a unified data set for the structured view; and the plug-in data starting updating method and the plug-in data ending updating method are used for wrapping all operation processes of the data set variables. For example, the extension class of the defined structured view may be as follows:
on this basis, as a preferred implementation manner, after step S2, the following operations are further included in this embodiment:
(1) when a plug-in wants to add data to a data set variable (plg _ data) of an original structured view, calling the plug-in data to start an update method (plg _ beginnupdate) first; the method comprises the steps of initializing a data set (a list here) as a data copy, traversing data set variables of an original structured view (data in the data set variables are stored in a data packet mode), and judging: if the data source of the currently traversed data packet (i.e. the WrapObject in the following text, see the following description in particular) is from the current plug-in (i.e. the data is added or modified by the current plug-in), solving the data in the data packet and putting the data into the data copy; otherwise, add a meaningless data (e.g., Null) as placeholder data to the data copy.
For example, the execution code for the plg _ beginnupdate method may be as follows:
(2) when the plug-in adds data to the data copy, calling a plug-in data end updating method (plg _ endUpdate); the method will remove all data packets belonging to the plug-in the data set variable (plg _ data) of the original structured view; then, traversing the data copy and judging: if the currently traversed data is not meaningless data (e.g., non-Null), the data packet is inserted into the data set variable (plg _ data) of the original structured view at the same position as the position in the data copy.
For example, the execution code for the plg endUpdate method may be as follows:
in the above code, wrappobject is a wrapper class of data, and is defined as follows:
Class WrapObject(object:Object,plugin:Object<Plugin>):Object；
the wrapper class may store the original data and the source of the plug-in for the data, so the method of determining the source of the data in step (1) is accomplished by determining the source of the plug-in.
In order to more clearly understand the operation and effects. The following is a specific example, as an illustration: suppose that the data set variables (plg _ data) of the original structured view include data B1, C1, B2, C2; the plug-in sources of B1 and B2 are B, and the plug-in sources of C1 and C2 are C.
When plug-in B wants to add data B3 to the data set variable (plg _ data) of the original structured view, the plg _ beginUpdate method is called first. Initializing a data set (a list here) as a data copy of the plug-in B, and then selecting data B1 and B2 belonging to the plug-in B from the data set by traversing the original structured view; b1 and B2 are put into the data copy of plug-in B, and for the data of which the source is not B, meaningless data (such as Null) is added to the corresponding position of the data copy to be used as placeholder data. At this time, the data copy of plug-in B is B1, Null, B2, Null. Plug-in B will then add B3 to the current data copy, and the data copy of plug-in B after addition is B1, Null, B2, Null, B3.
Thereafter, the plg endUpdate method will be called. The method removes all data packets belonging to the plug-in B from a data set variable (plg _ data) of an original structured view, wherein the data in the removed data set variable (plg _ data) are C1 and C2; then, traversing the data copy of the plug-in B, and packaging and inserting the non-meaningless data B1, B2 and B3 into the data set variables (plg _ data) of the original structured view, wherein the positions of the data set variables (plg _ data) are the same as those of the data copy of the plug-in B, namely, the data in the data set variables (plg _ data) of the original structured view after insertion are B1, C1, B2, C2 and B3, and the added data B3 does not cover the data of any previous plug-in.
It can be seen from the above operation that, when data is added by each plug-in, each plug-in can only operate its respective data copy, and the data copies of the plug-ins are independent from each other, so that the plug-in B cannot acquire the data added by the plug-in C to the data set, and the possibility of mutual modification of the data among the plug-ins is also eliminated, thereby achieving the purpose of protecting the data; in addition, when the data in each data copy is written back to the data set of the original structured view, the data is inserted according to the same position in each plug-in data copy, so that the coverage between the previous data and the next data is avoided, and the integrity and the accuracy of the data are ensured.
Example two
A second embodiment of the present invention provides a method for separating services of a structured view, which has the same basic steps as the first embodiment, except that as a preferred implementation, the method further includes a rendering process of the structured view:
when the structured view starts to be rendered, the view data source protocol method (such as UITableViewDataSource protocol method) or the view entrustment protocol method (such as UITableViewDataSource protocol method) of the data source (DataSource) instance is called back by data in the data collection variable (plg _ data) one by one, and the data source (DataSource) is a main element instance (such as AHost) at the moment, so that the main element instance (such as AHost) distributes all callbacks to the data source (DataSource) in the specified plug-in instance as required; the data source (dataSource) instance of the plug-in that placed the data will receive the callback and return its service Cell. And forwarding all the view data source protocol methods and the view delegation protocol methods according to the mode so as to complete the rendering of the whole structured view and the event callback.
The above distribution process is illustrated by taking the callback tableViewCellForRow of the data acquisition view Cell as an example. The executable code of tableViewCellForRow is as follows:
the tableViewCellForRow is a callback of the system list view, the callback takes the index and the view as reference, and a list item view corresponding to the index is obtained for displaying. The execution process comprises the following steps: acquiring a data packet under a corresponding index in an original view data set; obtaining the source of the data packet (for determining which plug-in); finding a view copy corresponding to the plug-in from the collection of view copies; the same callback method of the plug-in is called, but the view entry is changed into the view copy entry, and the index is unchanged.
EXAMPLE III
Based on the same inventive concept, as shown in fig. 2, a third embodiment of the present invention provides a system for separating structured view services, which includes:
a definition module 10 for defining an extension class of the structured view, configured with a master startup plug-in method for starting all plug-ins related to the master; defining a realization protocol of the plug-in, configuring a plug-in starting realization method for realizing the starting of each plug-in;
the first starting module 20 is used for controlling the main part of the structured view to start all related plug-ins by calling the main part starting plug-in method when the plug-ins are started by the structured view; in the starting process, a plug-in class related to a main part is found by instantiating the structured view main part, the plug-in class is instantiated, and a corresponding view copy is created for each plug-in according to the main part instance and the plug-in instance; assigning the entrustment and the data source of the original structured view as a master instance;
a second starting module 30, configured to call back the plug-in starting implementation method of the relevant plug-in when the first starting module completes the operation; in the callback process, the view copy instance corresponding to the plug-in is transmitted to the plug-in starting implementation method as an entry, so that the relevant plug-ins have respective view copies, and the view copies can play back all operations, except for setting delegation and data sources, of the plug-ins in the original structured view.
Various modifications and specific examples in the foregoing method embodiments are also applicable to the system of the present embodiment, and the detailed description of the method is clear to those skilled in the art, so that the detailed description is omitted here for the sake of brevity.
Example four
Based on the same inventive concept, a fourth embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, which when executed by a processor, implements a method for structured view service separation as provided in any of the embodiments of the present invention, the method comprising:
defining an extension class of the structured view, which is configured with a host initiated plug-in method; defining an implementation protocol of the plug-in, and configuring a plug-in starting implementation method;
when the plug-in is started by the structured view, the main part of the structured view starts all related plug-ins by calling the plug-in starting method of the main part; in the starting process, a plug-in class related to a main part is found by instantiating the structured view main part, the plug-in class is instantiated, and a corresponding view copy is created for each plug-in according to the main part instance and the plug-in instance; assigning the entrustment and the data source of the original structured view as a master instance;
meanwhile, the plug-in starting implementation method of the relevant plug-in is called back; in the callback process, the view copy instance corresponding to the plug-in is transmitted to the plug-in starting implementation method as an entry, so that the relevant plug-ins have respective view copies, and the view copies can play back all operations, except for setting delegation and data sources, of the plug-ins in the original structured view.
Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer-readable storage medium may be, for example but not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer 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.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer 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 computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, 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 computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
EXAMPLE five
Based on the same inventive concept, a fifth embodiment of the present invention further provides an electronic device, which includes a memory and a processor, wherein the memory stores a computer program running on the processor, and the processor executes the computer program to implement all or part of the method steps in the first embodiment.
The Processor may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. The general purpose processor may be a microprocessor or the processor may be any conventional processor or the like which is the control center for the computer device and which connects the various parts of the overall computer device using various interfaces and lines.
The memory may be used to store the computer programs and/or modules, and the processor may implement various functions of the computer device by running or executing the computer programs and/or modules stored in the memory and invoking data stored in the memory. The memory may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, video data, etc.) created according to the use of the cellular phone, etc. In addition, the memory may include high speed random access memory, and may also include non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), at least one magnetic disk storage device, a Flash memory device, or other volatile solid state storage device.
Generally, the time-sharing loading management method, the storage medium, the electronic device and the system provided by the embodiments of the present invention can implement time-sharing loading, conveniently adjust and manage the loading time of the service function module, reduce the coupling between the loading logic of the live broadcast room and the live broadcast room controller, improve the reusability of the loading logic, and provide good user experience.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Note that: the above-described embodiments are merely examples and are not intended to be limiting, and those skilled in the art can combine and combine some steps and devices from the above-described separately embodiments to achieve the effects of the present invention according to the concept of the present invention, and such combined and combined embodiments are also included in the present invention, and such combined and combined embodiments are not described herein separately.
Advantages, effects, and the like, which are mentioned in the embodiments of the present invention, are only examples and are not limiting, and they cannot be considered as necessarily possessed by the various embodiments of the present invention. Furthermore, the foregoing specific details disclosed herein are merely for purposes of example and for purposes of clarity of understanding, and are not intended to limit the embodiments of the invention to the particular details which may be employed to practice the embodiments of the invention.
The block diagrams of devices, apparatuses, systems involved in the embodiments of the present invention are only given as illustrative examples, and are not intended to require or imply that the connections, arrangements, configurations, etc. must be made in the manner shown in the block diagrams. These devices, apparatuses, devices, systems may be connected, arranged, configured in any manner, as will be appreciated by those skilled in the art. Words such as "including," "comprising," "having," and the like are open-ended words that mean "including, but not limited to," and are used interchangeably therewith. As used in connection with embodiments of the present invention, the terms "or" and "refer to the term" and/or "and are used interchangeably herein unless the context clearly dictates otherwise. The word "such as" is used in connection with embodiments of the present invention to mean, and is used interchangeably with, the word "such as but not limited to".
The flow charts of steps in the embodiments of the present invention and the above description of the methods are merely illustrative examples and are not intended to require or imply that the steps of the various embodiments must be performed in the order presented. As will be appreciated by those skilled in the art, the order of the steps in the above embodiments may be performed in any order. Words such as "thereafter," "then," "next," etc. are not intended to limit the order of the steps; these words are only used to guide the reader through the description of these methods. Furthermore, any reference to an element in the singular, for example, using the articles "a," "an," or "the" is not to be construed as limiting the element to the singular.
In addition, the steps and devices in the embodiments of the present invention are not limited to be implemented in a certain embodiment, and in fact, some steps and devices in the embodiments of the present invention may be combined according to the concept of the present invention to conceive new embodiments, and these new embodiments are also included in the scope of the present invention.
The respective operations in the embodiments of the present invention may be performed by any appropriate means capable of performing the corresponding functions. The means may comprise various hardware and/or software components and/or modules including, but not limited to, hardware circuitry or a processor.
The method of an embodiment of the invention includes one or more acts for implementing the method described above. The methods and/or acts may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and/or use of specific actions may be modified without departing from the scope of the claims.
Various changes, substitutions and alterations to the techniques described herein may be made by those skilled in the art without departing from the techniques of the teachings as defined by the appended claims. Moreover, the scope of the claims of the present disclosure is not limited to the particular aspects of the process, machine, manufacture, composition of matter, means, methods and acts described above. Processes, machines, manufacture, compositions of matter, means, methods, or acts, presently existing or later to be developed that perform substantially the same function or achieve substantially the same result as the corresponding aspects described herein may be utilized. Accordingly, the appended claims are intended to include within their scope such processes, machines, manufacture, compositions of matter, means, methods, or acts.
The previous description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects without departing from the scope of the invention. Thus, the present invention is not intended to be limited to the aspects shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
The foregoing description has been presented for purposes of illustration and description. Furthermore, the description is not intended to limit embodiments of the invention to the form disclosed herein. While a number of example aspects and embodiments have been discussed above, those of skill in the art will recognize certain variations, modifications, alterations, additions and sub-combinations thereof. And those not described in detail in this specification are within the skill of the art.
Claims (10)
1. A method for separating structured view services, comprising the steps of:
defining an extension class of the structured view, which is configured with a host initiated plug-in method; defining an implementation protocol of the plug-in, and configuring a plug-in starting implementation method;
when the plug-in is started by the structured view, the main part of the structured view starts all related plug-ins by calling the plug-in starting method of the main part; in the starting process, a plug-in class related to a main part is found by instantiating the structured view main part, the plug-in class is instantiated, and a corresponding view copy is created for each plug-in according to the main part instance and the plug-in instance; assigning the entrustment and the data source of the original structured view as a master instance;
meanwhile, the plug-in starting implementation method of the relevant plug-in is called back; in the callback process, the view copy instance corresponding to the plug-in is transmitted to the plug-in starting implementation method as an entry, so that the relevant plug-ins have respective view copies, and the view copies can play back all operations, except for setting delegation and data sources, of the plug-ins in the original structured view.
2. The method of structured view service separation according to claim 1, wherein: and when the structured view master is instantiated, the corresponding instance of the structured view master is obtained by instantiating the self-defined structured view master class.
3. The method for structured view service separation according to claim 1, wherein importing a view copy instance corresponding to a plug-in as an entry into the plug-in startup implementation method such that the associated plug-ins have respective view copies comprises the following operations:
defining the access parameters of the plug-in startup implementation method to comprise a main part identifier hostIdentifier and a structured view tableView;
when the plug-in starting implementation method of the related plug-in is called back, the import parameter hostIdentifier is assigned to be a specific instance of the main part identifier, and the import parameter tableView is assigned to be a view copy instance corresponding to the plug-in.
4. The method for structured view business separation according to claim 1, wherein the extension class of the structured view is further configured with:
a data set variable for returning a unified data set for the structured view;
and the plug-in data starting updating method and the plug-in data ending updating method are used for wrapping all operation processes of the data set variables.
5. The method of structured view service separation according to claim 4, wherein the method further comprises the steps of:
when a plug-in needs to add data to a data set variable of an original structured view, calling the plug-in data to start an updating method; the method comprises the steps of initializing a data set as a data copy of the plug-in, traversing data set variables and judging: if the data source of the current data packet is from the plug-in, solving the data in the data packet and putting the data in the data copy of the plug-in; otherwise, adding meaningless data as position occupying data to the data copy of the plug-in;
when the plug-in adds data to the data copy, calling the plug-in data ending updating method; the method removes all data packets belonging to the plug-in the data set variable; then, traversing the data copy of the plug-in and judging: and if the current data is nonsensical data, inserting the data packet into the current data set variable, wherein the position of the data packet is the same as that of the data in the data copy.
6. The method of structured view business separation of claim 5, further comprising a structured view rendering process:
when the structured view starts to be rendered, a view data source protocol method or a view entrusting protocol method of a data source example is called back one by one through data in a data set variable, and a main part example corresponding to the data source can distribute all call backs to the data source in a specified plug-in example as required;
the data source instance of the plug-in for placing the data receives the call-back and returns the service Cell of the call-back;
and forwarding all the view data source protocol methods and the view delegation protocol methods according to the mode so as to complete the rendering of the whole structured view and the event callback.
7. The method for structured view business separation according to claim 1, wherein the extension class of the structured view is further configured with: a method for refreshing all plug-ins associated with the master, and a method for uninstalling all plug-ins associated with the master;
the implementation protocol is also configured with: methods for implementing plug-in refreshes, and methods for implementing plug-in uninstallations.
8. A storage medium having a computer program stored thereon, characterized in that: the computer program, when executed by a processor, implements the method of any one of claims 1 to 7.
9. An electronic device comprising a memory and a processor, the memory having stored thereon a computer program that runs on the processor, characterized in that: the processor, when executing the computer program, implements the method of any of claims 1 to 7.
10. A system for structured view service separation, comprising:
a definition module for defining an extension class of the structured view, configured with a master startup plug-in method; defining an implementation protocol of the plug-in, and configuring a plug-in starting implementation method;
the first starting module is used for controlling the main part of the structured view to start all related plug-ins by calling the main part starting plug-in method when the plug-ins are started by the structured view; in the starting process, a plug-in class related to a main part is found by instantiating the structured view main part, the plug-in class is instantiated, and a corresponding view copy is created for each plug-in according to the main part instance and the plug-in instance; assigning the entrustment and the data source of the original structured view as a master instance;
the second starting module is used for calling back the plug-in starting implementation method of the relevant plug-in when the first starting module finishes the operation; in the callback process, the view copy instance corresponding to the plug-in is transmitted to the plug-in starting implementation method as an entry, so that the relevant plug-ins have respective view copies, and the view copies can play back all operations, except for setting delegation and data sources, of the plug-ins in the original structured view.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011062895.3A CN112162793B (en) | 2020-09-30 | 2020-09-30 | Method, storage medium, electronic device and system for separating structured view services |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011062895.3A CN112162793B (en) | 2020-09-30 | 2020-09-30 | Method, storage medium, electronic device and system for separating structured view services |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112162793A true CN112162793A (en) | 2021-01-01 |
| CN112162793B CN112162793B (en) | 2022-05-10 |
Family
ID=73860898
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011062895.3A Active CN112162793B (en) | 2020-09-30 | 2020-09-30 | Method, storage medium, electronic device and system for separating structured view services |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112162793B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114090113A (en) * | 2021-10-27 | 2022-02-25 | 北京百度网讯科技有限公司 | Method, device and equipment for dynamically loading data source processing plug-in and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5734863A (en) * | 1986-04-14 | 1998-03-31 | National Instruments Corporation | Method and apparatus for providing improved type compatibility and data structure organization in a graphical data flow diagram |
| WO2006030015A2 (en) * | 2004-09-17 | 2006-03-23 | International Business Machines Corporation | Display and installation of portlets on a client platform |
| US20090077546A1 (en) * | 2007-09-14 | 2009-03-19 | International Business Machines Corporation | Method, Apparatus and Systems thereof for Implementing Non-Function Logic Extensibly |
| US20120174064A1 (en) * | 2010-12-30 | 2012-07-05 | Adam Polly | Management of objects within a meta-data repository |
| CN106990987A (en) * | 2017-04-05 | 2017-07-28 | 上海新炬网络信息技术有限公司 | Plug-in unit based on karaf_agent ends/Service Component automatic managing device and method |
-
2020
- 2020-09-30 CN CN202011062895.3A patent/CN112162793B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5734863A (en) * | 1986-04-14 | 1998-03-31 | National Instruments Corporation | Method and apparatus for providing improved type compatibility and data structure organization in a graphical data flow diagram |
| WO2006030015A2 (en) * | 2004-09-17 | 2006-03-23 | International Business Machines Corporation | Display and installation of portlets on a client platform |
| US20090077546A1 (en) * | 2007-09-14 | 2009-03-19 | International Business Machines Corporation | Method, Apparatus and Systems thereof for Implementing Non-Function Logic Extensibly |
| US20120174064A1 (en) * | 2010-12-30 | 2012-07-05 | Adam Polly | Management of objects within a meta-data repository |
| CN106990987A (en) * | 2017-04-05 | 2017-07-28 | 上海新炬网络信息技术有限公司 | Plug-in unit based on karaf_agent ends/Service Component automatic managing device and method |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114090113A (en) * | 2021-10-27 | 2022-02-25 | 北京百度网讯科技有限公司 | Method, device and equipment for dynamically loading data source processing plug-in and storage medium |
| CN114090113B (en) * | 2021-10-27 | 2023-11-10 | 北京百度网讯科技有限公司 | Method, device, equipment and storage medium for dynamically loading data source processing plug-in |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112162793B (en) | 2022-05-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109032691B (en) | Applet running method and device and storage medium | |
| US11706331B2 (en) | Information processing method and apparatus, storage medium, and electronic device | |
| CN108062252B (en) | Information interaction method, object management method, device and system | |
| CN110417766A (en) | A kind of method and apparatus of protocol analysis | |
| WO2019022827A1 (en) | Systems and methods for providing patchable rom firmware | |
| CN113312032B (en) | Front-end project resource updating method and device, electronic equipment and storage medium | |
| CN111651219A (en) | Method and equipment for managing multi-module project configuration file | |
| CN112162793B (en) | Method, storage medium, electronic device and system for separating structured view services | |
| CN107133160B (en) | Server and client | |
| CN113157345A (en) | Automatic starting method and device for front-end engineering | |
| CN109725887B (en) | Data interaction method and device based on message research and development framework and terminal equipment | |
| CN109343970B (en) | Application program-based operation method and device, electronic equipment and computer medium | |
| CN110267077A (en) | Offline cache method, apparatus, terminal and readable storage medium storing program for executing | |
| CN111581576B (en) | Development processing method and device based on micro-service and storage medium | |
| CN109815202B (en) | Log editing method and related device | |
| CN110673827A (en) | Resource calling method and device based on android system and electronic equipment | |
| CN108804088B (en) | Protocol processing method and device | |
| CN116755788A (en) | On-line rule modification method, device, equipment and storage medium | |
| CN110825373A (en) | Dynamic method and device for mobile terminal | |
| CN112579212A (en) | Cross-language calling method, calling party device and called party device | |
| CN115390991A (en) | Virtual machine import and export method, device, equipment and storage medium | |
| CN107092601B (en) | Resource file construction method, resource file application method and device | |
| WO2022099913A1 (en) | Interface configuration method and apparatus, and device and medium | |
| CN110311935A (en) | A kind of sharing method shares deployment system and client | |
| US20220261238A1 (en) | Method and system for deploying third-party application to microcontroller by means of edge assistance |
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 | ||
| EE01 | Entry into force of recordation of patent licensing contract | ||
| EE01 | Entry into force of recordation of patent licensing contract |
Application publication date: 20210101 Assignee: Yidu Lehuo Network Technology Co.,Ltd. Assignor: WUHAN DOUYU YULE NETWORK TECHNOLOGY Co.,Ltd. Contract record no.: X2023980041383 Denomination of invention: Methods, storage media, electronic devices, and systems for separating structured view services Granted publication date: 20220510 License type: Common License Record date: 20230908 |