CN106843708A

CN106843708A - Electronic equipment and method for deleting object

Info

Publication number: CN106843708A
Application number: CN201510883748.5A
Authority: CN
Inventors: 梁德胜
Original assignee: Huawei Device Dongguan Co Ltd
Current assignee: Huawei Device Co Ltd
Priority date: 2015-12-03
Filing date: 2015-12-03
Publication date: 2017-06-13
Also published as: WO2017092680A1

Abstract

A kind of electronic equipment and method for deleting object is the embodiment of the invention provides, is related to data processing field.The method includes：At least one object interface element, the object of at least one object interface elements correlation at least one are shown in display screen；The gesture at least one object interface element is detected in Touch sensitive surface, the gesture includes gesture speed information and gestures direction information；When the gesture speed and gestures direction meet predetermined condition, at least one object is deleted.Cause that electronic equipment is more smooth with interacting for user by the technical scheme, improve the efficiency that electronic equipment processes affairs.

Description

Electronic device and method for deleting object

Technical Field

This document relates to electronic devices with touch-sensitive surfaces, including but not limited to electronic devices with touch-sensitive surfaces for mobile application interface elements (application interface elements) and methods.

Background

In recent years, the use of portable electronic devices with touch sensitive surfaces has increased dramatically. Such portable electronic devices have greatly increased the number of applications or "apps". For example, image and video camera applications provide content generation opportunities for users, such as taking pictures or recording videos. The notes application allows the user to read or write down notes. An application program may correspond to an application interface element on a graphical user interface of a portable electronic device. Such application interface elements are sometimes also referred to as: an application icon (app icon), an application shortcut (app shortcut), an application button (appbutton), an application tool (app widget), and the like. As shown in fig. 1, a method for deleting an application or a file in an electronic device in the prior art is as follows: firstly, a user presses an icon of an application program or a file to be deleted for a long time, the electronic equipment displays a trash can icon, the user continues to drag the icon until the trash can icon is covered, then the user releases the finger, the electronic equipment pops up a dialog box to prompt the user whether to delete the application program or the file, and the user confirms manually. Therefore, the above-mentioned manner of deleting the application is very complicated and time-consuming, which significantly reduces the intelligent interaction capability of the electronic device with the user.

Disclosure of Invention

Accordingly, there is a need for faster and more efficient methods and interfaces for electronic devices to interact with users, improving the transaction processing capabilities of the electronic devices. Such methods and interfaces may supplement or replace conventional methods of managing application interface elements. Such methods and interfaces may respond more quickly and intelligently to a user's personality needs, help the user use less time to achieve substantially the same effect of managing application interface elements, and create a more efficient human-machine interface. For battery-powered devices, such methods and interfaces can conserve power and can increase the time between battery charges.

Some embodiments herein provide the above-described methods and user interfaces through the disclosed devices. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a laptop, tablet, or handheld device, or a wearable device). In some embodiments, the device has a trackpad. In some embodiments, the device has a touch-sensitive display (also referred to as a "touchscreen," "touchscreen display," or "display with a touch-sensitive surface"). In some embodiments, an apparatus has a Graphical User Interface (GUI), one or more processors, memory, and one or more modules, programs, or sets of instructions stored in the memory for performing a plurality of functions. In some embodiments, the user interacts with the GUI primarily through finger contacts and/or gestures on the touch-sensitive surface. In some embodiments, these functions may include image editing, drawing, rendering, word processing, web page creation, disc editing, spreadsheet making, game playing, answering a telephone call, video conferencing, emailing, instant messaging, exercise support, digital photography, digital video recording, web browsing, digital music playing, and/or digital video playing. Executable instructions for performing these functions may be included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.

In a first aspect, an embodiment of the present invention provides a portable electronic device. The apparatus comprises: a display, wherein the display comprises a touch-sensitive surface and a display screen; one or more processors; a memory; a plurality of application programs; and one or more programs. The one or more programs are stored in the memory and configured to be executed by the one or more processors. The one or more programs include instructions. The instructions are for: displaying at least one object interface element on the display screen, the at least one object interface element being associated with at least one object; detecting, at the touch-sensitive surface, a gesture for the at least one object interface element, the gesture comprising a gesture speed and a gesture direction; and when the gesture speed and the gesture direction meet the preset conditions, deleting the at least one object. Therefore, the individual requirements of the user can be responded more quickly and intelligently, the manual operation of the user is reduced, the transaction processing efficiency of the electronic equipment is greatly improved, and the electric power is also saved.

With reference to the first aspect, in a first possible implementation manner of the first aspect, the object interface element specifically includes: an application interface element or a file interface element, the application interface element being associated with an application program, the file interface element being associated with file data.

With reference to the first implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the predetermined condition specifically includes: the gesture speed is greater than or equal to a predetermined threshold and the gesture direction information is to the right of the display screen.

With reference to the second implementation manner of the first aspect, in a third possible implementation manner of the first aspect, when the gesture speed information is smaller than the predetermined threshold, the at least one object interface element is moved according to the detected gesture.

With reference to the first aspect, in a fourth possible implementation manner of the first aspect, before the touch-sensitive surface detects the gesture with respect to the at least one object interface element, the method includes: determining whether the at least one object is deletable: detecting a gesture at the touch-sensitive surface for the at least one object interface element if the at least one object is deletable; if the at least one object is undeletable, prompting the user.

With reference to the first aspect or the fourth implementation manner of the first aspect, in a fifth possible implementation manner of the first aspect, the at least one object interface element is specifically a first application interface element and a second application interface element, the first application interface element is associated with a first application, and the second application interface element is associated with a second application; wherein the detecting a gesture for the at least one object interface element on the touch-sensitive surface, and deleting the at least one object when the gesture speed and the gesture direction satisfy predetermined conditions, specifically: detecting, at the touch-sensitive surface, gestures for the first application interface element and the second application interface element; and when the gesture speed and the gesture direction meet preset conditions, uninstalling the first application program and the second application program.

With reference to the first aspect or the fourth implementation manner of the first aspect, in a sixth possible implementation manner of the first aspect, the at least one object interface element is specifically a first file interface element and a second file interface element, the first file interface element is associated with first file data, and the second file interface element is associated with second file data; wherein the detecting a gesture for the at least one object interface element on the touch-sensitive surface, and deleting the at least one object when the gesture speed and the gesture direction satisfy predetermined conditions, specifically: detecting, at the touch-sensitive surface, gestures for the first file interface element and the second file interface element; and when the gesture speed and the gesture direction meet preset conditions, erasing the first file data and the second file data.

With reference to the first aspect or the fourth implementation manner of the first aspect, in a seventh possible implementation manner of the first aspect, the at least one object interface element is specifically a third file interface element and a fourth application interface element, the third file interface element is associated with third file data, and the fourth application interface element is associated with a fourth application program; wherein the detecting a gesture for the at least one object interface element on the touch-sensitive surface, and deleting the at least one object when the gesture speed and the gesture direction satisfy predetermined conditions, specifically: detecting, at the touch-sensitive surface, gestures for the third file interface element and the fourth application interface element; and when the gesture speed and the gesture direction meet preset conditions, erasing the third file data and uninstalling the fourth application program.

In a second aspect, the present embodiments provide a method for deleting an object for a portable electronic device comprising a display and a plurality of applications, wherein the display comprises a touch-sensitive surface and a display screen, the method comprising: displaying at least one object interface element on the display screen, the at least one object interface element being associated with at least one object; detecting, at the touch-sensitive surface, a gesture for the at least one object interface element, the gesture comprising gesture speed information and gesture direction information; and when the gesture speed and the gesture direction meet the preset conditions, deleting the at least one object.

With reference to the second aspect, in a first possible embodiment of the second aspect, the object interface element specifically includes: an application interface element or a file interface element, the application interface element being associated with an application program, the file interface element being associated with file data.

With reference to the first embodiment of the second aspect, in a second possible embodiment of the second aspect, the predetermined condition specifically includes: the gesture speed is greater than or equal to a predetermined threshold and the gesture direction information is to the right of the display screen.

In combination with the second embodiment of the second aspect, in a third possible embodiment of the second aspect, the at least one object interface element is moved in accordance with the detected gesture when the gesture speed information is less than the predetermined threshold.

