[go: up one dir, main page]

WO2017084497A1 - Terminal, procédé et système permettant de réaliser une page d'application multimode - Google Patents

Terminal, procédé et système permettant de réaliser une page d'application multimode Download PDF

Info

Publication number
WO2017084497A1
WO2017084497A1 PCT/CN2016/104380 CN2016104380W WO2017084497A1 WO 2017084497 A1 WO2017084497 A1 WO 2017084497A1 CN 2016104380 W CN2016104380 W CN 2016104380W WO 2017084497 A1 WO2017084497 A1 WO 2017084497A1
Authority
WO
WIPO (PCT)
Prior art keywords
window
application page
corresponding mode
terminal
class
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2016/104380
Other languages
English (en)
Chinese (zh)
Inventor
涂成义
朱兴昌
孔建华
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Publication of WO2017084497A1 publication Critical patent/WO2017084497A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/957—Browsing optimisation, e.g. caching or content distillation
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/451—Execution arrangements for user interfaces

Definitions

  • the present invention relates to a terminal, a method and system for implementing an application page, and particularly to a terminal, method and system for implementing a multi-mode application page.
  • the invention provides a terminal, a method and a system for implementing a multi-mode application page, so as to solve the problem that the user experience is poor, the application development efficiency is not high, and the application development efficiency is not high, such as the use of the native application page, the web application page or the hybrid application page in the related art. problem.
  • a method for implementing a multi-mode application page comprising: selecting a step, selecting an application page class of a corresponding mode according to different scenarios of the terminal; Steps: controlling an application page class of the corresponding mode to obtain a window handle to form a window object; and displaying a step of: controlling the window object to display an application page of the corresponding mode.
  • the selecting step further includes: determining, by using an XML plug-in, different scenarios of the terminal and selecting an application page class of the corresponding mode.
  • the method further includes: an inheriting step, and controlling an application page class of the corresponding mode to inherit a window subclass of the corresponding mode.
  • the method further includes: determining, determining, by the window pool, whether the number of the window handles has reached a preset maximum value, if the number of the window handles allocated by the window pool is not up to Setting the maximum value, performing the obtaining step; and releasing the step, if the number of the window handles allocated by the window pool reaches a preset maximum value, controlling the window pool to release the window object.
  • the method further includes: a recycling step, when the display of the application page ends, the control window pool reclaims the window handle.
  • a terminal comprising a memory and a processor, wherein the memory stores program instructions, and the processor processes the program instructions to perform the following steps: Selecting an application page class of the corresponding mode in the different scenarios of the terminal; acquiring the step, controlling the application page class of the corresponding mode to obtain a window handle, forming a window object; and displaying the step of: controlling the window object to display the application page of the corresponding mode .
  • the selecting step further comprises determining, by using an XML plugin, different scenarios of the terminal and selecting an application page class of the corresponding mode.
  • the processor further performs an inheritance step before the performing the obtaining step, and the application page class that controls the corresponding mode inherits the window subclass of the corresponding mode.
  • the processor further includes: a determining step of determining, by the processor, whether the number of the window handles allocated by the window pool has reached a preset maximum value, if the window is allocated by the window pool If the number of handles does not reach a preset maximum value, the obtaining step is performed; and the releasing step, if the number of the window handles allocated by the window pool reaches a preset maximum value, controlling the window pool to release the window object .
  • the processor further performs: a recycling step after the displaying step, when the display of the application page ends, the control window pool reclaims the window handle.
  • a system for implementing a multi-mode application page is provided, the system is applied to a terminal, and the system includes: a selection module, configured to select an application page of a corresponding mode according to different scenarios of the terminal. a class; an acquisition module, an application page class configured to control the corresponding mode to obtain a window handle, forming a window object; and a display module configured to control the window object to display the application page of the corresponding mode.
  • the selecting module further includes: determining, by using an XML plug-in, different scenarios of the terminal and selecting an application page class of the corresponding mode.
  • system further includes: an inheritance module, where the application page class that is configured to control the corresponding mode inherits a window subclass of the corresponding mode.
  • the system further includes: a determining module, configured to determine whether the number of the window handles allocated by the window pool has reached a preset maximum value, if the preset maximum value is not reached, And the obtaining, by the obtaining module, the application page class acquiring the window handle of the corresponding mode to instantiate, forming a window object; and releasing the module, if the number of the window handles allocated by the window pool reaches a preset maximum value Controlling the window pool to release the window object.
  • a determining module configured to determine whether the number of the window handles allocated by the window pool has reached a preset maximum value, if the preset maximum value is not reached, And the obtaining, by the obtaining module, the application page class acquiring the window handle of the corresponding mode to instantiate, forming a window object; and releasing the module, if the number of the window handles allocated by the window pool reaches a preset maximum value Controlling the window pool to release the window object.
  • system further includes: a recycling module, configured to: when the display of the application page ends, the control window pool reclaims the window handle.
  • a recycling module configured to: when the display of the application page ends, the control window pool reclaims the window handle.
  • Another embodiment of the present invention provides a computer storage medium storing execution instructions for performing the method in the above embodiments.
  • the application page of the corresponding mode is flexibly selected for display, thereby realizing a multi-mode application page, which not only improves the efficiency of application development, but also develops a multi-mode application. Adapting to different scenarios greatly enhances the user experience.
  • FIG. 1 is a schematic diagram showing the display of a native application page in the prior art
  • FIG. 2 is a schematic diagram showing display of a webpage application page in the prior art
  • FIG. 3 is a schematic diagram showing a preferred embodiment of a hybrid application page of the present invention.
  • FIG. 4 is a functional block diagram of a preferred embodiment of a system for implementing a multi-mode application page
  • FIG. 5 is a schematic structural diagram of a preferred embodiment of a method for implementing a multi-mode application page according to the present invention.
  • FIG. 6 is a block diagram of a preferred embodiment of a window class employed by a method of implementing a multi-mode application page of the present invention
  • FIG. 7 is a flow chart of a method of a preferred embodiment of a method for implementing a multi-mode application page of the present invention.
  • FIG. 8 is a flowchart of a method of another preferred embodiment of a method for implementing a multi-mode application page according to the present invention.
  • FIG. 9 is a flow chart of a method for recycling a window handle in a method for implementing a multi-mode application page in accordance with the present invention.
  • FIG. 1 is a schematic diagram showing a native application page 10 displayed on the terminal 1 in the prior art.
  • the Native App page 10 refers to an application page generated using a native component.
  • the terminal 1 can be a mobile phone, a computer, a television, or the like.
  • the display screen of the native application page 10 includes “title”, “content”, “tag” and the like (as shown in FIG. 1 ).
  • the native application page 10 is developed based on the native component, and the displayed native application page 10 has good adaptability to the terminal 1 and the operation is smooth, but the development efficiency of the native application page 10 is low and the cost is high, and the portability is relatively high. difference.
  • the web application page 20 refers to an application page generated by using a web view component.
  • the display interface of the native application page 20 includes a “title”, a “content”, a “tag”, and the like (as shown in FIG. 2 ).
  • the page view component loading page is invoked.
  • the web application is based on HyperText Markup Language 5 (HTML 5). It has strong portability and high development efficiency. However, the rendering capability of the web view component is worse than that of the native component, and different operating system and device performance also affect the webpage. An important factor in the performance of the view component, therefore, the web application page 20 generated using only the web page view component has a poor user experience.
  • the Hybrid App page 30 refers to an application page generated by both the native application component and the web page view component.
  • the hybrid application page 30 uses both the native component and the webpage view component, and through the analysis of the application page, the components with high experience requirements and complex animation effects are implemented by the original components, and the requirements are lower, and the layout is lower. Complex pages are implemented using the web view component.
  • three layouts can be applied to the hybrid application page 30, which refers to the components and data on the application page. The three layouts are as follows: The first one is based on native components, and the web view component is embedded in the application page.
  • This layout method is suitable for business function logic.
  • the functional modules with more complex logic are developed by web page view components, so that they can be used in various terminal applications.
  • a function module for ordering a movie needs to obtain price, payment means, input password and confirm payment success.
  • These processes involve the processing of interactions between multiple systems and functional modules.
  • the business functions are logically complex, and are developed using web page view components, so that the functional modules are portable, and one system can be compatible with multiple systems.
  • web pages are used.
  • the view component is dominated and the native component floats on the layout.
  • This layout is suitable for components that cannot be implemented using the web view component. It needs to be implemented with native components such as player components, camera components, and so on.
  • Third, the native component and the web view component are scattered.
  • the third type is suitable for the case where the hybrid application page 30 is complicated. For example, the need to enable multiple web page view components to generate the hybrid application page 30 is likely to cause display anomalies and less application scenarios.
  • FIG. 4 is a functional model of a preferred embodiment of a system for implementing a multi-mode application page of the present invention Block diagram. As shown in the above three modes of application pages shown in FIG. 1, FIG. 2 and FIG. 3, FIG. 4 is a description of a system for implementing the application pages of the three modes.
  • the system 4 implementing a multi-mode application page includes one or more modules on which the system is installed. In this embodiment, the one or more modules include: a selection module 40, an obtaining module 41, a display module 42, an inheritance module 43, a determining module 44, a releasing module 45, and a recycling module 46, wherein the multi-mode application page is implemented.
  • the system 4 also includes a processor 47 and a memory 48.
  • a module as referred to in the present invention refers to a series of computer program segments that are executed by a processor of a terminal and perform certain technical functions, which are stored in the memory 48, and the processor 47 executes the computer program segments.
  • the selection module 40 is configured to select an application page class 51 of the corresponding mode according to different scenarios of the terminal 1 (as shown in FIG. 5).
  • the different scenarios may include: different operating systems of the terminal 1, different versions of the operating system, different screen resolutions, and the like.
  • the application page class 51 of the corresponding mode refers to one of three types of application page classes of a native application page class, a webpage application page class, and a hybrid application page class corresponding to different scenarios.
  • the obtaining module 41 is configured to control the application page class 51 of the corresponding mode to obtain the window handle 520 to form the window object 53.
  • the window handle 520 is obtained from the window pool 52 (as shown in FIG. 5), and the application page class 51 of the corresponding mode acquires the window handle 520 and instantiates it to form the window object 53.
  • the display module 42 is configured to control the window object 53 to display an application page of the corresponding mode.
  • the selection module 40 needs to select the application page class 51 of the corresponding mode.
  • the scene of the above application page and the selectable corresponding mode application page class 51 can be set as:
  • Scenario 1 The application page class 51 of the corresponding mode is selected according to different operating systems. If the terminal 1 is an open source terminal operating system, the selection module 40 selects a native application page class; for a closed terminal operating system, the selection module 40 selects a hybrid application page class.
  • Scenario 2 Select the application page of the corresponding mode according to different system versions of the same operating system. Class 51. For example, the version before Android 4.0 has poor compatibility with the web view component, so the selection module 40 selects the native application page class; in the version after Android 4.0, the selection module 40 selects the web application page class.
  • Scenario 3 The application page class 51 of the corresponding mode is selected according to different terminal 1 having different screen aspect ratios. For a terminal having a large screen aspect ratio, the selection module 40 selects a hybrid application page class; for a terminal having a small aspect ratio, the selection module 40 selects a web application page class.
  • the scene determination and selection of the terminal 1 by the selection module 40 can be implemented by an Extensible Markup Language (XML) (hereinafter referred to as XML) plug-in 50 (as shown in FIG. 5).
  • XML Extensible Markup Language
  • the XML plug-in 50 realizes the application page class 51 corresponding to the corresponding mode by judging the different scenarios of the terminal 1, avoiding hard coding, improving the flexibility of application on the terminal 1, and facilitating maintenance of the version.
  • An XML plugin 50 of an application page class 51 that selects a corresponding mode according to different scenarios has the following format:
  • Each application page corresponds to a pages configuration item, the pages are the parent tags of the page, the pages include a plurality of page sub-tabs, and each page tag represents a condition for selecting the application page class 51 of the corresponding mode.
  • the key indicates the unique identifier of the application page. When opening the application page, only the identifier needs to be specified. Page check is the condition for judging the scene. The operating system, version, screen aspect ratio, etc. of the terminal 1. If the default is default, it means that the judgment condition cannot be matched. By default, the web application page class (homeWebwindow) is selected, and the value indicates the package path of the application page class 51 of the corresponding mode.
  • the application page class 51 of the corresponding mode is a collection of data and operation functions related to the application page.
  • the native application page class can implement an interface of a native component, and the native component can be a layout class, a text class, or a picture class component.
  • the web application page class can implement the interface of the web view component, and the implementable functions in the web view component include getUrl(), loadUrl(), etc., and the hybrid application page class needs to implement the interface of the native component and the interface of the webpage view component at the same time. .
  • the obtaining module 41 controls the application page class 51 of the corresponding mode to obtain the window handle 520, and forms a window object 53, and the display module 42 finally applies the native application page 10 and the webpage application.
  • Page 20 or hybrid application page 30 is displayed to the user.
  • the inheritance module 43 is configured to inherit the window subclass of the corresponding mode from the application page class 51 of the corresponding mode.
  • the window subclass of the corresponding schema inherits the window class that encapsulates the underlying public method functions.
  • the application page class 51 of the corresponding mode is instantiated by the acquisition module 41 to obtain the window handle 520. Before the window object 53 is formed, the window object 53 may be further included.
  • the application page class 51 of the corresponding mode inherits the window subclass of the corresponding mode, and the window subclass of the corresponding mode inherits the window class 60 (shown in FIG. 6) that encapsulates the underlying common method function.
  • the window class 60 uniformly encapsulates the underlying public method functions, preferably including functions that call transition animations, functions that manage the history stack, and functions that control the lifecycle of the window class.
  • the function that calls the transition animation is used to implement the animation effect of the application page switching in the application page transition.
  • the function of managing the history stack is used to save and destroy the browsed page, and the control window class life cycle function is used for management. Creation, start, stop, and destruction of window classes.
  • the window class 60 derives three window subclasses, which are a native application window subclass, a web application window subclass, and a hybrid application window subclass, and the native application page class, the web application page class, and the hybrid application page class respectively inherit the above native application.
  • Window subclass web application window subclass, mixed application window subclass.
  • the native application window subclass can implement the interface of the native component, and the native component can be a layout class, a text class, a picture class component, etc., the webpage should The interface of the web view component can be implemented by using the window subclass.
  • the implementable functions in the web view component include getUrl(), loadUrl(), etc., and the hybrid application window subclass needs to implement the interface of the native component and the interface of the webpage view component at the same time.
  • the application page class of the corresponding mode respectively inherits the corresponding window class subclass, so that the application page class of the mode only needs to implement specific layout and business logic without paying attention to the underlying basic functional part.
  • the separate architecture reduces the coupling of functional modules and improves development efficiency.
  • the determining module 44 is configured to determine whether the number of window handles 520 allocated by the window pool 52 has reached a preset maximum value.
  • the preset maximum value refers to a certain rule may be set to determine the number of window handles 520 when the window pool 52 is initially managed.
  • the set rule is the maximum number rule, i.e., the number of window handles 520 that have a maximum value preset in the window pool 52.
  • the maximum number rule can limit the unlimited growth of the window object 53, ensuring management and optimization of the memory of the terminal 1.
  • the obtaining module 41 controls the application page class 51 of the corresponding mode to obtain the window handle 520 in the window pool 52 to be instantiated, forming the window object 53, and displaying Module 42 ultimately displays the native application page 10, web application page 20, or hybrid application page 30 to the user.
  • the release module 45 is arranged to control the window pool 52 to release the window object 53 when the number of window handles 520 allocated in the window pool 52 has reached a preset maximum value.
  • the release module 45 can control the window pool 52 to execute the release rule to release the window object 53 according to the priority of the window object 53 and the creation order.
  • the release rule is to first release the window object 53 with a lower priority, and in the case of the same priority, release the window object 53 that has been created for the longest time.
  • the window pool 52 executes the release rule, the window pool 52 has an assignable window handle 520.
  • the determination module 44 again determines whether the number of window handles 520 allocated in the window pool 52 has reached a preset maximum value.
  • the recycling module 46 is configured to unload elements of the application page on the window object 53 when the display of the application page ends, and control the window pool 52 to recycle the window handle 520.
  • the recycling module 46 is further configured to determine whether to cache data for the application page. For an application page with frequent operations and high loading frequency, data can be cached for the application page, and can be quickly loaded when the next display is performed, without re-requesting data. If the application page does not need to be cached With page data, the process ends. If it is necessary to cache the data of the application page, the recycling module 46 is further configured to perform data caching and end the recycling of the window object 53.
  • FIG. 7 is a flow chart of a method of a preferred embodiment of a method for implementing a multi-mode application page of the present invention. As shown in FIG. 1, FIG. 2 and FIG. 3, the application page generation manners of the three modes are shown in FIG. 7, and FIG. 7 is a description of the selection method of the application pages of the three modes.
  • Step 70 The selection module 40 selects an application page class of the corresponding mode according to different scenarios of the terminal 1.
  • the different scenarios may include: different operating systems of the terminal 1, different screen resolutions, and the like.
  • Step 71 The acquisition module 41 controls the application page class 51 of the corresponding mode to acquire the window handle 520 to form the window object 53.
  • the window handle 520 is obtained from the window pool 52 (as shown in FIG. 5), and the application page class 51 of the corresponding mode acquires the window handle 520 and instantiates it to form the window object 53.
  • Step 72 The display module 42 controls the window object 53 to display the application page of the corresponding mode.
  • the selection module 40 needs to select the application page class 51 of the corresponding mode.
  • the scene of the above application page and the selectable corresponding mode application page class 51 can be set as:
  • Scenario 1 The application page class 51 of the corresponding mode is selected according to different operating systems. If the terminal 1 is an open source terminal operating system, the selection module 40 selects a native application page class; for a closed terminal operating system, the selection module 40 selects a hybrid application page class.
  • Scenario 2 Select the application page class 51 of the corresponding mode according to different system versions of the same operating system. For example, the version before Android 4.0 has poor compatibility with the web view component, so the selection module 40 selects the native application page class; in the version after Android 4.0, the selection module 40 selects the web application page class.
  • Scenario 3 The application page class 51 of the corresponding mode is selected according to different terminal 1 having different screen aspect ratios. For a terminal having a large screen aspect ratio, the selection module 40 selects a hybrid application page class; for a terminal having a small aspect ratio, the selection module 40 selects a web application page class.
  • the scene determination and selection of the terminal 1 by the selection module 40 can be implemented by an Extensible Markup Language (XML) (hereinafter referred to as XML) plug-in 50 (as shown in FIG. 5).
  • XML Extensible Markup Language
  • the XML plug-in 50 realizes the application page class 51 corresponding to the corresponding mode by judging the different scenarios of the terminal 1, avoiding hard coding, improving the flexibility of application on the terminal 1, and facilitating maintenance of the version.
  • Each application page corresponds to a pages configuration item, the pages are the parent tags of the page, the pages include a plurality of page sub-tabs, and each page tag represents a condition for selecting the application page class 51 of the corresponding mode.
  • the key indicates the unique identifier of the application page. When opening the application page, only the identifier needs to be specified.
  • Page check is a condition for judging the scene, including the operating system, version, screen aspect ratio, and the like of the terminal 1. If the default is default, it means that the judgment condition cannot be matched. By default, the web application page class (homeWebwindow) is selected, and the value indicates the package path of the application page class 51 of the corresponding mode.
  • the application page class 51 of the corresponding mode is a collection of data and operation functions related to the application page.
  • the native application page class can implement an interface of a native component, and the native component can be a layout class, a text class, or a picture class component.
  • the web application page class can implement the interface of the web view component, and the implementable functions in the web view component include getUrl(), loadUrl(), etc., and the hybrid application page class needs to implement the interface of the native component and the interface of the webpage view component at the same time. .
  • the obtaining module 41 controls the application page class 51 of the response mode to obtain the window handle 520, and forms a window object 53, and the display module 42 finally applies the native application page 10 and the webpage application.
  • Page 20 or hybrid application page 30 is displayed to the user.
  • the application page class 51 of the corresponding mode is instantiated by the acquisition module 41 to obtain the window handle 520. Before the window object 53 is formed, the window object 53 may be further included.
  • the inheritance module 43 controls the application page class 51 of the corresponding mode to inherit the window subclass of the corresponding mode.
  • the window subclass of the corresponding schema inherits the window class 60 (shown in Figure 6) that encapsulates the underlying public method functions.
  • the window class 60 uniformly encapsulates the underlying public method functions, preferably including functions that call transition animations, functions that manage the history stack, and functions that control the lifecycle of the window class.
  • the function that calls the transition animation is used to implement the animation effect of the application page switching in the application page transition.
  • the function of managing the history stack is used to save and destroy the browsed page, and the control window class life cycle function is used for management. Creation, start, stop, and destruction of window classes.
  • the window class 60 derives three window subclasses, which are a native application window subclass, a web application window subclass, and a hybrid application window subclass, and the native application page class, the web application page class, and the hybrid application page class respectively inherit the above native application. Window subclass, web application window subclass, mixed application window subclass.
  • the native application window subclass can implement an interface of a native component, and the native component can be a layout class, a text class, a picture class component, etc.
  • the web application window subclass can implement an interface of the webpage view component, and the webpage view component can be
  • the implementation functions include getUrl(), loadUrl(), etc.
  • the hybrid application window subclass needs to implement both the interface of the native component and the interface of the webpage view component.
  • the application page class of the corresponding mode respectively inherits the corresponding window class subclass, so that the application page class of the mode only needs to implement specific layout and business logic without paying attention to the underlying basic functional part.
  • the separate architecture reduces the coupling of functional modules and improves development efficiency.
  • FIG. 8 is a flow chart of a method of another preferred embodiment of a method for implementing a multi-mode application page according to the present invention.
  • Step 80 The selection module 40 selects an application page class of the corresponding mode according to different scenarios of the terminal 1.
  • Step 81 The determining module 44 determines whether the number of window handles 520 allocated by the window pool 52 has reached a preset maximum value.
  • the preset maximum value refers to a certain rule may be set to determine the number of window handles 520 when the window pool 52 is initially managed.
  • the set rule is the maximum number rule, i.e., the number of window handles 520 that have a maximum value preset in the window pool 52.
  • the maximum number rule can limit the unlimited growth of the window object 53, ensuring management and optimization of the terminal memory. If the number of window handles 520 allocated by the window pool 52 does not reach the preset maximum value, the release module 45 is not required to control the window pool 52 to release the window object 53, and the flow proceeds to flow 81. If the number of window handles 520 allocated by window pool 52 has reached a preset maximum value, then step 84 is reached.
  • Step 82 The acquisition module 41 controls the application page class 51 of the corresponding mode to acquire the window handle 520 to form the window object 53.
  • Step 83 The acquisition module 41 controls the application page class 51 of the corresponding mode to acquire the window handle 520 to form the window object 53.
  • the window handle 520 is obtained from the window pool 52 (as shown in FIG. 5), and the application page class 51 of the corresponding mode acquires the window handle 520 and instantiates it to form the window object 53.
  • Step 84 When the number of window handles 520 allocated in the window pool 52 has reached a preset maximum value, the release module 45 controls the window pool 52 to release the window object 53. When there is no window handle 520 available in the window pool 52, the release module 45 can control the window pool 52 to execute the release rule to release the window object 53 according to the priority of the window object 53 and the creation order. In this embodiment, the release rule is to first release the window object 53 with a lower priority, and in the case of the same priority, release the window object 53 that has been created for the longest time. When the window pool 52 executes the release rule, the window pool 52 has an assignable window handle 520, which proceeds to flow 81.
  • FIG. 9 is a flow chart of a method for recycling a window handle in a method for implementing a multi-mode application page in accordance with the present invention.
  • Step 91 When the application page display ends, the recycling module 46 unloads the elements of the application page on the window object 53, and controls the window pool 52 to recycle the window handle 520.
  • Step 92 The recovery module 46 determines whether to perform data caching on the application page. For application pages with frequent operations and high loading frequency, data caching can be performed on the application page. The next time you display it, you can load it quickly without having to re-request the data. If the application page does not need to cache the application page data, the process ends.
  • Step 93 If it is necessary to cache the data of the application page, the recycling module 46 performs data caching and ends the recycling of the window object 53.
  • Embodiments of the present invention also provide a storage medium.
  • an execution instruction is stored in the storage medium, and the execution instruction is used to execute the foregoing method.
  • the foregoing storage medium may include, but is not limited to, a USB flash drive, a Read-Only Memory (ROM), and a Random Access Memory (RAM).
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • the terminal, the method, and the system for implementing the multi-mode application page provided by the embodiments of the present invention have the following beneficial effects: by judging different scenarios of the terminal, flexibly selecting an application page of the corresponding mode for display, thereby implementing a A multi-modal application page not only improves the efficiency of application development, but also develops multi-mode applications that can better adapt to different scenarios and greatly enhance the user experience.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Databases & Information Systems (AREA)
  • Human Computer Interaction (AREA)
  • Data Mining & Analysis (AREA)
  • User Interface Of Digital Computer (AREA)
  • Stored Programmes (AREA)

