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.01
·=D STATES DEPARTMENT OF COMMERCE
United States Patent and Trademark Office
May 09, 2011
THIS IS TO CERTIFY THAT ANNRXED IS A TRUE COPY FROM THE
RECORDS OF THIS OFFICE OF THE FILE WRAPPER AND CONTENTS
OF:
APPLICATION NUMBER: 11/620,717
FILING DATE: January 07, 2007
PATENT NUMBER: 7,844,915
ISSUE DATE: November 30, 2010
By Authority of the
Under Secretary of Commerce for Intellectual Property
and Director of the United States Patent and Trademark Office
M. K. CARTER
Certifying Officer
APLNDC00027081
NONPUBLICATION REQUEST UNDER 35 U.S.C. 122(b)(2)(B)(i)
First Named Inventor Andrew Platzer
Title
APPL_QATION PSOjgRA
Attomey Docket No.
Express Mail No.:
NQ INTERFAÇES FOR SÇROLLlNe OPERATIONS
4880P4895
I hereby certify that the invention disclosed in the attached application has not and will not be the
subject of an application filed in another country, or under a multilateral agreement, that requires
publication at eighteen months after filing.
I hereby request that the attached application not be published under 35 U.S.C. 122(b).
January 7, 2007
Date
/Jeremv Schweigert/
Signature
(408) 720-8300
Telephone Number
Jeremy Schweigert
Typed or Printed Name
¯¯
56,244
Registration No.
This request must be signed in compliance with 37 CFR 1.33(b) and submitted with the application
upon filing,
Applicant may rescind this nonpublication request at any time. If applicant rescinds a request that
an application not be published under 35 U.S.C. 122(b), the application will be scheduled for
publication at eighteen months from the earliest claimed filing date for which a benefit is claimed.
If applicant subsequently files an application directed to the invention disclosed in the attached
apphcation m another country, or under a multilateral international agreement, that requires
pubhcation of applications eighteen months after filing, the applicant must notify the United States
Patent and Trademark Office of such filing within forty-five (45) days after the date of the filing of
such foreign or international application. Faîlure to do so will result in abandonment of this
application (35 U.S.C. 122(b)(2)(B)(iiî)).
Based on Form PTO/SB/35 (08-03) as modified by BLAKELY, SOKOLOFF, TAYLOR & ZAFMAN LLP on 07/31/04.
APLNDC00027082
UTILITY PATENT APPLICATION TRANSMITTAL
(Only for new non-provisional applications under 37 CFA 1.53(b))
Attorney Docket No.
4860P4895
(maximum 12 characters)
First Named Inventor
Title:
Andrew Platzer
. APPUCATION PROGRAMMtNG INTERFACES FOR ScRoLUNG OPERATiONS
Express Mail Labei No.
ADDRESS TO:
Commissioner for Patents
P.O. Box 1450
Alexandria, Virginia 22313-1450
APPLICATION ELEMENTS
See MPEP chapter 600 concerning utility patent application contents.
1-
Fee Transmittal Form (e.g., PTO/SB/17)
(Submit an original and a duplicate for fee processing)
2.
Applicant Claims Small Entity Status. (37 CFR 1.27)
3.
X
Specification
(Total Pages
59
\
(preferred arrangement set forth below)
- Descriptive Title of the Invention
- Cross Reference to Related Applications
- Statement Regarding Fed sponsored R & D
- Reference sequence lísting, a table,
or a computer program listing appendix
- Background of the Invention
- Brief Summary of the invention
- Brief Description of the Drawings (if filed)
- Detailed Description
- Claim(s)
- Abstract of the Disclosure
4.
X
Drawings(s) (35 USC 113)
5.
X
Oath or Declaration
(Total Sheets
37
1
(Total Pages 3 1
a.
Newly Executed (Original or Copy)
b.
Copy from a Prior Application (37 CFR 1.63(d))
(for Continuation/Divisional with Box 18 completed)
I.
c.
_
i
DELETIONS OF INVENTOR(S) Signed statement attached deleting
inventor(s) named in the prior application, see 37 CFR 1.63(d)(2)
and 1.33(b).
Unsigned.
6-
Application Data Sheet. (37 CFR 1.76)
7-
CD-ROM or CD-R in duplicate, large table or Computer Program (Appendix)
8.
Nucleotide and/or Amino Acid Sequence Submission
(if applicable, all necessary)
a-
Computer Readable Form (CRF)
b-
Specification Sequence Listing on:
L
CD-ROM or CD-R (2 copies); or
iL
paper
Statements verifying identity of above copies
c-
Application
- 1 -
4860P4895
APLNDC00027083
ACCOMPANYÏÑÒ
9.
Assignment Papers (cover sheet & documents(s))
10.
a.
Separate 37 CFR 3.73(b) Statement (where there is an assignee)
b.
Power of Attorney
11.
English Translation Document (if applicable)
12.
a.
Information Disclosure Statement (IDS)/PTO-1449 (or PTO/SB/08)
b. Copies of IDS Citations
13.
Preliminary Amendment
14.
Return Receipt Postcard (MPEP 503) (Should be specifically itemized)
15.
Certified Copy of Priority Document(s) (if foreign priority is claimed)
16.
X
Nonpublication Request under 35 U.S.C. 122(b)(2)(B)(i). Applicant must attach
form PTO/SSIM nr its amuuniant
17A.
'¯¯" " ¯¯"
Claim for Foreign Priority
178.
X
17C.
Other:
Appendix A (4 pages)
X
Pursuant to 37 C.F.R. 1.136(a)(3), applicant(s) hereby request and authorize the U.S.
Patent and Trademark Office to (1) treat any concurrent or future reply that requires
a petition for extension of time as incorporating a petition for extension of time for the
appropriate length of time and (2) charge all required fees, including extension of time
fees and fees under 37 C.F.R. 1,16 and 1.17, to Deposit Account No. 02-2666.
18. If a CONTINUING APPLICATION, check appropriate box, and supply the requisite information below
, or in
an Application Data Sheet Under 37 C F.R. 1.76:
Continuation
Of Prior Application No.:
Divisional
Examiner
Continuation-in-part (CIP)
Group Art Unit
(which is a
continuation/
divisional/ _ CIP of prior application no.
which is a
continuation/
divisional/ _ CIP of prior application no-
ust entire chain of priority)
Applicant(s): Also include a Preliminary Amendment to amend the specification to claim priority.
For CONTINUATION AND DIVISIONAL APPS only: The entire disclosure of the prior application, from which an oath or
declaration îs supplied under Box 5b, is considered a part of the disclosure of the accompanying continuation or
divisional application and is hereby incorporated by reference. The încorporation can oniv be relied upon when a portion
has been madvertentlyomitted from the submitted aplication parts.
19.
X
Correspondence Address
Customer Number or Bar Code Label
or
Correspondence Address Below
08791
(Insert Customer No. or Attach Bar Code Label herej
NAME
Jeremv Schweiaert
BLAKELY, SOKOLOFF, TAYLOR & ZAFMAN LLP
ADDRESS 12400 Wilshire Boulevard
CITY
Country
Seventh Flogr
I pp. Anpdet
U.S A
STATE
C lifemi
TELEPHONE (40m 790-Rann
ZIP CODE 90025
FAX
(4083 720-BRAS
Name (PRINT/TYPE):
Jeremv Schweiand
Registration No: 56,244
Signature:
/Jeremy Schweigert/
Date: Januarv 7. 2007
Application
-2-
4860P4895
APLNDC00027084
CLAIMS
What is claimed is:
1.
A machine implemented method for scrolling on a display of a device comprising:
receivmg a user mput;
creating an event object in response to the user input;
determining whether the event object invokes a scroll or gesture operation;
issuing at least one scroll or gesture call based on invoking the scroll or gesture
operation;
responding to at least one scroll call, if issued, by scrolling 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; and
responding to at least one gesture call, if issued, by scaling the view associated
with the event object based on receiving a plurality of input points in the form of the user
mput.
2. The method as in claim l, further comprising:
rubberbanding a scrolling region displayed within the window by a predetermined
maximum displacement when the scrolling region exceeds a window edge based on the
scroll.
3. The method as in claim 1, further comprising:
attaching scroll indicators to a content edge of the window.
4. The method as in claim 1, further comprising:
attaching scroll indicators to the window edge.
5. The method as in claim 1, wherein determining whether the event object invokes a
scroll or gesture operation is based on receiving a drag user input for a certain time
period.
-39APLNDC00027085
6. The method as in claim 1, further comprising;
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.
7. 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.
8.
A machine readable medium storing executable program instructions which when
executed cause a data processing system to perform a method comprising:
receivmg a user mput;
creating an event object in response to the user input;
determining whether the event object invokes a scroll or gesture operation;
issuing at least one scroll or gesture call based on invoking the scroll or gesture
operation;
responding to at least one scroll call, if issued, by scrolling 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; and
responding to at least one gesture call, if issued, by scaling the view associated
with the event object based on receiving a plurality of input points in the form of the user
mput.
9. The medium as in claim 8, further comprising:
rubberbanding a scrolling region displayed within the window by a predetermined
maximum displacement when the scrolled region exceeds a window edge based on the
scroll
10. The medium as in claim 8, further comprising:
attaching scroll indicators to a content edge of the view.
-40APLNDC00027086
l 1. The medium as in claim 8, further comprising:
attaching scroll indicators to a window edge of the view.
12. The medium as in claim 8, wherein determining whether the event object invokes a
scroll or gesture operation is based on receiving a drag user input for a certain time
period.
13. The medium as in claim 8, further comprising:
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
mput.
14. The medium as in claim 8, 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,
15. In an environment with user interface software interacting with a software
application, a method for operating through an application programming interface (API),
compnsmg:
transferring a set bounce calL
16. The method as in claim 15, further comprises:
setting at least one of maximum and minimum bounce values.
17. The method as in claim 15, wherein transferring the set bounce call causes a bounce
of a 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 of a device at the end of the scroll.
18. The method as in claim 15, wherein transferring the set bounce call is either one of
issuing, initiating, invoking or receiving the set bounce call.
-41APLNDC00027087
19. The method as in claim 15, 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.
20.
A machine readable medium storing executable program instructions which when
executed cause a data processing system to perform a method comprising:
transferring a set bounce call
21. The medium as in claim 20, further comprises:
setting at least one of maximum and minimum bounce values.
22. The medium as in claim 20, wherein transferring the set bounce call causes a bounce
of a 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 of a device at the end of the scroll.
23. The medium as in claim 20, wherein transferring the set bounce call is either one of
issuing, initiating, invoking or receiving the set bounce call.
24. The medium as in claim 20, 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.
25. In an environment with user interface software interacting with a software
application, an apparatus, comprising:
means for transferring a set bounce call.
26. In an environment with user interface software interacting with a software
application, a method for operating through an application programming interface (API),
comprismg:
receiving a set bounce call.
-42-
APLNDC00027088
27. The method as in claim 26, further comprises:
setting at least one of maximum and minimum bounce values.
28. The method as in claim 26, wherein receiving the set bounce call causes a bounce of
a 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
29.
A machine readable medium storing executable program instructions which when
executed cause a data processing system to perform a method comprising:
receiving a set bounce call.
30. The medium as in claim 29, further comprises:
setting at least one of maximum and minimum bounce values.
31. The medium as in claim 29, wherein receiving a set bounce call causes a bounce of a
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.
32. In an environment with user interface software interacting with a software
application, an apparatus, comprising:
means for receiving a set bounce call.
33. In an environment with user interface kit interacting with a software application, a
method for operating through an application programming interface (API), comprising:
transferring a rubberband call to cause rubberbanding a scrolled region displayed
within a display region of a device.
34. The method as in claim 33, wherein rubberbanding a scrolled region occurs by a
predetermined maximum displacement when the scrolled region exceeds a display edge
based on the scroll.
-43-
APLNDC00027089
35. The method as in claim 33, further comprising:
transferring an edge rubberband call to set displacement values for at least one
display edge.
36. The method as in claim 33, wherein at the end of the scroll, the scrolled region
associated with content returns within the display region.
37. The method as in claim 33, wherein transferring the rubberband call is either one of
issuing, initiating, invoking or receiving the rubberband call.
38. The method as in claim 33, 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.
39.
A machine readable medium storing executable program instructions which when
executed cause a data processing system to perform a method comprising:
transferring a rubberband call to cause rubberbanding a scrolled region displayed
within a display region of a device.
40. The medium as in claim 39, wherein rubberbanding a scrolled region occurs by a
predetermined maximum displacement when the scrolled region exceeds a window edge
of the view based on the scroll.
41. The medium as in claim 39, further comprising:
transferring an edge rubberband call to set displacement values for at least one
display edge.
42. The medium as in claim 39, wherein transferring the rubberband call is either one of
issuing, initiating, invoking or receiving the rubberband call.
-44-
APLNDC00027090
43. The method as in claim 39, 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.
44. In an environment with user interface software interacting with a software
application, an apparatus, comprising:
means for transferring a rubberband call to cause rubberbanding a scrolled region
displayed within a view.
45. In an environment with user interface kit interacting with a software application, a
method for operating through an application programming interface (API), comprising:
receiving a rubberband call to cause rubberbanding a scrolled region displayed
within a view.
46. The method as in claim 45, wherein rubberbanding a scrolled region occurs by a
predetermined maximum displacement when the scrolled region exceeds a window edge
of the view based on the scroll,
47. The method as in claim 45, further comprising:
receiving an edge rubberband call to set displacement values for at least one
display edge.
48.
A machine readable medium storing executable program instructions which when
executed cause a data processing system to perform a method comprising:
receiving a rubberband call to cause rubberbanding a scrolled region displayed
within a view.
49. The medium as in claim 48, wherein rubberbanding a scrolled region occurs by a
predetermined maximum displacement when the scrolled region exceeds a window edge
of the view based on the scroll
-45-
APLNDC00027091
50. The medium as in claim 48, further comprising:
receiving an edge rubberband call to set displacement values for at least one
display edge.
51. In an environment with user interface software interacting with a software
application, an apparatus, comprising:
means for receiving a rubberband call to cause rubberbanding a scrolled region
displayed within a view.
52. In an environment with user interface software interacting with a software
application and a user input contacting a view of a display of a device, a method for
operating through an application programming interface (API) , comprising:
transferring a directional scroll call to determine if directional scrolling is
enabled.
53. The method as in claim 52, further comprising:
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.
54. The method of claim 52, wherein a drag user input forming an angle with a
horizontal direction that is less than or equal to a first scroll angle locks the scrolling in
the horizontal direction.
55. The method of claim 52, wherein a drag user input forming an angle with a vertical
direction that is less than or equal to a second scroll angle locks the scrolling in the
vertical direction.
56. The method as in claim 52, wherein transferring the directional scroll angle call is
either one of issuing, initiating, invoking or receiving the directional scroll angle call.
-46-
APLNDC00027092
57. The method as in claim 52, 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 comprising:
transferring a directional scroll call to determine if directional scrolling is
enabled.
59. The medium as in claim 58, further comprising:
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.
60. The medium of claim 58, wherein a drag user input forming an angle with a
horizontal direction that is less than or equal to a first scroll angle locks the scrolling in
the horizontal direction.
61. The medium of claim 58, wherein a drag user input forming an angle with a vertical
direction that is less than or equal to a second scroll angle locks the scrolling in the
vertical direction.
62. The medium as in claim 58, wherein transferring the directional scroll angle call is
either one of issuing, initiating, invoking or receiving the directional scroll angle calL
63. The method 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.
64. In an environment with user interface software interacting with a software
application, an apparatus, comprising:
means for transferring a directional scroll call to determine if directional
-47APLNDC00027093
scrolling is enabled.
65. In an environment with user interface software interacting with a software
application and a user input contacting a view of a display of a device, a method for
operating through an application prog-- - ing interface (API) , comprising:
receiving a directional scroll call to determine if directional scrolling is
enabled.
66. The method as in claim 65, further comprising:
receiving 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.
67. The method of claim 65, wherein a drag user input forming an angle with a
horizontal direction that is less than or equal to a first scroll angle locks the scrolling in
the horizontal direction.
68. The method of claim 65, wherein a drag user input forming an angle with a vertical
direction that is less than or equal to a second scroll angle locks the scrolling in the
vertical direction.
69.
A machine readable medium storing executable program instructions which when
executed cause a data processing system to perform a method comprising:
receiving a directional scroll call to determine if directional scrolling is
enabled.
70. The medium as in claim 69, further comprising:
receiving 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.
-48-
APLNDC00027094
7 L The medium of claim 69, wherein a drag user input forming an angle with a
horizontal direction that is less than or equal to a first scroll angle locks the scrolling in
the horizontal direction.
72. The medium of claim 69, wherein a drag user input forming an angle with a vertical
direction that is less than or equal to a second scroll angle locks the scrolling in the
vertical direction.
73. In an environment with user interface software interacting with a software
application, an apparatus, comprising:
means for receiving a directional scroll call to determine if directional
scrolling is enabled.
74. A computer read medium containing executable instructions, comprising:
program code configured, when executed, to transfer a bounce call through an
application programming interface to cause a bounce of a 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.
75. The medium as in claim 74, wherein transferring the bounce call is either one of
issuing, initiating, invoking or receiving the bounce call.
76. A computer read medium containing executable instructions, comprising:
program code configured, when executed, to transfer a rubberband call through an
application programming interface to cause a rubberband effect on a scrolled region by a
predetermined maximum displacement when the scrolled region exceeds a display edge
based on a scroll.
77. The medium as in claim 76, wherein transferring the rubberband call is either one of
issuing, initiating, invoking or receiving the rubberband call
-49APLNDC00027095
78. A computer read medium containing executable instructions, comprising:
program code configured, when executed, to transfer a directional scroll call
through an application programming interface to set a scroll angle for locking the
scrolling in at least one of a vertical or horizontal direction.
79. The medium as in claim 78, wherein transferring the directional scroll call is either
one of issuing, initiating, invoking or receiving the directional scroll call.
80. A platform for performing scrolling operations, comprising:
a processing unit coupled to an input panel;
a memory coupled to the processor; and
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 bounce call through an application
programming interface to cause a bounce of a 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.
81. The platform of claim 80, wherein the one or more programs further comprise
instructions for transferring a rubberband call through an application programming
interface that has a rubberband effect on a scrolled region by a predetermined maximum
displacement when the scrolled region exceeds a display edge based on a scroll.
82. The platform of claim 80, wherein the one or more programs further comprise
instructions for transferring a directional scroll call through an application programming
interface to set a scroll angle for locking the scrolling in at least one of a vertical or a
horizontal direction.
83. The platform as in claim 80, wherein transferring the bounce call is either one of
issuing, initiating, invoking or receiving the bounce call.
-50-
APLNDC00027096
84. The platform as in claim 81, wherein transferring the rubberband call is either one of
issuing, initiating, invoking or receiving the rubberband call.
85. The platform as in claim 82, wherein transferring the directional scroll call is either
one of issuing, initiating, invoking or receiving the directional scroll call.
86. 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 bounce operation to cause a bounce of a 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.
87. The framework of claim 86, wherein the one or more programs further comprise
instructions that when executed provide an application programming interface to specify
a rubberband operation that has a rubberband effect on a scrolled region by a
predetermined maximum displacement when the scrolled region exceeds a display edge
based on a scroll.
88. The framework of claim 86, wherein the one or more programs further comprise
instructions that when executed provide an application programming interface to specify
a directional scroll operation to set a scroll angle for locking the scrolling in at least one
of a vertical or a horizontal direction.
-51APLNDC00027097
ABSTRACT
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 programming 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 a
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.
-52APLNDC00027098
4860P4895
PATENT APPLICATION
ELECTRONICALLY FILED
Januarv 7. 2007
UNITED STATES PATEN I APPLK A flON
FOR
APPUCATION PROGRAMMING INTERFACES FOR SCROLLING OPERATIONS
INVENTORS:
ANDREW PLATZER
ScoTT HERZ
PREPARED BY:
BLAKELY, SOKOLOFF, TAYLOR & ZAFMAN
12400 WILSHIRE BOULEVARD
SEVENTH FLOOR
Los ANGELES, CA 90025-1026
(408) 720-8300
-1APLNDC00027099
A.PPLICATION PROGR^MMING INTERFACES FOR SCROLLING OPERATIONS
FIELD OF THE DISCLOSURF
[0001] This disclosure relates to application programming interfaces that provide
scrolling operations.
COMPUTER PROGRAM 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 programming language that can be interpretative or compled
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 A.PI is
said to be an implementation of the APL
[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.
APLNDC00027100
[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 mputs.
-3-
APLNDC00027101
SUMMARY 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 programming interfaces between the user interface
software and software applications. Example application programming interfaces
transfer function calls to implement scrolling, gesturing, and animating 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 programming 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 a
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. A method for
operating through an application programming 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 gesture operations
for a display of a device. 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.
-4-
APLNDC00027102
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.
-5-
APLNDC00027103
BRIEF DESCRIPTION OF THE OR A WTNGS
[0015] The disclosure is described by way of example with reference to the
accompanying drawings, wherein:
[0016] FIG. I 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;
[0027J FIG. 12 illustrates details of an application programming interface in flow chart
form according to certain teachings of the present disclosure;
-6-
APLNDC00027104
[0028] FIG. 13 illustrates details of an application programming interface in flow chart
form according to certain teachings of the present disclosure;
[0029] FIG. 14 illustrates details of an application programming 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;
-7-
APLNDC00027105
[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.
APLNDC00027106
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 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
-9APLNDC00027107
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 programmable 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 transmitting
information in a form readable by a machine (e.g., a computer). For example, a machinereadable 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 programming 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.
- 0-
APLNDC00027108
[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 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
-11-
APLNDC00027109
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 separate devices. Examples of a
portable media player are described in published U.S. patent application numbers
2003/0095096 and 2004/0224638, both of which are incorporated by reference.
[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 a view (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 I10. For
example, an input may end at a certain position on a display of the device. The scrolling
-12-
APLNDC00027110
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 i 12.
[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 mouse/finger 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
zoomog 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,
(0069] FIG. 2 illustrates details of an application programming interface in flow chart
form according to certain teachings of the present disclosure. The application
programming ínterface operates in an environment with user interface software
interacting with a software application in order to provide a bounce operation. The
-13-
APLNDC00027111
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 m 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 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
-14-
APLNDC00027112
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 direction).
[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 touch-sensitive 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 the displayed objects, as opposed to a physical boundary associated with
the window 410 and/or the display 408. As illustrated in Figure 5B, 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 SC, 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
velocíty 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 tenninus.
-15-
APLNDC00027113
[0076] In at least some embodiments of the present disclosure, the method 200 performs
the bounce operations described in FIGS. 5A-SC. 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 interface 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 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 wíthin 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.
-16-
APLNDC00027114
(0080] In this example, the email 3534 from Aaron Jones is the first email in the list and
thus is the terrninus 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 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 scrollmg
operation. The method 700 for operating through an application programming interface
(API) includes transfe1Ting a directional scroll angle call to determine if directional
scrolling is enabled at block 702. The method 700 further includes transferring a
- 7APLNDC00027115
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 used 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 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 lockíng 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
-18-
APLNDC00027116
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 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 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
programming 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
-19-
APLNDC00027117
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 l104. Alternatively, the method
l100 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.
[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 detection 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.
-20-
APLNDC00027118
(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 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
-21APLNDC00027119
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 perforn the gesture event. The user 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.
-22APLNDC00027120
[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 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
-23-
APLNDC00027121
displayed in the display area 1604 and 1652. In performing the scaling transform from
FIG. 16A to FIG. 16B, the 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 lx. It may be desirable for the
user to scale from 2x to lx 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 input having a plurality of input points at
block 1702. The method 1700 further includes transferring a rotation gesture start call at
-24-
APLNDC00027122
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
animation associated 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 APL 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 occurred,
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 in response to the view being modified by the
ammation.
[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 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.
-25-
APLNDC00027123
[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 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 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
-26-
APLNDC00027124
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 2l04. 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
ammations.
[00117]
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 in 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
-27APLNDC00027125
changing from the first state to the second state may occur incrementally 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.
[00120]
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
-28APLNDC00027126
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 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 nonmedia content from the second memory location, and scanning the media and non-media
-29-
APLNDC00027127
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 m vanous 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. 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
-30-
APLNDC00027128
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 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 screen 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 other movement in a display, control
input device settings, or to make other changes to one or more settings of the device, n
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 displaylinput 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
-31-
APLNDC00027129
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 of 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 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 display/input 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
-32-
APLNDC00027130
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 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 provide one 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, 5B, 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 commumcation. 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
-33-
APLNDC00027131
integrated circuit), FPGA (field-programmable gate array) or DSP (digital signal
processor). Digital processing 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, sensor(s) 3110, and display device
-34APLNDC00027132
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
inputloutput 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.
[00145]
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
-35-
APLNDC00027133
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
programming 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 hierarchy 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 hierarchy of layers operating below the hierarchy
of views.
[00149]
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 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 bounce call through an API to cause a bounce of a scrolled region in an
opposite direction of a scroll based on a region past an edge of the scrolled region being
-36-
APLNDC00027134
visible in a display region at the end of the scroll. In an embodiment, the one or more
programs include instructions for transferring a rubberband call through an API to cause
a rubberband effect on a scrolled region by a predetermined maximum displacement
when the scrolled region exceeds a display edge based on a scroll. In an embodiment, the
one or more programs include instructions for transferring a directional scroll call
through an API to set a scroll angle for locking the scrolling in at least one of a vertical or
a horizontal direction.
[00151]
In an embodiment, the one or more programs include instructions for
transferring a scroll hysteresis call through an API to determine whether a user input
invokes a scroll. In an embodiment, the one or more programs include instructions for
transferring a deceleration scroll call through an API to set a deceleration factor for a user
input based on the user input invoking a scroll. In an embodiment, the one or more
programs include instructions for transferring a scroll indicator call through an API to
determine whether at least one scroll indicator attaches to a content edge or a display
edge of a display region.
[00152]
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.
[00153]
In an embodiment, the library of the framework provides an API for
specifying a bounce operation to cause a bounce of a 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. In an embodiment, the library of the framework
provides an API for specifying a rubberband operation that has a rubberband effect on a
scrolled region by a predetermined maximum displacement when the scrolled region
exceeds a display edge based on a scroll. In an embodiment, the library of the framework
provides an API for specifying a directional scroll operation to set a scroll angle for
locking the scrolling in at least one of a vertical or a horizontal direction.
[00154]
In an embodiment, the library of the framework provides an API for
specifying a scroll hysteresis operation to determine whether a user input invokes a scroll.
-37-
APLNDC00027135
In an embodiment, the library of the framework provides an API for specifying a
deceleration scroll operation to set a deceleration factor for a user input based on the user
input invoking a scrolL In an embodiment, the library of the framework provides an API
for specifying a scroll indicator operation to determine whether at least one scroll
indicator attaches to a content edge or a display edge of a display region.
[00155]
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.
-38-
APLNDC00027136
Attorney Docket No.:
4860P4895
First Named inventor:
Check One:
Andrew Plgtger
PATENT
Comotete If Known:
X
Declaration Submitted with
Initial Filing
OR
Declaration Submitted After
Initial Filing (Surcharge under
Examiner Name:
37 C.F.R. § L T6(e) Required).
Application No.:
Filing Date:
Jarmarv 7. 2nn7
Art Unit:
DECLARATION FOR UTILITY OR DESIGN PATENT APPLICATION
I hereby declare that:
Each inventor's residence, mailing address, and citizenship are as stated below next to their name.
I believe the inventor(s) named below to be the original and first inventor(s) of the subject matter which
is claimed and for which a patent is sought on the invention entitled:
APPLICATION PROGRAMMING INTERFACES FOR SCROLLING OPERATIONS
the specification of which
X
is attached hereto OR
was filed on (MM/DD/YYYY)
as United States Application Number
or PCT International Application Number
and was amended on (MM/DD/YYYY)
Januarv 7.2007
(it applicable)
I hereby state that I have reviewed and understand the contents of the above-identified specification,
including the claim(s), as amended by any amendment specifically referred to above.
I do not know and do not believe that the claimed invention was ever known or used in the United States
of America before my invention thereof, or patented or described in any printed publication in any
country before my invention thereof or more than one year prior to this application. I do not know and do
not believe that the claimed invention was in public use or on sale in the United States of America more
than one year prior to this application, nor do I know or believe that the invention has been patented or
made the subject of an inventor's certificate issued before the date of this application in any country
foreign to the United States of America on an application filed by me or my legal representatives or
assigns more than twelve months (for a utility patent application) or six months (for a design patent
application) poor to this application.
I acknowledge the duty to disclose information which is material to patentability as defined in 37 C.F.R.
1.56, including for continuation-in-part applications, material information which became available
between the filing date of the prior application and the national or PCT international filing date of the
continuation-in-part application.
BSTZ/Apple Computer, Inc.
-1·
4860P4895
APLNDC00027137
l hereby claim foreign priority benefits under 35 U.S.C. 119(a)-(d) or (f), or 365(b) of any foreign
application(s) for patent, inventor's or plant breeder's rights certificate(s), or 365(a) of any PCT
international application which designated at least one country other than the United States of America
listed below and have also identified below, by checking the box, any foreign application for patent,
inventor's or plant breeder's rights certificate(s), or any PCT international application having a filing date
before that of the application on which priority is claimed:
Priority
Claimed?
EIGE Ÿ9tf!90. Appijcatiot1(S)
Certified
Copy Attactled?
(Number)
(Country)
(Foreign Filing Date MM/DD/YYYY)
Yes
No
Yes
No
(Number)
(Country)
(Foreign Filing Date MM/DD/YYYY)
Yes
No
Yes
No
(Number)
(Country)
(Foreign Filing Date MM/DD/YYYY)
i
i
Yes
i
I hereby declare that all statements made herein of my own knowledge are true and that all
statements made on information and belief are believed to be true; and further that these
statements were made with the knowledge that willful false statements and the like so made are
punishable by fine or imprisonment, or both, under 18 U.S.C. 1001 and that such willful false
statements may jeopardize the validity of the application or any patent issued thereon.
NAME OF SOLE OR FIRST INVENTOR: O A petition has been filed for this unsigned inventor
Full Name:
Andrew Platzer
(Given Name (First and Middle [if any]), Family Name (or Surname), and Suffix [if any])
Inventor's Signature
Residence
Date
Santa. 89
!!ffirnia 08
Mailing Address
CANADA
og
3224 El Sobrante St.
Santa Clara, CA 95051
NAME OF SECOND INVENTOR:
Full Name:
Citizenship
(City, State, Country)
O A petition has been filed for this unsigned inventor
Scott Herz
(Given Name (First and Middle [if any]), Family Name (or Surname), and Suffix lif any))
Inventor's Signature
Residence
Date
Santa ÇlaracCa@y·nia- US
Citizenship
(Oty, State, Country)
Mailing Address
ç¾
(Country)
2469 Rebecca Lvun Way
Santa Clara. CA 95050
SSTZ/Apple Computer, Inc.
-2·
4860P4895
APLNDC00027138
Page l of 4
APPENDIX A
API SOFTWARE ConR
I
2
3
4
- (AffineTransform)transform:
- (void)setTransform:(AffineTransform)transform: //
animatable
@interface UIView(Animation)
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
+ (void)beginAnimation: (String*)animationIDS; //
animationID can be nil if
you don't want to have an identifer for the group
+ (void)beginAnimations: (String*)animationID context: (void*) context // additional
context info passed to will start/did stop selectors
+(void)endAnimations;
+(void)setAnimationDelegate:(id)delegate;
+(void)setAnimationDuration:(TimeInterval)duration:
+(void)setAnimationDelay:(TimeInterval)delay;
+(void)setAnimationStartTime:(AbsoluteTime)start;
+(void)setAnimationCurve:(UIViewAnimationCurve)curve;
- (BOOL)handleEvent: (Event)event;
// this is called if the app is going to be suspending back to a previous
application.
// 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.
(BOOL)animateSuspensionReturningToLastApp:AbsoluteTime)startTime;
// Set the status bar mode, orientation over duration. If processSynchlD 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. 0 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.
- (void) synchronizedDrawingWithID: (int)processSynchlD; // used for status bar
resize
46
//
APLNDC00027139
Page 2 of 4
APPENDIX A
API SOFTWARE COUR
47
// Gesture delegate method, event will be nil if gesture was not event-driven (ie
48
programatically or animation).
49
@interface Object(UIViewGestureDelegate)
50
51
- (void)willStartGestures: (UIView *)view forEvent: (GSEvent)event;
52
53
- (void)didFinishGestures: (UIView *)view forEvent: (Event)event;
54
55
- (void)willStartGesture: (UIGestureType)type inView: (UIView *) view
56
forEvent: (Event)event;
57
58
- (void)gestureDidChange: (UIGestureType)type inView: (UIView *) view
59
forEvent: (Event)event;
60
61
- (void)didFinishGesture: (UIGestureType)type inView: (UIView *) view
62
forEvent: (Event)event;
63
@end
64
65
UIGestureAttributeZooms // Number (BOOL)
66
67
typedef enum {
68
UIScrollerEventModeInterceptOnDrag,
//
send mouseDown / mouseUp to
69
subviews if not dragged
70
UIScrollerEventModePass,
//
send
71
mouseDown/mouseDrag/mouseUp to subviews
72
UIScrollerEventModelntercept,
//
send mouseDown / mouseUp to subviews
73
} UIScrollerEventMode;
74
- (void)setEventMode:(UIScrollerEventMode)mode;
75
76
- (void)setDirectionalScrolling:(BOOL)flag;
77
78
- (void)setDirectionalScrollingAngle:(float)flag;
79
80
- (void)setScrollDecelerationFactor:(float)factor;
81
82
- (void)setBounces:(BOOL)bounces;
83
84
- (void)setThumbDetectionEnabled:(BOOL)flag;
85
86
- (void)setShowScrollerIndicators:(BOOL)flag;
87
88
89
90
91
- (void)setScrollerIndicator:(Rect)rect;
- (void)setScrollerindicatorsPinToContent:(BOOL)flag;
APLNDC00027140
Page 3 of 4
92
93
94
95
96
97
98
99
APPENDIX A
API SOFTWARE CODE
- (void)setAllowsRubberBanding:(BOOL)flag;
// Call setRubberBand:forEdges:
with RUBBER_BAND_HEIGHT for the top and bottom edges
- (void)setAllowsFourWayRubberBanding:(BOOL)flag; // Calls
setRubberBand: for Edges: with RUBBER_BAND_HEIGHT for all edges
- (void)setRubberBand: (float) value for Edges:
set for top and bottom edges
(UIRectEdge) edges: // Default
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
I15
116
117
118
119
120
121
122
123
124
@interfacebject (UIAnimationDelegate)
-(void)animator: (UIAnimator*)animator
startAnimation:(UIAnimation*)animation;
-(void)animator: (UIAnimator*)animator
stopAnimation:(UIAnimation*)animation;
-(void)animator: (UIAnimator*)animator stopAnimation: (UIAnimation*)animation
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
@interface UIFrameAnimation
:
UIAnimation {
Rect _startFrame;
Rect _endFrame;
UIRectFields fieldsToChange;
}
- (void) setStartFrame: (Rect)start;
- (void) setEndFrame: (Rect)end;
- (void) setSignificantRectFields: (UIRectFields)fields;
137
- (void)contentMouseUpInView:(UIView*)mouseUpView
withEvent:(Event)event;
// default calls -mouseUp; on view
- (Point)scroller:(UIScroller *)scroller
adjustSmoothScrollEnd:(Point)offset velocity:(Size)velocity;
-(Rect)endFrame;
@end
APLNDC00027141
Page 4 of 4
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
APPENDIX A
API SOr i vv ARE CODE
@interface UlAlphaAnimation : UIAnirnation
@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;
APLNDC00027142
Electronic Acknowledgement Receipt
EFS ID:
1421698
Application Number:
11620717
International Application Number:
Confirmation Number:
Title of Invention:
First Named Inventor/Applicant Name:
Customer Number:
Filer:
Filer Authorized By:
Attorney Docket Number:
Receipt Date:
9801
Application Programming Interfaces for Scrolling Operations
Andrew Platzer
08791
Kevin G. Shao/David Castro
Kevin G. Shao
4860P4895
07-JAN-2007
Filing Date:
Time Stamp:
Application Type:
23:21:43
Utility
Payment information:
Submitted with Payment
yes
Payment was successfully received in RAM
$8800
RAM confirmation Number
1281
Deposit Account
022666
The Director of the USPTO is hereby authorized to charge indicated fees and credit any overpayment as follows:
Charge any Additional Fees required under 37 C.F.R. Section 1.16 and 1.17
File Listing:
APLNDC00027143
Document
Number
.
Document Description
File Name
File Size(Bytes)
Multi
Pages
Part /.zip (if appl.)
1
Transmittal of New Application
P4895_trans.PDF
106531
no
2
Nonpublication request from
applicant.
P4895- nonpub.PDF
44845
no
1
Oath or Declaration filed
P4895 dec.PDF
97717
no
2
P4895_spec.PDF
2152873
yes
52
Warnings:
Information:
2
Warnings:
Information:
3
Warnings:
Information:
4
Multipart Description/PDF files in .zip description
Document Description
Start
End
Application Data Sheet
1
1
Specification
2
38
Claims
39
51
Abstract
52
52
Warnings:
Information:
5
Appendix to the Specification
P4895_appendix.PDF
133299
no
4
Drawings
P4895_figs.PDF
593650
no
37
Fee Worksheet (PTO-06)
fee-info.pdf
8545
no
2
Warnings:
Information:
6
Warnings:
Information:
7
APLNDC00027144
Warnings:
Information:
Total Files Size (in bytes):
3137460
This Acknowledgement Receipt evidences receipt on the noted date by the USPTO of the indicated documents,
characterized by the applicant, and including page counts, where applicable. It serves as evidence of receipt
similar to a Post Card, as described in MPEP 503.
New Annlications Under 35 U.S.C. 111
If a new application is being filed and the application includes the necessary components for a filing date (see
37 CFR 1.53(b)-(d) and MPEP 506), a Filing Receipt (37 CFR 1.54) will be issued in due course and the date
shown on this Acknowledgement Receipt will establish the filing date of the application.
National Staae of an International Annlication under 35 U.S.C. 371
If a timely submission to enter the national stage of an international application is compliant with the conditions
of 35 U.S.C. 371 and other applicable requirements a Form PCT/DO/EO/903 indicating acceptance of the
application as a national stage submission under 35 U.S.C. 371 will be issued in addition to the Filing Receipt,
in due course.
APLNDC00027145
Electronic Patent Application Fee Transmittal
Application Number:
Filing Date:
Title of Invention:
Application Programming Interfaces for Scrolling Operations
First Named Inventor/Applicant Name:
Andrew Platzer
Filer:
Kevin G. Shao/David Castro
Attorney Docket Number:
4860P4895
Filed as Large Entity
Utility
Filing Fees
.
Description
Fee Code
Quantity
Amount
Sub-Total in
USD($)
Utility application filing
1011
1
300
300
Utility Search Fee
1111
1
500
500
Utility Examination Fee
1311
1
200
200
Claims in excess of 20
1202
68
50
3400
Independent claims in excess of 3
1201
22
200
4400
Basic Filing:
Pages:
Claims:
Miscellaneous-Filing:
APLNDC00027146
.
Description
Fee Code
Quantity
Amount
Sub-Total in
USD($)
Petition:
Patent-Appeals-and-Interference:
Post-Allowance-and-Post-Issuance:
Extension-of-Time:
Miscellaneous:
Total in USD ($)
8800
APLNDC00027147
100
RECEIVE A USER INPUT
102
CREATE AN EVENT OBJECT IN
RESPONSE TO THE USER INPUT
104
DETERM INE WHETHER THE EVENT OBJECT
INVOKES A SCROLL OR GESTURE
OPERATION
lŠSUEAT 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 lŠŠUED,CHANGE A VIEW ASSOCIATED
WITH THE EVENT OBJECT BASED ON
RECEIVlNG A PLURALITY OF INPUT POINTS
IN THE FORM OF THE USER INPUT
FIG. 1
APLNDC00027148
200
TRANSFER A SET BOUNCE CELL
202
SET AT LEAST ONE OF MAXIMUM AND
MINIMUM BOUNCEVALUES
204
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
REGlON AT THE END OF THE SCROLL
206
FIG. 2
300
TRANSFER A RUBBERBAND CALL TO CAUSE
RUBBERBANDING A SCROLLED REGION
DISPLAYED WITHIN A DISPLAY REGION
302
TRANSFER AN EDGE RUBBERBAND CALL TO
SET DISPLACEMENT VALUES FOR AT LEAST
ONE EDGE OF THE DISPLAY REGION
304
FIG. 3
APLNDC00027149
GUI
DISPLAY
408
I
400
INFORMATION
MOVEMENT
414
.
412-1
INFO4RMATION
INFORMATION
416
INFORMATION
412-4
Wl4N1DOW
MENU
FIG. 4
APLNDC00027150
GUI
DISPLAY
408
400
eeooo
e
*
INFORMATION
412-1
VELOCfTY
510-1
DISTANCE
512-1
TERMINUS a
x
/
514
WiNDOW 410
MENU
FIG. 5A
APLNDC00027151
GUI
DISPLAY
408
400
I
00000
I
O
TERMINUS .._ _
514
WINDOW 410
INFORMATION
412-1
MENU
FIG. 5B
APLNDC00027152
GUI
DISPLAY
408
400
eeooo
VELOCITY
510-2
INFORMATION
412-1
DISTANCE
512-1
TERMINUS
514
WINDOW
410
MENU
FIG. 5C
APLNDC00027153
PORTABLE MULT)FUNCTION DEVICE
100
' SPEAKER
3500A
'
UFTICAL
,
111
SENSOR 164
A 4û2
'
ÛUrtent Time
Mailboxes
3502
PNUXIMITY
SENSOR R
R4
O 40
inb0X
504
Bruce Walker3606-2 January 30, 2006
Lunch meeting today 36°6-2
10-2
Kim Brook 3506-3
3508-3
January 30, 2006 510-3
Bob Adams
Project Orion
January 29, 2006
3514
g Darin Adler
J, January 29, 2006
Draft agreement~
3512-2
fantasy football
/
Aaron Jones
Fwd: status report
January 29, 2006
Kim Brook
January 28, 2006
Re: proposal
3532
3518
3520
162
3124
"MICROPHONEN
3526
3510
HOME
FIG. 6A
APLNDC00027154
PORTABLE MULTIFUNCTION DEVICE
100
2(L6
SPEAKI-R
3500A
'
OPTICAL
111
'
PROXIMITY *
SENSOR 164
AE
Current Time
Mailboxes
3502
SENSOR 166
B
© 4_O
Inbox
504
Aaron Jones36°6¯'
asio.1
3508-1 January 30, 2006
Re: Project Orion 3R4
Bruce Walker 3506-2 January 30, 2006
Lunch meeting today 3508-2
Kirn Brook a"° 3
3530
| January 30, 20062510-3
Draft agreement 3508-3
3514
Bob AdamS
Project Orion
_, January 29, 2006
*/
3 2-2Darin Adler
fantasy football
January 29, 2006
Aaron JoneS
Fwd: status report
3520
35_22
MICROPHON
1L3
January 29, 2006
324
3
3510
HOME
204
FIG. 6B
APLNDC00027155
PORTABLE MULTIFUNCTION DEVICE
100
216
SPEAKt-R
OPTICAL
111
SENSOR 164
3500A
AE
'
Current Time
Mailboxes
3502
FNUXIMITY '
SENSOR 1L6
40_4
InbOX
504
3R6
Aaron Jones36°61
3508-1
Re: Project Orion~
asso-a
January 30, 2006~
Bruce Walker 3506-2 January 30, 20063510-2
Lunch rneeting today 3508-2
3530
Kirn Brook2506-3
Draft agreernent 3508-3
January 30, 2006 3510-3
3514
Bob AdamS
Project Orion
January 29, 2006
/
3 2-2Darin Adler
January 29, 2006
fantasy football
3518
MICROPHONE'
113
}
HOME
214
FIG. 6C
APLNDC00027156
PORTABLE MULTIFUNCTION DEVICE
100
20fi
SPEAKER
OPliCAL
111
SENSOR 164
3500A
A AQ2
!$
'
Current Time
Mailboxes
3502
PROXIMITY '
SENSOR 166
B
4
Inbox
504
Aaron Jones26"¯1 January 30, 2006 sto-1
3508-1
Re: Project Orion
3534
3
1Bruce Walker
January 30, 2006 3510-2
Lunch meeting today 3508-2
Kim Brook 3506-3
3508-3
January 30, 20063510-3
Bob AdamS
Project Orion
January 29, 2006
3 2-2Darin Adler
January 29, 2006
Draft agreement~
fantasy football
Aaron Jones
Fwd: status report
January 29, 2006
3518
3520
352.2
'MICROPHONE
3524
3526
351
HOME
FIG. 6D
APLNDC00027157
700
TRANSFER A DIRECTIONAL SCROLL CALL
TO DETERMINE IF DIRECTIONAL SCROLLlNG
IS ENABLED
EL2
TRANSFER 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
LOCK 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
LOCK THE SCROLLING IN THE VERTICAL
DIRECTION IF A USER INPUT FORMS AN
ANGLE WITH A VERTICAL DIRECTION THAT
ISLESSTHANOREQUALTOASECOND
SCROLL ANGLE
708
FIG. 7
APLNDC00027158
i
l
I
\
/
\
\
I
I
810
1
i
I
\
I
\
i
l
I
i
i
I
l
i
i
808'
806
I
'
--,
802
\
I
'812
i
i
i
I
I
I
i
i
i
\
\
\
/
\
804
FIG. 8
APLNDC00027159
900
TRANSFER A DECELERATION SCROLL CALL
TO SET A DECELERATION FACTOR FOR A
DRAGUSERINPUTTHATINVOKESASCROLL
902
SLOW THE SCROLL TO A STOP BASED
ON THE SPEED OF THE DRAG USER INPUT
904
FIG. 9
1000
TRANSFER A SCROLL HYSTERESIS CALL TO
DETERMINE WHETHER THE USER INPUT
INVOKES A SCROLL
SET THE HYSTERESIS VALUE FOR
DETERMINING WHETHER A USER INPUT
INVOKES A SCROLL
1004
FIG. 10
APLNDC00027160
1100
TRANSFER A SCROLL lNDICATOR CALL TO
DETERMINE WHETHER AT LEAST ONE
SCROLL INDICATOR ATTACHES TO A SCROLL
REGl0N OR A WINDOW EDGE
1102
OPTIONALLY ATTACH SCROLL INDICATORS
TO A SCROLL REGION BASED ON
THE SCROLL INDICATOR CALL
1104
OPTIONALLY ATTACH SCROLL INDICATORS
TO A WINDOW EDGE BASED ON
THE SCROLL INDICATOR CALL
FIG. 11
1200
TRANSFER AN INADVERTENT USER INPUT
CALL TO DETERMINE WHETHER THE USER
INPUT WAS INADVERTENT
IGNORE THE INADVERTENT USER INPUT
BASED ON THE INADVERTENT USER INPUT
CALL
1204
FIG. 12
APLNDC00027161
1300
TRANSFER A HANDLE GESTURE EVENT CALL
1302
TRANSFER A GESTURE CHANGE CALL IN
RESPONSETOTHEHANDLEGESTURE
EVENT CALL
1304
FIG. 13
1400
TRANSFER A SCALING TRANSFORM CALL
TO DETERMINE A SCALING TRANSFORM
FOR A VIEW ASSOCIATED WITH A USER
INPUT HAVING A PLURALITY OF INPUT POINTS
TRANSFER A SCALING GESTURE START
CALL
14.O_4
TRANSFER A SCALING GESTURE PROGRESS
CALL
TRANSFER A SCALING GESTURE END
CALL
1408
FIG. 14
APLNDC00027162
1502
' ,,
1504
1508
1516
1
i
it
I
i
‡i
?
FIG. 15
APLNDC00027163
1
1614
06
1
166
1654
1650
1602
1604
1652
I
I
I
I
I
FIG. 16A
FIG. 16B
APLNDC00027164
1670
1672
680
676
678
682
674
FIG. 16C
APLNDC00027165
1700
TRANSFER A ROTATION TRANSFORM CALL
TO DETERMINE A ROTATION TRANSFORM
FOR A VIEW ASSOCIATED WITH A USER
INPUT HAVING A PLURALITY OF INPUT POINTS
1702
TRANSFER A START ROTATION GESTURE
CALL
1704
TRANSFER ROTATION GESTURE
PROCESS CALL
1706
TRANSFER A ROTATION GESTURE END
CALL
1708
FIG. 17
APLNDC00027166
1800
i
ANY
ANIMATION?
18_00 2
NO
YES
PROGRESS?
18Æ
YES
L
CALCULATE NEXT
STATE
1806
NO
4
NO
DELEGATE?
1808
YES
NOTIFY
DELEGATE
1810
I
FIG. 18
APLNDC00027167
1900
START AT LEAST TWO ANIMATIONS
1902
DETERMINE THE PROGRESS OF EACH
ANIMATION
1904
UPDATE EACH OF AT LEAST TWO
ANIMATIONS BASED ON A SINGLE TIMER
1906
FIG. 19
APLNDC00027168
2000
PROVIDE A SINGLE ANIMATION TIMER
2002
ANIMATE A PLURALITY OF ANIMATIONS
WITH THE SINGLE ANIMATION TIMER
2004
FIG. 20
APLNDC00027169
2100
SET ATTRIBUTES OF VIEWS
INDEPENDENTLY WITH EACH VIEW BEING
ASSOCIATED WITH PROCESS
2102
TRANSFER A SYNCHRONIZATION CALL
TO SYNCHRONIZE ANIMATIONS FOR THE
MULTIPLE VIEWS OF THE DISPLAY
2104
TRANSFER A SYNCHRONIZATION
CONFIRMATION MESSAGE WHEN A
SYNCHRONIZATION FLAG IS ENABLED BASED
ON THE LIST OF THE PROCESS BElNG
SYNCHRONIZED
UPDATE THE ATTRIBUTES
OF THE VIEWS INDEPENDENTLY
TRANSFER A START ANIMATION CALL TO
DRAW THE REQUESTED ANIMATIONS
2110
FIG. 21
APLNDC00027170
2200
2210
2220
FIG. 22A
2200
2210
222û
FIG. 22B
APLNDC00027171
2300
CONSTRUCT A DATA STRUCTURE HAVING
A HIERARCHY OF LAYERS WITH A
LAYER BEING ASSOCIATED WITH A
VIEW AND OWNING THE VIEW
2302
REMOVE THE LAYER FROM THE DATA
STRUCTURE
SWITCH OWNERSHIP OF THE VIEW
FROM THE LAYER TO THE VIEW
2306
FIG. 23
2400
CONSTRUCT A DATA STRUCTURE HAVING
A HIERARCHY OF LAYERS WITH A
LAYER BEING ASSOCIATED WITH A
VIEW
2402
STORE THE DATA STRUCTURE IN MEMORY
MAINTAIN A RETAINED COUNT OF THE
NUMBER OF REFERENCES TO THE VIEW
FROM OTHER OBJECTS
DEALLOCATE THE VIEW FROM MEMORY
IF THE RETAINED COUNT JS ZERO
FIG. 24
APLNDC00027172
EM
22
2508
2512
;
2532
2_m
FIG. 25A
2532
21
2512
2B
FIG. 25B
APLNDC00027173
2600
CONSTRUCT A DATA STRUCTURE HAVING
A HIERARCHY OF LAYERS ASSOCIATED
WITH THE USER INTERFACE OF THE
DEVICE
DETERMINE WHETHER EACH LAYER OF THE
DATA STRUCTURE IS ASSOCIATED WITH
MEDIA OR NON-MEDIA CONTENT
2604
DETACH MEDIA CONTENT FROM THE DATA
STRUCTURE
2606
STORE MEDIA CONTENT IN A FIRST
MEMORY LOCATION
STORE NON-MEDIA CONTENT IN A SECOND
MEMORY LOCATION
2610
COMPOSITE THE MEDIA AND NON-MEDIA
CONTENT FOR DISPLAY ON THE
DEVICE
2612
FIG. 26
APLNDC00027174
2700
2712
2704
-
2710
I
2706
2720
2130
_2_740
I
I
I
I
i
i
2722
2732
2742
FIG. 27
APLNDC00027175
2838
2834
2832
2800
)
2836
2840
o
.
2844
2842
2846
FIG. 28
APLNDC00027176
2950
2960
'
2956
2962
'
2952
2954
2964
2958
FIG. 29
APLNDC00027177
3084 3098
3070
3093
3089
3095
3087
3091
3097
FIG. 30A
3070
3092
3084A
3088
3087
3096
3094
3089
3091
FIG. 30B
APLNDC00027178
DISPLAY DEVICE
3106
BACKLIGHT
3106A
ANTENNA
SY3 M
| DIGITAL AND/ORANALOG RF
-- TRANSCEIVER ¯
H2
STORAGE
DEVICE
3104
DIG-TAL
PROCESSING
SYSTEM
3113
/
AUDIO
* TRANSDUCER
\
_3101
MEDIA
PROCESSING
SYETEM
3609
|
|
\
\
MICROPHONE
/
'
SENSOR(S)
3110
INPUT
DEVICE(S)
3105
BATTERY
3107
105A
FIG. 31
APLNDC00027179
3200
3208
CACHE
(OPTIONAL)
3202
MICROPR CESSOR
3204
MEMORY
3206
BUS
3210
DISPLAY
CONTROLLER
AND
DISPLAY
DEVICE
(OPTIONAL)
3212
llO
CONTROLLER(S)
\
*
3216
3214
I/O DEVICE(S)
(E G., KEYBOARD,
CURSORCONTROL
DEVICE, NETWORK
INTERFACE)
'
SENSOR(S)
FOR USER
ACTIVITY
FIG. 32
APLNDC00027180
Disclaimer: Justia Dockets & Filings provides public litigation records from the federal appellate and district courts. These filings and docket sheets should not be considered findings of fact or liability, nor do they necessarily reflect the view of Justia.
Why Is My Information Online?