Apple Inc. v. Samsung Electronics Co. Ltd. et al

Filing 563

EXHIBITS re #559 Declaration in Support, filed byApple Inc.. (Attachments: #1 Exhibit 5.02, #2 Exhibit 5.03, #3 Exhibit 5.04, #4 Exhibit 5.05, #5 Exhibit 5.06, #6 Exhibit 5.07, #7 Exhibit 5.08, #8 Exhibit 5.09, #9 Exhibit 5.10, #10 Exhibit 5.11, #11 Exhibit 6.1, #12 Exhibit 6.2, #13 Exhibit 6.3, #14 Exhibit 6.4, #15 Exhibit 6.5)(Related document(s) #559 ) (Jacobs, Michael) (Filed on 12/29/2011)

EXHIBIT 5.09

WO2008/085877

PCT/US2008/000103

28/37

2700

2702

2712

2704

27 0

i

I

2706

2720

2722

2730

2732

2740

2742

FIG. 27

APLNDC00027681

WO2008/085877

PCT/US2008/000103

29/37

2838

2832

2800

2834

2836

--/

2840

2842

2846

FIG. 28

APLNDC00027682

WO2008/085877

PCT/US2008/000103

30/37

2950

2960

2956

2962

2952

2954

2964
2958

FIG. 29

APLNDC00027683

WO2008/085877

PCT/US2008/000103

31/37
3084 3098
3070
3093
3089

3095

3087

3091

3097

FIG. 30A
3070

3092
3084A

3088
3087

3096

3094

3089
lj

3091

FIG. 30B

APLNDC00027684

o
DISPLAY DEVICE
11 0]ì

BACKLIGHT
STORAGE

DEVICE
3_101

ANTENNA
SYSTEM
10

DIGITAL ANDIOR
- T S IVREFR ~
gg

I

DIG TAL
PROCESSING
3Y3rEM
i
3133
MEÑA
i
PROCFSSING

/
AUDIO
i TRANSDUCER

,

SYSTEM
TLOS.

I
MICROPHONE

SENSOR(S)

INPUT
DEVICE(S)

'

BATTERY

1101

105A

FIG. 31

a oc

APLNDC00027685

WO2008/085877

PCT/US2008/000103

33/37

3200
CACHE
(OPTIONAL)

\ 3208
/

3202

MICROPROCESSOR

3204
MEMORY
3206

BUS

3210
DISPLAY
CONTROLLER
AND
DISPLAY
DEVICE
(OPTIONAL)

3212
I/O
CONTROLLER(S)

3216
3214

1/O DEVICE(S)
(E.G., KEYBOARD,
CURSOR CONTROL
DEVICE, NETWORK
INTERFACE)

SENSOR(S)
FOR USER
ACTIVITY

FIG. 32

APLNDC00027686

WO2008/085877

PCT/US2008/000103

34/37

3306
3308

3302
3304

FIG. 33A

APLNDC00027687

WO2008/085877

PCT/US2008/000103

35/37

3358

3356

3352
3354

FIG. 338

APLNDC00027688

WO2008/085877

PCT/US2008/000103

36/37

3362
3366

3360

FIG. 33C

APLNDC00027689

WO 2008/085877

PCT/US2008/000103

37/37

3400

CONSTRUCT A HIERARCHY OF VIEWS
OPERATING ON TOP OF A HIERARCHY OF
LAYERS
3402

PROVIDE ACCESS TO THE HIERARCHY OF
VIEWS WITHOUT PROVIDING A · --- TO THE
HIERARCHY OF LAYERS
3404

FIG. 34

APLNDC00027690

INTERNATIONAL SEARCH REPORT

.

International appn©etion No
PCT/US2008/000103

A. CLASSlFICATION OF SUBJECT MATTER -

INV.

GO6F9/44

ACCording to International Patent Classification (IPC) orto both national classification and IPC
B. FIELDS SEARCHED

Mmimum cocumentation searched (classification system followed by classification symbols)

GO6 F

uocumentation searoned other than minimum documentation to the extent that such documents are included in the fields searched

t-lectronic data base consulted during the intemational search (name of data base and, where practical, search terms used)

EPO-Internal, INSPEC

C. DOCUMENTS CONSIDERED TO BE RELEVANT

Category*

X

Citation of document, with indication, where appropriate, of the relevant passages

Relevant to claim No.

US 2003/132959 A1 (SIMISTER J BRET [US] ET
AL) 17 July 2003 (2003-07-17)
page 1, paragraph 6

page 1, paragraph 11
16

1,3-9,
11-18,24

page 2, paragraph

page 2, paragraph 39 - page 3, paragraph
40

page 3, paragraphs 44,46,47,49
page 4, paragraphs 56,57,59,60

page 5, paragraph 72-75
Y

page 6, paragraph 82-85

page 7, paragraph 96 - page 8, paragraph

2,10,

103

19-23, 25

Further documents are listed in the continuation of Box C.
* Special categories of cited documents:

See patent family annex

'A' document defining the general state of the art which is not

"T• later document published after the international filing date
or priority date and not in conflict with the application but
cited to understand the principle or theory underlying the

"E" earliet document but published on or after the international
filing date

"X" document of particular relevance; the clairned invention

considered to be of particular relevance

"L' document which may throw doubts on priority claim(s) or
which is cited to establish the publication date of another
citation or other special reason (as specified)
"O' documerit referrirtg to an oral disclosure, use, exhibition or
other means
"P' document pubÍished prior to the internallonal filing date but
later than the priority date claimed
Date of the actual completion of the International search

28 May 2008
Name and mailing address of the ISA/
European Patent Office. P.B. 5818 Patentiaan 2
NL - 2280 HV Rijswijk
Tel. [phone], TX. 31 651 opo ni,
FaX: [phone]

invention

cannot be considered novel or cannot be considered to
Involve an inventive step when the document is taken alone
'Y' document of particular relevance; the claimed invention
cannot be considered to involve an inventive step when the
document is combined with one or more other such documents, such combination being obvious to a person skilled
in the art.
'&' document member of the same patent family
Date of malling of the international search report

03/06/2008
Authorized officer

Del

CM aro,

SU vi a

orm PDT/ISA/210 (second sheet) (April 2005)

APLNDC00027691

INTERNATIONAL SEARCH REPORT

internationgappHeadon No

PCT/US2008/000103
C(Continuation).

Category*

Y

DOCUMENTS CONSIDERED TO BE RELEVANT

Citation of document, with indication, where appropriate, of the relevant passages

WO 2006/067711 A (KONINKL PHILIPS
ELECTRONICS NV ENL]; HOLTMAN KOEN JG [NL]) 29 June 2006 (2006-06-29)
page 4, line 4 - line 16

2,10,
19-23,25

US 2006/190833 A1 (SANGIOVANNI 30HN [US]
ET AL) 24 August 2006 (2006-08-24)
page 4, paragraph 49 - page 5, paragraph
58

1-25

page
page
page
page

A

Relevant to claim No.

4, line 31
5, line 29
7, line 18
11, line 5

-'page
- page
- page
- page

5, I ne 25
6, 1 ne 3
8, l'ne 10
13, line 18

orm PCT/ISAl2to (continuation of second sheet) (April 2005)

APLNDC00027692

INTERNATIONAL SEARCH REPORT
information on patent family members

Patent document
cited in search report

Pubilcation
date

.

Iriternatio

PCT/USŽ008/000103
Patent family
member(s)

US 2003132959

A1

17-07-2003

WO
US

WO 2006067711

A

-29-06-2006

Al

24-08-2006

03063004 A1
2006026526 A1

Pubilcation
date

NONE

US 2006190833

application No

31-07-2003
02-02-2006

NONE '

Forrn PCTASA/210 (patent family annex) (April2005)

APLNDC00027693

(12) IN ·

-ATIONAL APPLICATION PUBLISHED UNDER THE PA xen i COOPERATION T

TY (PCT)

(19) World Intellectual PropertaytOrganization
(43) International Publication Date

(10) International Publication Number

17 July 2008 (17.07.2008)

WO 2008/085848 A1
(74) Agents: SCHELLER, James, C., Jr. et al.; Blakely,
Sokoloff, Taylor & Zafman LLP, 1279 Oakmead Parkway,
Sunnyvale, CA 94085-4040 (US).

(51) International Patent Classification:
GO6F 3/048 (2006.01)
(21) International Application Number:
PCT/US2008/000060

(22) International Filing Date:

(81) Designated States (unless otherwise indicated, for every

kind of national protection available): AE, AG, AL, AM,
AO, AT, AU, AZ, BA, BB, BG, BH, BR, BW, BY, BZ, CA,
CH, CN, CO, CR, CU, CZ, DE, DK, DM, DO, DZ, EC, EE,
EG, ES, FI, GB, GD, GE, GH, GM, GT, HN, HR, IRJ, ID,
IL, IN, IS, IP, KE, KG, KM, KN, KP, KR, KZ, LA, LC,

3 January 2008 (03.01.2008)

(25) Filing Language:

English

(26) Publication Language:

English

(36) Priority Data:
11/620,727

7 January 2007 (07.01.2007)

LK, LR, LS, LT, LU, LY, MA, MD, ME, MG, MK, MN,
MW, MX, MY, MZ, NA, NG, NI, NO, NZ, OM, PG, PH,
PL, PT, RO, RS, RU, SC, SD, SE, SG, SK, SL, SM, SV,
SY, TJ, TM, TN, TR, TT, TZ, UA, UG, US, UZ, VC, VN,
ZA, ZM, ZW

US

(71) Applicant (for all designated States except US): APPLE
INC. [US/US]; 1 Infinite Loop, Cupertino, CA 95014 (US).

(84) Designated States (unless otherwise indicated, for every
kind of regional protection available): ARIPO (BW, GH,

GM, KE, LS, MW, MZ, NA, SD, SL, SZ, TZ, UG, ZM,
ZW), Eurasian (AM, AZ, BY, KG, KZ, MD, RU, TJ, TM),
European (AT, BE, BG, CH, CY, CZ, DE, DK, EE, ES, FI,
FR, GB, GR, HR, HU, IE, IS, IT, LT, LU, LV, MC, MT, NL,

(72) Inventor; and
(75) Inventor/Applicant (for US only): BLU-·- =ERG,
Christopher [US/US]; 3600 21st Street, Apt. #305, San
Francisco, CA 94114 (US).

[Continued on next page]

(54) Title: APPLICATION PROGR^

---

GUI AY

DIS

iiiiiiiiiiiiiiiii

A ING INTERFACES FOR G

400

\NFORMATION

OPERATIONS

(57) Abstract: At least certain embodiments of the present
disclosure include an environment with user interface software interacting with a software application to provide gesture operations for a display of a device. A method for operating through an application programming interface (API)
in this environment includes transferring a scaling transform
call. The gesture operations include performing a scaling
transform such as a zoom in or zoom out in response to a
user input having two or more input points. The gesture operations also include performing a rotation transform to rotate an image or view in response to a user input having two
or more input points.

MOVEMENT

NFORMATION

416

INFORMATION

WINDOW

APLNDC00027694

WO 2008/085848 A1
NO, PL, PT, RO, SE, SI, SK, TR), OAPI (BF, BJ, CF, CG,
CI, CM, GA, GN, GQ, GW, ML, MR, NE, SN, TD, TG).

IllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllIlllllllllllli IIII
Published:
- with international search report

APLNDC00027695

WO 2008/085848

PCT/US2008/000060

APPLICATION PROGRAMMING INTERFACES FOR GESTURE
OPERATIONS
FIELD OF THE DISCLOSURE

[0001] This disclosure relates to application programming interfaces that provide
gesture operations.

COMPUTER PROGR^M LISTING
[0002] A portion of the disclosure of this patent document contains material
which is subject to copyright protection. The copyright owner has no objection

to facsimile reproduction by anyone of the patent document or the patent
disclosure, as it appears in the Patent & Trademark Office patent file or records,
but otherwise reserves all copyright rights whatsoever.
[0003] Applicant has submitted herewith Computer Program Listings which are
included as Appendix A, attached.
BACKGROUND OF THE DISCLOSURE
[0004] An API is a source code interface that a computer system or program

library provides in order to support requests for services from a software
application. An API is specified in terms of a progr

ing language that can be

interpretative or compiled when an application is built, rather than an explicit
low level description of how data is laid out in memory. The software that
provides the functionality described by an API is said to be an implementation of
the API.
[0005] Various devices such as electronic devices, computing systems, portable

devices, and handheld devices have software applications. The API interfaces
between the software applications and user interface software to provide a user
of the device with certain features and operations. A user may desire certain
operations such as scrolling, selecting, gesturing, and animating operations for a
display of the device.

-l-

APLNDC00027696

WO 2008/085848

PCT/US2008/000060

