WO2017166858A1

WO2017166858A1 - Method and device for reversely controlling mobile page

Info

Publication number: WO2017166858A1
Application number: PCT/CN2016/108933
Authority: WO
Inventors: 黎河军
Original assignee: 百度在线网络技术（北京）有限公司
Priority date: 2016-03-31
Filing date: 2016-12-07
Publication date: 2017-10-05
Also published as: CN105912319A; CN105912319B

Abstract

A method and device for reversely controlling a mobile page. The method for reversely controlling a mobile page comprises: receiving a touch event for reverse control sent by another terminal (S11); recognizing a gesture event according to the touch event and determining an element to be reversely controlled (S12); and if the element is an element on an HTML page, configuring an HTML parameter for the element according to the gesture event, so that the element is processed according to the HTML parameter, to respond to the gesture event (S13). The method can avoid limitation by a mobile operating system to the use of interfaces, thereby conveniently implementing the reverse control of a mobile page.

Description

Method and device for controlling mobile page in reverse

Cross-reference to related applications

The present application claims the priority of the Chinese patent application No. 201610202382.5, which is filed on March 31, 2016, which is filed on March 31, 2016 by Baidu Online Network Technology (Beijing) Co., Ltd., entitled "Method and Apparatus for Reverse Control of Mobile Pages".

Technical field

The present invention relates to the field of Internet technologies, and in particular, to a method and apparatus for controlling a mobile page in reverse.

Background technique

In the interconnection scheme between the mobile phone and the vehicle, the online solution of the projection mobile phone interface to the vehicle display is often used. At this time, the operation performed by the user on the vehicle end is synchronously transmitted to the mobile terminal, and the mobile terminal receives the operation to actively trigger the relevant page. The binding behavior of the element.

When the page of the application displayed on the mobile phone is a HyperText Markup Language (HTML) page, since the HTML page is dynamically loaded through the network in many cases, and the context of the HTML5 page runs with the code of the application. The context is independent of each other, so there needs to be a well-established mechanism to implement the HTML page of the mobile phone to the mobile phone. Reverse control.

In the related art, the event is generated by using the underlying event interface of the mobile phone system to generate an event, thereby transmitting an event to the page element at the system level, thereby triggering the binding behavior of the page element. However, the existing mobile operating system limits the use of the interface, for example, in the iOS system requires auditing, in the android system needs to have root privileges. Therefore, the reverse control implemented by the underlying event interface of the mobile phone system is not convenient in application.

Summary of the invention

The present invention aims to solve at least one of the technical problems in the related art to some extent.

Therefore, an object of the present invention is to provide a method for reversely controlling a mobile page, which can avoid the limitation of the interface used by the mobile operating system and conveniently implement reverse control of the mobile page.

Another object of the present invention is to provide an apparatus for back-controlling a mobile page.

In order to achieve the above object, a method for reversely controlling a mobile page according to the first aspect of the present invention includes: receiving a touch event sent by another terminal for reverse control; identifying a gesture event according to the touch event, and Determining an element to be inversely controlled; if the element is an element in an HTML page, configuring an HTML parameter for the element according to the gesture event, such that the element is processed according to the HTML parameter in response to the gesture event.

The method for back-controlling a mobile page proposed by the first aspect of the present invention, by configuring an HTML parameter according to a gesture event, when an element to be reversely controlled is an element in an HTML page, The element can be processed according to the configured HTML parameters in response to the gesture event, thereby implementing reverse control of the elements in the HTML page, and the reverse control flow does not invoke the interface of the operating system, thereby avoiding the interface of the mobile operating system The restrictions used make it easy to implement reverse control of the mobile page.

In order to achieve the above object, an apparatus for reversely controlling a mobile page according to a second aspect of the present invention includes: a communication module, configured to receive a touch event sent by another terminal for reverse control; and a gesture recognition module, configured to: Identifying a gesture event according to the touch event, and determining an element to be inversely controlled; and a conversion module, configured to configure an HTML parameter for the element according to the gesture event if the element is an element in an HTML page, The element is processed in response to the HTML parameter in response to the gesture event.

The device for back-controlling a mobile page proposed by the second aspect of the present invention can make an element according to a configured HTML by configuring an HTML parameter according to a gesture event when an element to be inversely controlled is an element in an HTML page. The parameters are processed in response to the gesture event, thereby implementing reverse control of the elements in the HTML page, and the reverse control flow does not invoke the interface of the operating system, thereby avoiding the limitation of the interface used by the mobile operating system, and conveniently implementing Reverse control of the mobile page.

The embodiment of the present application further provides a terminal, including: a processor; a memory for storing processor-executable instructions; wherein the processor is configured to: receive a touch event sent by another terminal for reverse control Identifying a gesture event based on the touch event and determining a to-be-controlled An element; if the element is an element in an HTML page, configuring an HTML parameter for the element according to the gesture event such that the element is processed according to the HTML parameter in response to the gesture event.