With reference to the second aspect or the second embodiment of the second aspect, in a fourth possible embodiment of the second aspect, before the touch-sensitive surface detects the gesture with respect to the at least one object interface element, the method includes: determining whether the at least one object is deletable: detecting a gesture at the touch-sensitive surface for the at least one object interface element if the at least one object is deletable; if the at least one object is undeletable, prompting the user.

With reference to the second aspect or the second embodiment of the second aspect, in a fifth possible embodiment of the second aspect, the at least one object interface element is specifically a first application interface element and a second application interface element, the first application interface element is associated with a first application, and the second application interface element is associated with a second application; wherein the detecting a gesture for the at least one object interface element on the touch-sensitive surface, and deleting the at least one object when the gesture speed and the gesture direction satisfy predetermined conditions, specifically: detecting, at the touch-sensitive surface, gestures for the first application interface element and the second application interface element; and when the gesture speed and the gesture direction meet preset conditions, uninstalling the first application program and the second application program.

With reference to the second aspect or the second embodiment of the second aspect, in a sixth possible embodiment of the second aspect, the at least one object interface element is specifically a first file interface element and a second file interface element, the first file interface element is associated with first file data, and the second file interface element is associated with second file data; wherein the detecting a gesture for the at least one object interface element on the touch-sensitive surface, and deleting the at least one object when the gesture speed and the gesture direction satisfy predetermined conditions, specifically: detecting, at the touch-sensitive surface, gestures for the first file interface element and the second file interface element; and when the gesture speed and the gesture direction meet preset conditions, erasing the first file data and the second file data.

With reference to the second aspect or the second embodiment of the second aspect, in a seventh possible embodiment of the second aspect, the at least one object interface element is specifically a third file interface element and a fourth application interface element, the third file interface element is associated with third file data, and the fourth application interface element is associated with a fourth application program; wherein the detecting a gesture for the at least one object interface element on the touch-sensitive surface, and deleting the at least one object when the gesture speed and the gesture direction satisfy predetermined conditions, specifically: detecting, at the touch-sensitive surface, gestures for the third file interface element and the fourth application interface element; and when the gesture speed and the gesture direction meet preset conditions, erasing the third file data and uninstalling the fourth application program.

In a third aspect, an embodiment of the present invention provides an electronic device. The electronic device specifically includes: a touch-sensitive display unit to detect a user's gesture with respect to an object interface element, the gesture including a gesture speed and a gesture direction, the object interface element including an application interface element and a file interface element; the processing unit is used for acquiring the gesture of the touch-sensitive display unit and judging whether the gesture meets a preset condition: and if the processing unit judges that the gesture meets the preset condition, deleting the object associated with the object interface element.

With reference to the third aspect, in a first possible embodiment of the third aspect, the predetermined condition specifically includes: the gesture speed is greater than or equal to a predetermined threshold and the gesture direction information is to the right of the display screen.

With reference to the first embodiment of the third aspect, in a second possible embodiment of the third aspect, before the touch-sensitive display unit detects the gesture with respect to the object interface element, the processing unit is further configured to: judging whether the object can be deleted: if the object is deletable, the touch-sensitive display unit detecting a gesture for an object interface element; if the object is undeletable, the user is prompted.

Based on the technical scheme, the electronic equipment can provide a more friendly method and a user interface for a user, and realizes the function of uninstalling a specific application program or erasing a specific file. At the same time, this also helps the user to use less time to achieve substantially the same effect of managing application interface elements and creates a more efficient human-machine interface. For battery-powered devices, such methods and interfaces can conserve power and can increase the time between battery charges. For battery-powered devices, such methods and interfaces can conserve power and can increase the time between battery charges.

Drawings

For a better understanding of the foregoing embodiments of the invention, as well as additional embodiments thereof, reference should be made to the following description of the embodiments taken in conjunction with the following drawings, wherein like reference numerals designate corresponding parts throughout the figures.

Fig. 1 is a graphical user interface showing how applications are deleted in the prior art.

FIG. 2A is a block diagram illustrating a portable electronic device with a touch-sensitive display in accordance with some embodiments.

FIG. 2B is a block diagram illustrating exemplary components for event processing according to some embodiments.

FIG. 3 illustrates a portable electronic device having a touch screen in accordance with some embodiments.

FIG. 4 is a block diagram of an exemplary electronic device with a display and a touch-sensitive surface in accordance with some embodiments.

FIG. 5 illustrates an exemplary graphical user interface for an application menu on a portable electronic device according to some embodiments.

6A-6C illustrate an exemplary graphical user interface for uninstalling an application interface element according to some embodiments.

Fig. 7A, 7B illustrate an exemplary graphical user interface for deleting a plurality of object interface elements, according to some embodiments.

FIG. 8 illustrates a functional block diagram of an electronic device according to some embodiments.

Detailed Description

Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail as not to unnecessarily obscure aspects of the embodiments.

The terminology used in the embodiments of the invention is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the examples of the present invention and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

It will also be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first application interface element may be named a second application interface element, and similarly, a second application interface element may be named a first application interface element without departing from the scope of the present invention.

It will also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

As used herein, the term "if" may be interpreted to mean "when.. or" after.. or "in response to a determination" or "in response to a detection," depending on the context. Similarly, the phrase "if it is determined," or "if [ a stated condition or event ] is detected," may be interpreted to mean "upon determining" or "in response to determining.

Embodiments of an electronic device, a user interface for such a device, and an associated process for using such a device are presented. In some embodiments, the electronic device is a portable electronic device, such as a mobile telephone, that also contains other functions, such as personal digital assistant and/or music player functions. Exemplary embodiments of the electronic device include, but are not limited to, a mountOr other operating system. Other electronic devices, such as laptop computers or tablet computers with touch sensitive surfaces (e.g., touch screen displays and/or touch pads) may also be used. It should also be understood that in some embodiments, the electronic device is not a portable electronic device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touch pad).

In the following discussion, an electronic device including a display and a touch-sensitive surface is presented. It should be understood, however, that the electronic device may include one or more other physical user interface devices, such as a physical keyboard, mouse, and/or joystick.

Electronic devices typically support a variety of applications, such as one or more of the following: a drawing application, a rendering application, a word processing application, a web page creation application, a disc editing application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an email application, an instant messaging application, an exercise support application, a photo management application (i.e., an image management application), a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.

Various applications executable on the electronic device may use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the device may be adjusted and/or varied from one application to the next and/or within the corresponding application. In this way, a common physical architecture of the electronic device (such as a touch-sensitive surface) may support various applications with a user interface that is intuitive and clear to the user.

Attention is now directed to embodiments of portable communication devices having touch sensitive displays. FIG. 2A is a block diagram illustrating a portable communication device 100 with a touch-sensitive display 112 in accordance with some embodiments. Touch-sensitive display 112 is sometimes referred to as a "touch screen" for convenience, and may also be referred to as or as a touch-sensitive display system, and may also be referred to as a display system having a touch-sensitive surface (touch-sensitive surface) and a display screen (display). Device 100 may include memory 102 (which may include one or more computer-readable storage media), a memory controller 122, one or more Central Processing Units (CPUs) 120, a peripheral interface 118, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input/output (I/O) subsystem 106, other input control devices 116, and an external port 124. The device 100 may include one or more optical sensors 164. These components may communicate over one or more communication buses or signal lines 103.

It should be understood that device 100 is only one example of a portable electronic device and that device 100 may have more or fewer components than shown, may combine two or more components, or may have a different configuration or arrangement of components. The various components shown in fig. 2A may be implemented in hardware, software, or a combination of software and hardware, including one or more signal processing and/or application specific integrated circuits.

The memory 102 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 102 by other components of device 100, such as CPU120 and peripheral interface 118, may be controlled by memory controller 122.

Peripheral interface 118 may be used to couple input and output peripherals of the device to CPU120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in the memory 102 to perform various functions of the device 100 and to process data. In some embodiments, the one or more processors 120 include an image signal processor and a dual or multi-core processor.

In some embodiments, peripherals interface 118, CPU120, and memory controller 122 may be implemented on a single chip, such as chip 104. In some other embodiments, they may be implemented on separate chips.