[0006] Scrolling is the act of sliding a directional (e.g., horizontal or vertical)
presentation of content, such as text, drawings, or images, across a screen or
display window. In a typical graphical user interface, scrolling is done with the
help of a scrollbar or using keyboard shortcuts, often the arrow keys. Gesturing
is a type of user input with two or more input points. Animating operations
include changing content within a given time period.

[0007] The various types of devices may have a limited display size, user
interface, software, API interface and/or processing capability which limits the
ease of use of the devices. User interfaces of devices implement APIs in order to
provide requested functionality and features. These user interfaces can have
difficulty interpreting the various types of user inputs and providing the intended
functionality associated with the user inputs.

SUMM^RY OF THE DESCRIPTION
[0008] At least certain embodiments of the present disclosure include one or

more application programming interfaces in an environment with user interface
software interacting with a software application. Various function calls or
messages are transferred via the application progr------ing interfaces between the

user interface software and software applications. Example application
progr wing interfaces transfer function calls to implement scrolling, gesturing,
and -,

ating operations for a device.

(0009] At least certain embodiments of the present disclosure include an
environment with user interface software interacting with a software application.
A method for operating through an application progr-swing interface (API) in
this environment includes transferring a set bounce call. The method further
includes setting at least one of maximum and minimum bounce values. The set
bounce call causes a bounce of ä scrolled region in an opposite direction of a

scroll based on a region past an edge of the scrolled region being visible in a

display region at the end of the scroll.
[0010] At least certain embodiments of the present disclosure include an
environment with user interface software interacting with a software application.

-2-

APLNDC00027697

WO 2008/085848

PCT/US2008/000060

A method for operating through an application progrw-sing interface (API) in
this environment includes transferring a rubberband call. Rubberbanding a

scrolled region within a display region occurs by a predetermined maximum
displacement when the scrolled region exceeds a display edge. The method
further includes transferring an edge rubberband call to set displacement values

for at least one edge of the display (e.g., top and bottom edges, left and right
edges).
[0011] At least certain embodiments of the present disclosure include an
environment with user interface software interacting with a software application
to provide gesture operations for a display of a device. A method for operating

through an application programming interface (API) in this environment includes
transferring a scaling transform call. The gesture operations include performing
a scaling transform such as a zoom in or zoom out in response to a user input
having two or more input points. The gesture operations also include performing
a rotation transform to rotate an image or view in response to a user input having
two or more input points. =
[0012] At least certain embodiments of the present disclosure include a method
for performing animations for a display of a device. The method includes
starting at least one animation. The method further includes determining the
progress of each animation. The method further includes completing each

animation based on a single timer. The single timer can be based on a redraw
interval of the display hardware.
[0013] Various devices which perform one or more of the foregoing methods
and machine readable media which, when executed by a processing system,
cause the processing system to perform these methods, are also described.
[0014] Other methods, devices and machine readable media are also described.
BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The disclosure is described by way of example with reference to the
accompanying drawings, wherein:

-3-

APLNDC00027698

WO 2008/085848

PCT/US2008/000060

[0016] FIG. 1 is flow chart of a method for responding to a user input of a data
processing device;

[0017] FIG. 2 illustrates details of an application programming interface in flow
chart form according to certain teachings of the present disclosure;

[0018] FIG. 3 illustrates details of an application programming interface in flow
chart form according to certain teachings of the present disclosure;

[0019] FIG. 4 is a schematic diagram illustrating an embodiment of user
interface of a portable electronic device 400 having a touch-sensitive display

408;
[0020] FIG. 5A-5C illustrate at least some embodiments of user interface of a
portable electronic device 400 having a touch-sensitive display;
[0021] FIG. 6A-6D illustrate the scrolling of a list of items to a terminus of the
list, at which point an area beyond the terminus is displayed and the list is then
scrolled in an opposite direction until the area beyond the terminus is no longer
displayed, in accordance with some embodiments;

[0022] FIG. 7 illustrates details of an application programming interface in flow
chart form according to certain teachings of the present disclosure;
[0023] FIG. 8 illustrates first and second scroll angles for locking a scroll of a

display of a device in a horizontal or vertical direction according to certain
teachings of the present disclosure;

[0024] FIG. 9 illustrates details of an application programming interface in flow
chart form according to certain teachings of the present disclosure;

(0025] FIG. 10 illustrates details of an application programming interface in flow
chart form according to certain teachings of the present disclosure;

[0026] FIG. 11 illustrates details of an application programming interface in flow
chart form according to certain teachings of the present disclosure;
[0027] FIG. 12 illustrates details of an application programming interface in flow
chart form according to certain teachings of the present disclosure;

[0028] FIG. 13 illustrates details of an application programming interface in flow
chart form according to certain teachings of the present disclosure;

-4-

APLNDC00027699

WO 2008/085848

PCT/US2008/000060

(0029] FIG. 14 illustrates details of an application progr,wing interface in flow
chart form according to certain teachings of the present disclosure;

(0030] FIG. 15 illustrates a display of a device having a scaling transform of a
view;

[0031] FIG. 16A and 16B illustrate a display of a device with a view having a
first and a second scaling factor;
[0032] FIG. 17 illustrates details of an application programming interface in flow
chart form according to certain teachings of the present disclosure;
[0033] FIG. 18 illustrates details of an application programming interface in flow

chart form according to certain teachings of the present disclosure;
[0034] FIG. 19 is flow chart of a method for animating views displayed on a
display of a device;
[0035] FIG. 20 is flow chart of a method for animating views displayed on a
display of a device;
[0036] FIG. 21 illustrates details of an application programming interface in flow
chart form according to certain teachings of the present disclosure;
[0037] FIG. 22A and 22B illustrate synchronizing the resizing of windows of a

display of a device;
[0038] FIG. 23 illustrates a method for switching ownership of a view of an
application displayed on a display of a data processing device;
[0039] FIG. 24 illustrates a method for memory management of a view of an

application displayed on a display of a device;
[0040] FIG. 25A and 25B illustrate a data structure having a hierarchy of layers
with a layer being associated with a view;
[0041] FIG. 26 illustrates a method for compositing media and non-media
content of user interface for display on a device;

[0042] FIG. 27 illustrates a data structure or layer tree having a hierarchy of
layers;
[0043] FIG. 28 is a perspective view of a device in accordance with one
embodiment of the present disclosure;

-5-

APLNDC00027700

WO 2008/085848

PCT/US2008/000060

[0044] FIG. 29 is a perspective view of a device in accordance with one
embodiment of the present disclosure;
(0045] FIG. 30 is a perspective view of a wireless device in accordance with one
embodiment of the present disclosure;

[0046] FIG. 31 is a block diagram of a system in which embodiments of the
present disclosure can be implemented;
[0047] FIG. 32 shows another example of a device in accordance with one
embodiment of the present disclosure;

[0048] FIG. 33A is a perspective view of a device in a first configuration (e.g. in
a laptop configuration) in accordance with one embodiment of the present
disclosure;
[0049] FIG. 33B is a perspective view of the device of FIG. 33A in a second
configuration (e.g. a transition configuration) in accordance with one
embodiment of the present disclosure;
[0050] FIG. 33C is a perspective view of the device of FIG. 33A in a third

configuration (e.g., a tablet configuration) in accordance with one embodiment of
the present disclosure; and
[0051] FIG. 34 illustrates details of an application programming interface in flow
chart form according to certain teachings of the present disclosure.
DETAILED DESCRIPTION

[0052] Various embodiments and aspects of the disclosure will be described with
reference to details discussed below, and the accompanying drawings will
illustrate the various embodiments. The following description and drawings are
illustrative of the disclosure and are not to be construed as limiting the

disclosure. Numerous specific details are described to provide a through
understanding of various embodiments of the present disclosure. However, in
certain instances, well-known or conventional details are not described in order
to provide a concise discussion of embodiments of the present disclosure.
[0053] Some portions of the detailed descriptions which follow are presented in
terms of algorithms which include operations on data stored within a computer

-6-

APLNDC00027701

WO 2008/085848

PCT/US2008/000060

memory. An algorithm is generally a self-consistent sequence of operations

leading to a desired result. The operations typically require or involve physical
manipulations of physical quantities. Usually, though not necessarily, these
quantities take the form of electrical or magnetic signals capable of being stored,
transferred, combined, compared, and otherwise manipulated. It has proven
convenient at times, principally for reasons of common usage, to refer to these
signals as bits, values, elements, symbols, characters, terms, numbers, or the like.
[0054] It should be borne in mind, however, that all of these and similar terms
are to be associated with the appropriate physical quantities and are merely

convenient labels applied to these quantities. Unless specifically stated
otherwise as apparent from the following discussion, it is appreciated that
throughout the description, discussions utilizing terms such as "processing" or

"computing" or "calculating" or "determining" or "displaying" or the like, can
refer to the action and processes of a data processing system, or similar
electronic device, that manipulates and transforms data represented as physical
(electronic) quantities within the system's registers and memories into other data

similarly represented as physical quantities within the system's memories or

registers or other such information storage, transmission or display devices.
[0055] The present disclosure can relate to an apparatus for performing one or
more of the operations described herein. This apparatus may be specially
constructed for the required purposes, or it may comprise a general purpose
computer selectively activated or reconfigured by a computer program stored in
the computer. Such a computer program may be stored in a machine (e.g.
computer) readable storage medium, such as, but is not limited to, any type of

disk including floppy disks, optical disks, CD-ROMs, and magnetic-optical
disks, read-only memories (ROMs), random access memories (RAMs), erasable
programmable ROMs (EPROMs), electrically erasable progr-mable ROMs
(EEPROMs), flash memory, magnetic or optical cards, or any type of media
suitable for storing electronic instructions, and each coupled to a bus.
[0056] A machine-readable medium includes any mechanism for storing or
trw-itting information in a form readable by a machine (e.g., a computer). For

-7-

APLNDC00027702

WO 2008/085848

PCT/US2008/000060

example, a machine-readable medium includes read only memory ("ROM");
random access memory ("RAM"); magnetic disk storage media; optical storage
media; flash memory devices; electrical, optical, acoustical or other form of
propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.); etc.
[0057] At least certain embodiments of the present disclosure include one or
application programming interfaces in an environment with user interface
software interacting with a software application. Various function calls or

messages are transferred via the application progr-------ng interfaces between the
user interface software and software applications. Transferring the function calls
or messages may include issuing, initiating, invoking or receiving the function
calls or messages. Example application programming interfaces transfer
function calls to implement scrolling, gesturing, and animating operations for a
device having a display region. An API may also implement functions having
parameters, variables, or pointers. An API may receive parameters as disclosed
or other combinations of parameters. In addition to the APIs disclosed, other
APIs individually or in combination can perform similar functionality as the
disclosed APIs.

[0058] The display region is a form of a window. A window is a display region
which may not have a border and may be the entire display region or area of a

display. In some embodiments, a display region may have at least one window
and/or at least one view (e.g., web, text, or image content). A window may have
at least one view. The methods, systems, and apparatuses disclosed can be
implemented with display regions, windows, and/or views.
[0059] At least certain embodiments of the present disclosure include scrolling

operations for scrolling a display of a device. The scrolling operations include
bouncing a scrolled region in an opposite direction of a scroll when a scroll
completes, rubberbanding a scrolled region by a predetermined maximum

displacement when the scrolled region exceeds a display edge, and setting a
scrolling angle that locks the scroll in a horizontal or vertical direction.
[0060] At least certain embodiments of the present disclosure include gesture
operations for a display of a device. The gesture operations include performing a

-8-

APLNDC00027703

WO 2008/085848

PCT/US2008/000060

scaling transform such as a zoom in or zoom out in response to a user input

having two or more input points. The gesture operations also include performing
a rotation transform to rotate an image or view in response to a user input having
two or more input points.
(0061] At least certain embodiments of the present disclosure include a method

for performing animations for a display of a device. The method includes
starting at least one animation. The method further includes determining the
progress of each animation. The method further includes completing each

animation based on a single timer. The single timer can be based on a redraw
interval of the display hardware.

[0062] At least certain embodiments of the disclosure may be part of a digital

media player, such as a portable music and/or video media player, which may
include a media processing system to present the media, a storage device to store
the media and may further include a radio frequency (RF) transceiver (e.g., an
RF transceiver for a cellular telephone) coupled with an antenna system and the
media processing system. In certain embodiments, media stored on a remote

storage device may be transmitted to the media player through the RF
transceiver. The media may be, for example, one or more of music or other
audio, still pictures, or motion pictures.

[0063] The portable media player may include a media selection device, such as
a click wheel input device on an iPod® or iPod Nano® media player from Apple
Computer, Inc. of Cupertino, CA, a touch screen input device, pushbutton
device, movable pointing input device or other input device. The media
selection device may be used to select the media stored on the storage device
and/or the remote storage device. The portable media player may, in at least

certain embodiments, include a display device which is coupled to the media
processing system to display titles or other indicators of media being selected
through the input device and being presented, either through a speaker or
earphone(s), or on the display device, or on both display device and a speaker or
earphone(s). In some embodiments, the display device and input device are