The embodiment of the present application further provides a non-transitory computer readable storage medium, when the instructions in the storage medium are executed by a processor of the terminal, enabling the terminal to perform a method for back-controling the mobile page. The method includes: receiving a touch event sent by another terminal for reverse control; identifying a gesture event according to the touch event, and determining an element to be inversely controlled; if the element is an element in an HTML page, according to The gesture event configures an HTML parameter for the element to cause the element to process in accordance with the HTML parameter in response to the gesture event.

The embodiment of the present application further provides a computer program product, when an instruction in the computer program product is executed by a processor, performing a method for back-controlling a mobile page, the method comprising: receiving a sending by another terminal a touch event for reverse control; recognizing a gesture event based on the touch event, and determining an element to be inversely controlled; if the element is an element in an HTML page, configuring the element according to the gesture event An HTML parameter to cause the element to process in accordance with the HTML parameter in response to the gesture event.

The additional aspects and advantages of the invention will be set forth in part in the description which follows.

DRAWINGS

The above and/or additional aspects and advantages of the present invention are described in the following description of embodiments with reference to the accompanying drawings Will become obvious and easy to understand, where:

1 is a schematic flow chart of a method for back-controling a mobile page according to an embodiment of the present invention;

2 is a schematic flow chart of a method for back-controling a mobile page according to another embodiment of the present invention;

3 is a schematic diagram of a click event recognition process receiving a press event in the embodiment of the present invention;

4 is a schematic diagram of a mobile event after receiving a click event in a click event identification process according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of a click event recognition process receiving a release event in an embodiment of the present invention; FIG.

6 is a schematic diagram of a double-click event identification process in an embodiment of the present invention;

7 is a schematic diagram of a double-click event recognition process after receiving a mobile event in an embodiment of the present invention;

8 is a schematic diagram of receiving a press event in a drag event recognition process in an embodiment of the present invention;

9 is a schematic diagram of a motion event after receiving a motion event in a drag event recognition process according to an embodiment of the present invention;

10 is a schematic diagram of receiving a release event in a drag event recognition process according to an embodiment of the present invention;

FIG. 11 is a schematic structural diagram of an apparatus for back-controling a mobile terminal according to an embodiment of the present invention; FIG.

FIG. 12 is a schematic structural diagram of an apparatus for back-controlling a mobile terminal according to another embodiment of the present invention.

detailed description

The embodiments of the present invention are described in detail below, and the examples of the embodiments are illustrated in the accompanying drawings, in which the same or similar reference numerals indicate the same or similar modules or modules having the same or similar functions. The embodiments described below with reference to the accompanying drawings are intended to be illustrative of the invention and are not to be construed as limiting. Rather, the invention is to cover all modifications, modifications and equivalents within the spirit and scope of the appended claims.

FIG. 1 is a schematic flow chart of a method for back-controling a mobile page according to an embodiment of the present invention. The method of this embodiment can be applied to the mobile terminal.

Referring to FIG. 1, the method of this embodiment includes:

S11: Receive a touch event sent by another terminal for reverse control.

Other terminals refer to the peers that are connected to the mobile terminal. For example, in the networking solution of a mobile phone and a car, the mobile terminal refers to a mobile phone, and the other terminal refers to a car phone.

When the vehicle end needs to control the mobile phone terminal in reverse, the car machine can send a reverse control event to the mobile phone, and the event is a native event of the application, specifically a touch event.

Touch events include: pressing an event, moving an event, and releasing an event.

Each touch event can include a corresponding parameter. In some specific examples, the representation of each touch event and the parameters included may be as follows:

First touch event: Press event: NATIVE_EVENT_TOUCH_DOWN

(a) The parameter location represents the pressed position coordinate (x, y);

(b) parameter points indicate the number of touch points (single finger / double finger / multi finger);

(c) The parameter timestamp indicates the time of occurrence.

Second touch event: Move event: NATIVE_EVENT_TOUCH_MOVE

(a) The parameter location represents the position coordinate (x, y) to which it is moved;

(c) The parameter timestamp indicates the time of occurrence.

Third touch event: Release event: NATIVE_EVENT_TOUCH_UP

S12: Identify a gesture event according to the touch event, and determine an element to be reversely controlled.

Among them, the gesture event is an event for triggering the element response.

Gesture events include: click events, double click events, long press events, and drag events.

Each gesture event can include a corresponding parameter. In some specific examples, the representation of each gesture event and the parameters it includes can be as follows:

First gesture event: Click event: H5_EVENT_TYPE_CLICK

(a) The parameter location indicates the click coordinates (x, y);

(c) The parameter timestamp indicates the time of occurrence.