RF (radio frequency) circuitry 108 receives and transmits RF signals, also called electromagnetic signals. The RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communication networks and other communication devices via electromagnetic signals. RF circuitry 108 may include well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a codec chipset, a Subscriber Identity Module (SIM) card, memory, and so forth. RF circuitry 108 may communicate with networks, such as the internet (also known as the World Wide Web (WWW)), intranets, and/or wireless networks, such as cellular telephone networks, wireless Local Area Networks (LANs), and/or Metropolitan Area Networks (MANs), as well as other devices via wireless communications. The wireless communication may use any of a variety of communication standards, protocols, and technologies, including, but not limited to, Global System for Mobile communications (GSM), Enhanced Data GSM Environment (EDGE), High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), wideband code division multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Wireless Fidelity (WI-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, and/or IEEE 802.11n), Voice over Internet protocol (VoIP), WI-MAX, email protocols (e.g., Internet Message Access Protocol (IMAP) and/or Post Office Protocol (POP)), instant messages (e.g., extensible Messaging field protocol (XMPP), Session initiation protocol for instant messaging and field utilization extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), (IMPS), And/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed on the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. The audio circuitry 110 receives audio data from the peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to the speaker 111. The speaker 111 converts the electrical signals into human-audible sound waves. The audio circuitry 110 also receives electrical signals converted by the microphone 113 from sound waves. The audio circuitry 110 converts the electrical signals to audio data and transmits the audio data to the peripheral interface 118 for processing. Audio data may be retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripheral interface 118. In some embodiments, the audio circuitry 110 also includes a headset jack (e.g., 212 in fig. 3). The headset jack provides an interface between the audio circuitry 110 and removable audio input/output peripherals, such as output-only headphones or a headset with both output (e.g., monaural or binaural headphones) and input (e.g., microphone).

The I/O subsystem 106 couples input/output peripheral devices on the device 100, such as the touch screen 112 and other input control devices 116, to a peripheral interface 118. The I/O subsystem 106 may include a display controller 156 and one or more input controllers 160 for other input control devices. The one or more input controllers 160 receive/transmit electrical signals from/to other input control devices 116. The other input control devices 116 may include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, and the like. In some alternative embodiments, the input controller 160 may be coupled (or not coupled) to any of: a keyboard, an infrared port, a USB port, and a pointing device such as a mouse. The one or more buttons (e.g., 208 in fig. 3) may include up/down buttons for volume control of the speaker 111 and/or microphone 113. The one or more buttons may include a push button (e.g., 206 in fig. 3).

Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives electrical signals from touch screen 112 and/or transmits electrical signals to touch screen 112. Touch screen 112 displays visual output to a user. The visual output may include graphics, text, icons, video, and any combination thereof (collectively "graphics"). In some embodiments, some or all of the visual output may correspond to a user interface object.

Touch screen 112 has a touch-sensitive surface, sensor, or group of sensors that accept input from a user based on tactile sensation and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and convert the detected contact into interaction with user interface objects (e.g., one or more soft keys, icons, web pages, or images) displayed on touch screen 112. In an exemplary embodiment, the point of contact between touch screen 112 and the user corresponds to a finger of the user. Without being particularly described, the touch screen 112 in the embodiment of the present invention specifically refers to a touch-sensitive display system having a touch-sensitive surface and a display screen.

The touch screen 112 may use LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies may be used in other embodiments. Touch screen 112 and display controller 156 may detect contact and any movement or breaking thereof using any of a variety of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used.

The touch screen 112 may have a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user may make contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which may be less accurate than stylus-based input due to the larger contact area of the finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command to perform the action desired by the user.

In some embodiments, in addition to a touch screen, device 100 may include a trackpad (not shown) for activating or deactivating particular functions. In some embodiments, the trackpad is a touch-sensitive area of the device that, unlike a touchscreen, does not display visual output. The trackpad may be a touch-sensitive surface separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.

The device 100 also includes a power system 162,. The power system 162 may include a power management system, one or more power sources (e.g., battery, Alternating Current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a Light Emitting Diode (LED)) and any other components associated with the generation, management and distribution of power in a portable device.

The device 100 may also include one or more optical sensors 164. FIG. 2A shows an optical sensor coupled to an optical sensor controller 158 in the I/O subsystem 106. The optical sensor 164 may include a Charge Coupled Device (CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The optical sensor 164 receives light from the environment projected through one or more lenses and converts the light into data representing an image. In conjunction with imaging module 143 (also referred to as a camera module), optical sensor 164 may capture still images or video. In some embodiments, one or more optical sensors are located on the back of device 100, opposite touch screen display 112 on the front of the device, so that the touch screen display can be used as a viewfinder for still and/or video image capture. In some embodiments, another one or more optical sensors are located on the front of the device so that a user can obtain images of the user for video conferencing while viewing other video conference participants on the touch screen display.

The device 100 may also include one or more proximity sensors 166. Fig. 2A shows a proximity sensor 166 coupled to the peripheral interface 118. Alternatively, the proximity sensor 166 may be coupled to the input controller 160 in the I/O subsystem 106. In some embodiments, the proximity sensor turns off and disables the touch screen 112 when the electronic device is placed near the user's ear (e.g., when the user is making a phone call).

Device 100 may also include one or more accelerometers 168. Fig. 2A shows accelerometer 168 coupled to peripheral interface 118. Alternatively, accelerometer 168 may be coupled to input controller 160 in I/O subsystem 106. In some embodiments, the information is displayed in a portrait view or a landscape view on the touch screen display based on an analysis of the data received from the one or more accelerometers. The device 100 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or beidou or other global navigation system) receiver (not shown) in addition to the accelerometer 168 for obtaining information about the position and orientation (e.g., portrait or landscape) of the device 100.

In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or set of instructions) 128, a contact/movement module (or set of instructions) 130, a graphics module (or set of instructions) 132, a text input module (or set of instructions) 134, a Global Positioning System (GPS) module (or set of instructions) 135, and an application program (or set of instructions) 136. Further, in some embodiments, memory 102 stores device/global internal state 157, as shown in fig. 2A and 3. Device/global internal state 157 includes one or more of: an active application state indicating which applications (if any) are currently active; display state indicating what applications, views, or other information occupy various areas of the touch screen display 112; sensor status, including information obtained from the various sensors of the device and the input control device 116; and position information about the position and attitude of the device.

The operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, ANDROID, or an embedded operating system such as Vx Works) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between the various hardware and software components. Further, in some embodiments, the memory 102 stores digital camera film 159 and digital image pipeline 161.

The communication module 128 facilitates communication with other devices through one or more external ports 124, and also includes various software components for processing data received by the RF circuitry 108 and/or the external ports 124. An external port 124 (e.g., Universal Serial Bus (USB), firewire, etc.) is adapted to couple directly to other devices or indirectly through a network (e.g., the internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as or similar to and/or compatible with a 30-pin connector used on iPod (trademark of Apple inc.) devices.

The contact/movement module 130 may detect contact with the touch screen 112 (in conjunction with the display controller 156) and other touch sensitive devices (e.g., a trackpad or physical click wheel). The contact/movement module 130 includes a number of software components for performing various operations related to contact detection, such as determining whether a contact has occurred (e.g., detecting a finger-down event), determining whether there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining whether the contact has terminated (e.g., detecting a finger-up event or a break in contact). The contact/movement module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact may include determining velocity (magnitude), velocity (magnitude and direction), and/or acceleration (change in magnitude and/or direction) of the point of contact, the movement of the point of contact being represented by a series of contact data. These operations may be applied to single point contacts (e.g., one finger contact) or multiple point simultaneous contacts (e.g., "multi-touch"/multiple finger contacts). In some embodiments, the contact/movement module 130 and the display controller 156 detect contact on a touch pad.

The contact/movement module 130 may detect a gesture input by the user. Different gestures on the touch-sensitive surface have different contact patterns. Thus, gestures may be detected by detecting specific contact patterns. For example, detecting a single-finger tap gesture includes detecting a finger-down event, and then detecting a finger-up (lift-off) event at the same location (or substantially the same location) as the finger-down event (e.g., at an icon location). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event, then detecting one or more finger-dragging events, and then subsequently detecting a finger-up (lift-off) event.

Graphics module 132 includes a number of known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the intensity of the displayed graphics. As used herein, the term "object" includes any object that may be displayed to a user, including without limitation text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations and the like.

In some embodiments, the graphics module 132 stores data representing graphics to be used. Each graphic may be assigned a corresponding code. The graphics module 132 receives one or more codes specifying graphics to be displayed from an application program or the like, and also receives coordinate data and other graphics attribute data together if necessary, and then generates screen image data to output to the display controller 156.

Text input module 134, which may be a component of graphics module 132, provides a soft keyboard for entering text in a variety of applications, such as contacts 137, email 140, instant message 141, browser 147, and any other application that requires text input.

The GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to the phone 138 for location-based dialing, to the camera 143 as picture/video metadata, and to applications that provide location-based services, such as weather desktop applets, local yellow pages desktop applets, and map/navigation desktop applets).