Abstract

La présente invention concerne un procédé, un terminal et un système permettant de réaliser une page d'application multimode. Le procédé est appliqué à un terminal et comprend : une étape de sélection permettant de sélectionner un mode correspondant de classe de page d'application sur la base de différents scénarios du terminal (70); une étape d'acquisition permettant de commander le mode correspondant de classe de page d'application afin d'acquérir un identifiant de fenêtre de manière à former un objet fenêtre (71); et une étape d'affichage permettant de contrôler l'objet fenêtre afin d'afficher le mode correspondant de classe de page d'application (72). Le procédé, le terminal et le système peuvent réaliser une page d'application multimode, de sorte que l'efficacité du développement d'application soit améliorée et une application multimode développée peut en outre être mieux adaptée à différents scénarios, améliorant ainsi fortement l'expérience utilisateur.
PCT/CN2016/104380 2015-11-18 2016-11-02 Terminal, procédé et système permettant de réaliser une page d'application multimode Ceased WO2017084497A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510799519.5A CN106708498A (zh) 2015-11-18 2015-11-18 一种实现多模式应用页面的终端、方法及系统
CN201510799519.5 2015-11-18

Publications (1)

Publication Number Publication Date
WO2017084497A1 true WO2017084497A1 (fr) 2017-05-26