Second gesture event: double click event: H5_EVENT_TYPE_DOUBLECLICK

(a) The parameter location represents the double-click position coordinate (x, y);

(b) Parameter points indicate the number of touch points (single finger / double finger / multi finger)

(c) The parameter timestamp indicates the time of occurrence.

The third gesture event: long press event: H5_EVENT_TYPE_LONGPRESS

(a) The parameter location represents the long-press position coordinate (x, y);

(c) The parameter timestamp indicates the time of occurrence.

The fourth gesture event: drag event: H5_EVENT_TYPE_DRAG

(a) The parameter location indicates dragging to the position coordinates (x, y);

(c) The parameter timestamp indicates the time of occurrence.

In the gesture event recognition, the above parameters of the gesture event may be acquired according to the parameters of the corresponding touch event, for example, the position coordinates of the click event, the occurrence time are the same as the position coordinates of the pressed event, and the pressing time. After determining the position coordinates of the gesture event, the element corresponding to the position coordinate may be determined as an element to be reversely controlled.

The specific process of recognizing a gesture event according to a touch event can be referred to the subsequent description.

S13: If the element is an element in an HTML page, configure an HTML parameter for the element according to the gesture event, so that the element is processed according to the HTML parameter in response to the gesture event.

Among them, the HTML page can specifically refer to the HTML5 page.

The development language of the gesture event is consistent with the operating system of the mobile terminal. For example, if the operating system is an iOS system, the language of the gesture event is ObjectC, and if the operating system is an android system, the language of the gesture event is java. The development language of the HTML page loaded by the application is not the native language. In order to make the elements in the HTML page respond to gesture events, it needs to be based on the gesture event as HTML. The elements in the page configure HTML parameters to enable reverse control of the elements in the HTML page.

The process of configuring HTML parameters based on click events can include:

According to the mark information of the elements in the HTML page in advance, starting from the element corresponding to the position coordinate of the click event, the bottom-up search type is a controllable element, and after finding the element whose type is controllable, the element is Click event (click) binding in the HTML page.

The tag information of the element may be the type of the tag element, the type may be divided into controllable and unreliable, the controllable element can respond to the click event, and the uncontrollable element cannot respond to the click event.

The elements in the HTML page are DOM elements, and the DOM elements are arranged in a tree structure. From bottom to top, according to the tree structure, from the leaf element to the parent element of the leaf element and then to the root element.

The process of configuring HTML parameters according to the drag event may include:

Starting from the element corresponding to the position coordinate of the drag event, looking up the scrollable element from bottom to top, after finding the scrollable element, determining whether the element also satisfies any of the following conditions:

The first condition: the element is the top element, and the size of the element is larger than the view size;

The second condition: The element is a normal element before the top element, and the size of the element is larger than the size of its parent element.

If the element is a scrollable element and also satisfies any of the above conditions, the scrolling parameter in the HTML page can be configured for the element according to the moving distance of the drag event.

Whether the element is a scrollable element can be determined according to the scrollable parameter of the element, and the scrollable parameters in the HTML page include: overflow or overflow-x and overflow-y, if overflow Not hidden, or neither overflow-x nor overflow-y are hidden, you can be sure that the element is a scrollable element.

The size of the element, the size of the parent element, and the view size can be determined based on the style information in the HTML page, and the like.

The moving distance of the drag event may be determined according to the position coordinate of the drag start event and the position coordinate of the drag end event, and the difference between the coordinates of the two positions is taken as the moving position.

The scrolling parameters in the HTML page set according to the moving distance may include: scrollleft and scrolltop, wherein scrollleft is used to determine the horizontal moving distance, and scrolltop is used to determine the vertical moving distance.

Since the gesture events that are often used in reverse control are click events and drag events, the above gives a way to configure HTML parameters based on click events and drag events. It can be understood that according to double click events and long press events. The way to configure HTML parameters can also be referred to for execution, and will not be described in detail here.

In some embodiments, as shown in FIG. 2, the method may further include:

S14: It is judged whether the element to be reversely controlled is an element in the HTML page, and if so, the above S13 is executed, otherwise, S15 is performed.

The element to be reversely controlled may be an element in an HTML page, or may be a native control that can be interacted in the application, and the interactive native control refers to a control that can be directly controlled by a gesture event.

Specifically, after the location coordinates are determined at the time of the gesture event recognition, the mobile terminal operating system provides The method can determine the native control and the control description information of the location. If the control is determined to be a browser control (webview) according to the description of the control, it can be determined that the element to be reversely controlled is an element in the HTML page, otherwise it is interactive. Native controls.

S15: If the above element is an interactive native control, the recognized gesture event is sent to the interactive native control, so that the interactive native control responds to the gesture event.