Application 136 may include the following modules (or sets of instructions), or a subset or superset thereof:

● contact module 137 (sometimes also referred to as a contact list or contact list);

● a telephone module 138;

● video conferencing module 139;

● e-mail client module 140;

● Instant Messaging (IM) module 141;

● exercise support module 142;

● camera module 143 for still and/or video images;

● an image management module 144;

● browser module 147;

● calendar module 148;

● desktop applet modules 149, which may include one or more of the following: a weather desktop applet 149-1, a stock market desktop applet 149-2, a calculator desktop applet 149-3, an alarm desktop applet 149-4, a dictionary desktop applet 149-5, and other desktop applets obtained by the user, and a user created desktop applet 149-6;

● a desktop applet creator module 150 for generating a user-created desktop applet 149-6;

● search module 151;

● video and music player module 152, which may be comprised of a video player module and a music player module;

● note module 153;

● map module 154;

● online video module 155;

● sound/audio recorder module 163; and/or

● notification module 165.

Examples of other applications 136 that may be stored in memory 102 include other word processing applications, other image editing applications, drawing applications, rendering applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.

In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, contacts module 137 may be used to manage contact lists or contact lists (e.g., stored in memory 102 or in memory 370 in application internal state 192 of contacts module 137), including: adding a name to the address book; deleting names from the address book; associating a telephone number, email address, physical address, or other information with a name; associating the image with a name; classifying and classifying names; providing a telephone number or email address to initiate and/or facilitate communication through telephone 138, video conference 139, email 140, or IM 141; and so on.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, phone module 138 may be used to enter a sequence of characters corresponding to a phone number, access one or more phone numbers in address book 137, modify an already entered phone number, dial a corresponding phone number, conduct a call, and disconnect or hang up when the call is completed. As described above, wireless communication may use any of a number of communication standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephony module 138, video conference module 139 includes executable instructions for initiating, conducting, and ending a video conference between a user and one or more other participants according to user instructions.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, email client module 140 includes executable instructions for creating, sending, receiving, and managing emails in response to user instructions. In conjunction with the image management module 144, the email client module 140 makes it very easy to create and send an email with a still image or a video image captured by the camera module 143.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, instant message module 141 includes executable instructions for inputting a sequence of characters corresponding to an instant message, modifying previously input characters, transmitting a corresponding instant message (e.g., using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for a phone-based instant message or using XMPP, SIMPLE, or IMPS for an internet-based instant message), receiving an instant message, and viewing the received instant message. In some embodiments, the transmitted and/or received instant messages may include graphics, photos, audio files, video files, and/or other attachments supported in MMS and/or Enhanced Messaging Service (EMS). As used herein, "instant message" refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module 146, workout support module 142 includes executable instructions for creating workouts (e.g., with time, distance, and/or calorie consumption goals); communicating with an exercise sensor (sports device); receiving exercise sensor data; calibrating a sensor for monitoring an exercise; selecting and playing music for exercise; and displaying, storing and transmitting exercise data.

In conjunction with touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact module 130, graphics module 132, digital image pipeline 161 (which converts raw data from the optical sensor into a final image or video), and image management module 144, camera module 143 includes executable instructions for capturing and storing still images or videos (including video streams) into memory 102 (e.g., in digital camera film 159), modifying characteristics of the still images or videos, or deleting the still images or videos from memory 102 (e.g., from digital camera film 159).

In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions for arranging, modifying (e.g., editing), or otherwise manipulating, labeling, deleting, presenting (e.g., in a digital slide or album), and storing still and/or video images, including still and/or video images stored in camera film 159.

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions for browsing the internet (including searching, linking to, receiving, and displaying web pages or portions thereof, and attachments and other files linked to web pages) according to user instructions.

In conjunction with the RF circuitry 108, the touch screen 112, the display system controller 156, the contact module 130, the graphics module 132, the text input module 134, the email client module 140, and the browser module 147, the calendar module 148 includes executable instructions for creating, displaying, modifying, and storing a calendar and data associated with the calendar (e.g., calendar entries, to-do task lists, etc.) according to user instructions.

In conjunction with the RF circuitry 108, the touch screen 112, the display system controller 156, the contact module 130, the graphics module 132, the text input module 134, and the browser module 147, the desktop applet module 149 is a mini-application (e.g., a weather desktop applet 149-1, a stock market desktop applet 149-2, a calculator desktop applet 149-3, an alarm desktop applet 149-4, and a dictionary desktop applet 149-5) or a mini-application created by a user (e.g., a user created desktop applet 149-6) that may be downloaded and used by the user. In some embodiments, the desktop applet includes an HTML (HyperText markup language) file, a CSS (cascading Style sheet) file, and a JavaScript file. In some embodiments, the desktop applet includes an XML (extensible markup language) file and a JavaScript file (e.g., Yahoo! desktop applet).

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the desktop applet creator module 150 may be used by a user to create a desktop applet (e.g., to turn a user-specified portion of a web page into the desktop applet).

In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions for searching memory 102 for text, music, sound, images, videos, and/or other files that match one or more search criteria (e.g., one or more search terms specified by a user) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speakers 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow a user to download and playback recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, as well as executable instructions for displaying, rendering, or otherwise playing back video (e.g., on touch screen 112 or on an external display connected via external port 124). In some embodiments, the device 100 may include the functionality of an MP3 player.

In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions for creating and managing notes, to-do task lists, and the like according to user instructions.

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 may be used to receive, display, modify, and store maps and data associated with maps (e.g., driving routes; data for stores and other points of interest at or near a particular location; and other location-based data) according to user instructions.

In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, online video module 155 includes instructions that allow a user to access, browse, receive (e.g., stream and/or download), playback (e.g., on the touch screen or on an external display connected via external port 124), send emails with links to particular online videos, and otherwise manage online videos in one or more file formats, such as h.264. In some embodiments, the link to a particular online video is sent using instant messaging module 141 instead of email client module 140.

In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, and microphone 113, sound/audio recorder module 163 includes executable instructions that allow a user to record audio (e.g., sounds) in one or more file formats, such as MP3 or AAC files, and executable instructions for rendering or otherwise playing back the recorded audio files.

In conjunction with touch-screen 112, display system controller 156, contact module 130, and graphics module 132, notification module 165 includes executable instructions to display notifications or alerts (such as incoming messages or incoming calls, calendar event reminders, application events, and the like) on touch-screen 112.

Each of the modules and applications described above corresponds to a set of executable instructions for performing one or more of the functions described above as well as the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise rearranged in various embodiments. In some embodiments, memory 102 may store a subset of the modules and data structures described above. In addition, memory 102 may store additional modules and data structures not described above.

In some embodiments, device 100 is a device on which the operation of a predefined set of functions is performed exclusively through a touch screen and/or a trackpad. By using a touch screen and/or touch pad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 may be reduced.

The predefined set of functions that can be performed exclusively through the touch screen and/or the touch pad include navigation between user interfaces. In some embodiments, device 100 is navigated from any user interface that may be displayed on device 100 to a main menu, or root menu when the trackpad is touched by a user. In such embodiments, the touch pad may be referred to as a "menu button". In some other embodiments, the menu button may be a physical push button or other physical input control device rather than a touchpad.

FIG. 2B is a block diagram illustrating exemplary components for event processing according to some embodiments. In some embodiments, memory 102 (in FIG. 2A) or memory 370 (in FIG. 4) includes event classifier 170 (e.g., in operating system 126) and corresponding application 136-1 (e.g., any of the aforementioned applications 137 and 151, 155, 380 and 390).