integrated while in other embodiments the display device and input device are
-9-

APLNDC00027704

WO 2008/085848

PCT/US2008/000060

separate devices. Examples of a portable media player are described in US patent
application No. 11/586,862, titled "Automated Response to and Sensing of User
Activity in Devices" and published U.S. patent application numbers
2003/0095096 and 2004/0224638 which have been incorporated by reference
into the present application.

[0064] Embodiments of the disclosure described herein may be part of other
types of data processing systems, such as, for example, entertainment systems or
personal digital assistants (PDAs), or general purpose computer systems, or
special purpose computer systems, or an embedded device within another device,

or cellular telephones which do not include media players, or multi touch tablet
devices, or other multi touch devices, or devices which combine aspects or
functions of these devices (e.g., a media player, such as an iPod®, combined
with a PDA, an entertainment system, and a cellular telephone in one device). In
this disclosure, electronic devices and consumer devices are types of devices.
[0065] FIG. 1 is flow chart of a method for responding to a user input of a
device. The method 100 includes receiving a user input at block 102. The user
input may be in the form of an input key, button, wheel, touch, or other means

for interacting with the device. The method 100 further includes creating an
event object in response to the user input at block 104. The method 100 further
includes determining whether the event object invokes a scroll or gesture

operation at block 106. For example, a single touch that drags a distance across a
display of the device may be interpreted as a scroll operation. In one
embodiment, a two or more finger touch of the display may be interpreted as a
gesture operation. In certain embodiments, determining whether the event object
invokes a scroll or gesture operation is based on receiving a drag user input for a
certain time period. The method 100 further includes issuing at least one scroll
or gesture call based on invoking the scroll or gesture operation at block 108.

The method 100 further includes responding to at least one scroll call, if issued,
by scrolling a window having adiew (e.g., web, text, or image content)

associated with the event object based on an amount of a scroll with the scroll
stopped at a predetermined position in relation to the user input at block 110.

-10-

APLNDC00027705

WO 2008/085848

PCT/US2008/000060

For example, an input may end at a certain position on a display of the device.
The scrolling may continue until reaching a predetermined position in relation to
the last input received from the user. The method 100 further includes
responding to at least one gesture call, if issued, by changing a view associated
with the event object based on receiving a plurality of input points in the form of
the user input at block 112.

[0066] In certain embodiments of the present disclosure, scroll operations
include attaching scroll indicators to a content edge of a display. Alternatively,
the scroll indicators can be attached to the display edge. In some embodiments,
user input in the form of a mouselfinger down causes the scroll indicators to be
displayed on the display edge, content edge, or window edge of the scrolled
region. If a mouse/finger up is then detected, the scroll indicators are faded out
from the display region, content edge, or window edge of the scrolled region.
[0067] In certain embodiments of the present disclosure, gesture operations

include responding to at least one gesture call, if issued, by rotating a view
associated with the event object based on receiving a plurality of input points in

the form of the user input. Gesture operations may also include scaling a view
associated with the event object by zoommg m or zooming out based on
receiving the user input.
[0068] In some embodiments, a device includes a display region having multiple
views or windows. Each window may have a multiple views including
superviews and subviews. It is necessary to determine which window, view,

superview, or subview is contacted by a user input in the form of a mouse up,
mouse down, or drag, etc. An API can set various modes for making this
determination. In one embodiment, a pass mode sends mouse down, mouse up,
and drag inputs to the nearest subview. In another embodiment, an intercept on

drag mode sends a drag input to the superview while mouse up and down inputs
are sent to the subview. In another embodiment, an intercept mode sends all
drag, mouse up and down inputs to the superview. The superview may be
scroller software operating as a subclass of a view software. The subview may

be view software operating as a subclass of the user interface software.

-11-

APLNDC00027706

WO 2008/085848

PCT/US2008/000060

[0069] FIG. 2 illustrates details of an application progrm.a..ing interface in flow
chart form according to certain teachings of the present disclosure. The
application programming interface operates in an environment with user
interface software interacting with a software application in order to provide a
bounce operation. The method 200 for providing a bounce operation includes
transferring a set bounce call at block 202. The method 200 further includes

setting at least one of maximum and minimum bounce values at block 204. The
minimum and maximum bounce values may be associated with at least one edge
of a window that has received a user input. The method 200 further includes
causing a bounce of a scrolled region in an opposite direction of a scroll based on

a region past the scrolled region being visible in a display region at the end of the
scroll at block 206. The scrolled region may be a content region.
[0070] In certain embodiments of the present disclosure, transferring the set
bounce call is either one of issuing, initiating, invoking or receiving the set

bounce call.
[0071] FIG. 3 illustrates details of an application programming interface in flow
chart form according to certain teachings of the present disclosure. The
application programming interface operates in an environment with user
interface software interacting with a software application in order to provide a
rubberband operation. The method 300 for providing a rubberband operation
includes transferring a rubberband call to cause rubberbanding a scrolled region

displayed within a display at block 302. The method 300 further includes
transferring an edge rubberband call to set displacement values for at least one

edge of the display at block 304. In some embodiments, the displacement values
are set for top and bottom edges, left and right edges, or all edges.
[0072] Rubberbanding a scrolled region according to the method 300 occurs by a
predetermined maximum displacement value when the scrolled region exceeds a

display edge of a display of a device based on the scroll. If a user scrolls content
of the display making a region past the edge of the content visible in the display,
then the displacement value limits the maximum amount for the region outside

-12-

APLNDC00027707

WO 2008/085848

PCT/US2008/000060

the content. At the end of the scroll, the content slides back making the region
outside of the content no longer visible on the display.
[0073] In certain embodiments of the present disclosure, transferring the
rubberband call is either one of issuing, initiating, invoking or receiving the

rubberband call.
[0074] Figure 4 is a schematic diagram illustrating an embodiment of user
interface of a portable electronic device 400 having a touch-sensitive display
408. The display 408 may include a window 410. The window 410 may include
one or more displayed objects, such as information objects 412-1 to 412-4. In an
exemplary embodiment, the information objects 412 may correspond to contact

information for one or more individuals in a list of items. The displayed objects
may be moved in response to detecting or determining movement 414 of a point
of contact with the display, such as that associated with one or more digits 416 of
a user (which are not drawn to scale in Figure 4). In some embodiments,

movement of the displayed objects may be accelerated in response to detecting
or determining accelerated movement of the point of contact. While
embodiment 400 includes one window 410, in other embodiments there may be
two or more display windows. In addition, while embodiment 400 illustrates
movement 414 in a particular direction, in other embodiments movement of the
displayed objects may be in response to movement 414 in one or more other
directions, or in response to a scalar (i.e., a determined or detected movement
independent of the directioti).

[0075] Figures 5A-5C illustrate the scrolling of a list of items on a device to a
terminus of the list, at which point one or more displayed items at the end of the

list smoothly bounce off the end of the display, reverse direction, and then
optionally come to a stop. Figure 5A is a schematic diagram illustrating an
embodiment of user interface of a portable electronic device 400 having a touchsensitive display. One or more displayed objects, such as information object 412-

1 may be a distance 512-1 from a terminus 514 of the list of items which is an
edge of a scrolled region and may be moving with a velocity 510-1 while the list
is being scrolled. Note that the terminus 514 is a virtual boundary associated with

-13-

APLNDC00027708

WO 2008/085848

PCT/US2008/000060

the displayed objects, as opposed to a physical boundary associated with the
window 410 and/or the display 408. As illustrated in Figure SB, when the one or

more displayed objects, such as the information object 412-1, reach or intersect
with the terminus 514, the movement corresponding to the scrolling may stop,
i.e., the scrolling velocity may be zero at an instant in time. As illustrated in

Figure 5C, the one or more displayed objects, such as the information 412-1, may
subsequently reverse direction. At a time after the intersection with the terminus

514, the information object 412-1 may have velocity 510-2 and may be a distance
512-2 from the terminus 514. In some embodiments, the magnitude of velocity

510-2 may be less than the magnitude of velocity 510-1 when the distance 512-2
equals the distance 512-1, i.e., the motion of the one or more displayed objects is
damped after the scrolling list reaches and "bounces" at its terminus.

(0076] In at least some embodiments of the present disclosure, the method 200
performs the bounce operations described in FIGS. 5A-5C. The bounce call
transferred at block 202 determines whether a bounce operation is enabled. The
maximum and minimum bounces values determine the amount of bouncing of
the scrolled region in an opposite direction of the scroll.

[0077] Figures 6A-6D illustrate the scrolling of a list of items to a terminus of
the list, at which point an area beyond the terminus is displayed and the list is
then scrolled in an opposite direction until the area beyond the terminus is no
longer displayed, in accordance with some embodiments. The rubberband

operation of method 300 is illustrated in the example of Figures 6A-6D with the
listed items being email messages. Figures 6A-6D illustrate an exemplary user
interface 3500A for managing an inbox in accordance with some embodiments.
An analogous user interfach may be used to display and manage other mailboxes
(e.g., drafts, sent, trash, personal, etc.). In addition, other types of lists are
possible, including but not limited to lists of instant message conversations,
favorite phone numbers, contact information, labels, email folders, email
addresses, physical addresses, ringtones, or album names.
[0078] If the list of emails fills more than the allotted screen area, the user may
scroll through the emails using vertically upward and/or vertically downward

-14-

APLNDC00027709

WO 2008/085848

PCT/US2008/000060

swipe gestures on the touch screen. In the example of Figure 6A, a portion of a

list of emails is displayed in the screen area, including a top displayed email 3530
from Bruce Walker and a bottom displayed email 3532 from Kim Brook. A user
performs a vertically downward swipe gesture 3514 to scroll toward the top of the
list. The vertically downward gesture 3514 need not be exactly vertical; a
substantially vertical gesture is sufficient. In some embodiments, a gesture within
a predetermined angle of being perfectly vertical results in vertical scrolling.
[0079] As a result of detecting the vertically downward gesture 3514, in Figure
6B the displayed emails have shifted down, such that the previous bottom
displayed email 3532 from Kim Brook is no longer displayed, the previous top
displayed email 3530 from Bruce Walker is now second from the top, and the

email 3534 from Aaron Jones, which was not displayed in Figure 6A, is now
displayed at the top of the list.

[0080] In this example, the email 3534 from Aaron Jones is the first email in the
list and thus is the terminus of the list. Upon reaching this email 3534, in
response to continued detection of the vertically downward gesture 3514, an area
3536 (Figure 6C) above the first email 3534 (i.e., beyond the terminus of the list)

is displayed. In some embodiments, the area displayed beyond the terminus of
the list is visually indistinct from the background of the list. In Figure 6C, both

the area 3536 and the background of the emails (e.g., emails 3534 and 3530) are
white and thus are visually indistinct.
(0081] Once vertically downward gesture 3514 is complete, such that a
corresponding object is no longer detected on or near the touch screen display,

the list is scrolled in an opposite direction until the area 3536 is no longer
displayed. Figure 6D illustrates the result of this scrolling in the opposite
direction, the email 3534 from Aaron Jones is now displayed at the top of the
screen area allotted to the list and the area 3536 is not displayed.
[0082] In the example of Figures 6A-6D, a vertically downward gesture resulted
in display of an area beyond the first item in the list. As described in Figure 3,
the values for the predetermined maximum displacement (e.g., display of an area

-15-

APLNDC00027710

WO 2008/085848

PCT/US2008/000060

beyond the first item in the list) are set at block 304 for top and bottom edges or

at block 306 for all edges of the window.
[0083] Similarly, a vertically upward gesture may result in display of an area
beyond the last item of the list, if the vertically upward gesture continues once

the list has been scrolled to the last item. The last item may be considered a
terminus of the list, similar to the first item. As discussed above, the gesture
need not be exactly vertical to result in vertical scrolling; a gesture within a
predefined range of angles from perfectly vertical is sufficient.

[0084] FIG. 7 illustrates details of an application programming interface in flow
chart form according to certain teachings of the present disclosure. The
application programming interface operates in an environment with user
interface software interacting with a software application in order to provide a
directional scrolling operation. The method 700 for operating through an
application programming interface (API) includes transferring a directional scroll
angle call to determine if diiectional scrolling is enabled at block 702. The
method 700 further includes transferring a directional scroll angle call to set a

scroll angle for locking the scrolling in at least one of a vertical or a horizontal
direction at block 704. The method 700 further includes locking the scrolling in

the horizontal direction if a user input forms an angle with a horizontal direction
that is less than or equal to a first scroll angle at block 706. The method 700
further includes locking the scrolling in the vertical direction if a user input
forms an angle with the vertical direction that is less than or equal to a second

scroll angle at block 708.
[0085] In certain embodiments, a user input in the form of a drag forms an angle
with the horizontal direction that is less than the first scroll angle. In this case, the
user presumably intends to scroll in the horizontal direction. The scrolling will be
locked in the horizontal direction until the user input exceeds the first scroll angle.

