CN109361948B - Interface management method, intelligent terminal and readable storage medium - Google Patents
Interface management method, intelligent terminal and readable storage medium Download PDFInfo
- Publication number
- CN109361948B CN109361948B CN201811280700.5A CN201811280700A CN109361948B CN 109361948 B CN109361948 B CN 109361948B CN 201811280700 A CN201811280700 A CN 201811280700A CN 109361948 B CN109361948 B CN 109361948B
- Authority
- CN
- China
- Prior art keywords
- page
- view
- instruction
- data
- management method
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/431—Generation of visual interfaces for content selection or interaction; Content or additional data rendering
- H04N21/4312—Generation of visual interfaces for content selection or interaction; Content or additional data rendering involving specific graphical features, e.g. screen layout, special fonts or colors, blinking icons, highlights or animations
- H04N21/4314—Generation of visual interfaces for content selection or interaction; Content or additional data rendering involving specific graphical features, e.g. screen layout, special fonts or colors, blinking icons, highlights or animations for fitting data in a restricted space on the screen, e.g. EPG data in a rectangular grid
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/45—Management operations performed by the client for facilitating the reception of or the interaction with the content or administrating data related to the end-user or to the client device itself, e.g. learning user preferences for recommending movies, resolving scheduling conflicts
- H04N21/458—Scheduling content for creating a personalised stream, e.g. by combining a locally stored advertisement with an incoming stream; Updating operations, e.g. for OS modules ; time-related management operations
- H04N21/4586—Content update operation triggered locally, e.g. by comparing the version of software modules in a DVB carousel to the version stored locally
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The invention discloses an interface management method, an intelligent terminal and a readable storage medium, wherein the interface management method comprises the steps of detecting a page/view display instruction; acquiring page/view data corresponding to the page/view display instruction according to the detected page/view display instruction, and rendering and displaying the page/view data; after the display is complete, page/view data is stored to the stack manager, the page/view including pages/views whose lifecycle is uniformly managed by the native system and pages/views whose lifecycle is not uniformly managed by the native system. According to the invention, the displayed page/view data is stored in the stack manager, the life cycle of the page/view is uniformly managed through the stack manager, and the display and disappearance of the page/view are uniformly controlled by the stack manager, so that the problems that the page/view in various floating windows does not exit and the like in the application can be solved, and the page overlapping problem caused by unfavorable control is further avoided.
Description
Technical Field
The invention relates to the technical field of electronics, in particular to an interface management method, an intelligent terminal and a readable storage medium.
Background
With the popularization of smart televisions, the requirements of the televisions on application diversity are higher and higher, the television is particularly important as a smart television manufacturer to custom develop some built-in applications for users to use, and according to the feedback of market generation sales, the television needs to be built with a built-in application capable of displaying and playing globally, namely, the application is displayed in a floating mode on a scene interface without playing and played in the background, and the television quits the background playing in scenes with playing. The application needs to cover views and pages, however, the android system does not have a scheme for uniformly managing the life cycles of the views and the pages, and the display and disappearance of the pages can be overlapped due to unfavorable management and control in the non-uniform management and control of the life cycles, the pages can not normally disappear, and the like, and particularly the problem that various floating windows in the application can not exit is solved. It becomes especially important to develop a suite of methods that can uniformly manage views and pages.
Disclosure of Invention
The invention mainly aims to provide an interface management method, an intelligent terminal and a readable storage medium, and aims to solve the problem that a page cannot normally disappear due to the fact that the life cycles of a view and the page cannot be unified and managed separately.
In order to achieve the above object, the interface management method provided by the present invention comprises:
detecting a page/view display instruction;
according to the detected page/view display instruction, acquiring page/view data corresponding to the page/view display instruction, and rendering and displaying the page/view data;
after the display is complete, the page/view data is stored to a stack manager, the page/view including pages/views whose lifecycle is uniformly managed by the native system and pages/views whose lifecycle is not uniformly managed by the native system.
Preferably, the first and second electrodes are formed of a metal,
after the step of storing the page/view data to the stack manager after the displaying is completed, the method further includes:
detecting an instruction for returning to a previous layer of page/view;
and acquiring the previous layer page/view data from the stack manager according to the detected instruction for returning to the previous layer page/view, and displaying according to the previous layer page/view data.
Preferably, after the step of storing the page/view data to the stack manager after the displaying is completed, the method includes:
detecting an instruction to return to a top-level page/view;
and acquiring top-level page/view data from a stack manager according to the detected instruction for returning to the top-level page/view, and displaying according to the top-level page/view data.
Preferably, the step of acquiring, according to the detected page/view display instruction, page/view data corresponding to the page/view display instruction, and rendering and displaying the page/view data includes:
searching a root directory corresponding to the page/view display instruction according to the page/view display instruction;
acquiring data of a page/view corresponding to the page/view display instruction from the root directory;
and rendering and displaying the data of the page/view.
Preferably, before the step of detecting a page/view display instruction, the method further includes:
detecting an application service starting instruction, and searching a root directory where the application service is located according to the application service starting instruction;
searching a configuration file corresponding to the application service in the root directory;
and analyzing the configuration file to obtain a data set corresponding to the application service starting instruction, wherein the data set comprises page/view data of the application service.
Preferably, after the step of storing the page/view data to the stack manager after the displaying is completed, the method further includes:
detecting a global exit instruction;
sending a global exit broadcast according to the detected global exit instruction;
and deleting the corresponding page/view data and the page/view being displayed in the stack manager according to the global exit broadcast.
Preferably, the step of deleting the corresponding page/view data and the page/view being displayed in the stack manager according to the global exit broadcast includes:
and searching and deleting the page/view data which is positioned at the top of the stack manager and corresponds to the global exit instruction.
Preferably, the step of deleting the corresponding page/view data and the page/view being displayed in the stack manager according to the global exit broadcast includes:
detecting a window being displayed and judging the type of the window;
if the window is a view, enabling a system process window management tool to delete the view;
and if the window is a page, calling a life cycle management method to delete the page.
In addition, the invention also provides an intelligent terminal which comprises a display, a storage unit, a processing unit and a control program of the interface management method, wherein the control program of the interface management method is stored on the storage unit and can run on a processor, and the interface management method is realized when the processor executes the control program of the interface management method.
In addition, the invention also provides a readable storage medium, wherein a control program is stored on the readable storage medium, and the control program realizes the interface management method when being executed by a processor.
According to the technical scheme, after a display instruction of the page/view is detected, page/view data corresponding to the page/view display instruction is obtained according to the page/view display instruction, the page/view data are rendered and displayed, the page/view data are stored in a stack manager after the display is finished, and the stack manager comprises the page/view with the lifecycle uniformly managed by a native system and the page/view with the lifecycle not uniformly managed by the native system. Through the mode, the displayed page/view data is stored in the stack manager, the life cycle of the page/view is uniformly managed through the stack manager, and the display and disappearance of the page/view are uniformly controlled through the stack manager, so that the problems that the page/view in various floating windows does not exit and the like in application can be solved, and the problem of page overlapping caused by unfavorable control is avoided.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the structures shown in the drawings without creative efforts.
Fig. 1 is a schematic structural diagram of a hardware module of an intelligent terminal according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating an interface management method according to a first embodiment of the present invention;
FIG. 3 is a flowchart illustrating an interface management method according to a second embodiment of the present invention;
FIG. 4 is a flowchart illustrating an interface management method according to a third embodiment of the present invention;
FIG. 5 is a flowchart illustrating an interface management method according to a fourth embodiment of the present invention;
FIG. 6 is a flowchart illustrating an interface management method according to a fifth embodiment of the present invention;
FIG. 7 is a flowchart illustrating an interface management method according to a sixth embodiment of the present invention;
FIG. 8 is a flowchart illustrating an interface management method according to a seventh embodiment of the present invention;
fig. 9 is a flowchart illustrating an interface management method according to an eighth embodiment of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that all the directional indicators (such as up, down, left, right, front, and rear … …) in the embodiment of the present invention are only used to explain the relative position relationship between the components, the movement situation, etc. in a specific posture (as shown in the drawing), and if the specific posture is changed, the directional indicator is changed accordingly.
In addition, the descriptions related to "first", "second", etc. in the present invention are only for descriptive purposes and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present invention, "a plurality" means at least two, e.g., two, three, etc., unless specifically limited otherwise.
In the present invention, unless otherwise expressly stated or limited, the terms "connected," "secured," and the like are to be construed broadly, and for example, "secured" may be a fixed connection, a removable connection, or an integral part; can be mechanically or electrically connected; they may be directly connected or indirectly connected through intervening media, or they may be connected internally or in any other suitable relationship, unless expressly stated otherwise. The specific meanings of the above terms in the present invention can be understood by those skilled in the art according to specific situations.
In addition, the technical solutions in the embodiments of the present invention may be combined with each other, but it must be based on the realization of those skilled in the art, and when the technical solutions are contradictory or cannot be realized, such a combination of technical solutions should not be considered to exist, and is not within the protection scope of the present invention.
The main idea of the embodiment scheme of the invention is as follows: the data after the view/page display of the life cycle is uniformly managed by the native system and the data after the view/page display of the life cycle is not uniformly managed by the native system are stored in the stack manager by self-defining the stack manager, when the page/view needs to be redisplayed, the correspondingly stored page/view data is taken out from the stack manager to display the page/view, and when the hidden page/view needs to be completely deleted, the page/view data in the stack manager is deleted. The display and hiding of the view and page controls are unified by the stack manager through the self-defined stack manager, so that the view and page life cycle in the application is managed in a unified mode, the problems that the view or page cannot disappear and cannot be displayed due to non-unified management and control are solved, and particularly, the management effect on the page/view displayed by the floating window application with the life cycle not managed by the native system is good.
The interface management method according to the embodiment of the present invention is mainly applied to a display device, and the display device may be a Personal Computer (PC), a portable computer, a mobile terminal, a smart television, or other equipment having a processing function.
Referring to fig. 1, fig. 1 is a schematic diagram of a hardware structure of a display device according to an embodiment of the present invention. In this embodiment of the present invention, the display device may include a processor 1001 (e.g., a Central Processing Unit, CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used for realizing connection communication among the components; the user interface 1003 may include a Display (Display), an input unit such as a Keyboard (Keyboard); the network interface 1004 may optionally include a standard wired interface, a WIreless interface (e.g., a WI-FI interface, WI-FI interface); the memory 1005 may be a Random Access Memory (RAM) or a non-volatile memory (non-volatile memory), such as a magnetic disk memory, and the memory 1005 may optionally be a storage device independent of the processor 1001.
Those skilled in the art will appreciate that the hardware configuration depicted in FIG. 1 is not intended to be limiting of the present invention, and may include more or less components than those shown, or some components in combination, or a different arrangement of components.
With continued reference to FIG. 1, the memory 1005 of FIG. 1, which is one type of computer-readable storage medium, may include an operating system, a network communication module, and an interface manager. In fig. 1, the network communication module is mainly used for connecting to a server and performing data communication with the server; and the processor 1001 may call an interface manager stored in the memory 1005.
Based on the hardware structure of the display device, various embodiments of the interface management method of the present invention are provided.
The invention provides an interface management method.
Referring to fig. 2, fig. 2 is a flowchart illustrating an interface management method according to a first embodiment of the present invention. In this embodiment, the interface management method includes the following steps:
step S10, detecting a page/view display instruction;
the interface management method in the embodiment of the invention can be executed by a display device such as a smart television and the like which takes an android system as a native system, the display device comprises a display interface and an input device connected with the display device, a user sends an operation instruction to the display device through the input device and shows an operation result through the display interface, and the input device can be a keyboard, a mouse, a touch screen or a remote controller and the like. When a user issues a display instruction of a page/view to the display apparatus through the input device, the processor 1001 can detect the page/view display instruction in real time and respond accordingly to the detected page/view display instruction. Further, the page/view display instructions may also be display instructions that are automatically initiated by the associated program, such as the display of a floating window, such as an auto-pop-out advertisement.
Step S20, according to the detected page/view display instruction, acquiring page/view data corresponding to the page/view display instruction, and rendering and displaying the page/view data;
after detecting the page/view display instruction, the processor 1001 acquires target page/view data corresponding to the display instruction from the memory 1005 according to the detected page/view, renders the acquired target page/view data, and displays the rendered target page/view data on the display interface. For example, when the display target of the page/view display instruction is a page, when an application program such as a browser receives the display instruction of the page, first, domain name resolution is performed according to a requested URL, and a request is issued to a server, a file (HTML, JS, CSS, image, etc.) is received, then, syntax resolution is performed on a loaded resource, a corresponding internal data structure (such as a DOM tree of the HTML, an (object) attribute table of the JS, a style rule of the CSS, etc.) is established, finally, a rendering tree is established, position calculation, style calculation, etc. are performed on each element, and then, the page is rendered according to the rendering tree.
Step S30, after the display is completed, storing the page/view data to a stack manager, the page/view including a page/view whose lifecycle is uniformly managed by the native system and a page/view whose lifecycle is not uniformly managed by the native system.
And displaying the page/view on the display interface by rendering the page/view data corresponding to the display instruction. After the page/view is displayed on the display interface, the page/view data is stored in the stack manager to be called when the page/view is displayed next time. It should be noted that, at this time, the page/view data stored in the stack manager is a window data type generated by the displayed page/view interface, and the page/view can be quickly displayed by calling the window data type without performing processes such as parsing or rendering the original page/view data. When using the page/view window class data held in the stack manager, the objects to be displayed can be directly instantiated according to the lie replacement principle. All managed page/view objects stored in the stack manager are integrated with a floating window, and the managed objects are unified in a reflection mode. Different types of child object display and hiding perform different operations, dropping objects into the stack manager for each page/view displayed. Meanwhile, the stack manager can store data after the page/view display of the life cycle is uniformly managed by the native system, and can also store data after the page/view display of the life cycle is not uniformly managed by the native system. Taking the android system as an example, the existing android system can only perform unified life cycle management on pages, the management on the life cycle of the view often needs to attach to the corresponding page, but cannot manage the life cycle of the view alone, and then for the floating window application, the native android system cannot manage the life cycle of the view. In the embodiment, the pages/views which are managed by the native system in a unified way or the pages/views which are not managed by the native system are all stored in the stack manager, and the stack manager can realize the unified management of all displayed pages/views.
In the technical solution of this embodiment, after a display instruction of a page/view is detected, page/view data corresponding to the page/view display instruction is obtained according to the page/view display instruction, the page/view data is rendered and displayed, and after the display is completed, the page/view data is stored in a stack manager, where the stack manager can store the data of the page/view whose lifecycle is uniformly managed by a native system and the data of the page/view whose lifecycle is not uniformly managed by the native system. The displayed page/view data is stored in the stack manager, the life cycle of the page/view is managed uniformly through the stack manager, the display and disappearance of the page/view are controlled by the stack manager, the problems that various floating windows do not exit and the like in the application can be solved, the life cycle management can be carried out on the scene of the floating window application of which the life cycle is not managed by the native system, and the problems that the page/view is overlapped and the like caused by unfavorable management and control due to the fact that the page/view which is not managed by the native system is still displayed when the page/view which is managed by the native system exits can be effectively avoided.
Referring to fig. 3, fig. 3 is a flowchart illustrating an interface management method according to a second embodiment of the present invention. Based on the foregoing embodiment shown in fig. 2, in this embodiment, after step S30, the method further includes:
step S40, detecting an instruction for returning to the previous layer of page/view;
and after the display device displays the current page/view, detecting an operation instruction of the current page/view in real time. The operation instructions for the current page/view comprise an operation instruction for returning to the previous page/view, an operation instruction for opening the next page/view, an operation instruction for returning to a specific page/view and an operation instruction for exiting the global state. When the display device detects a certain type of operation instruction, the operation related to the operation instruction is executed. When the display device detects an instruction of returning to a page/view on the previous layer of the current page/view, the display device further judges whether the current page/view instruction is a top-level page/view, and if the current page/view is the top-level page/view, the processor sends an operation instruction of exiting the global application service. If the current page/view is not the top level page/view, the page/view data at the layer above the current page/view is searched from the stack manager.
Step S50, acquiring the previous page/view data from the stack manager according to the detected instruction for returning to the previous page/view, and displaying according to the previous page/view data.
After detecting the instruction to return to the previous page/view, the processor 1001 acquires the previous page/view data from the stack manager according to the detected instruction to return to the previous page/view, and displays the previous page/view in the form of a window. Because the previous page/view data is stored in the stack management in the window type data, the previous page/view can be directly displayed according to the data of the previous page/view, and the processes of parsing and rendering are not needed. It should be noted that, when the previous page/view enters the next page/view, the previous page/view data is stored in the restack manager, and the previous page/view is hidden in the background operation state, when the previous page/view is opened again, the previous page/view is placed in the front end for display, and the background operation is closed.
In the computer field, a stack is a data structure in which data items are arranged in order, and when a stack manager holds data in a stack manner, the data items can be inserted or deleted at one end (stack top), and the characteristics are as follows: the last object put into the stack is always taken out first, i.e. last in first out queue. First-in data is placed at the bottom of the stack (low address), last-out data is placed at the top of the stack (high address), and first-out data is at the top of the stack (high address). When the upper page/view is needed to be opened, the data of the current page/view is removed from the top of the stack, the data of the upper page/view is acquired, and the upper page/view is displayed.
Referring to fig. 4, fig. 4 is a flowchart illustrating an interface management method according to a third embodiment of the present invention. Based on the foregoing embodiment shown in fig. 2, in this embodiment, after step S30, the method further includes:
step S41, detecting an instruction for returning to the top page/view;
step S51, acquiring top-level page/view data from the stack manager according to the detected instruction for returning to the top-level page/view, and displaying according to the top-level page/view data.
And after the display device displays the current page/view, detecting an operation instruction of the current page/view in real time. When the display device detects an instruction to return to the top page/view, the processor 1001 preferably retrieves the top page/view data at the bottom of the stack (top of the stack) of the stack manager from the stack manager layer by layer pop (removing) the data at the top of the stack until the data of the second page/view is removed from the stack manager, and displays it on the display interface in the form of a window. In other embodiments, the stack manager may also save data in a heap manner, where the order of storage and entry into and out of the stack manager is arbitrary, i.e., there is no first-in-last-out or first-in-first-out rule for the heap. At this time, when the processor 1001 detects an instruction to return to the top-level top page/view, the data address of the top-level page/view is acquired according to the instruction of the top-level page/view, and the data of the top-level page/view is acquired by looking up the address to display the top-level page/view.
Referring to fig. 5, fig. 5 is a flowchart illustrating an interface management method according to a fourth embodiment of the present invention. Based on the above-mentioned embodiment shown in fig. 2, in this embodiment, step S20 includes:
step S21, according to the page/view display instruction, searching the root directory corresponding to the page/view display instruction;
step S22, obtaining data of the page/view corresponding to the page/view display instruction from the root directory;
and step S23, rendering and displaying the data of the page/view.
When the display instruction of the page/view is detected, the root directory corresponding to the page/view display instruction is searched according to the page/view display instruction, the data of the page/view corresponding to the page/view display instruction is obtained from the root directory, and the page/view data is rendered and displayed on the display interface in a window mode. Specifically, after a page/view display instruction is detected, target page/view original data are downloaded through a network, the target page/view original data are decompressed to a root directory of a current application, a json file of a display layout in the decompressed directory is found, and the parsed data are stored in a json object. And simultaneously searching a resource folder with the same name of the function item, such as WholeEcologyHDRDoly which represents the name of the function TAG and also represents the name of a file resource packet corresponding to the function, loading the data and the resource to a corresponding page and forming the page/view to be displayed through rendering. Or the data of each page/view is already stored in the root directory, and the data and the resources are loaded to the corresponding page through the data of each page/view and the resource folder with the same name of the function item, and the page/view to be displayed is formed through rendering.
It can be understood that, when the page/view display instruction is detected, the page/view data corresponding to the page/view display instruction may be first searched from the stack management, and if the page/view data corresponding to the page/view display instruction cannot be found from the stack management, the root directory of the page/view corresponding to the page/view display instruction is searched, and the page/view data is obtained from the root directory.
Referring to fig. 6, fig. 6 is a flowchart illustrating an interface management method according to a fifth embodiment of the present invention. Based on the foregoing embodiment shown in fig. 2, in this embodiment, step S10 further includes:
step S01, detecting an application service starting instruction, and searching a root directory where the application service is located according to the application service starting instruction;
step S02, searching the configuration file corresponding to the application service in the root directory;
step S03, parsing the configuration file to obtain a data set corresponding to the application service start instruction, where the data set includes page/view data of the application service.
The page/view exists based on the application service, and before the page/view is displayed, the corresponding application service needs to be started. When the processor 1001 detects an application service start instruction, it searches for a root directory corresponding to the application service, and searches for a corresponding page configuration file from the root directory. And analyzing the page configuration file to obtain a data set corresponding to the application service, wherein the data set comprises each page/view data of the application service. An application service is installed in a system in advance through a network, and a root directory corresponding to the application service is generated, and the root directory stores information such as a storage directory of each resource file corresponding to the application service, a storage directory of a configuration file of local information, and a configured root description file. When the page/view display is needed, acquiring data corresponding to the page/view from the application service, and rendering and displaying the page/view data so as to display the page/view in a window form on the display interface.
Referring to fig. 7, fig. 7 is a flowchart illustrating an interface management method according to a sixth embodiment of the present invention. Based on the foregoing embodiment shown in fig. 2, in this embodiment, after step S30, the method further includes:
step S60, detecting a global exit instruction;
step S70, sending a global exit broadcast according to the detected global exit instruction;
step S80, deleting the corresponding page/view data and the page/view being displayed in the stack manager according to the global exit broadcast.
The global exit instruction may be an instruction to exit a certain application service, or may be an instruction to exit all running application services. When the global exit instruction is detected, the target application service corresponding to the global exit instruction is judged, a global exit broadcast is sent to the window control module, the window control module identifies the application service needing global exit according to the global exit broadcast, and deletes the displayed page/view corresponding to the application service and hides the page/view running in the background. According to the embodiment, the display and disappearance of the page/view can be managed through the stack manager, the display objects in the stack manager can be cleaned uniformly, and the problem that the floating window type window does not exit in the life cycle which is not managed by the native system can be effectively solved. And the quick exit of the floating window application can be simplified by setting a shortcut key.
Referring to fig. 8, fig. 8 is a flowchart illustrating an interface management method according to a seventh embodiment of the present invention. Based on the above-mentioned embodiment shown in fig. 7, in this embodiment, the step S80 includes:
step S81, searching and deleting the page/view data corresponding to the global exit instruction and positioned at the top of the stack manager;
and step S82, deleting the page/view which is displayed and corresponds to the global exit instruction.
When the application program runs, a certain memory is applied to be allocated to the stack manager, and different application programs have different memory intervals in the stack manager. When a global quit instruction is detected, a global quit broadcast is sent to the window management and control module, the window management and control module identifies the application service needing global quit, and then the page/view data set of the application service needing global quit is found out from the stack manager.
When the page/view data set of the application service needing global exit is found, the page/view data set of the application service needing global exit is stored in a certain memory interval in the stack manager. And circularly removing the page/view data at the top of the stack in the target memory interval until all the page/view data corresponding to the global exit instruction are removed.
Referring to fig. 9, fig. 9 is a flowchart illustrating an interface management method according to an eighth embodiment of the present invention. Based on the above-mentioned embodiment shown in fig. 8, in this embodiment, the step S82 includes:
step S821 of detecting a window being displayed and determining a type of the window;
step S822, if the window is a view, enabling a system process window management tool to delete the view;
in step S823, if the window is a page, the life cycle management method is invoked to delete the page.
For the page/view being displayed, a system function can be called to delete the page/view being displayed, for the view window, a system process window management tool (such as a windows manager) is started to delete the view, and for the page window, a life cycle management method (such as a finish () method) is called to delete the page. Specifically, when receiving the global quit instruction, the window management and control module deletes the page/view which is being displayed on the display interface and corresponds to the application service which needs to quit the global. And when the window type is a page, the window management and control module calls a finish () method to delete the page from the display interface. Therefore, the deletion of the page/view which runs in the background and the page/view which is displayed at the front end is realized, the purpose of uniformly managing the display and the disappearance of the page/view is achieved, the display objects in all stack managers can be uniformly cleaned, and the problems that various floating windows cannot exit and the like in application are solved.
In addition, the present invention further provides an intelligent terminal, which includes a display, a memory 1005, a processor 1001, and a control program of an interface management method stored in the memory and operable on the processor, where the processor implements the following steps when executing the control program of the interface management method:
step S10, detecting a page/view display instruction;
step S20, according to the detected page/view display instruction, acquiring page/view data corresponding to the page/view display instruction, and rendering and displaying the page/view data;
step S30, after the display is completed, storing the page/view data to a stack manager, the page/view including a page/view whose lifecycle is uniformly managed by the native system and a page/view whose lifecycle is not uniformly managed by the native system.
In the technical solution of this embodiment, after a display instruction of a page/view is detected, according to the page/view display instruction, page/view data corresponding to the page/view display instruction is acquired, the page/view data is rendered and displayed, and after the display is completed, the page/view data is stored in a stack manager, where the page/view includes a page/view whose lifecycle is uniformly managed by a native system and a page/view whose lifecycle is not uniformly managed by the native system. The displayed page/view data is stored in the stack manager, the life cycle of the page/view is managed uniformly through the stack manager, the display and disappearance of the page/view are controlled by the stack manager, the problems that various floating windows do not exit and the like in the application can be solved, the life cycle management can be carried out on the scene of the floating window application of which the life cycle is not managed by the native system, and the problems that the page/view is overlapped and the like caused by unfavorable management and control due to the fact that the page/view which is not managed by the native system is still displayed when the page/view which is managed by the native system exits can be effectively avoided.
Further, step S30 is followed by:
step S40, detecting an instruction for returning to the previous layer of page/view;
step S50, acquiring the previous page/view data from the stack manager according to the detected instruction for returning to the previous page/view, and displaying according to the previous page/view data.
Further, step S30 may be followed by:
step S41, detecting an instruction for returning to the top page/view;
step S51, acquiring top-level page/view data from the stack manager according to the detected instruction for returning to the top-level page/view, and displaying according to the top-level page/view data.
Further, step S20 includes:
step S21, according to the page/view display instruction, searching the root directory corresponding to the page/view display instruction;
step S22, obtaining data of the page/view corresponding to the page/view display instruction from the root directory;
and step S23, rendering and displaying the data of the page/view.
Further, step S10 is preceded by:
step S01, detecting an application service starting instruction, and searching a root directory where the application service is located according to the application service starting instruction;
step S02, searching the configuration file corresponding to the application service in the root directory;
step S03, parsing the configuration file to obtain a data set corresponding to the application service start instruction, where the data set includes page/view data of the application service.
Further, step S30 is followed by:
step S60, detecting a global exit instruction;
step S70, sending a global exit broadcast according to the detected global exit instruction;
step S80, deleting the corresponding page/view data and the page/view being displayed in the stack manager according to the global exit broadcast.
Further, step S80 includes:
step S81, searching and deleting the page/view data corresponding to the global exit instruction and positioned at the top of the stack manager;
and step S82, deleting the page/view which is displayed and corresponds to the global exit instruction.
Further, step S82 further includes:
step S821 of detecting a window being displayed and determining a type of the window;
step S822, if the window is a view, enabling a system process window management tool to delete the view;
in step S823, if the window is a page, the life cycle management method is invoked to delete the page.
By the technical scheme, the deletion of the page/view which runs at the background and the page/view which is displayed at the front end is hidden, the purpose of uniformly managing the display and disappearance of the page/view is achieved, the display objects in all stack managers can be uniformly cleaned, and the problems that various floating windows cannot exit and the like in application are solved.
The invention also provides a readable storage medium having stored thereon a computer program which, when executed by a processing unit, implements an interface management method as described above.
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, CD-ROM, 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.
It should be noted that in the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention, and all modifications and equivalents of the present invention, which are made by the contents of the present specification and the accompanying drawings, or directly/indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (9)
1. An interface management method, characterized in that the interface management method comprises:
detecting a page/view display instruction;
according to the detected page/view display instruction, acquiring page/view data corresponding to the page/view display instruction, and rendering and displaying the page/view data;
after the display is completed, storing the page/view data to a stack manager, the page/view comprising pages/views whose lifecycle is uniformly managed by the native system and pages/views whose lifecycle is not uniformly managed by the native system; the page/view data in the stack manager is a Windows data type generated by a displayed page/view interface;
after the step of storing the page/view data to the stack manager after the displaying is completed, the method further includes:
detecting a global exit instruction;
sending a global exit broadcast according to the detected global exit instruction;
and deleting the corresponding page/view data and the page/view being displayed in the stack manager according to the global exit broadcast.
2. The interface management method of claim 1, wherein after the step of storing the page/view data to a stack manager after the displaying is complete, further comprising:
detecting an instruction for returning to a previous layer of page/view;
and acquiring the previous layer page/view data from the stack manager according to the detected instruction for returning to the previous layer page/view, and displaying according to the previous layer page/view data.
3. The interface management method of claim 1, wherein said step of storing said page/view data to a stack manager after display is complete, comprises:
detecting an instruction to return to a top-level page/view;
and acquiring top-level page/view data from a stack manager according to the detected instruction for returning to the top-level page/view, and displaying according to the top-level page/view data.
4. The interface management method according to any one of claims 1 to 3, wherein the step of acquiring, rendering and displaying the page/view data corresponding to the page/view display instruction according to the detected page/view display instruction includes:
searching a root directory corresponding to the page/view display instruction according to the page/view display instruction;
acquiring data of a page/view corresponding to the page/view display instruction from the root directory;
and rendering and displaying the data of the page/view.
5. The interface management method according to claim 4, wherein said step of detecting a page/view display instruction is preceded by the step of:
detecting an application service starting instruction, and searching a root directory where the application service is located according to the application service starting instruction;
searching a configuration file corresponding to the application service in the root directory;
and analyzing the configuration file to obtain a data set corresponding to the application service starting instruction, wherein the data set comprises page/view data of the application service.
6. The interface management method according to claim 1, wherein the step of deleting the corresponding page/view data and the page/view being displayed located in the stack manager according to the global exit broadcast comprises:
and searching and deleting the page/view data which is positioned at the top of the stack manager and corresponds to the global exit instruction.
7. The interface management method according to claim 1, wherein the step of deleting the corresponding page/view data and the page/view being displayed located in the stack manager according to the global exit broadcast further comprises:
detecting a window being displayed and judging the type of the window;
if the window is a view, enabling a system process window management tool to delete the view;
and if the window is a page, calling a life cycle management method to delete the page.
8. An intelligent terminal, comprising a display, a storage unit, a processing unit, and a control program of an interface management method stored on the storage unit and operable on a processor, wherein the processor implements the interface management method according to any one of claims 1 to 7 when executing the control program of the interface management method.
9. A readable storage medium on which a control program is stored, the control program, when executed by a processor, implementing the interface management method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811280700.5A CN109361948B (en) | 2018-10-30 | 2018-10-30 | Interface management method, intelligent terminal and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811280700.5A CN109361948B (en) | 2018-10-30 | 2018-10-30 | Interface management method, intelligent terminal and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109361948A CN109361948A (en) | 2019-02-19 |
| CN109361948B true CN109361948B (en) | 2021-11-09 |
Family
ID=65347245
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811280700.5A Active CN109361948B (en) | 2018-10-30 | 2018-10-30 | Interface management method, intelligent terminal and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109361948B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110162303A (en) * | 2019-04-26 | 2019-08-23 | 深圳智链物联科技有限公司 | A kind of Pagination Display method, system and terminal device |
| CN113395365B (en) * | 2020-03-12 | 2022-11-15 | 中国移动通信集团山东有限公司 | Method and device for integrating view of micro-service system, computer equipment and storage medium |
| CN111901686B (en) * | 2020-08-03 | 2022-04-08 | 海信视像科技股份有限公司 | Method for keeping normal display of user interface stack and display equipment |
| CN111857938A (en) * | 2020-08-05 | 2020-10-30 | 广州繁星互娱信息科技有限公司 | Management method and device of popup view, terminal and storage medium |
| CN116048646B (en) * | 2022-07-01 | 2024-05-10 | 荣耀终端有限公司 | Process processing method and electronic equipment |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103279349A (en) * | 2013-05-31 | 2013-09-04 | 正益无线（北京）科技有限公司 | Mobile phone or PDA multi-window browsing system based on moving middleware |
| CN105573835A (en) * | 2015-12-22 | 2016-05-11 | 网易（杭州）网络有限公司 | Interface combined management system and method as well as terminal |
| CN106293584A (en) * | 2016-08-05 | 2017-01-04 | 深圳市金立通信设备有限公司 | A kind of double-screen display method and terminal |
| CN106708498A (en) * | 2015-11-18 | 2017-05-24 | 中兴通讯股份有限公司 | Terminal for realizing multi-mode application page, method and system |
| CN107506200A (en) * | 2017-09-12 | 2017-12-22 | 深圳市金立通信设备有限公司 | A kind of screen content switching method, terminal and computer-readable recording medium |
| CN107609199A (en) * | 2017-10-24 | 2018-01-19 | 网易无尾熊（杭州）科技有限公司 | A kind of method, equipment and storage medium for handling and recovering the page |
| CN108134812A (en) * | 2017-11-10 | 2018-06-08 | 人人行科技股份有限公司 | Data processing method and device |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5455951A (en) * | 1993-07-19 | 1995-10-03 | Taligent, Inc. | Method and apparatus for running an object-oriented program on a host computer with a procedural operating system |
| US7761900B2 (en) * | 2006-08-02 | 2010-07-20 | Clarendon Foundation, Inc. | Distribution of content and advertisement |
| JP2015114799A (en) * | 2013-12-11 | 2015-06-22 | キヤノン株式会社 | Information processing device, control method, program, and storage medium |
-
2018
- 2018-10-30 CN CN201811280700.5A patent/CN109361948B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103279349A (en) * | 2013-05-31 | 2013-09-04 | 正益无线（北京）科技有限公司 | Mobile phone or PDA multi-window browsing system based on moving middleware |
| CN106708498A (en) * | 2015-11-18 | 2017-05-24 | 中兴通讯股份有限公司 | Terminal for realizing multi-mode application page, method and system |
| CN105573835A (en) * | 2015-12-22 | 2016-05-11 | 网易（杭州）网络有限公司 | Interface combined management system and method as well as terminal |
| CN106293584A (en) * | 2016-08-05 | 2017-01-04 | 深圳市金立通信设备有限公司 | A kind of double-screen display method and terminal |
| CN107506200A (en) * | 2017-09-12 | 2017-12-22 | 深圳市金立通信设备有限公司 | A kind of screen content switching method, terminal and computer-readable recording medium |
| CN107609199A (en) * | 2017-10-24 | 2018-01-19 | 网易无尾熊（杭州）科技有限公司 | A kind of method, equipment and storage medium for handling and recovering the page |
| CN108134812A (en) * | 2017-11-10 | 2018-06-08 | 人人行科技股份有限公司 | Data processing method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109361948A (en) | 2019-02-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109361948B (en) | Interface management method, intelligent terminal and readable storage medium | |
| US11175968B2 (en) | Embedding an interface of one application into an interface of another application | |
| US9846699B2 (en) | System and methods thereof for dynamically updating the contents of a folder on a device | |
| EP3657358A1 (en) | Method, device and system for persistent data processing, and readable storage medium | |
| RU2611988C2 (en) | Icon display method and device | |
| CN110020325B (en) | Page loading method, device, equipment and readable storage medium | |
| CN108228293B (en) | Interface skin switching method and device | |
| US20150317059A1 (en) | Application management method for a mobile terminal and the mobile terminal | |
| CN107045546B (en) | Webpage processing method and device and intelligent terminal | |
| CN112836074B (en) | Wallpaper display method and equipment | |
| CN105955770A (en) | Application program uninstalling method and terminal | |
| CN115309470B (en) | Method, device, equipment and storage medium for loading widget | |
| CN112948844A (en) | Control method and device and electronic equipment | |
| CN104182266B (en) | A kind of application installation method and device | |
| CN111158788A (en) | Desktop starter control method and device and storage medium | |
| CN104731897A (en) | Method and device for achieving information displaying | |
| CN112148395A (en) | Page display method, device, equipment and storage medium | |
| CN108304169B (en) | Implementation method, device and equipment for HTML5 application | |
| CN109840113B (en) | Application data processing method and equipment, storage medium and terminal thereof | |
| CN108572985B (en) | Page display method and device | |
| CN106302821B (en) | Data request method and equipment thereof | |
| CN112966201B (en) | Object processing method, device, electronic equipment and storage medium | |
| CN107301089B (en) | APP deployment and calling method and terminal | |
| CN110622135B (en) | System and method for providing content items in situations involving suboptimal network conditions | |
| CN109032728B (en) | UI (user interface) display method, intelligent terminal and computer-readable storage medium |
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 |