Since the interactive native controls are consistent with the language of the gesture event, the gesture events can be directly responded to the reverse control of the interactive native controls.

In the above process, a process of recognizing a gesture event according to a touch event is involved, and the specific process may be as follows.

Wherein, when the flow of the gesture event is recognized according to the touch event, the recognition of the click event, the double-click event, the long-press event, and the drag event may be started simultaneously after receiving the touch event.

In some embodiments, when the event identification is clicked, the following processes may be included:

If the received touch event is a press event, an event is pushed onto the stack for the press event;

If the received touch event is a moving event, it is determined whether the moving distance is less than a preset distance value, and if it is less, the event is pushed onto the stack;

If the received touch event is a release event, it is determined whether the startup time is within a preset range when the recognition is started, and if it is within the preset range, the click event is recognized.

The above moving distance may be determined according to the position coordinates of the first event (press event) in the stack and the position coordinates of the current event (moving event), and the difference between the coordinates of the two positions is determined as the moving distance.

The above startup time may be determined according to the occurrence time of the first event (press event) in the stack and the occurrence time of the last event (press event or movement event), and the difference between the two times is determined as the startup time.

In the above-mentioned click event identification process, the specific processing flow of receiving each touch event can be referred to the following embodiment.

FIG. 3 is a schematic diagram of a click event recognition process receiving a press event in the embodiment of the present invention. Referring to Figure 3, the process includes:

S31: The received touch event is a press event.

S32: It is judged whether the recognition has been started, and if so, S33 is executed, otherwise, S34 is executed.

Wherein, it is possible to set whether the identifier is activated, and according to the identifier, it can be determined whether the identification has been started.

Initially, the identification may be set to identify a state that is not activated, and when the identification is initiated, the identification is updated to identify the activated state.

S33: End recognition.

S34: Start recognition and perform event stacking on the pressed event.

When the recognition is not initiated, the recognition is initiated and the pressed event is placed on the stack.

When events are placed on the stack, they can be placed in order, so that the first and last events in the stack can be identified in subsequent processes.

4 is a schematic diagram of a mobile event after receiving a click event identification process in an embodiment of the present invention. Referring to Figure 4, the process includes:

S41: The received touch event is a mobile event.

S42: It is judged whether the recognition has been started, and if so, S43 is executed, otherwise, S45 is executed.

S43: Determine whether the moving distance is smaller than the first preset distance value, and if yes, execute S44, otherwise, execute S45.

The preset distance value can be set according to experience or the like.

S44: Perform event stacking on the mobile event.

S45: End recognition.

FIG. 5 is a schematic diagram of a click event recognition process receiving a release event in an embodiment of the present invention. Referring to Figure 5, the process includes:

S51: Receiving the touch event is a release event.

S52: It is judged whether the recognition has been started, and if so, S53 is executed, otherwise, S55 is executed.

S53: Determine whether the startup time is within a preset range. If yes, execute S54; otherwise, execute S55.

The preset range can be set based on experience and the like.

S54: Determine to identify the click event.

S55: End recognition.

In some embodiments, when double-clicking event recognition, it may be based on the identification of a click event, including the following process.

FIG. 6 is a schematic diagram of a double-click event recognition process in an embodiment of the present invention. Referring to Figure 6, the process includes:

S61: A click event is recognized.

For the identification process of the click event, refer to the foregoing embodiment, and details are not described herein again.

S62: Determine whether the time of the last click event is not empty, if yes, execute S63, otherwise, execute S64.

The identified click event may be one or more. If it is one, the last click event refers to the one click event, and if there are multiple, the time of each click event may be determined. Clicks the most recent click event from the current time as the last click event.

Initially, the time of the last click event can be set to null, and subsequent updates can be made as appropriate.

S63: When not empty, calculate a difference between the current time and the time of the last click event, and determine whether the difference is less than a preset interval. If yes, execute S65, otherwise execute S64.

S64: Update the time of the last click event to the current time when it is empty or less than the preset interval.

S65: Update the time of the last click event to null.

S66: Determine to identify the double-click event.

In some embodiments, when long-press event recognition, the following processes may be included:

If the received touch event is a moving event, it is determined whether the moving distance is less than a second preset distance value, and if it is less, determining whether the starting time is greater than a preset duration; if greater than, determining to identify a long press event;

If the received touch event is a release event, the identification ends.

The above startup time may be determined according to the occurrence time of the first event (press event) in the stack and the occurrence time of the current component (moving event), and the difference between the two times is determined as the startup time.

FIG. 7 is a schematic diagram of a double-click event recognition process in the embodiment of the present invention after receiving a mobile event. Referring to Figure 7, the process includes:

S71: The received touch event is a mobile event.

S72: It is judged whether the recognition has been started, and if so, S73 is executed, otherwise, S76 is executed.