A second scroll angle may be uhed for locking the user input in the vertical
direction. The second scroll angle may be set equal to the first scroll angle.
[0086] FIG. 8 illustrates first and second scroll angles for locking a scroll of a
display of a device in a horizontal or vertical direction. The horizontal direction

-16-

APLNDC00027711

WO 2008/085848

PCT/US2008/000060

802 and vertical direction 804 are in reference to a window or a display of a

device. As discussed in the method 700, a user input such as a drag movement
forming an angle with the horizontal direction 802 less than or equal to the first
scrolling angle 806 or 808 will lock the user input in the horizontal direction. In
a similar manner, a user input forming an angle with the vertical direction 810
less than or equal to the second scrolling angle 810 or 812 will lock the user

input in the vertical direction. The first and second scrolling angles may be set at
the same angle or at different angles as well. For example, the first and second
scrolling angles may be set at 25 degrees. A user input less than or equal to 25

degrees with respect to the horizontal or vertical direction will lock the scrolling
in the appropriate direction.
[0087] In some embodiments, the horizontal and vertical locking angles can be
determined in part by the aspect of the content. For example, content in the form
of a tall page may receive a larger vertical locking angle compared to the
horizontal locking angle.

[0088] FIG. 9 illustrates details of an application programming interface in flow
chart form according to certain teachings of the present disclosure. The

application programming interface operates in an environment with user
interface software interacting with a software application in order to provide a
deceleration scroll operation. The method 900 for providing the deceleration
scroll operation includes transferring a deceleration scroll call to set a
deceleration factor for a drag user input at block 902. The method 900 further
includes slowing the scroll to a stop based on the speed of the drag user input and
the deceleration factor at block 904.
[0089] In certain embodiments, a user input in the form of a drag invokes a

scroll operation for a certain time period. The user input has a certain speed.
The scroll of the scrolled region of a window or a display region of a display of a
device will be stopped after the user input stops by applying a deceleration factor
to the speed of the user input during the drag movement.

[0090] FIG. 10 illustrates details of an application progr

ing interface in flow

chart form according to certain teachings of the present disclosure. The

-17-

APLNDC00027712

WO 2008/085848

PCT/US2008/000060

application programming interface operates in an environment with user
interface software interacting with a software application in order to provide a
scroll hysteresis operation. The method 1000 for providing the scroll hysteresis
operation includes transferring a scroll hysteresis call to determine whether a
user input invokes a scroll at block 1002. The method 1000 further includes
setting a hysteresis value for determining whether a user input invokes a scroll at

block 1004.
[0091] In certain embodiments, a user input in the form of a drag over a certain

distance across a display or window within a display of a device invokes a scroll
operation. The hysteresis value determines the certain distance which the user

.

input must drag across the display or window prior to invoking a scroll
operation. A user input that does not drag the certain predetermined distance
will not invoke a scroll operation and may be considered a mouse up or down
input or other type of input.
[0092] FIG. 11 illustrates details of an application programming interface in flow
chart form according to certain teachings of the present disclosure. The

application progr -------ing interface operates in an environment with user
interface software interacting with a software application in order to attach a
scroll indicator to a scroll region edge or a window edge of a device. In some

embodiments, the scroll region edge is associated with a content edge. The
window or display edge may be associated with the edge of a display region.

The method 1100 for providing the scroll indicator includes transferring a scroll
indicator call to determine whether at least one scroll indicator attaches to an
edge of a scroll region or a window edge at block 1102. A scroll indicator may

be displayed on any display edge, window edge or scroll region edge. The
method I100 further includes optionally attaching at least one scroll indicator to
the edge of the scroll region based on the scroll indicator call at block 1104.

Alternatively, the method 1100 further includes optionally attaching at least one
scroll indicator to the window edge of the view based on the scroll indicator call

at block 1106.

-18-

APLNDC00027713

WO 2008/085848

PCT/US2008/000060

[0093] In some embodiments, the operations of method 1100 can be altered,
modified, combined, or deleted. For example, block 1104 can be deleted.
Likewise, block 1106 can be deleted from the method 1100. Alternatively, the
order of block 1104 and block 1106 can be switched. Other methods having
various operations that have been disclosed within the present disclosure can also
be altered, modified, rearranged, collapsed, combined, or deleted.

[0094] In certain embodiments of the present disclosure, transferring the scroll
indicator call is either one of issuing, initiating, invoking or receiving the scroll
indicator call. For example, the user interface software (e.g., software kit or
library) may receive the scroll indicator call from the software application.
[0095] FIG. 12 illustrates details of an application programming interface in
flow chart form according to certain teachings of the present disclosure. The
application programming interface operates in an environment with user
interface software interacting with a software application in order to determine if
an inadvertent user input contacts a view of a display of a device. The method
1200 includes transferring an inadvertent user input call to determine whether the

user input was inadvertent at block 1202. The method 1200 further includes
ignoring the inadvertent user input based on the determination of the inadvertent
user input call at block 1204. In one embodiment, the inadvertent user input call
comprises a thumb detectioti call to determine whether the user input was an
inadvertent thumb.

[0096] In certain embodiments of the present disclosure, transferring the
inadvertent user input call is either one of issuing, initiating, invoking or
receiving the inadvertent user input call.

[0097] A gesture API provides an interface between an application and user
software in order to handle gesturing. Gesturing may include scaling, rotating, or
other changes to a view, window, or display. A mask may merely permit certain
changes while limiting or not permitting other changes. Events of all kinds come
into the application via a graphics framework. They are enqueued, collaleced if
necessary and dispatched. If the events are system level events (e.g., application
should suspend, device orientation has changed, etc) they are routed to the

-19-

APLNDC00027714

WO 2008/085848

PCT/US2008/000060

application having an instance of a class of the user interface software. If the
events are hand events based on a user input, the events are routed to the window

they occurred over. The window then routes these events to the appropriate
control by calling the instance's mouse and gesture methods. The control that
receives a mouse down or mouse entered function will continue to get all future

calls until the hand is lifted. If a second finger is detected, the gesture methods or
functions are invoked. These functions may include start, change, and end
gesture calls. The control that receives start gesture call will be sent all future
change gesture calls until the gesture ends.
[0098] FIG. 13 illustrates details of an application programming interface in flow

chart form according to certain teachings of the present disclosure. The
application programming interface operates in an environment with user
interface software interacting with a software application in order to provide a
gesture operation. The method 1300 for providing the gesture operation includes
transferring a handle gesture event call at block 1302. The method 1300 further
includes transferring a gesture change call in response to the handle gesture event

call at block 1304.
[0099] In certain embodiments, a user input in the form of two or more points is

received by a display of a device. A multi-touch driver of the device receives the
user input and packages the event into an event object. A window server
receives the event object and determines whether the event object is a gesture
event object. If the window server determines that a gesture event object has
been received, then user interface software issues or transfers the handle gesture

call at block 1302 to a software application associated with the view. The
software application confirms that a gesture event has been received and passes
the handle gesture call to a library of the user interface software. The window
server also associates the gesture event object with the view that received the
user input. The library responds by transferring a gesture change call in response

to the handle gesture event call at block 1304.
[00100]

In one embodiment, a window or view associated with the user

input receives the change call in order to perform the gesture event. The user

-20-

APLNDC00027715

WO 2008/085848

PCT/US2008/000060

software that provides the view receives a gesture start event call, a gesture
changed event call, a zoom to scale setting for the view, and a gesture end call.
The gesture calls receive an input of a gesture event which may be base event
having a type such as a hand event, keyboard event, system event, etc. A
delegate associated with the application receives a start gesture call, gesture did

change call, and gesture did finish call. The user software is dynamically linking
into the application during the run time of the gesture process.

[00101]

In some embodiments, the gesture changed function call contains

the following information about the gesture:
the number of fingers currently down;
the number of fingers initially down;
the rotation of the hand;

the scale of the hand;
the translation of the hand;

the position of the inner and outermost fingers; and
the pressure of the first finger.
In other embodiments, more information about each finger down may be

included as follows.
the stage of the finger (just touch down, fully pressed, lifting off, etc);
the position of the finger;