Family

ID=58717296

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/104380 Ceased WO2017084497A1 (fr) 2015-11-18 2016-11-02 Terminal, procédé et système permettant de réaliser une page d'application multimode

Country Status (2)

Country Link
CN (1) CN106708498A (fr)
WO (1) WO2017084497A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113778573A (zh) * 2020-05-29 2021-12-10 北京沃东天骏信息技术有限公司 一种在用户界面中实现页面的方法及系统
WO2024179249A1 (fr) * 2023-02-27 2024-09-06 华为技术有限公司 Procédé d'affichage de dispositif électronique, dispositif électronique et support de stockage

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107329979A (zh) * 2017-05-31 2017-11-07 阿里巴巴集团控股有限公司 一种数据对象展示方法及装置
CN107678817A (zh) * 2017-09-21 2018-02-09 北京三快在线科技有限公司 视图切换方法和装置以及计算设备
CN107784120A (zh) * 2017-11-17 2018-03-09 深圳泉眼体育运营管理有限公司 发布运营活动网页的方法及装置
CN109361948B (zh) * 2018-10-30 2021-11-09 深圳Tcl数字技术有限公司 界面管理方法、智能终端及可读存储介质
CN109656555A (zh) * 2018-11-30 2019-04-19 深圳市汇川技术股份有限公司 操作界面实现方法、系统、机器人示教器及存储介质
CN109933253A (zh) * 2019-01-23 2019-06-25 努比亚技术有限公司 应用启动控制方法、终端及计算机可读存储介质
CN111506848A (zh) * 2019-01-30 2020-08-07 阿里巴巴集团控股有限公司 网页处理方法、装置、设备及可读存储介质
CN110007983B (zh) * 2019-03-29 2022-06-07 网易传媒科技（北京）有限公司 粒子喷射动画的实现方法、介质、装置和计算设备
CN114095291A (zh) * 2020-07-31 2022-02-25 青岛海信电子产业控股股份有限公司 一种多设备接入显示方法及设备
CN118152056A (zh) * 2024-03-20 2024-06-07 中建八局第一数字科技有限公司 一种教学资源的展示方法、装置、计算机设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102426524A (zh) * 2011-11-02 2012-04-25 青岛海信移动通信技术股份有限公司 终端上的图形用户界面显示方法和设备
CN103309687A (zh) * 2012-03-09 2013-09-18 联想(北京)有限公司 电子设备及其应用程序启动方法
CN103677872A (zh) * 2012-09-10 2014-03-26 联想(北京)有限公司 一种信息处理方法、装置和电子设备
CN104183227A (zh) * 2013-05-20 2014-12-03 中兴通讯股份有限公司 应用程序的显示处理方法及装置
CN104503655A (zh) * 2014-11-28 2015-04-08 晨星半导体股份有限公司 应用程序界面显示控制方法及装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102087596B (zh) * 2011-01-28 2014-07-30 深圳市同洲电子股份有限公司 嵌入式浏览装置及其多页面混合显示方法
CN104461491B (zh) * 2013-09-24 2017-10-27 阿里巴巴集团控股有限公司 一种Hybrid组件的运行方法和系统
CN103744652B (zh) * 2013-12-19 2017-02-08 深圳市蓝凌软件股份有限公司 一种跨移动终端的混合app开发方法及装置
CN104793966A (zh) * 2014-01-21 2015-07-22 中国科学院声学研究所 一种Android本地应用的显示加载方法及系统
CN104808971B (zh) * 2014-01-24 2020-02-21 北京三星通信技术研究有限公司 网络应用程序管理器、方法、装置和移动终端
CN103995884A (zh) * 2014-05-29 2014-08-20 北京中电普华信息技术有限公司 一种混合应用页面的切换方法及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102426524A (zh) * 2011-11-02 2012-04-25 青岛海信移动通信技术股份有限公司 终端上的图形用户界面显示方法和设备
CN103309687A (zh) * 2012-03-09 2013-09-18 联想(北京)有限公司 电子设备及其应用程序启动方法
CN103677872A (zh) * 2012-09-10 2014-03-26 联想(北京)有限公司 一种信息处理方法、装置和电子设备
CN104183227A (zh) * 2013-05-20 2014-12-03 中兴通讯股份有限公司 应用程序的显示处理方法及装置
CN104503655A (zh) * 2014-11-28 2015-04-08 晨星半导体股份有限公司 应用程序界面显示控制方法及装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113778573A (zh) * 2020-05-29 2021-12-10 北京沃东天骏信息技术有限公司 一种在用户界面中实现页面的方法及系统
WO2024179249A1 (fr) * 2023-02-27 2024-09-06 华为技术有限公司 Procédé d'affichage de dispositif électronique, dispositif électronique et support de stockage