S73: Determine whether the moving distance is smaller than the second preset distance value, and if yes, execute S74; otherwise, execute S76.

The second preset distance value may be set according to experience or the like, and may be the same as or different from the first preset distance value described above.

S74: determining whether the startup time is greater than a preset duration, if yes, executing S75, otherwise, executing S76.

The preset duration can be set according to experience and the like.

S75: Determine to identify a long press event.

S76: End recognition.

In some embodiments, when the event identification is dragged, the following processes may be included:

If the received touch event is a press event, the event is pushed onto the stack, and the control corresponding to the position coordinate of the pressed event is acquired, and when the space is a draggable control, the drag start event is sent;

If the received touch event is a moving event, the event is pushed onto the mobile event, and the position coordinate of the moving event is determined to be inside the draggable control, and if it is internal, the dragging event is sent;

If the received touch event is a release event, an event is pushed onto the stack, and a position of the release event is determined to be inside the draggable control, and if it is internal, a drag end event is sent.

In the above-mentioned drag event identification process, the specific processing flow of receiving each touch event can be referred to the following embodiments.

FIG. 8 is a schematic diagram of a drag event recognition process receiving a press event in the embodiment of the present invention. Referring to Figure 8, the process includes:

S81: The received touch event is a press event.

S82: Initialization identification.

The initialization identification includes, for example, determining whether the recognition has been initiated, and if it has been started, ending the identification, and if not, initiating the identification.

S83: After the recognition is started, an event is pushed onto the stack for the press event.

S84: Acquire a control corresponding to the position coordinate of the pressed event, and determine whether the control is a draggable control, and if yes, execute S85; otherwise, execute S86.

Draggable controls include, for example, UIScrollView, BTapDetectingView, and UIWebView.

If the control at the position coordinate of the pressed event is any of the above controls, it is determined that the control is a draggable control.

S85: Send a drag start event.

At this point, the drag start event can be recognized and a drag start event can be sent.

S86: End recognition.

FIG. 9 is a schematic diagram of a motion event after receiving a motion event in a drag event recognition process according to an embodiment of the present invention. Referring to Figure 9, the process includes:

S91: The received touch event is a mobile event.

S92: It is judged whether the recognition has been started, and if so, S94 is executed, otherwise, S93 is executed.

S93: End recognition.

S94: Perform event stacking on the mobile event.

S95: Determine whether the position coordinate of the movement event is inside the draggable control, and if yes, execute S96; otherwise, execute S97.

S96: Send a drag to perform an event.

At this point, the dragging event can be recognized, and the drag can be sent to perform the event.

S97: Send a drag end event.

At this point, the drag end event can be recognized and the drag end event can be sent.

FIG. 10 is a schematic diagram of a drag event recognition process in a process of receiving a release event in an embodiment of the present invention. Referring to Figure 10, the process includes:

S101: Receiving a touch event is a release event.

S102: It is judged whether the recognition has been started, and if so, S103 is executed, otherwise, S106 is executed.

S103: Perform an event on the release event.

S104: Determine whether the position coordinate of the release event is inside the draggable control, and if yes, execute S105; otherwise, execute S106.

S105: Send a drag end event.

S106: End recognition.

It can be understood that, in the above gesture event recognition process, after the click event, the double click event, or the long press event is recognized, the corresponding gesture event may be sent to the subsequent module for event distribution at one time. In the process of recognizing the drag event, since the drag event is an event that lasts for a period of time, the event can be sent to the subsequent module for event distribution multiple times during the entire drag process.

In this embodiment, when the element to be reversely controlled is an element in the HTML page, according to the hand The potential event configures the HTML parameter for the element, which can cause the element to process according to the configured HTML parameter in response to the gesture event, thereby implementing reverse control of the element in the HTML page, and the reverse control flow does not call the interface of the operating system, so Avoid the restrictions on the use of the interface by the mobile operating system, and conveniently implement reverse control of the mobile page.

FIG. 11 is a schematic structural diagram of an apparatus for back-controling a mobile terminal according to an embodiment of the present invention. Referring to FIG. 11, the device 110 includes a communication module 111, a gesture recognition module 112, and a conversion module 113.

The communication module 111 is configured to receive a touch event sent by another terminal for reverse control;

Taking another terminal as a vehicle, for example, referring to FIG. 12, the communication module can receive a touch event sent by the vehicle.

The gesture recognition module 112 is configured to identify a gesture event according to the touch event, and determine an element to be reversely controlled;

The conversion module 113 is configured to configure an HTML parameter for the element according to the gesture event if the element is an element in an HTML page, so that the element is processed according to the HTML parameter in response to the gesture event.

Optionally, the touch event includes: a press event, a move event, and a release event;

The gesture events include: a click event, a double click event, a long press event, and a drag event;

The gesture recognition module is specifically configured to:

When the touch event is received, a click event, a double click event, a long press event, and The identification of the drag event.

In some embodiments, referring to FIG. 12, the gesture recognition module 112 includes: a first unit, a second unit, a third unit, and a fourth unit;

The first unit is for:

If the received touch event is a release event, it is determined whether the startup time is within a preset range, and if it is within the preset range, it is determined that the click event is recognized.

The second unit is for:

Identify click events;

Determine if the last click event is not empty;

If it is not empty, calculate a difference between the current time and the time of the last click event, and determine whether the difference is less than a preset time interval;

If it is less than, the time of the last click event is updated to null and it is determined that the double-click event is recognized.

The third unit is used to:

If the received touch event is a mobile event, determine whether the moving distance is less than a second preset distance value, and if it is less, determine whether the starting time is greater than a preset duration; if greater than, determine to identify the long By event;

If the received touch event is a release event, the identification ends.

The fourth unit is used to:

The converting module is configured to configure an HTML parameter for the element according to the gesture event, including:

If the gesture event is a click event, according to the mark information of the element in the HTML page in advance, starting from the element corresponding to the position coordinate of the click event, the bottom-up search type is a controllable element, and the type is found. After being a controllable element, bind the element to a click event in an HTML page.

If the gesture event is a drag event, starting from an element corresponding to the position coordinate of the drag event, searching for a scrollable element from bottom to top, and after finding the scrollable element, determining whether the element is still Meet any of the following conditions:

The element is a top element, and the size of the element is larger than a view size; or,

The element is a normal element, and the size of the element is larger than the size of the parent element of the element;

If the element is a scrollable element and also satisfies any of the above conditions, the scrolling parameter in the HTML page is configured for the element according to the moving distance of the drag event.

In some embodiments, referring to FIG. 12, the apparatus 110 further includes:

The event distribution module 114 is configured to determine whether an element to be reversely controlled is an element in an HTML page, and send the gesture event to the conversion module when the element is an element in an HTML page, When the element is an interactive native control, the gesture event is sent to the interaction module;

The interaction module 115 is configured to send the received gesture event to the interactive native control, so that the interactive native control responds to the gesture event.

It is to be understood that the present embodiment corresponds to the foregoing method embodiments. For details, refer to related descriptions in the method embodiments, and details are not described herein.

In this embodiment, when the element to be reversely controlled is an element in the HTML page, the HTML parameter is configured for the element according to the gesture event, so that the element can be processed according to the configured HTML parameter to respond to the gesture event, thereby implementing the HTML page. The reverse control of the element, and the reverse control process does not call the interface of the operating system, so the restriction of the interface used by the mobile operating system can be avoided, and the reverse control of the mobile page can be conveniently implemented.

The embodiment of the present application further provides a terminal, including: a processor; a memory of instructions, wherein the processor is configured to: receive a touch event sent by another terminal for reverse control; identify a gesture event according to the touch event, and determine an element to be reversely controlled; The element is an element in an HTML page that is configured with HTML parameters in accordance with the gesture event such that the element is processed in response to the gesture event in response to the HTML parameter.

It should be noted that in the description of the present invention, the terms "first", "second" and the like are used for descriptive purposes only, and are not to be construed as indicating or implying relative importance. Moreover, in the description of the present invention, unless otherwise It has been stated that the meaning of "multiple" means at least two.

Any process or method description in the flowcharts or otherwise described herein may be understood to represent a module, segment or portion of code that includes one or more executable instructions for implementing the steps of a particular logical function or process. And the scope of the preferred embodiments of the invention includes additional implementations, in which the functions may be performed in a substantially simultaneous manner or in an opposite order depending on the functions involved, in the order shown or discussed. It will be understood by those skilled in the art to which the embodiments of the present invention pertain.

It should be understood that portions of the invention may be implemented in hardware, software, firmware or a combination thereof. In the above-described embodiments, multiple steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented by any one or combination of the following techniques well known in the art: having logic gates for implementing logic functions on data signals. Discrete logic circuits, application specific integrated circuits with suitable combinational logic gates, programmable gate arrays (PGAs), field programmable gate arrays (FPGAs), etc.

One of ordinary skill in the art can understand that all or part of the steps carried by the method of implementing the above embodiments can be completed by a program to instruct related hardware, and the program can be stored in a computer readable storage medium. When executed, one or a combination of the steps of the method embodiments is included.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing module, or each unit may exist physically separately, or two or more units may be integrated into one module. in. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. The integrated modules, if implemented in the form of software functional modules and sold or used as stand-alone products, may also be stored in a computer readable storage medium.

The above mentioned storage medium may be a read only memory, a magnetic disk or an optical disk or the like.