the proximity of the finger (how hard you're touching);
the orientation of the finger (what angle the ovoid is at);
the length of the major and minor axis;
the velocity of the finger; and
the eccentricity of the finger's ovoid.
(00102]

A gesture event object may be a chord event object having a

chord count (e.g., number of fingers contacted the view or display), a chord start

-21-

APLNDC00027716

WO 2008/085848

PCT/US2008/000060

event, a chord change event, and a chord end event. A chord change event may
include a scaling or rotation transform.

[00103]

FIG. 14 illustrates details of an application programming interface

in flow chart form according to certain teachings of the present disclosure. The
application programming interface operates in an environment with user interface
software interacting with a software application in order to provide a scaling
transform of a display region, window, or view of a display of a device. The
method 1400 for providing the scaling transform includes transferring a scaling

transform call to determine a scaling transform for a view associated with a user
input having a plurality of input points at block 1402. The method 1400 further
includes transferring a scaling gesture start call at block 1404. The method 1400
further includes transferring a scaling gesture progress call at block 1406. The

method 1200 further includes transferring a scaling gesture end call at block 1408.
[00104]

In certain embodiments, a user input in the form of two or more

input points (e.g., fingers) moves together or apart to invoke a gesture event that
performs a scaling transform on the view associated with the user input. A scale
transform includes a minimum and maximum scale factor. FIG. 15 illustrates a

display 1502 of a device having a scaling transform of a view. The view 1504
(e.g., web, text, or image content) has a first scale factor. A user input (e.g., two
fingers moving apart) associated with the view 1504 is interpreted as a gesture
event to zoom out from view 1504 to view 1508 having a second scale factor that
exceeds the maximum scale factor of the view 1516. A snapback flag determines
whether the zoom out can proceed past the maximum scale factor to view 1508

prior to snapping back to the maximum scale factor associated with view 1516.
[00105]

FIG. 16A illustrates a display 1604 of a device having a first

scaling factor of a view 1616. A user input (e.g., two fingers 1608 and 1610
moving together) associated with the view 1614 is interpreted as a gesture event

to zoom in from view 1614 to view 1664 having a second scale factor as
illustrated in FIG. 16B. The dashed regions 1602 and 1650 represent the total
area of the content with the only content being displayed in the display area 1604

and 1652. In performing the scaling transform from FIG. 16A to FIG. 16B, the

-22-

APLNDC00027717

WO 2008/085848

PCT/US2008/000060

center of the gesture event, center 1612 for FIG. 16A and center 1660 for FIG.
16B, remains in the same position with respect to the display 1604. The scroll
indicator 1606 shrinks to become scroll indicator 1654 during the transform to
indicate that a smaller portion of the total content 1650 is being displayed on
display 1604 as a result of the zoom in operation. The dashed region 1650 is
larger than the dashed region 1602 to represent that a larger portion of content is

not being displayed on display 1652 in FIG. 16B as a result of the zoom in
operation.

[00106]

In at least some embodiments of the present disclosure, a user

desires to change a view 1670 from a scale factor of 2x to a scale factor of lx as
illustrated in FIG. 16C. A first set of user inputs 1672 and 1674 that move to the
second set of user inputs 1676 and 1678 will decrease the scale factor from 2x to
1x. It may be desirable for the user to scale from 2x to 1x without having to
move the user inputs a large distance across the view 1670. In an environment
with user interface software interacting with a software application, a gesture
scaling transform flag may be set in order to determine a scaling transform for a
view associated with a user input having a plurality of input points. The scaling
transform flag scales either from a current scale factor to a minimum scale factor
or from the current scale factor to a maximum scale factor. For example, a flag

may be set at the position associated with a 1.5x scale factor and a third set of
user inputs 1680 and 1682. A user desiring to change the scale factor from 2x to
lx would only have to move his fingers, the user inputs, from the first set 1672
and 1674 to the third set 1680 and 1682 if the gesture scaling transform flag has

been set at a scale factor of 1.5x.
[00107]

FIG. 17 illustrates details of an application programming interface

in flow chart form according to certain teachings of the present disclosure. The

application programming interface operates in an environment with user interface
software interacting with a software application in order to provide a rotation
transform of a view, window, or display region of a display of a device. The
method 1700 for providing the rotation transform includes transferring a rotation
transform call to determine a rotation transform for a view associated with a user

-23-

APLNDC00027718

WO 2008/085848

PCT/US2008/000060

input having a plurality of input points at block 1702. The method 1700 further
includes transferring a rotation gesture start call at block 1704. The method 1700
further includes transferring a scaling gesture progress call at block 1706. The
method 1700 further includes transferring a scaling gesture end call at block 1708.
[00108]

In certain embodiments, a user input in the form of two or more

input points rotates to invoke a gesture event that performs a rotation transform
on the view associated with the user input. The rotation transform includes a

minimum and maximum degree of rotation for associated minimum and
maximum rotation views. The user input may temporarily rotate a view past a
maximum degree of rotation prior to the view snapping back to the maximum
degree of rotation.
[00109]

FIG. 18 illustrates details of an application programming interface

in flow chart form according to certain teachings of the present disclosure. The
application programming interface operates in an environment with user

interface software interacting with a software application in order to notify a
delegate of at least one animationcassociated with a display region, window, or
view of a display of a device. A delay in the animation may be specified by the
API. Also, multiple animations may be assigned priority by the API. The
method 1800 for notifying the delegate includes determining whether any

animation occurs at block 1802. The method 1800 further includes checking the
progress of an animation at block 1804. If progress has ou maed, then the next
state (e.g., position, opacity, or transform) of the animation can be calculated at

block 1806. If progress has completed at block 1806, then at block 1808 it is
determined whether the view associated with the completed animation is
associated with a delegate. If so, a delegate call is transferred to notify the

delegate of the animation for the view at block 1810. The delegate operating
under the control of the software application can change other views m response
to the view being modified by the animation.
[00110]

In certain embodiments, software invokes an animation that

performs a scaling transform on the view associated with the user input. A

display may include numerous views. The view being increased in size by the
-24-

APLNDC00027719

WO 2008/085848

PCT/US2008/000060

scaling transform may obstruct other views in which case the other views may
need to be reduced in size. Alternatively, the view being decreased in size by the
scaling transform may create additional area for other views to increase in size.

[00111]

FIG. 19 is flow chart of a method for animating a display region,

windows, or views displayed on a display of a device. The method 1900 includes
starting at least two animations at block 1902. The method 1900 further includes
determining the progress of each animation at block 1904. The method 1900
further includes completing each animation based on a single timer at block 1906.

[00112]

In certain embodiments of the present disclosure, the single timer

includes a timer based on a redraw interval which is a time period between the
display of a current frame and a next frame of the display of the device. In this
case, changes in animation are updated to the display during the redraw interval
in order to display the changes during the next frame of the display. The
progress of each animation may be calculated periodically or based upon a
progress call.
[00113]

The method 1900 may further include determining whether each

animation is associated with a delegate. The delegate is then notified of the
animation. Other views not associated with an animation may be changed
depending on the software application controlling the delegate.
[00114]

FIG. 20 is flow chart of a method for animating a display region,

windows, or views displayed on a display of a device. The method 2000
includes providing a single animation timer at block 2002. The method 2000
further includes animating a plurality of animations with the single animation

timer at block 2004. For example, a single timer may control all animations
which occur simultaneously. The animations may include a transform, a frame,
and an opacity animation. A animation transform may include a scaling or
rotation transform. A frame animation may include resizing of a frame. An
opacity animation changes the opacity from opaque to transparent or vice versa.
[00115]

FIG. 21 illustrates details of an application progr-------ing interface

in flow chart form according to certain teachings of the present disclosure. The
application progr

ning interface operates in an environment with user

-25-

APLNDC00027720

WO 2008/085848

PCT/US2008/000060

interface software interacting with multiple software applications or processes in
order to synchronize animations associated with multiple views or windows of a
display of a device. The method 2100 for synchronizing the animations includes
setting attributes of views independently with each view being associated with a
process at block 2102. For example, an attribute or property of a view may
include a position, size, opacity, etc. An animation alters one or more attributes

from a first state to a second state. The method 2100 further includes
transferring a synchronization call to synchronize animations for the multiple
views of the display at block 2104. The synchronization call may include input

parameters or arguments such as an identification of the synchronization of the
processes and a list of the processes that are requesting animation of the multiple

views. In one embodiment, the synchronization call includes the identification
and the number of processes that are requesting animation. In one embodiment,
each application or process sends a synchronization call at different times. The

method 2100 further includes transferring a synchronization confirmation
message when a synchronization flag is enabled at block 2106. The
synchronization flag can be enabled when the processes to be synchronized have
each sent messages to a window server operating the user interface software.

The method 2100 further includes updating the attributes of the views from a
first state to a second state independently at block 2108. In one embodiment, the
window server receives the updated attributes from each process at different
times. The method 2100 further includes transferring a start animation call to

draw the requested animations when both processes have updated attributes
associated with the second state at block 2110.

[00116]

In some embodiments, a first data structure or layer tree

represents a hierarchy of layers that correspond to the views or windows of the
processes. A second data structure or render tree represents a similar copy of the

layer tree. However, the render tree is not updated until the independent
processes have completed their separate animations. At this time, the render tree
updates and redraws the screen with the new animations.

-26-

APLNDC00027721

WO 2008/085848

[00117]

PCT/US2008/000060

FIG. 22A and 22B illustrate synchronizing the resizing of views

or windows of a display of a device. For example, a window 2210 associated
with a first process with a size attribute may mcrease m size by changing from a
first state, window 2210 in FIG. 22A, to a second state, window 2210 in FIG.
22B. At approximately the same time, a second window 2220 may decrease in
size in proportion to the increase in size of the first window 2210. The method
2100 provides synchronization of the resizing.of the windows 2210 and 2220

illustrated in FIG. 22A and 22B. The animations in changing from the first state
to the second state may occur ins.w,,,entally and occur with the synchronization

of method 2100.
[00118]

FIG. 23 illustrates a method for switching ownership of a view of

an application displayed on a display of a data processing device. The method
2300 includes constructing a data structure having a hierarchy of layers with a
layer being associated with a view and owning the view at block 2302. The layers
may be content, windows, video, images, text, media, or any other type of object
for user interface of the application. The method 2300 further includes removing
the layer from the data structure at block 2304. The method 2300 further includes
switching ownership of the view from the layer to the view at block 2306.

{00119]

In some embodiments, each layer from the data structure is

associated with a view. The layer associated with the view sends a delegate
function call to the view in order to generate content provided by the view. A
first pointer reference points from the layer to the view. A second pointer
reference points from the view to the layer. The number of references pointing to

an object such as the view is defined as the retained count of the object. The view
may receive notification that the layer will be removed from the data structure.
Removing the layer from the data structure may occur based on the view
associated with the layer being removed from the display of the device. When the
layer is removed from the data structure or layer tree the pointer from the layer to
the view will be removed. The view will have a retained count of zero and be
deallocated or removed from memory if the ownership of the view is not reversed.
The view will have a retained count of at least one if ownership is reversed.
-27-

APLNDC00027722

WO 2008/085848

[00120]

PCT/US2008/000060

FIG. 24 illustrates a method for memory management of a view of

an application displayed on a display of a device. The method 2400 includes
constructing a data structure having a hierarchy of layers with at least one layer

being associated with the view at block 2402. The method 2400 further includes
storing the data structure in memory at block 2404. The method 2400 further
includes maintaining a retained count of the number of references to the view

from other objects at block 2406. The method 2400 further includes deallocating
the view from memory if the retained count is zero at block 2408. As discussed
above, the retained count of the view will be decremented if the layer is removed
from the data structure. Removing the layer from the data structure may occur
based on the view associated with the layer being removed from the display of
the device.

[00121]

FIG. 25A and 25B illustrate a data structure having a hierarchy of

layers with a layer being associated with a view. The data structure includes

layers 2502, 2504, and 2506. Layer 2506 is associated with the view 2510. The
layer 2506 associated with the 2510 view sends a delegate call to the view in
order to generate content provided by the view. A first pointer reference 2508
points from the layer 2506 to the view 2510. A second pointer reference 2512
points from the view 2510 to the layer 2506. A third pointer reference 2532 may
point from user interface (UI) controller 2530 to the view 2510. The UI
controller 2530 may control operations associated with the view 2510 such as
scrolling the view 2510 in response to a user input. The view 2510 in FIG. 25A

has a retained count of two.based on the pointer references 2508 and 2532.
[00122]

If the layer 2506 is removed from the data structure as illustrated

in FIG. 25B, then the pointer 2508 is removed. View 2510 will have a lower
retained count as illustrated in FIG. 25B. If view 2510 has a retained count of
zero, then the memory storing the view 2510 will be deallocated.

[00123]

FIG. 26 illustrates a method for compositing media and non-

media content of user interface for display on a device. The method 2600
includes constructing a data structure having a hierarchy of layers associated

with the user interface of the device at block 2602. The method 2600 further

-28-

APLNDC00027723

WO 2008/085848

PCT/US2008/000060

includes determining whether each layer of the data structure is associated with

media or non-media content at block 2604. The data structure or layer tree is
traversed in order to determine whether each of the layers of the data structure is
associated with media or non-media content. The method 2600 further includes
detaching a layer associated with media content from the data structure at block
2606. The method 2600 further includes storing media content in a first memory

location at block 2606. The method 2600 further includes storing non-media
content in a second memory location at block 2608. The method 2600 further
includes compositing the media and non-media content for display on the device

at block 2610.
[00124]

In some embodiments, compositing the media and non-media

content includes retrieving the media content from the first memory location,
retrieving the non-media content from the second memory location, and scanning
the media and non-media content directly to the display. The memory location
can be any type of memory located in cache, main memory, a graphics
processing unit, or other location within a device. The media content may
include video, video plug-in, audio, image, or other time varying media. The

media content may be in the form of a YUV model with the Y representing a
luminance component (the brightness) and U and V representing chrominance
(color) components. The media content may be scanned to the display at a rate

of substantially twenty to forty frames per second. The media content may be
scaled prior to being scanned to the display of the device.

[00125]

The non-media content may include content, views, and images

that do not require frequent updating. The non-media content may be in the form
of a RGB model which is an additive model in which red, green, and blue (often

used in additive light models) are combined in various ways to reproduce other
colors. The non-media content may be scanned to the display at a slower rate
compared to the media content.
[00126]

FIG. 27 illustrates a data structure or layer tree having a hierarchy

of layers. The layers can be associated with media and non-media content. For
example, layer 2704 is associated with media content 2706 such as a video.
-29-

APLNDC00027724

WO 2008/085848

PCT/US2008/000060

Layer 2710 is associated with non-media content 2712 which may be user
interface view for the video. Layers 2720, 2730, and 2740 are associated with
non-media content 2722, 2732, and 2742, respectively, that forms the

components of the non-media content 2712. The method 2600 will determine
whether each layer of the data structure is associated with media or non-content.
Any layers associated with media content such as layer 2704 will be removed
from the data structure and processed in a separate memory location.

[00127]

In some embodiments, the methods, systems, and apparatuses of

the present disclosure can be implemented in various devices including
electronic devices, consumer devices, data processing devices, desktop
computers, portable computers, wireless devices, cellular devices, tablet devices,

handheld devices, multi touch devices, multi touch data processing devices, any
combination of these devices, or other like devices. Figures 4-6 and 28-33
illustrate examples of a few of these devices.
[00128]

FIG. 28 illustrates a device 2800 according to one embodiment of

the disclosure. FIG. 28 shows a wireless device in a telephone configuration

having a "candy-bar" style. In FIG. 28, the wireless device 2800 may include a
housing 2832, a display device 2834, an input device 2836 which may be an
alphanumeric keypad, a speaker 2838, a microphone 2840 and an antenna 2842.
The wireless device 2800 also may include a proximity sensor 2844 and an
accelerometer 2846. It will be appreciated that the embodiment of FIG. 28 may
use more or fewer sensors and may have a different form factor from the form

factor shown in FIG. 28.
[00129]

The display device 2834 is shown positioned at an upper portion

of the housing 2832, and the input device 2836 is shown positioned at a lower
portion of the housing 2832. The antenna 2842 is shown extending from the

housing 2832 at an upper portion of the housing 2832. The speaker 2838 is also
shown at an upper portion of the housing 2832 above the display device 2834.
The microphone 2840 is shown at a lower portion of the housing 2832, below the
input device 3286. It will be appreciated that the speaker 2838 and microphone

-30-

APLNDC00027725

WO 2008/085848

PCT/US2008/000060

2840 can be positioned at any location on the housing, but are typically
positioned in accordance with a.user's ear and mouth, respectively.
[00130]

The display device 2834 may be, for example, a liquid crystal

display (LCD) which does not include the ability to accept inputs or a touch
input

which also includes an LCD. The input device 2836 may include,

for example, buttons, switches, dials, sliders, keys or keypad, navigation pad,
touch pad, touch screen, and the like. Any well-known speaker, microphone and
antenna can be used for speaker 2838, microphone 2840 and antenna 2842,
respectively.
[00131]

The data acquired from the proximity sensor 2844 and the

accelerometer 2846 can be combined together, or used alone, to gather
information about the user's activities. The data from the proximity sensor 2844,
the accelerometer 2846 or both can be used, for example, to activate/deactivate a

display backlight, initiate commands, make selections, control scrolling,
gesturing, animating or othpr movement in a display, control input device
settings, or to make other changes to one or more settings of the device. In
certain embodiments of the present disclosure, the device 2800 can be used to
implement at least some of the methods discussed in the present disclosure.
[00132]

FIG. 29 shows a device 2950 in accordance with one embodiment

of the disclosure. The device 2950 may include a housing 2952, a display/input
device 2954, a speaker 2956, a microphone 2958 and an optional antenna 2960
(which may be visible on the exterior of the housing or may be concealed within

the housing). The device 2950 also may include a proximity sensor 2962 and an
accelerometer 2964. The device 2950 may be a cellular telephone or a device
which is an integrated PDA and a cellular telephone or a device which is an
integrated media player and a cellular telephone or a device which is both an
entertainment system (e.g. for playing games) and a cellular telephone, or the

device 2950 may be other types ôf devices described herein. In one particular
embodiment, the device 2950 may include a cellular telephone and a media

player and a PDA, all contained within the housing 2952. The device 2950 may
have a form factor which is small enough that it fits within the hand of a normal

-31-

APLNDC00027726

WO 2008/085848

PCT/US2008/000060

adult and is light enough that it can be carried in one hand by an adult. It will be
appreciated that the term "portable" means the device can be easily held in an
adult user's hands (one or both); for example, a laptop computer and an iPod are
portable devices.
[00133]

In one embodiment, the displaylinput device 2954 may include a

multi-point touch input screen in addition to being a display, such as an LCD. In
one embodiment, the multi-point touch screen is a capacitive sensing medium
configured to detect multiple touches (e.g., blobs on the display from a user's
face or multiple fingers concurrently touching or nearly touching the display) or

near touches (e.g., blobs on the display) that occur at the same time and at
distinct locations in the plane of the touch panel and to produce distinct signals
representative of the location of the touches on the plane of the touch panel for
each of the multiple touches.
[00134]

In certain embodiments of the present disclosure, the device 2800

can be used to implement at least some of the methods discussed in the present
disclosure.
[00135]

FIGS. 30A and 30B illustrate a device 3070 according to one

embodiment of the disclosure. The device 3070 may be a cellular telephone

which includes a hinge 3087 that couples a display housing 3089 to a keypad
housing 3091. The hinge 3087 allows a user to open and close the cellular

telephone so that it can be placed in at least one of two different configurations
shown in FIGS. 30A and 30B. In one particular embodiment, the hinge 3087
may rotatably couple the display housing to the keypad housing. In particular, a
user can open the cellular telephone to place it in the open configuration shown
in FIG. 30A and can close the cellular telephone to place it in the closed

configuration shown in FIG. 30B. The keypad housing 3091 may include a
keypad 3095 which receives inputs (e.g. telephone number inputs or other
alphanumeric inputs) from a user and a microphone 3097 which receives voice

input from the user. The display housing 3089 may include, on its interior
surface, a display 3093 (e.g. an LCD) and a speaker 3098 and a proximity sensor
3084; on its exterior surface, the display housing 3089 may include a speaker
-32-

APLNDC00027727

WO 2008/085848

PCT/US2008/000060

3096, a temperature sensor 3094, a display 3088 (e.g. another LCD), an ambient
light sensor 3092, and a proximity sensor 3084A. Hence, in this embodiment,
the display housing 3089 may include a first proximity sensor on its interior
surface and a second proximity sensor on its exterior surface.
[00136]

In at least certain embodiments, the device 3070 may contain

components which providpsone or more of the functions of a wireless
communication device such as a cellular telephone, a media player, an
entertainment system, a PDA, or other types of devices described herein. In one
implementation of an embodiment, the device 3070 may be a cellular telephone

integrated with a media player which plays MP3 files, such as MP3 music files.
[00137]

Each of the devices shown in FIGS. 4, 5A, SB, 5C, 6A, 6B, 6C,

6D, 28, 29, 30A and 30B may be a wireless communication device, such as a
cellular telephone, and may include a plurality of components which provide a

capability for wireless communication. FIG. 31 shows an embodiment of a
wireless device 3070 which includes the capability for wireless communication.
The wireless device 3070 may be included in any one of the devices shown in

FIGS. 4, 5A, 5B, 5C, 6A, 6B, 6C, 6D, 28, 29, 30A and 30B, although alternative
embodiments of those devices of FIGS. 4, 5A, 5B, 5C, 6A, 6B, 6C, 6D, 28, 29,
30A and 30B may include more or fewer components than the Wireless device

3070.
[00138]

Wireless device 3070 may include an antenna system 3101.

Wireless device 3070 may also include a digital and/or analog radio frequency
(RF) transceiver 3102, coupled to the antenna system 3101, to transmit and/or
receive voice, digital data and/or media signals through antenna system 3101.
[00139]

Wireless device 3070 may also include a digital processing

system 3103 to control the digital RF transceiver and to manage the voice, digital
data and/or media signals. Digital processing system 3103 may be a general
purpose processing device, such as a microprocessor or controller for example.

Digital processing system 3103 may also be a special purpose processing device,
such as an ASIC (application specific integrated circuit), FPGA (fieldprogrammable gate array) or DSP (digital signal processor). Digital processing
-33-

APLNDC00027728

WO 2008/085848

PCT/US2008/000060

system 3103 may also include other devices, as are known in the art, to interface
with other components of wireless device 3070. For example, digital processing
system 3103 may include analog-to-digital and digital-to-analog converters to
interface with other components of wireless device 3070. Digital processing

system 3103 may include a media processing system 3109, which may also
include a general purpose or special purpose processing device to manage media,
such as files of audio data.
[00140]

Wireless device 3070 may also include a storage device 3104,

coupled to the digital processing system, to store data and/or operating programs
for the Wireless device 3070. Storage device 3104 may be, for example, any

type of solid-state or magnetic memory device.
[00141]

Wireless device 3070 may also include one or more input devices

3105, coupled to the digital processing system 3103, to accept user inputs (e.g.,
telephone numbers, names, addresses, media selections, etc.) Input device 3105
may be, for example, one or more of a keypad, a touchpad, a touch screen, a
pointing device in combination with a display device or similar input device.

[00142)

Wireless device 3070 may also include at least one display device

33106, coupled to the digital processing system 3103, to display information
such as messages, telephone call information, contact information, pictures,
movies and/or titles or other indicators of media being selected via the input
device 3105. Display device 3106 may be, for example, an LCD display device.
In one embodiment, display device 3106 and input device 3105 may be
integrated together in the same device (e.g., a touch screen LCD such as a multi-

touch input panel which is integrated with a display device, such as an LCD
display device). The display device 3106 may include a backlight 3106A to
illuminate the display device 3106 under certain circumstances. It will be
appreciated that the Wireless device 3070 may include multiple displays.
[00143]

Wireless device 3070 may also include a battery 3107 to supply

operating power to components of the system including digital RF transceiver

3102, digital processing system 3103, storage device 3104, input device 3105,
microphone 3105A, audio transducer 3108, media processing system 3109,

-34-

APLNDC00027729

WO 2008/085848

PCT/US2008/000060

sensor(s) 3110, and display device 3106. Battery 3107 may be, for example, a

rechargeable or non-rechargeable lithium or nickel metal hydride battery.
Wireless device 3070 may also include audio transducers 3108, which may
include one or more speakers, and at least one microphone 3105A. In certain

embodiments of the present disclosure, the wireless device 3070 can be used to
implement at least some of the methods discussed in the present disclosure.
[00144]

-

FIG. 32 shows another example of a device according to an

embodiment of the disclosure. This device 3200 may include a processor, such
as microprocessor 3202, and a memory 3204, which are coupled to each other

through a bus 3206. The device 3200 may optionally include a cache 3208
which is coupled to the microprocessor 3202. This device may also optionally
include a display controller and display device 3210 which is coupled to the
other components through the bus 3206. One or more input/output controllers
3212 are also coupled to the bus 3206 to provide an interface for input/output
devices 3214 and to provide an interface for one or more sensors 3216 which are
for sensing user activity. The bus 3206 may include one or more buses
connected to each other through various bridges, controllers, and/or adapters as is
well known in the art. The input/output devices 3214 may include a keypad or
keyboard or a cursor control device such as a touch input panel. Furthermore,

the input/output devices 3214 may include a network interface which is either for
a wired network or a wireless network (e.g. an RF transceiver). The sensors

3216 may be any one of the sensors described herein including, for example, a
proximity sensor or an ambient light sensor. In at least certain implementations
of the device 3200, the microprocessor 3202 may receive data from one or more
sensors 3216 and may perform the analysis of that data in the manner described
herein. For example, the data may be analyzed through an artificial intelligence
process or in the other ways described herein. As a result of that analysis, the
microprocessor 3202 may then automatically cause an adjustment in one or more
settings of the device.

-35-

APLNDC00027730

WO 2008/085848

[00145]

PCT/US2008/000060

In certain embodiments of the present disclosure, the device 3200

can be used to implement at least some of the methods discussed in the present
disclosure.
[00146]

FIGS. 33A-C show another example of a device according to at

least certain embodiments of the disclosure. FIG. 33A illustrates a laptop device

3300 with a keyboard 3302, a body 3304, a display frame 3306, and a display
3308. The laptop device 3300 can be converted into a tablet device as illustrated

in FIG. 33B and FIG. 33C. FIG. 33B illustrates the conversion of the laptop
device into a tablet device. An edge of a display frame 3356 containing a display
3358 is slide within the body 3354 across the top of a keyboard 3352 until
forming a tablet device as illustrated in FIG. 33C. The tablet device with a

display 2362 and a display frame 3366 rests on top of a body 3360.
[00147]

In certain embodiments of the present disclosure, the laptop

device 3300 can be used to implement at least some of the methods discussed in
the present disclosure.

[00148]

FIG. 34 illustrates details of an application programming interface

in flow chart form according to certain teachings of the present disclosure. The
application progr

ing interface operates in an environment with user interface

software interacting with a software application. In some embodiments, a
hierarchy of views operates on top of a hi.....hy of layers within the user
interface software. The API operates as illustrated in method 3400 that includes
constructing a hierarchy of views operating on top of a hierarchy of layers at
block 3402. The method 3400 further includes providing access to the hierarchy
of views without providing access to the hierarchy of layers at block 3404. An
application may interact with the hierarchy of views via the API without
accessing the hi

[00149]

hy of layers operating below the hierarchy of views.

In some embodiments, a platform provides various scrolling,

gesturing, and animating operations. The platform includes hardware
components and an operating system. The hardware components may include a
processing unit coupled to an input panel and a memory coupled to the
processor. The operating system includes one or more programs that are stored

-36-

APLNDC00027731

WO 2008/085848

PCT/US2008/000060

in the memory and configured to be executed by the processing unit. One or
more programs include various instructions for transferring function calls or
messages through an application programming interface in order to perform
various scrolling, gesturing, and animating operations.
[00150]

In an embodiment, the one or more programs include instructions

for transferring a scaling transform call through an API to determine a scaling

transform for a view associated with a user input having a plurality of input
points. In an embodiment, the one or more programs include instructions for
transferring a rubberband call through an API to determine a rotation transform

for a view associated with a user input having a plurality of input points.
[00151]

In some embodiments, the platform includes a framework

containing a library of software code. The framework interacts with the
programs of the platform to provide application programming interfaces for
performing various scrolling, gesturing, and animating operations. The
framework also includes associated resources (e.g., images, text, etc.) that are
stored in a single directory.
[00152]

In an embodiment, the library of the framework provides an API

for specifying a scaling transform for a view associated with a user input having

a plurality of input points. In an embodiment, the library of the framework

provides an API for specifying a a scaling transform for a view associated with a
user input having a plurality of input points.
[00153]

In the foregoing specification, the disclosure has been described

with reference to specific exemplary embodiments thereof. It will be evident that

various modifications may be made thereto without departing from the broader
spirit and scope of the disclosure as set forth in the following claims. The
specification and drawings are, accordingly, to be regarded in an illustrative
sense rather than a restrictive sense.

-37-

APLNDC00027732

WO 2008/085848

PCT/US2008/000060

APPENDIX A
API SOr i vv A * CODE
1
2
3
4
5

- (AffmeTransform)transform;
- (void)setTransform:(AffineTransform)transform: //

6
7

+ (void)beginAnimation: (String*)animationIDS;
you don't want to have an identifer for the group

8
9

+ (void)beginAnimations: (String*)animationID context: (void*) context // additional
context info passed to will start/did stop selectors

animatable

@interface UIView(Animation)
//

animationID can be nil if

10
11
12
13
14
15
I6
17
18
19
20
21

+(void)endAnimations;

// this is called if the app is going to be suspending back to a previous
application.

22
23
24
25
26
27

// the app should return YES if it is going to perform animation, otherwise it should
// return NO. The startTime argument is a start time for any animations to begin so that
// the animations are synchronized with a window server. If the application's
// implementation of this method returns YES, it should later call [UIApp
suspendWith ANimation:NO] when
// it is finished animating.