Also Published As

Publication number Publication date
CN106708498A (zh) 2017-05-24

Similar Documents

Publication Publication Date Title
WO2017084497A1 (fr) Terminal, procédé et système permettant de réaliser une page d'application multimode
US10423527B2 (en) Memory management and image display for mobile devices
US9396572B2 (en) Image correlation method and electronic device thereof
TWI766896B (zh) 頁面展示方法及裝置
US9710950B2 (en) Extensible sprite sheet generation mechanism for declarative data formats and animation sequence formats
US9507480B1 (en) Interface optimization application
US20190080017A1 (en) Method, system, and device that invokes a web engine
CN112800370A (zh) 业务单据的处理方法、装置、计算机设备和存储介质
US20140040789A1 (en) Tool configuration history in a user interface
JP2021512415A (ja) デジタルコンポーネントのバックドロップレンダリング
CN109361948B (zh) 界面管理方法、智能终端及可读存储介质
WO2017107851A1 (fr) Procédé et dispositif permettant de libérer et de mettre à jour un composant d'application de bureau
CN111158820B (zh) 控件点击事件处理方法、装置、电子设备及存储介质
CN109040767A (zh) 一种直播间加载方法、系统、服务器及存储介质
CN103617055B (zh) 一种在浏览器中启动应用程序的方法、装置和浏览器
US9501415B1 (en) Image caching system to support fast scrolling of images in a graphical user interface
CN112948844B (zh) 控制方法、装置及电子设备
CN113391808A (zh) 页面的配置方法、装置及电子设备
US20240220184A1 (en) Screen projection method and related apparatus
US12001777B2 (en) Font switching method and electronic device
CN114816411B (zh) 增强现实模型转换的方法、装置、设备及存储介质
CN108304169B (zh) 针对html5应用的实现方法、装置和设备
CN112578973B (zh) 内容选择方法、装置、设备及计算机可读存储介质
US20140292759A1 (en) Method, Apparatus and Computer Program Product for Managing Media Content
CN103544051A (zh) 一种操作方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16865674

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16865674

Country of ref document: EP

Kind code of ref document: A1