Event sorter 170 receives the event information and determines application 136-1 and application view 191 of application 136-1 to which the event information is to be passed. The event sorter 170 includes an event monitor 171 and an event scheduler module 174. In some embodiments, the application 136-1 includes an application internal state 192, the application internal state 192 indicating a current application view that is displayed on the touch-sensitive display 112 when the application is active or executing. In some embodiments, the device/global internal state 157 is used by the event classifier 170 to determine which application(s) are currently active, and the application internal state 192 is used by the event classifier 170 to determine the application view 191 to which to pass event information.

In some embodiments, the application internal state 192 includes additional information, such as one or more of the following: resume information to be used when the application 136-1 resumes execution, user interface state information indicating information being displayed by the application 136-1 or information that is ready for display by the application 136-1, a state queue for enabling a user to return to a previous state or view of the application 136-1, and a repeat/undo queue of previous actions taken by the user.

Event monitor 171 receives event information from peripheral interface 118. The event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112 as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or sensors (such as proximity sensor 166), accelerometer 168, and/or microphone 113 (through audio circuitry 110). Information received by peripheral interface 118 from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

In some embodiments, event monitor 171 sends requests to peripheral interface 118 at predetermined intervals. In response, peripheral interface 118 transmits the event information. In other embodiments, peripheral interface 118 transmits event information only when there is a significant event (e.g., receiving input above a predetermined noise threshold and/or receiving input for more than a predetermined duration).

In some embodiments, event classifier 170 further includes hit view determination module 172 and/or active event recognizer determination module 173.

When touch-sensitive display 112 displays more than one view, hit view determination module 172 provides a software process for determining where a sub-event has occurred within one or more views. The view consists of controls and other elements that the user can see on the display.

Another aspect of the user interface associated with an application is a set of views, sometimes referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application view (of the respective application) in which the touch is detected may correspond to a programmatic level within a programmatic or view hierarchy of applications. For example, the lowest level view in which a touch is detected may be referred to as a hit view, and the set of events identified as correct inputs may be determined based at least in part on the hit view of the initial touch starting with the touch-based gesture.

Hit view determination module 172 receives information related to sub-events of the touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy that should handle the sub-event. In most cases, the hit view is the lowest level view in which the initiating sub-event (i.e., the first sub-event in the sequence of sub-events that form an event or potential event) occurs. Once the hit view is identified by the hit view determination module, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.

The active event recognizer determination module 173 determines which view or views within the view hierarchy should receive a particular sequence of sub-events. In some embodiments, the active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of the sub-event are actively involved views, and thus determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if the touch sub-event is completely confined to the area associated with a particular view, the higher views in the hierarchy will remain actively involved views.

The event scheduler module 174 schedules event information to an event recognizer (e.g., event recognizer 180). In embodiments that include an active event recognizer determination module 173, the event dispatcher module 174 passes the event information to the event recognizer determined by the active event recognizer determination module 173. In some embodiments, the event scheduler module 174 stores event information in an event queue, which is retrieved by the corresponding event receiver module 182.

In some embodiments, the operating system 126 includes an event classifier 170. Alternatively, application 136-1 includes event classifier 170. In another embodiment, the event classifier 170 is a stand-alone module or is part of another module stored in the memory 102, such as the contact/movement module 130.

In some embodiments, the application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, the respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of the event recognizers 180 are part of a separate module, such as a user interface toolkit (not shown) or a higher level object from which the application 136-1 inherits methods and other characteristics. In some embodiments, the respective event handlers 190 comprise one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 may utilize or call data updater 176, object updater 177, or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views 191 include one or more corresponding event handlers 190. Additionally, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.

The corresponding event recognizer 180 receives event information (e.g., event data 179) from the event classifier 170 and identifies events from the event information. The event recognizer 180 includes an event receiver 182 and an event comparator 184. In some embodiments, the event recognizer 180 further comprises at least a subset of: metadata 183, and event delivery instructions 188 (which may include sub-event delivery instructions).

The event receiver 182 receives event information from the event classifier 170. The event information includes information about the sub-event, such as a touch or touch movement. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event relates to movement of a touch, the event information may further include a velocity and a direction of the sub-event. In some embodiments, the event comprises rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information comprises corresponding information about the current orientation of the device (also referred to as the device pose).

Event comparator 184 compares the event information to predefined event or sub-event definitions and determines an event or sub-event or determines or updates the state of an event or sub-event based on the comparison. In some embodiments, event comparator 184 includes event definitions 186. Event definition 186 contains definitions of events (e.g., predefined sub-event sequences), such as event 1(187-1), event 2(187-2), and others. In some embodiments, sub-events in event 187 include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, the definition of event 1(187-1) is a double click on the displayed object. For example, the double tap includes a first touch (touch start) on the displayed object for a predetermined length of time, a first lift-off (touch end) for a predetermined length of time, a second touch (touch start) on the displayed object for a predetermined length of time, and a second lift-off (touch end) for a predetermined length of time. In another example, the definition of event 2(187-2) is a drag on the displayed object. For example, the drag includes a touch (or contact) on the displayed object for a predetermined length of time, a movement of the touch on touch-sensitive display 112, and a lift-off of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.

In some embodiments, event definition 187 includes definitions of events for respective user interface objects. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with a sub-event. For example, in an application view in which three user interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a corresponding event handler 190, the event comparator uses the results of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects the event handler associated with the object and sub-event that triggered the hit test.

In some embodiments, the definition of the respective event 187 further includes a delay action that delays the delivery of the event information until after the sequence of sub-events has been determined to indeed correspond or not to the event type of the event identifier.

When the respective event recognizer 180 determines that a sub-event string does not match any event in the event definition 186, the respective event recognizer 180 enters an event not possible, event failed, or event ended state, which then disregards subsequent sub-events of the touch-based gesture. In this case, the other event recognizers (if any) that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

In some embodiments, the respective event recognizer 180 includes metadata 183 with configurable attributes, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable attributes, flags, and/or lists that indicate how event recognizers may interact with each other. In some embodiments, metadata 183 includes configurable attributes, flags, and/or lists that indicate whether a sub-event is passed to varying levels in the view or programmatic hierarchy.

In some embodiments, when one or more particular sub-events of an event are identified, the respective event identifier 180 activates an event handler 190 associated with the event. In some embodiments, the respective event identifier 180 passes event information associated with the event to the event handler 190. The activation event handler 190 is distinct from sending (and deferring sending) sub-events to the corresponding hit view. In some embodiments, the event recognizer 180 throws a flag associated with the recognized event, and the event handler 190 associated with the flag receives the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about sub-events without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the sub-event string or to actively involved views. Event handlers associated with the sub-event strings or with actively involved views receive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates a phone number used in contacts module 137, or stores a video file used in video player module 145. In some embodiments, object updater 176 creates and updates objects used in application 136-1. For example, the object updater 177 creates a new user interface object, or updates the location of a user interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on the touch-sensitive display.

In some embodiments, event handler 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

It should be understood that the foregoing discussion regarding event processing of user touches on a touch sensitive display also applies to other forms of user inputs (not all of which are initiated on a touch screen) utilizing an input device to operate electronic device 100, such as coordinating mouse movements and mouse button presses (with or without single or multiple keyboard presses or holds), user movement taps, drags, scrolls, etc. on a touch pad, stylus inputs, movements of the device, verbal instructions, detected eye movements, biometric inputs, and/or any combination thereof, which may be used as inputs corresponding to sub-events defining an event to be recognized.

FIG. 3 illustrates a portable electronic device 100 having a touch screen 112 in accordance with some embodiments. The touch screen may display one or more graphics within the User Interface (UI) 200. In this embodiment, as well as other embodiments described below, a user may select one or more of these graphics by, for example, gesturing over the graphics with one or more fingers 202 (not drawn to scale in the figure) or with one or more styli 203 (not drawn to scale in the figure). In some embodiments, the selection of the one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture may include one or more taps, one or more swipes (left to right, right to left, up, and/or down), and/or a finger (right to left, left to right, up, and/or down) that has made contact with device 100. In some embodiments, inadvertent contact with a graphic does not select the graphic. For example, when the gesture corresponding to the selection is a tap, a swipe gesture that sweeps over an application icon does not select the corresponding application.

Device 100 may also include one or more physical buttons, such as a "home screen" or menu button 204. As previously described, the menu button 204 may be used to navigate to any application 136 in a set of applications that may be running on the device 100. Alternatively, in some embodiments, the menu buttons are implemented as soft keys in a GUI displayed on touch screen 112.