28
29

(BOOL)animateSuspensionReturningToLastApp:AbsoluteTime)startTime;

30
31

// Set the status bar mode, orientation over duration. If processSynchID is non-zero,
used as sync ID.

32
33
34
35
36
37
38
39
40
41
42
43
44
45

- (void) setStatusBarMode: (UIStatusBarMode) mode
orientation: (UIStatusBarOrientation) orientation duration:(float)duration
processSynchID: (int)processSynchID;
// Sets the status bar mode. O duration means no animation
- (void) setStatusBarMode: (UIStatusBarMode)mode
orientation: (UIStatusBarOrientation)orientation duration: (float)duration;
- (void) setStatusBarMode: (UIStatusBarMode)mode duration:(float)duration; //
uses the default orientation.
- (UIStatusBarOrientation) statusBarOrientation;
- (UIStatusBarOrientation) statusBarMode;
// Status bar rect in non-rotated window coordinates.

46

//

+(void)setAnimationDelegate:(id)delegate;
+(void)setAnimationDuration:(TimeInterval)duration;
+(void)setAnimationDelay:(TimeInterval)delay;
+(void)setAnimationStartTime:(AbsoluteTime)start;
+(void)setAnimationCurve:(UIViewAnimationCurve)curve;
- (BOOL)handleEvent: (Event)event;