In the description of the present specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" and the like means a specific feature described in connection with the embodiment or example. A structure, material or feature is included in at least one embodiment or example of the invention. In the present specification, the schematic representation of the above terms does not necessarily mean the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in a suitable manner in any one or more embodiments or examples.

Although the embodiments of the present invention have been shown and described, it is understood that the above-described embodiments are illustrative and are not to be construed as limiting the scope of the invention. The embodiments are subject to variations, modifications, substitutions and variations.

Claims

A method for inversely controlling a mobile page, which is characterized by comprising:

Receiving touch events sent by other terminals for reverse control;

Identifying a gesture event according to the touch event, and determining an element to be reversely controlled;

If the element is an element in an HTML page, an HTML parameter is configured for the element in accordance with the gesture event such that the element is processed in response to the gesture event in response to the gesture parameter.
The method of claim 1 wherein

The touch event includes: a press event, a move event, and a release event;

The gesture events include: a click event, a double click event, a long press event, and a drag event.
The method according to claim 2, wherein the recognizing the gesture event according to the touch event comprises:

Upon receiving the touch event, recognition of a click event, a double click event, a long press event, and a drag event is simultaneously initiated.
The method according to any one of claims 2-3, wherein, when the click event is recognized, the recognizing the gesture event according to the touch event comprises:

If the received touch event is a press event, an event is pushed onto the stack for the press event;

If the received touch event is a moving event, it is determined whether the moving distance is less than a preset distance value, and if it is less, the event is pushed onto the stack;

If the received touch event is a release event, it is determined whether the startup time is within a preset range, and if it is within the preset range, it is determined that the click event is recognized.
The method according to any one of claims 2 to 4, wherein, when the double-click event is recognized, the recognizing the gesture event according to the touch event comprises:

Identify click events;

Determine if the last click event is not empty;

If it is not empty, calculate a difference between the current time and the time of the last click event, and determine whether the difference is less than a preset time interval;

If it is less than, the time of the last click event is updated to null and it is determined that the double-click event is recognized.
The method according to any one of claims 2 to 5, wherein, when recognizing a long press event, the recognizing a gesture event according to the touch event comprises:

If the received touch event is a press event, an event is pushed onto the stack for the press event;

If the received touch event is a moving event, it is determined whether the moving distance is less than a second preset distance value, and if it is less, determining whether the starting time is greater than a preset duration; if greater than, determining to identify a long press event;

If the received touch event is a release event, the identification ends.
The method according to any one of claims 2-6, wherein, when the drag event is recognized, the drag event includes: a drag start event, a drag progress event, and a drag end event, the basis The touch event identifies a gesture event, including:

If the received touch event is a press event, the event is pushed onto the stack, and the control corresponding to the position coordinate of the pressed event is acquired, and when the space is a draggable control, the drag start event is sent;

If the received touch event is a moving event, the event is pushed onto the mobile event, and the position coordinate of the moving event is determined to be inside the draggable control, and if it is internal, the dragging event is sent;

If the received touch event is a release event, an event is pushed onto the stack, and a position of the release event is determined to be inside the draggable control, and if it is internal, a drag end event is sent.
The method according to any one of claims 1 to 7, wherein the configuring the HTML parameter for the element according to the gesture event comprises:

If the gesture event is a click event, according to the mark information of the element in the HTML page in advance, starting from the element corresponding to the position coordinate of the click event, the bottom-up search type is a controllable element, and the type is found. After being a controllable element, bind the element to a click event in an HTML page.
The method according to any one of claims 1-8, wherein the configuring the HTML parameter for the element according to the gesture event comprises:

If the gesture event is a drag event, starting from an element corresponding to the position coordinate of the drag event, searching for a scrollable element from bottom to top, and after finding the scrollable element, determining whether the element further satisfies the following conditions: Any of the following:

The element is a top element, and the size of the element is larger than a view size; or,

The element is a normal element, and the size of the element is larger than the size of the parent element of the element;

If the element is a scrollable element and also satisfies any of the above conditions, the scrolling parameter in the HTML page is configured for the element according to the moving distance of the drag event.
The method of any of claims 1-9, further comprising:

Determining whether the element to be reversely controlled is an element in an HTML page;

If the element to be back-controlled is an interactive native control, the recognized gesture event is sent to the interactive native control such that the interactive native control responds to the gesture event.
A device for controlling a mobile page in reverse, comprising:

a communication module, configured to receive a touch event sent by another terminal for reverse control;

a gesture recognition module, configured to identify a gesture event according to the touch event, and determine an element to be reversely controlled;

And a conversion module, configured to configure an HTML parameter for the element according to the gesture event, if the element is an element in an HTML page, to cause the element to process according to the HTML parameter in response to the gesture event.
The device according to claim 11, wherein the touch event comprises: a press event, a move event, and a release event; the gesture event includes: a click event, a double click event, a long press event, and a drag event The gesture recognition module is specifically configured to:

When the touch event is received, a click event, a double click event, a long press event, and The identification of the drag event.
The device according to any one of claims 11 to 12, wherein the gesture recognition module comprises a first unit for identifying a click event, the first unit for:

If the received touch event is a press event, an event is pushed onto the stack for the press event;

If the received touch event is a moving event, it is determined whether the moving distance is less than a preset distance value, and if it is less, the event is pushed onto the stack;

If the received touch event is a release event, it is determined whether the startup time is within a preset range, and if it is within the preset range, it is determined that the click event is recognized.
The device according to any one of claims 11 to 13, wherein the gesture recognition module comprises a second unit for identifying a double click event, the second unit for:

Identify click events;

Determine if the last click event is not empty;

If it is not empty, calculate a difference between the current time and the time of the last click event, and determine whether the difference is less than a preset time interval;

If it is less than, the time of the last click event is updated to null and it is determined that the double-click event is recognized.
The device according to any one of claims 11-14, wherein the gesture recognition module comprises a third unit for identifying a long press event, the third unit for:

If the received touch event is a press event, an event is pushed onto the stack for the press event;

If the received touch event is a moving event, determining whether the moving distance is less than a second preset distance value, If it is smaller, it is determined whether the startup time is greater than a preset duration; if it is greater, it is determined that a long press event is recognized;

If the received touch event is a release event, the identification ends.
The device according to any one of claims 11-15, wherein the drag event comprises: a drag start event, a drag progress event, and a drag end event, the gesture recognition module includes The fourth unit of the event, the fourth unit is used to:

If the received touch event is a press event, the event is pushed onto the stack, and the control corresponding to the position coordinate of the pressed event is acquired, and when the space is a draggable control, the drag start event is sent;

If the received touch event is a moving event, the event is pushed onto the mobile event, and the position coordinate of the moving event is determined to be inside the draggable control, and if it is internal, the dragging event is sent;

If the received touch event is a release event, an event is pushed onto the stack, and a position of the release event is determined to be inside the draggable control, and if it is internal, a drag end event is sent.
The device according to any one of claims 11 to 16, wherein the conversion module is configured to configure HTML parameters for the element according to the gesture event, including:

If the gesture event is a click event, according to the mark information of the element in the HTML page in advance, starting from the element corresponding to the position coordinate of the click event, the bottom-up search type is a controllable element, and the type is found. After being a controllable element, tie the element to a click event in the HTML page set.
The device according to any one of claims 11-17, wherein the conversion module is configured to configure HTML parameters for the element according to the gesture event, including:

If the gesture event is a drag event, starting from an element corresponding to the position coordinate of the drag event, searching for a scrollable element from bottom to top, and after finding the scrollable element, determining whether the element further satisfies the following conditions: Any of the following:

The element is a top element, and the size of the element is larger than a view size; or,

The element is a normal element, and the size of the element is larger than the size of the parent element of the element;

If the element is a scrollable element and also satisfies any of the above conditions, the scrolling parameter in the HTML page is configured for the element according to the moving distance of the drag event.
The device according to any one of claims 11 to 18, further comprising:

An event distribution module, configured to determine whether an element to be reversely controlled is an element in an HTML page, and when the element is an element in an HTML page, send the gesture event to the conversion module, where the element When the native control is interactive, the gesture event is sent to the interaction module;

And an interaction module, configured to send the received gesture event to the interactive native control, so that the interactive native control responds to the gesture event.
A terminal, comprising: a processor; a memory for storing processor-executable instructions; wherein the processor is configured to:

Receiving touch events sent by other terminals for reverse control;

Identifying a gesture event according to the touch event, and determining an element to be reversely controlled;

If the element is an element in an HTML page, an HTML parameter is configured for the element in accordance with the gesture event such that the element is processed in response to the gesture event in response to the gesture parameter.
A non-transitory computer readable storage medium characterized by enabling a terminal to perform a method of back-controlling a mobile page when the instructions in the storage medium are executed by a processor of the terminal, the method comprising :

Receiving touch events sent by other terminals for reverse control;

Identifying a gesture event according to the touch event, and determining an element to be reversely controlled;

If the element is an element in an HTML page, an HTML parameter is configured for the element in accordance with the gesture event such that the element is processed in response to the gesture event in response to the gesture parameter.
A computer program product, wherein when an instruction in the computer program product is executed by a processor, a method of back-controlling a mobile page is performed, the method comprising:

Receiving touch events sent by other terminals for reverse control;

Identifying a gesture event according to the touch event, and determining an element to be reversely controlled;

If the element is an element in an HTML page, an HTML parameter is configured for the element in accordance with the gesture event such that the element is processed in response to the gesture event in response to the gesture parameter.