In one embodiment, device 100 includes touch screen 112, menu buttons 204, push buttons 206 for turning the device on and off and locking the device, volume adjustment button(s) 208, Subscriber Identity Module (SIM) card slot 210, headset jack 212, and docking/charging external port 124. Pressing the button 206 may be used to power the device on and off by pressing the button and holding the button in a pressed state for a predefined time interval; locking the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or unlocking the device or initiating an unlocking process. In an alternative embodiment, device 100 may also accept voice input through microphone 113 for activating or deactivating certain functions.

FIG. 4 is a block diagram of an exemplary electronic device with a display and a touch-sensitive surface in accordance with some embodiments. The device 300 need not be portable. In some embodiments, the device 300 is a laptop computer, desktop computer, tablet computer, multimedia player device, navigation device, educational device (such as a child learning toy), gaming system, or control device (e.g., a home or industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. In some embodiments, processing unit 310 includes an image signal processor and a dual or multi-core processor. The communication bus 320 may include circuitry (sometimes referred to as a chipset) that interconnects and controls communication between system components. Device 300 includes an input/output (I/O) interface 330 having a display 340, display 340 typically being a touch screen display. The I/O interface 330 may also include a keyboard and/or mouse (or other pointing device) 350 and a touchpad 355. The device 300 also includes an optical sensor 164 and an optical sensor controller 158. Memory 370 includes high speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices; and may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Optionally, memory 370 may include one or more storage devices remotely located from CPU 310. In some embodiments, memory 370 stores programs, modules, and data structures similar to, or a subset of, the programs, modules, and data structures stored in memory 102 of portable electronic device 100 (FIG. 2A). Further, the memory 370 may store additional programs, modules, and data structures not present in the memory 102 of the portable electronic device 100. For example, memory 370 of device 300 may store drawing module 380, presentation module 382, word processing module 384, web page creation module 386, disk editing module 388, and/or spreadsheet module 390, while memory 102 of portable electronic device 100 (FIG. 2A) may not store these modules.

Each of the above identified elements of fig. 4 may be stored in one or more of the aforementioned memory devices. Each of the identified modules corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 may store a subset of the modules and data structures described above. In addition, memory 370 may store additional modules and data structures not described above.

Attention is now directed to embodiments of a user interface ("UI") that may be implemented on the portable electronic device 100.

FIG. 5 illustrates an exemplary user interface for an application menu on the portable electronic device 100 according to some embodiments. A similar user interface may be implemented on device 300. In some embodiments, the user interface 400 includes the following elements, or a subset or superset thereof:

● signal strength indicators 402 for wireless communications (such as cell phone signals and Wi-Fi signals);

● time 404;

● Bluetooth indicator 405;

● battery status indicators 406;

● have a tray 408 of common application icons, such as:

■ a phone 138 that may include an indicator 414 of the number of missed calls or voice message messages;

■, an email client 140 that may include an indicator 410 of the number of unread emails;

■ browser 147; and

■ video and music player 152, also known as iPod (trademark of Apple inc.) module 152; and

■ icons of other applications such as:

◆IM 141；

image management 144;

a camera 143;

weather 149-1;

stock market 149-2;

exercise support 142;

a calendar 148;

alarm clock 149-4;

a map 154;

diamond 153;

settings 412 that provide access to settings of the device 100 and its various applications 136; and

an online video module 155, also referred to as YouTube (trademark of Google inc.) module 155.

Further, while the following examples are given primarily with reference to finger inputs (e.g., single finger contact, single finger tap gesture, single finger swipe gesture), it should be understood that in some embodiments one or more of these finger inputs are replaced by inputs from another input device (e.g., stylus inputs).

User interface and associated process

Attention is now directed to embodiments of a user interface ("UI") and associated processes that may be implemented on an electronic device, such as device 300 or portable electronic device 100, having a display and a touch-sensitive surface.

Fig. 6A-6C illustrate an exemplary user interface for deleting an object (e.g., an application), according to some embodiments. The user interfaces in these figures are used to illustrate the processes and/or functions described below.

In the embodiment of the present invention, the object specifically refers to a target pointing object associated with the displayed icon. For example, icon a is an icon, i.e., an application interface element, of application a displayed on the touch screen 112 of the device. Then application a is the target pointer associated with icon a. When a user contacts icon a through the touch-sensitive surface, i.e., activates application a associated with icon a, a specific graphical user interface of application a is displayed on touch screen 112. Alternatively, the object may be a file. For example, upon activation of the image management application 144, the graphical user interface of the application is displayed on the touch screen 112, and the image displayed as a thumbnail at this time may also be considered an icon, which we may refer to as a file interface element, and the target pointer of the icon is the image file data (e.g., an image in JPG or JEPG format) associated with the icon. Therefore, when the user operates the icon, the user operates the associated image file data, for example, the name of the icon is modified. Activating the icon, i.e., activating its associated image file, causes it to be displayed on touch screen 112.

To select an object, this may be accomplished by selecting an object interface element (such as an icon) with which the object is associated. In an embodiment, an object interface element may be dragged or moved, and when the finger is lifted, the object (such as an application, file, etc.) associated therewith is opened. The terms "select", "move", "drag", "contact", "touch", and "fast move" are generally described herein with reference to a touch screen display. However, in alternative embodiments, the term is also intended to include desired user actions with respect to other input devices. For example, in the case of a proximity screen (proximity screen), the user need not be in direct contact with the screen in order to select, move or drag an object interface element or other information. Thus, the above terms are intended to include: the user need only be located near the device in order to perform the desired function. For example, when used in the context of a proximity screen device, the term "contact" does not imply a direct contact to activate the proximity device, but a nearby or close contact.

Fig. 6A shows a Graphical User Interface (GUI) displayed on touch screen 112 of device 100.

A plurality of object interface elements (501-504) are displayed on the graphical user interface, wherein the object interface elements 501, 502 and 503 are application icons, i.e. application interface elements, and each application icon is associated with an application. Object interface element 504 is a file icon, i.e., a file interface element, each file icon being associated with a file datum. According to the embodiment of the invention, the object associated with the object interface element is deleted through the specific gesture acted on the object interface element, so that the intelligent interaction capacity between the electronic equipment and the user is greatly improved, and the transaction processing efficiency of the electronic equipment is also improved.

Now, we will use the uninstalled application as an example to describe the embodiment in detail. As shown in fig. 6A, the touch screen 112 may detect a first gesture 505 of the user for the application icon 503, the first gesture may be a gesture of selecting the application icon 503, and the first gesture 505 may be a gesture of rapidly moving a finger and lifting off, rapidly moving away from the touch screen surface after selecting the application icon 503. The electronic device can now detect the gesture speed and gesture direction of the first gesture 505 through the touch screen 112.

The central processing unit 120 of the electronic device may determine the gesture speed of the first gesture 505 from the data received about the first gesture by the touch screen 112. How to determine the existing technology is not described herein. When the central processing unit 120 determines that the gesture speed satisfies the predetermined condition, the application associated with the application icon 503 is uninstalled. The user may pre-store a threshold value of the gesture speed in the memory 102, and when it is determined that the detected gesture speed is greater than or equal to the threshold value, the central processing unit 120 may determine that the first gesture belongs to a gesture moving fast on the touch screen, that is, the first gesture 505 may serve as an instruction for triggering application uninstallation. After the CPU120 compiles the first gesture into an uninstall command, the application associated with the application icon 503 to which the first gesture 505 is applied is uninstalled. It will be appreciated that before the associated application is uninstalled, it may be displayed on touch screen 112 in the form of a dynamic GUI to indicate to the user that the application is about to be uninstalled, as shown in fig. 6B, and icon 507 may be an animated display indicating that the application is most about to be uninstalled. Of course, the application program may be indicated to the user in other user-sensible manners, and the embodiment is not limited herein.

Of course, before executing the uninstall command, the user may be prompted in a user-perceptible manner to indicate whether the application will be approved by the uninstall user. The uninstall operation may be performed after receiving an instruction for the user to confirm approval.

As shown in FIG. 6C, after the application is uninstalled, the current graphical user interface may be re-laid out.

In some further embodiments, the electronic device can erase a file associated with the file interface element based on the detected gesture. As shown in fig. 6A, the touch screen 112 may detect a second gesture of the user with respect to the file icon 504 (i.e., file interface element), which may be a gesture to select the file icon 504, which may be a quick finger movement and lifting off the touch screen surface after the file icon 504 is selected. The electronic device may now detect the gesture speed of the second gesture through touch screen 112.

The central processing unit 120 of the electronic device may determine the gesture speed of the second gesture through the data regarding the second gesture received by the touch screen 112. How to determine the existing technology is not described herein. When the central processing unit 120 determines that the gesture speed satisfies the predetermined condition, the file associated with the file icon 504 is erased. The user may pre-store a threshold value of the gesture speed in the memory 102, and when it is determined that the detected gesture speed is greater than or equal to the threshold value, the central processing unit 120 may determine that the second gesture belongs to a gesture moving fast on the touch screen, that is, the second gesture may serve as an instruction for triggering the file erasure. After the CPU120 compiles the second gesture into an erase command, the file associated with the file icon 504 acted on by the second gesture is erased. It will be appreciated that prior to the associated file data being erased, it may be displayed on touch screen 112 in the form of a dynamic GUI auxiliary to indicate to the user that the file is about to be erased. Of course, the file may be indicated to the user in other ways perceivable by the user, and the embodiment is not limited herein.

In still other embodiments, if the gesture speed information detected by the central processing unit 120 is less than the threshold, the position of the object interface element (e.g., icon 503, icon 504) may be moved according to the detected gesture (e.g., the first gesture or the second gesture described above).

In some other embodiments, the touch screen 112 may detect a gesture direction in addition to detecting a gesture speed, that is, which direction of the touch screen 112 the user's finger is moving quickly. Further, in an embodiment, the condition: when the gesture speed is greater than or equal to the predetermined threshold and the gesture direction is towards the right side of the touch screen 112, the cpu120 uninstalls the application program selected by the first gesture or erases the file selected by the second gesture. As shown in fig. 6A, icon 506 represents the direction of gesture 505.

In some other embodiments, before the touch-sensitive surface of the touch screen 112 detects a gesture for the application icon 503 or the file icon 504, the central processing unit 120 may further determine whether the object corresponding to the icon may be deleted: if the object is deletable, detecting a gesture at the touch-sensitive surface for an object interface element (i.e., icon 503 or icon 504); if not, the user is prompted.

In still other embodiments, the gesture may also operate on two or more object interface elements, i.e., the gesture detected by touch screen 112 is selected on two or more icons. The following embodiments are illustrated with two object interface elements as examples.

For example, the object interface elements selected by the gestures (including the first gesture or the second gesture) may be a first application interface element associated with a first application and a second application interface element associated with a second application. As shown in FIG. 7A, a first application interface element (icon 502) is associated with an image management application and a second application interface element (icon 503) is associated with a twitter application. Touch screen 112 detects gesture 605 with its origin on icon 503, then passes icon 502 in the direction of the gesture shown by icon 606, and the finger is then quickly lifted off touch screen 112. We can consider this gesture 605 to be for a first application interface element (icon 502) and a second application interface element (icon 503). The central processing unit 120 of the electronic device receives the data of the gesture 605 through the touch screen 112, and can determine the gesture speed of the gesture 605. When the central processing unit 120 determines that the gesture speed satisfies a predetermined condition, for example, that the gesture speed is greater than or equal to a predetermined threshold, the image management application associated with the first application interface element (icon 502) and the twitter application associated with the second application interface element (icon 503) are uninstalled. It will be appreciated that prior to the associated application being uninstalled, display on touch screen 112 in the form of a dynamic GUI may be facilitated to indicate to the user that the application is about to be uninstalled. Of course, the application program may be indicated to the user in other user-sensible manners, and the embodiment is not limited herein.

In some other embodiments, the object interface elements selected by the gesture (including the first gesture or the second gesture) may be specifically a first file interface element and a second file interface element. The first file interface element is associated with first file data and the second file interface element is associated with second file data. As shown in FIG. 7B, it is the user that activates the open gallery graphical user interface upon selection of icon 502 in FIG. 6A. Photos or videos in the gallery are shown in the interface in the form of thumbnail icons, for example, icon 601 is associated with picture file data with the name of 4, icon 602 is associated with video file data with the name of 5, and icon 603 is associated with picture file data with the name of 6. The particular format of the picture or video is not limited herein.

Touch screen 112 detects gesture 607, which starts on icon 601, then passes icon 602 in the direction of the gesture shown by icon 606, and the finger is then quickly lifted off touch screen 112. We can consider this gesture 607 to be for a first file interface element (icon 601) and a second file interface element (icon 602). The central processing unit 120 of the electronic device receives the data of the gesture 607 through the touch screen 112, and can determine the gesture speed of the gesture 607. When the central processing unit 120 determines that the gesture speed satisfies a predetermined condition, for example, that the gesture speed is greater than or equal to a predetermined threshold, the image file associated with the first file interface element (icon 601) and the video file associated with the second file interface element (icon 602) are erased. It will be appreciated that the associated files may be assisted in display on touch screen 112 in the form of a dynamic GUI to indicate to the user that the image and video files are about to be erased before the associated files are erased. Of course, the file may be indicated to the user in other ways perceivable by the user, and the embodiment is not limited herein.

In some other embodiments, the object interface elements selected by the gesture (including the first gesture or the second gesture) may be specifically a third file interface element and a fourth application interface element. The third file interface element corresponds to third file data, and the fourth application interface element corresponds to a fourth application program. As in the previous embodiment, after detecting the gesture for the third file interface element and the fourth application interface element on the touch-sensitive surface of the touch screen 112, the central processing unit 120 determines whether the gesture speed satisfies a predetermined condition, and when the predetermined condition is satisfied, erases the third file data and uninstalls the fourth application program.

In some other embodiments, the touch screen 112 may detect a gesture direction in addition to detecting a gesture speed, that is, which direction of the touch screen 112 the user's finger is moving quickly. Further, in an embodiment, the condition: when the gesture speed is greater than or equal to the predetermined threshold and the gesture direction is towards the right side of the touch screen 112, the cpu120 uninstalls the application program selected by the first gesture or erases the file selected by the second gesture. Such as icon 608 in fig. 7B to indicate the gesture direction of gesture 607.

Herein, unless specifically stated, the user's gesture is flexible and may be a click, double click, circle, line, single finger touch, or multi-finger touch, among others. One of ordinary skill in the art will appreciate that the selection of a particular gesture is flexible as long as substantially the same result is achieved. In this context, unless specifically stated otherwise, the location or region of the touch-sensitive surface at which the user's gesture is applied is also flexible, and may be a region or vicinity of an application interface element displayed by the display screen, a blank region of the display screen where no application interface element is displayed, a region of a function setting displayed by the display screen, and so forth. It will be appreciated by those skilled in the art that the gestures can be flexibly configured to act on specific locations or regions of the touch-sensitive surface, so long as substantially the same effect is achieved.

In some further embodiments, a computer readable storage medium may be provided that stores one or more programs, the one or more programs comprising instructions, which when executed by a portable electronic device that includes a display and a plurality of applications, cause the portable electronic device to perform the following. The computer readable storage medium described above may be used to execute the events in the embodiments described above.

In still other embodiments, a graphical user interface on an electronic device comprising a display including a touch-sensitive surface and a display screen, a memory, a plurality of applications, and one or more processors to execute one or more programs stored in the memory may be provided, including the graphical user interface described and illustrated in the above embodiments.

Fig. 8 illustrates a functional block diagram of an electronic device 700 configured in accordance with the principles of the present invention described above, in accordance with some embodiments. The functional blocks of the device can be implemented by hardware, software, or a combination of hardware and software to carry out the principles of the present invention. Those skilled in the art will appreciate that the functional blocks described in fig. 8 may be combined or separated into sub-blocks to implement the principles of the present invention as described above. Thus, the description herein may support any possible combination or separation or further definition of the functional blocks described herein.

As shown in fig. 8, the electronic device 700 includes: a touch-sensitive display unit 701, the touch-sensitive display unit 701 being configured to display a screen interface and configured to receive a gesture; and a processing unit 702, the processing unit 702 being coupled to the touch sensitive display unit 701. In an embodiment, the touch-sensitive display unit 701 receives a gesture of a user for an object interface element, where the gesture may include a gesture speed and a gesture direction; the processing unit 702 obtains the gesture of the touch-sensitive display unit 701, and determines whether the gesture speed is greater than or equal to a predetermined threshold, and if the processing unit 702 determines that the gesture speed is greater than or equal to the predetermined threshold, the processing unit 702 deletes the object associated with the object interface element. The meaning of terms such as object, object interface element, etc. in the present embodiment refers to the above embodiments. The electronic device 700 may be used to implement the technical solutions in the above-described embodiments.

In some embodiments, the processing unit 702 may specifically include a touch screen receiving unit 7021, an action interpreting unit 7022, an event distributing unit 7023, a main screen receiving unit 7024, an event judging unit 7025, an application uninstalling unit 7026, and a file erasing unit 7027.

The functions of the electronic device 700 are described below, and those skilled in the art will appreciate that the following functions are in accordance with the various embodiments of the electronic device, system, apparatus, method, graphical user interface, information processing apparatus (e.g., processor chip or set of processor chips), and computer-readable storage medium described herein, which are combined and/or integrated with one another in any combination that will occur directly and without doubt to those skilled in the art after understanding the present disclosure.

Touch screen receiving unit 7021: the touch-sensitive display receives signals of user gesture touch screen operation, which may include actions of pressing, moving, lifting, and the like.

Action interpretation unit 7022: the unit is used for interpreting the original actions of pressing, moving, lifting and the like into events of clicking, long pressing, quick moving and the like;

the event distributing unit 7023: passing the event in the system action interpretation unit to an upper application (e.g., the main screen receiving unit 7024);

the main screen receiving unit 7024: the main screen receives the event, sends the event to the following processing units corresponding to the event and executes the process corresponding to the event;

event determining unit 7025: judging whether the current event meets a preset condition, for example, whether the gesture speed of the gesture is greater than or equal to a preset threshold value, and starting a corresponding processing unit after the judgment is finished;

application uninstalling unit 7026: if the gesture speed of the gesture is determined to be greater than or equal to the predetermined threshold value according to the event determining unit 7025, the application program clicked by the gesture is unloaded;

file erasing unit 7027: if the gesture speed of the gesture is determined to be greater than or equal to the predetermined threshold value according to the event determination unit 7025, the file clicked by the gesture is erased.

In the above embodiment, the file may specifically be a picture or a video in an image management application program, or may also be a contact in a contact application program.

It should be appreciated that those of ordinary skill in the art will recognize from the understanding herein that the operations described above with reference to fig. 6A-6C, 7A-7B may be implemented by the components shown in fig. 2A-2B. For example, event monitor 171 in event sorter 170 detects a contact on touch-sensitive display 112 and event scheduler module 174 passes the event information to application 136-1. A respective event recognizer 180 of application 136-1 compares the event information to respective event definitions 186 and determines whether a first contact at a first location on the touch-sensitive surface corresponds to a predefined event or sub-event, such as a selection of an object on a user interface. When a respective predefined event or sub-event is detected, the event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 may utilize or call data updater 176 or object updater 177 to update application internal state 192. In some embodiments, event handler 190 accesses a respective GUI updater 178 to update the content displayed by the application. Similarly, those skilled in the art will clearly know how other processes may be implemented based on the components shown in FIGS. 2A-2B.

The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated.

Claims

1. A portable electronic device, comprising:

a display, wherein the display comprises a touch-sensitive surface and a display screen;

one or more processors;

a memory;

a plurality of application programs; and

one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising instructions for:

displaying at least one object interface element on the display screen, the at least one object interface element being associated with at least one object;

detecting, at the touch-sensitive surface, a gesture for the at least one object interface element, the gesture comprising a gesture speed and a gesture direction;

and when the gesture speed and the gesture direction meet the preset conditions, deleting the at least one object.

2. The portable electronic device of claim 1, wherein the object interface element specifically comprises: an application interface element or a file interface element, the application interface element being associated with an application program, the file interface element being associated with file data.

3. The method according to claim 2, characterized in that said predetermined conditions comprise in particular: the gesture speed is greater than or equal to a predetermined threshold and the gesture direction information is to the right of the display screen.

4. The method of claim 3, wherein the at least one object interface element is moved in accordance with the detected gesture when the gesture speed information is less than the predetermined threshold.

5. The method as recited in claim 1, prior to the touch-sensitive surface detecting a gesture directed to the at least one object interface element, the method comprising: determining whether the at least one object is deletable: detecting a gesture at the touch-sensitive surface for the at least one object interface element if the at least one object is deletable; if the at least one object is undeletable, prompting the user.

6. The method according to claim 1 or 5, characterized in that said at least one object interface element is embodied as a first application interface element and a second application interface element, said first application interface element being associated with a first application and said second application interface element being associated with a second application;

wherein,

the detecting a gesture for the at least one object interface element on the touch-sensitive surface, and deleting the at least one object when the gesture speed and the gesture direction satisfy predetermined conditions, specifically:

detecting, at the touch-sensitive surface, gestures for the first application interface element and the second application interface element;

and when the gesture speed and the gesture direction meet preset conditions, uninstalling the first application program and the second application program.

7. The method according to claim 1 or 5, wherein the at least one object interface element is embodied as a first file interface element and a second file interface element, the first file interface element being associated with first file data and the second file interface element being associated with second file data;

wherein,

detecting, at the touch-sensitive surface, gestures for the first file interface element and the second file interface element;

and when the gesture speed and the gesture direction meet preset conditions, erasing the first file data and the second file data.

8. The method according to claim 1 or 5, wherein the at least one object interface element is embodied as a third file interface element and a fourth application interface element, the third file interface element being associated with third file data and the fourth application interface element being associated with a fourth application;

wherein,

detecting, at the touch-sensitive surface, gestures for the third file interface element and the fourth application interface element;

and when the gesture speed and the gesture direction meet preset conditions, erasing the third file data and uninstalling the fourth application program.

9. A method of deleting an object for a portable electronic device comprising a display and a plurality of applications, wherein the display comprises a touch-sensitive surface and a display screen, the method comprising:

detecting, at the touch-sensitive surface, a gesture for the at least one object interface element, the gesture comprising gesture speed information and gesture direction information;

10. The method of claim 9, wherein the object interface element specifically comprises: an application interface element or a file interface element, the application interface element being associated with an application program, the file interface element being associated with file data.

11. The method according to claim 10, characterized in that said predetermined conditions comprise in particular:

the gesture speed is greater than or equal to a predetermined threshold and the gesture direction information is to the right of the display screen.

12. The method of claim 11, wherein the at least one object interface element is moved in accordance with the detected gesture when the gesture speed information is less than the predetermined threshold.

13. The method of claim 9 or 11, wherein prior to the touch-sensitive surface detecting the gesture to the at least one object interface element, the method comprises:

determining whether the at least one object is deletable: detecting a gesture at the touch-sensitive surface for the at least one object interface element if the at least one object is deletable; if the at least one object is undeletable, prompting the user.

14. The method according to claim 9 or 11, wherein the at least one object interface element is embodied as a first application interface element and a second application interface element, the first application interface element being associated with a first application and the second application interface element being associated with a second application;

wherein,

15. The method according to claim 9 or 11, wherein the at least one object interface element is embodied as a first file interface element and a second file interface element, the first file interface element being associated with first file data and the second file interface element being associated with second file data;

wherein,

16. The method according to claim 9 or 11, wherein the at least one object interface element is embodied as a third file interface element and a fourth application interface element, the third file interface element being associated with third file data and the fourth application interface element being associated with a fourth application;

wherein,

17. An electronic device, characterized in that the electronic device specifically includes:

a touch-sensitive display unit to detect a user's gesture with respect to an object interface element, the gesture including a gesture speed and a gesture direction, the object interface element including an application interface element and a file interface element;

the processing unit is used for acquiring the gesture of the touch-sensitive display unit and judging whether the gesture meets a preset condition: and if the processing unit judges that the gesture meets the preset condition, deleting the object associated with the object interface element.

18. The electronic device according to claim 17, wherein the predetermined condition specifically comprises: the gesture speed is greater than or equal to a predetermined threshold and the gesture direction information is to the right of the display screen.

19. The electronic device of claim 18, wherein prior to the touch-sensitive display unit detecting the gesture to the object interface element, the processing unit is further to:

judging whether the object can be deleted: if the object is deletable, the touch-sensitive display unit detecting a gesture for an object interface element; if the object is undeletable, the user is prompted.