- (void) synchronizedDrawingWithID: (int)processSynchID; // used for status bar
resize

-38-

APLNDC00027733

WO2008/085848

PCT/US2008/000060

APPENDIX A
API SOFTW
© CODE
47
48

// Gesture delegate method. event will be nil if gesture was not event-driven (ie
programatically or animation).

49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67

@interface Object(UIViewGestureDelegate)

68
69
70
71
72
73

UIScrollerEventModeInterceptOnDrag, // send mouseDown / mouseUp to
subviews if not dragged
UIScrollerEventModePass,
//
send
mouseDown/mouseDrag/mouseUp to subviews
UIScrollerEventModeIntercept, // send mouseDown / mouseUp to subviews
} UIScrollerEventMode;

74
75
76
77
78
79
80
81
82

- (void)setEventMode:(UIScrollerEventMode)mode;

83
84
85
86
87
88
89
90
91

- (void)willStartGestures: (UIView *)view forEvent: (GSEvent)event;
- (void)didFinishGestures: (UIView *)view forEvent: (Event)event;
- (void)willStartGesture: (UIGestureType)type inView: (UIView *) view
forEvent: (Event)event;
- (void)gestureDidChange: (UIGestureType)type inView: (UIView *) view
forEvent: (Event)event;

- (void)didFinishGesture: (UIGestureType)type inView: (UIView *) view
forEvent: (Event)event;
@end
UIGestureAttributeZooms // Number (BOOL)
typedef enum {

- (void)setDirectionalScrolling:(BOOL)flag;
- (void)setDirectionalScrollingAngle:(float)flag;

- (void)setScrollDecelerationFactor:(float)factor;
- (void)setBounces:(BOOL)bounces;

- (void)setThumbDetectionEnabled:(BOOL)flag;

- (void)setShowScrollerIndicators:(BOOL)flag;
- (void)setScrollerIndicator:(Rect)rect;
- (void)setScrollerIndicatorsPinToContent:(BOOL)flag;

-39-

APLNDC00027734

WO 2008/085848

PCT/US2008/000060

APPENDIX A
API SOFTWARE CODE
92
93

- (void)setAllowsRubberBanding:(BOOL)flag; // CallsetRubberBand:forEdges:
with RUBBER BAND HEIGHT for the top and bottom edges

94
95
96
97

- (void)setAllowsFourWayRubberBanding:(BOOL)flag;
// Calls
setRubberBand: for Edges: with RUBBER_BAND_HEIGHT for all edges

98

- (void)setRubberBand: (float) vallie for Edges: (UIRectEdge) edges: // Default

99
100
101
102
103
104
105
106
107
108
109
110
111

set for top and bottom edges
- (void)contentMouseUpInView:(UIView*)mouseUpView
withEvent:(Event)event;
// default calls -mouseUp; on view

- (Point)scroller:(UIScroller *)scroller
adjustSmoothScrollEnd:(Point)offset velocity:(Size)velocity;
@interfacebject (UIAnimationDelegate)
-(void)animator: (UIAnimator*)animator
startAnimation:(UIAnimation*)animation;
-(void)animator: (UIAnimator*)animator
stopAnimation:(UIAnimation*)animation;

112

-(void)animator: (UIAnimator*)animator stopAnimation: (UIAnimation*)animation

113
114
115
116
l 17
120
121
122
123
124

fraction: (float) fraction;
@end
//
@interface UITransformAnimation :
UIAnimation {
@ protected
AffineTransform
startTransform;
AffineTransform
endTransform;
}
-(void)setStartTransform: (AffineTransform)start;
-(void)setEndTransform: (AffineTransform)end;
- (AffineTransform)transformForFraction: (float) fraction;
@end

125

//

126
127
128
129
130
131
132
133
134
135
136
137

@interface UIFrameAnimation
:
UIAnimation {
Rect _startFrame;
Rect _endFrame;
UIRectFields fieldsToChange;
}
- (void) setStartFrame: (Rect)start;
- (void) setEndFrame: (Rect)end;
- (void) setSignificantRectFields: (UIRectFields)fields;

118
119

-(Rect)endFrame;
@end

-40-

APLNDC00027735

WO2008/085848

PCT/US2008/000060

APPENDIX A
API SOFTWARE CODE

138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153

154

@interface UIAlphaAnimation : UIAnimation
@protected
float
startAlpha;
float
_endAlpha;
}
- (void)setStartAlpha: (float)start;
- (void)setEndAlpha: (float)end;
- (void)alphaForFraction: (float)fraction;

{

@end
@interface UIRotationAnimation
:
UIAnimation {
float _startAngle;
float _endAngle;
- (void)setStartRotationAngle: (float)degrees;
- (void)setEndRotationAngle: (float) degrees;

-41-

APLNDC00027736

WO 2008/085848

PCT/US2008/000060

CLAIMS

What is claimed is:
1.

In an environment with a device having a display with multiple views and

user interface software interacts with a software application, a method for
operating through an application programming interface (API), comprising:
transferring a handle gesture event call; and
transferring a gesture change call in response to the handle gesture event
call.
2.

The method as in claim I wherein the handle gesture event call is

transferred in response to a gesture event associated with a user input that
comprises a plurality of input points touching the display.
3.

The method as in claim 2, wherein the gesture event comprises a chord

event object having a chord count, chord start event, chord change event, and
chord end event.
4.

The method as in claim 1, wherein transferring the handle gesture event

call is either one of issuing, initiating, invoking and receiving the handle gesture
event call.
5.

The method as in claim 1, wherein transferring the gesture change call is

either one of issuing, initiating, invoking and receiving the handle change call.
6.

The method as in claim 1, wherein the device is one of: a data processing

device, a portable device, a portable data processing device, a multi touch device,
a multi touch portable device, a wireless device, and a cell phone.
7.

A machine readable medium storing executable program instructions

which when executed cause a data processing system to perform a method

comprismg:
-42-

APLNDC00027737

WO 2008/085848

PCT/US2008/000060

transferring a handle gesture event call; and
transferring a gesture change call in response to the handle gesture event
call.

8.

The medium as in claim 7 wherein the handle gesture event call is

transferred in response to a gesture event associated with a user input that
comprises a plurality of input points touching the display.
9.

The medium as in claim 7, wherein the gesture object comprises a chord

event object having a chord count, chord start event, chord change event, and
chord end event.
10.

The medium as in claim 7, wherein transferring the handle gesture event

call is either one of issuing, initiating, invoking and receiving the handle gesture
event call.

11.

The medium as in claim 7, wherein transferring the gesture change call is

either one of issuing, initiating, invoking and receiving the handle change call.
12.

The medium as in claim 7, wherein the data processing system is one of:

a data processing device, a portable device, a portable data processing device, a
multi touch device, a multi touch portable device, a wireless device, and a cell
phone.
13.

In an environment with a user interface software interacting with a

software application, an apparatus, comprising:
means for transferring a handle gesture event call; and

means for transferring a gesture change call in response to the handle
gesture event call.

-43-

APLNDC00027738

WO 2008/085848

14.

PCT/US2008/000060

In an environment with a device having a display with multiple views and

user interface software interacts with a software application, a method for
operating through an application programming interface (API), comprising:
receiving a handle gesture event call; and
receiving a gesture change call in response to the handle gesture event

call.
15.

The method as in claim 14 wherein the handle gesture event call is

received in response to a gesture event associated with a user input that
comprises a plurality of input points touching the display.
16.

The method as in claim 14, wherein the gesture event comprises a chord

event object having a chord count, chord start event, chord change event, and
chord end event.
17.

A machine readable medium storing executable program instructions

which when executed cause a data processing system to perform a method
comprismg:
receiving a handle gesture event call; and
receiving a gesture change call in response to the handle gesture event

call.
18.

The medium as in claim 17 wherein the handle gesture event call is

received in response to a gesture event associated with a user input that
comprises a plurality of input points touching the display.
19.

The medium as in claim 18, wherein the gesture event comprises a chord

event object having a chord count, chord start event, chord change event, and

chord end event.

-44-

APLNDC00027739

WO 2008/085848

20.

PCT/US2008/000060

In an environment with a user interface software interacting with a

software application, an apparatus, compnsmg:
means for receiving a handle gesture event call; and
means for receiving a gesture change call in response to the handle
gesture event call.
21.

In an environment with a device having a display with multiple views and

user interface software interacts with a software application, a method for
operating through an application programming interface (API), comprising:
transferring a scaling transform call to determine a scaling transform for a
view associated with a user input having a plurality of input points.
22.

The method of claim 21, further comprising:
transferring a start scaling gesture call;

transferring a scaling gesture progress call; and
transferring a scaling gesture end call.
23.

The method of claim 21, wherein the scaling transform comprises a

minimum and maximum scale factor.
24.

The method of claim 21, wherein the scaling transform varies from the

minimum to the maximum scale factor based on a flag being disabled.
25.

The method of claim 21, wherein the scaling transform varies from the

minimum to slightly past the maximum scale factor based on the flag being

enabled prior to snapping back to the maximum scale factor.
26.

The method as in claim 21, wherein transferring the scaling transform

call is either one of issuing, initiating, invoking and receiving the scaling
transform call.

-45-

APLNDC00027740

WO 2008/085848

27.

PCT/US2008/000060

The method as in claim 21, wherein the device is one of: a data

processing device, a portable device, a portable data processing device, a multi
touch device, a multi touch portable device, a wireless device, and a cell phone.
28.

A machine readable medium storing executable program instructions

which when executed cause a data processing system to perform a method

comprismg:
transferring a scaling transform call to determine a scaling transform for a
view associated with a user input having a plurality of input points.

29.

The medium of claim 28, further comprising:
transferring a start scaling gesture call;

transferring a scaling gesture progress call; and
transferring a scaling gesture end call.
30.

The medium of claim 28, wherein the scaling transform comprises a

minimum and rnaximum scale factor.
31.

The medium of claim 28, wherein the scaling transform varies from the

minimum to the maximum scale factor based on a flag being disabled.
32.

The medium of claim 28, wherein the scaling transform varies from the

minimum to slightly past the maximum scale factor based on the flag being
enabled prior to snapping back to the maximum scale factor.

33.

The medium as in claim 28, wherein transferring the scaling transform

call is either one of issuing, initiating, invoking and receiving the scaling
transform call.
35.

The medium as in claim 28, wherein the data processing system is one of:

a data processing device, a portable device, a portable data processing device, a
-46-

APLNDC00027741

WO 2008/085848

PCT/US2008/000060

multi touch device, a multi touch portable device, a wireless device, and a cell

phone.
36.

In an environment with a user interface software interacting with a

software application, an apparatus, comprising:
means for transferring a scaling transform call to determine a scaling
transform for a view associated with a user input having a plurality of input
points.

37.

In an environment with a device having a display with multiple views and

user interface software interacts with a software application, a method for
operating through an application programming interface (API), comprising:
receiving a scaling transform call to determine a scaling transform for a
view associated with a user input having a plurality of input points.
38.

The method of claim 37, further comprising:
receiving a start scaling gesture call;
receiving a scaling gesture progress call; and
- ving a scaling gesture end call.

39.

The method of claim 37, wherein the scaling transform comprises a

minimum and maximum scale factor.
40.

The method of claim 37, wherein the scaling transform varies from the

minimum to the maximum scale factor based on a flag being disabled.
41.

The method of claim 37, wherein the scaling transform varies from the

minimum to slightly past the maximum scale factor based on the flag being
enabled prior to snapping back to the maximum scale factor.

-47-

APLNDC00027742

WO 2008/085848

42.

PCT/US2008/000060

A machine readable medium storing executable program instructions

which when executed cause a data processing system to perform a method
comprismg:
receiving a scaling transform call to determine a scaling transform for a
view associated with a user input having a plurality of input points.
43.

The medium of claim 37, further comprising:
receiving a start scaling gesture call;
receiving a scaling gesture progress call; and
receiving a scaling gesture end call.

44.

The medium of claim 37, wherein the scaling transform comprises a

minimum and maximum scale factor.
45.

The medium of claim 37, wherein the scaling transform varies from the

minimum to the maximum scale factor based on a flag being disabled.
46.

The medium of claim 37, wherein the scaling transform varies from the

minimum to slightly past the maximum scale factor based on the flag being
enabled prior to snapping back to the maximum scale factor.
47.

In an environment with a user interface sofhvare interacting with a

software application, an apparatus, comprismg:
means for receiving for transferring a scaling transform call to determine

a scaling transform for a view associated with a user input having a plurality of
input points.
48.

In an environment with a device having a display with multiple views and

user interface software interacts with a software application, a method for
operating through an application progr

ing interface (API), comprising:

-48-

APLNDC00027743

WO 2008/085848

PCT/US2008/000060

setting a gesture scaling transform flag to determine a scaling transform

for a view associated with a user input having a plurality of input points.
49.

The method of claim 48, wherein the scaling transform flag scales either

from a current scale factor to a minimum scale factor or from the current scale
factor to a maximum scale factor.
50.

A machine readable medium storing executable program instructions

which when executed cause a data processing system to perform a method
comprismg:
setting a gesture scaling transform flag to determine a scaling transform
for a view associated with a user input having a plurality of input points.
51.

The medium of claim 50, wherein the scaling transform flag scales either

from a current scale factor to a minimum scale factor or from the current scale

factor to a maximum scale factor.
52.

In an environment with a user interface software interacting with a

software application, an apparatus, comprising:
means for setting a gesture scaling transform flag to determine a scaling
transform for a view associated with a user input having a plurality of input
points.
53.

In an environment with a device having a display with multiple views and

user interface software interacts with a software application, a method for
operating through an application programming interface (API), comprising:
transferring a rotation transform call to determine a rotation transform for

a view associated with a user input having a plurality of input points.
54.

The method of claim 53, further comprising:
transferring a start rotation gesture call;

-49-

APLNDC00027744

WO 2008/085848

PCT/US2008/000060

transferring a gesture rotation progress call; and
transferring a rotation gesture end call.
55.

The method of claim 53, wherein the rotation transform comprises a

minimum and maximum degree of rotation for associated minimum and
maximum rotation views.
56.

The method as in claim 53, wherein transferring the rotation transform

call is either one of issuing, initiating, invoking and receiving the scaling
transform call.

57. The method as in claim 53, wherein the device is one of: a data processing
device, a portable device, a portable data processing device, a multi touch device,
a multi touch portable device, a wireless device, and a cell phone.
58.

A machine readable medium storing executable program instructions

which when executed cause a data processing system to perform a method
comprismg:
transferring a rotation transform call to determine a rotation transform for

a view associated with a user input having a plurality of input points.
59.

The medium of claim 58, further comprising:
transferring a start rotation gesture call;

transferring a gesture rotation progress call; and
transferring a rotation gesture end call.
60.

The medium of claim 58, wherein the rotation transform comprises a

minimum and maximum degree of rotation for associated minimum and
maximum rotation views.

-50-

APLNDC00027745

WO 2008/085848

61.

PCT/US2008/000060

The medium as in claim 58, wherein transferring the rotation transform

call is either one of issuing, initiating, invoking and receiving the scaling
transform call.

62.

The medium as in claim 58 wherein the data processing system is one of:

a data processing device, a portable device, a portable data processing device, a
multi touch device, a multi touch portable device, a wireless device, and a cell

phone.
63.

In an environment with a user interface software interacting with a

software application, an apparatus, comprising:
means for transferring a rotation transform call to determine a scaling
transform for a view associated with a user input having a plurality of input
points.

64.

In an environment with a device having a display with multiple views and

user interface software interacts with a software application, a method for

operating through an application programming interface (API), comprising:
receiving a rotation transform call to determine a rotation transform for a
view associated with a user input having a plurality of input points.

65.

The method of claim 64, further comprising:
receiving a start rotation gesture call;

receiving a gesture rotation progress call; and
receiving a rotation gesture end call.
66.

The method of claim 64, wherein the rotation transform comprises a

minimum and maximum degree of rotation for associated minimum and
maximum rotation views.

-51-

APLNDC00027746

WO 2008/085848

67.

PCT/US2008/000060

A machine readable medium storing executable program instructions

which when executed cause a data processing system to perform a method
comprismg:
receiving a rotation transform call to determine a rotation transform for a
view associated with a user input having a plurality of input points.

68.

The medium of claim 67, further comprising:
receiving a start rotation gesture call;
receiving a gesture rotation progress call; and
receiving a rotation gesture end call.

69.

The medium of claim 67, wherein the rotation transform comprises a

minimum and maximum degree of rotation for associated minimum and
maximum rotation views.
70.

In an environment with a user interface software interacting with a

software application, an apparatus, comprising:

means for receiving a rotation transform call to determine a scaling
transform for a view associated with a user input having a plurality of input

points.
71.

In an environment with a device having a display with multiple views and

user interface software interacts with a software application, a method for
operating through an application programming interface (API), comprising:
transferring a delegate call to notify a delegate of a gesture event.

72.

The method of claim 71, wherein the delegate call notifies the delegate of

the gesture event associated with a scaling transform on a view in order for the
delegate operating under the control of the software application to change other
views in response to the view being modified by the gesture event.

-52-

APLNDC00027747

WO 2008/085848

73.

PCT/US2008/000060

The method as in claim 71, wherein transferring the delegate call is either

one of issuing, initiating, invoking and receiving the delegate call.
74.

A machine readable medium storing executable program instructions

which when executed cause a data processing system to perform a method
comprismg:
75.

transferring a delegate call to notify a delegate of a gesture event.
The medium of claim 74, wherein the delegate call notifies the delegate

of the gesture event associated with a scaling transform on a view in order for the
delegate operating under the control of the software application to change other
views in response to the view being modified by the gesture event.
76.

The medium as in claim 74, wherein transferring the delegate call is

either one of issuing, initiating, invoking and receiving the delegate call.
77.

In an environment with a user interface software interacting with a

software application, an apparatus, comprising:

means for transferring a delegate call to notify a delegate of a gesture
event.

78.

In an environment with a device having a display with multiple views and

user interface software interacts with a software application, a method for
operating through an application progrwring interface (API), comprising:

receiving a delegate call to notify a delegate of a gesture event.
79.

The method of claim 78, wherein the delegate call notifies the delegate of

the gesture event associated with a scaling transform on a view in order for the
delegate operating under the control of the software application to change other
views in response to the view being modified by the gesture event.

-53-

APLNDC00027748

WO 2008/085848

80.

PCT/US2008/000060

A machine readable medium storing executable program instructions

which when executed cause a data processing system to perform a method
compnsmg:
receiving a delegate call to notify a delegate of a gesture event.
81.

The medium of claim 78, wherein the delegate call notifies the delegate

of the gesture event associated with a scaling transform on a view in order for the

delegate operating under the control of the software application to change other
views in response to the view being modified by the gesture event.
82.

In an environment with a user interfàce software interacting with a

software application, an apparatus, comprising:
means for receiving a delegate call to notify a delegate of a gesture event.

83.

A device comprising:
an input panel which is configured to receive user input in the form of

two or more input points;
a display device integrated with the input panel;

a central processing unit coupled to the input panel;
a memory coupled to the processor;
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
programs including:
instructions for detecting a movement of an user input on or near
the input panel;
instructions for handling a gesture event associated with a view in
response to detecting the user input.
84.

The device as in claim 83 further comprising instructions for performing

a scaling transform associated with the view.

-54-

APLNDC00027749

WO 2008/085848

85.

PCT/US2008/000060

The device as in claim 83 wherein the processor is configured to

determine which view the user input intends to select based on having positive
and negative charges for each contact of the input panel.

86. The method as in claim 83, wherein the device is one of: a data processing
device, a portable device, a portable data processing device, a multi touch device,
a multi touch portable device, a wireless device, and a cell phone.
87.

A computer read medium containing executable instructions, comprising:
program code configured, when executed, to transfer a scaling transform

call through an application programming interface to determine a scaling
transform for a view associated with a user input having a plurality of input
points.

88. The medium as in claim 87, wherein transferring the scaling transform call is
either one of issuing, initiating, invoking or receiving the scaling transform call.
89.

A computer read medium containing executable instructions, comprising:
program code configured, when executed, to transfer a rotation transform

call through an application programming interface to determine a rotation
transform for a view associated with a user input having a plurality of input

points.
90.

The medium as in claim 89, wherein transferring the rotation transform

call is either one of issuing, initiating, invoking or receiving the rotation
transform call.

91.

A platform for performing scrolling operations, comprising:
a processing unit coupled to an input panel;
a memory coupled to the processor; and

-55-

APLNDC00027750

WO 2008/085848

PCT/US2008/000060

one or more programs, wherein the one or more programs are stored in
the memory and configured to be executed by the processing unit, the programs
including:
instructions for transferring a scaling transform call through an
application programming interface to determine a scaling transform for a view
associated with a user input having a plurality of input points.
92.

The platform of claim 91, wherein the one or more programs further

comprise instructions for transferring a rotation transform call through an
application programming interface to determine a rotation transform for a view

associated with a user input having a plurality of input points.
93.

The platform as in claim 91, wherein transferring the scaling transform

call is either one of issuing, initiating, invoking or receiving the scaling

transform call.
94.

The platform as in claim 92, wherein transferring the rotation transform

call is either one of issuing, initiating, invoking or receiving the rotation
transform call.
95.

A framework for performing scrolling operations, comprising:

a directory for storing one or more programs and associated resources, wherein
the programs contain instructions that when executed provide an application
programming interface to specify a scaling transform for a view associated with
a user input having a plurality of input points.
96.

The framework of claim 95, wherein the one or more programs further

comprise instructions that when executed provide an application progr

ing

interface to specify a rotation transform for a view associated with a user input
having a plurality of input points.

-56-

APLNDC00027751

WO 2008/085848

PCT/US2008/000060

1/37

100

RECEIVE A USER INPUT
102

CREATE AN EVENT OBJECT IN
RESPONSETOTHEUSERINPUT
104
DETERMINE WHETHER THE EVENT OBJECT
INVOKES A SCROLL OR GESTURE
OPERATION

ISSUE AT LEAST ONE SCROLL OR
GESTURE CALL BASED ON INVOKING
THE SCROLL OR GESTURE OPERATION

RESPOND TO AT LEAST ONE SCROLL CALL,
IF ISSUED, SCROLL A WINDOW HAVING A
VIEW ASSOCIATED WITH THE EVENT OBJECT
BASED ON AN AMOUNT OF A SCROLL WITH
THE SCROLL STOPPED AT A PREDETERMINED
POSITION IN RELATION TO THE USER INPUT
110
RESPOND TO AT LEAST ONE GESTURE CALL,
IF ISSUED, CHANGE A VIEW ASSOCIATED
WITH THE EVENT OBJECT BASED ON
RECEIVING A PLURALITY OF INPUT POINTS
IN THE FORM OF THE USER INPUT
112

FIG. 1

APLNDC00027752

WO 2008/085848

PCT/US2008/000060

2/37
200

TRANSFER A SET BOUNCE CELL
202

SET AT LEAST ONEOF MAXIMUM AND
MINIMUM BOUNCEVALUES

CAUSE A SLIGHT BOUNCE OF A SCROLLED
REGION IN AN OPPOSITE DIRECTION OF A
SCROLL BASED ON A REGION PAST AN EDGE
OF A CONTENT BEING VISIBLE IN A DISPLAY
REGION AT THE END OF THE SCROLL

FIG. 2
300

TRANSFER A RUBBERBAND CALL TO CAUSE
RUBBERBANDING A SCROLLED REGION
DISPLAYED WITHIN A DISPLAY REGION

TRANSFER AN EDGE RUBBERBAND CALL TO
SET DISPLACEMENT VALUES FOR AT LEAST
ONE EDGE OF THE DISPLAY REGION
304

FIG. 3

APLNDC00027753

WO2008/085848

PCT/US2008/000060

3/37

GUI
DISPLAY
408

400

00000

INFORMATION
412-1

MOVEMENT
414
INFO4RMATION

d

INFORMATION

416

INFORMATION
412-4

WINDOW
410

N

/

MENU

FIG. 4

APLNDC00027754

WO2008/085848

PCT/US2008/000060

4/37

GUI
DISPLAY

400

408

eeooo

INFORMATION

DISTANCE
512-

VELOCITY ·¯¯¯
510-1

TERMINUS .y.
514

WINDOW 410

MENU

FIG. 5A

APLNDC00027755