WO2000060514A1 - Methods, systems, and computer program products for conveying information through a multiple pane display - Google Patents

Methods, systems, and computer program products for conveying information through a multiple pane display Download PDF

Info

Publication number
WO2000060514A1
WO2000060514A1 PCT/US2000/007187 US0007187W WO0060514A1 WO 2000060514 A1 WO2000060514 A1 WO 2000060514A1 US 0007187 W US0007187 W US 0007187W WO 0060514 A1 WO0060514 A1 WO 0060514A1
Authority
WO
WIPO (PCT)
Prior art keywords
day
month
pane
view
displaying
Prior art date
Application number
PCT/US2000/007187
Other languages
French (fr)
Other versions
WO2000060514A8 (en
WO2000060514A9 (en
Inventor
Mona Singh
Original Assignee
Ericsson, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ericsson, Inc. filed Critical Ericsson, Inc.
Priority to AU38974/00A priority Critical patent/AU3897400A/en
Publication of WO2000060514A1 publication Critical patent/WO2000060514A1/en
Publication of WO2000060514A8 publication Critical patent/WO2000060514A8/en
Publication of WO2000060514A9 publication Critical patent/WO2000060514A9/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00Digital computers in general; Data processing equipment in general
    • G06F15/02Digital computers in general; Data processing equipment in general manually operated with input through keyboard and computation using a built-in program, e.g. pocket calculators
    • G06F15/025Digital computers in general; Data processing equipment in general manually operated with input through keyboard and computation using a built-in program, e.g. pocket calculators adapted to a specific application
    • G06F15/0266Digital computers in general; Data processing equipment in general manually operated with input through keyboard and computation using a built-in program, e.g. pocket calculators adapted to a specific application for time management, e.g. calendars, diaries
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance

Definitions

  • the present invention relates generally to the field of computer display systems, and, more particularly, to conveying information through multiple windows or panes.
  • FIG. 1 depicts a conventional PDA device 22, which includes a display screen 24, feature access buttons 26a, 26b, and 26c, and a stylus 28.
  • the display screen 24 is typically made using "touch screen” technology, which allows a user to interact with the display screen using, for example, their finger or the stylus 28.
  • PDA devices evolve their capabilities continue to expand with today's PDAs providing such features as electronic date and address books, e-mail, memo pads (handwriting recognition), Internet browsers, and phone/facsimile access.
  • FIG. 2 depicts a typical cellular phone or mobile terminal 32 that includes a display screen 34.
  • smartphones or wireless information devices To compete with PDAs that provide communication capabilities, such as voice calls, facsimile transmission, Internet access, and e-mail, a new generation of mobile terminals 32, known as smartphones or wireless information devices, now include personal organization features, such as date and address books, to-do lists, and memo pads.
  • a stylus 36 can be used to interact with the display screen 34 to invoke and operate these various features.
  • These smartphones or wireless information devices may also include a foldout keyboard (not shown) that can be used to input information and/or a display screen on the backside of he device opposite the keypad .
  • the display screen size may also be limited.
  • a first object which can be, for example, a month calendar view or a day diary view
  • a second object which can also be a month calendar view or a day diary view
  • a third object can then be displayed in the first pane while maintaining the second object in the second pane in its current state.
  • Information such as calendar and/or day diary information, can therefore be conveyed via a pair of panes on a display screen.
  • the present invention is applicable to any size display, it may be particularly useful in computing devices having small display screens because information can be conveyed using only two panes. Moreover, the present invention preserves the meaning associations between the information presented in the two panes, which allows a user to navigate between the views in a natural manner.
  • the first and second objects may comprise various permutations of a month calendar view and a day diary view.
  • the first and second objects may both be month calendar views where the first and second months are either consecutive or non-consecutive.
  • the first and second objects may both be day diary views, or the first object may be a day diary view while the second object is a month calendar view.
  • the month calendar view may include a day diary icon for displaying the day diary view associated with an identified day in the month and previous and next month icons.
  • the day diary view may include a month calendar icon for displaying the month calendar view associated with the day diary view and previous and next day icons.
  • methods, systems, and computer program products can enable a pair of panes to be displayed on a display screen.
  • a first object which can be, for example, a month calendar view or a day diary view, is displayed in the first pane.
  • a second object which can also be a month calendar view or a day diary view, is displayed in the second pane.
  • the month calendar view includes a day diary icon for displaying the day diary view associated with an identified day in the month, a day icon corresponding to each day in the month calendar view for displaying the day diary view associated with that day, and previous and next month icons.
  • the day diary view includes a month calendar icon for displaying the month calendar view associated with the day diary and previous and next day icons.
  • invocation of the next or previous day icons may cause the day diary view to cross a month boundary.
  • the month calendar view is updated to show the new month corresponding to the month navigated to by the user in the day diary view.
  • the first and second panes may be oriented horizontally on the display screen with the first pane being to the left of the second pane.
  • the first and second objects may be ordered chronologically with the first object being contemporaneous with or preceding the second object in time.
  • FIG. 1 illustrates a conventional personal digital assistant device
  • FIG. 2 illustrates a conventional mobile terminal device that includes a display screen
  • FIG. 3 is a block diagram that illustrates methods, systems, and computer program products for conveying information in accordance with the present invention
  • FIG. 4 illustrates a multiple window or pane display screen in accordance with the present invention
  • FIG. 5 is a state diagram of the methods, systems, and computer program products of FIG. 3;
  • FIGS. 6 A - 6D illustrate the display of FIG. 4 for the methods, systems, and computer program products of FIG. 3 in the various states of FIG. 5;
  • FIGS. 7A - 7D are a flow chart illustrating operations of the methods, systems, and computer program products of FIG. 3 in a first state of FIG. 5;
  • FIGS. 8A - 8F are a flow chart illustrating operations of the methods, systems, and computer program products of FIG. 3 in a second state of FIG. 5;
  • the present invention can be embodied as a method, a computer system, or a computer program product. Accordingly, the present invention can take the form of an entirely hardware embodiment, an entirely software (including firmware, resident software, micro-code, etc.) embodiment, or an embodiment containing both software and hardware aspects. Furthermore, the present invention can take the form of a computer program product on a computer-usable or computer-readable storage medium having computer-usable program code means embodied in the medium for use by or in connection with an instruction execution system.
  • a computer-usable or computer-readable medium can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with an instruction execution system, apparatus, or device.
  • the computer-usable or computer-readable medium can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, and a portable compact disc read-only memory (CDROM). Note that the computer-usable or computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via. for instance, optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
  • Computing device 42 includes a processor 44, which communicates with a memory 46 via an address/data bus 48.
  • the processor 44 can be any commercially available or custom microprocessor suitable for an embedded application.
  • the memory 46 is representative of the overall hierarchy of memory devices containing the software and data used to implement the functionality of the computing device 42.
  • the memory 46 can include, but is not limited to, the following types of devices: cache, ROM, PROM, EPROM, EEPROM, flash, SRAM, and DRAM.
  • the memory 46 may hold four major categories of software and data used in the computing device 42: the operating system 52; the application programs 54; the input/output (I/O) device drivers 56; and the application pro gram data 58.
  • the operating system 52 is typically designed for embedded applications and, preferably, is relatively compact to make the most efficient use of the memory 46.
  • One such example of an operating system meeting these criteria is the LINUX operating system, which is provided as free software by the Free Software Foundation, 59 Temple Place, Suite 330, Boston, MA 0211-1307, through a GNU public license and is used in a preferred embodiment of the present invention.
  • LINUX is typically bundled with other software to form a "distribution," which can then be downloaded from an Internet site or obtained on a diskette or CD-ROM.
  • the I/O device drivers 56 include software routines that are accessed through the operating system 52 by the application programs 54 to communicate with devices such as a display screen, certain components of the memory 46, and I/O ports such as a serial port or infra red (IR) port for transferring data to another device or system.
  • the static and dynamic data used by the application programs 54 is represented by the application data 58.
  • the application programs 54 comprise the programs that implement the various features of the computing device 42.
  • the application programs 54 may include software to implement features such as e-mail, Internet access, or word processing. In addition to these programs, information can be conveyed to a user in accordance with the present invention via a day planner/scheduler program 60.
  • the day planner/scheduler program 60 and the I/O device drivers 56 can be written in a high-level programming language, such as the JAVA programming language sold by Sun Microsystems, Inc., 901 San Antonio Road, Palo Alto, CA 94303, for development convenience. Nevertheless, some code segments of the day planner/scheduler program 60 or the I/O device drivers 56 can be written in assembly or machine language to optimize speed, memory usage, or layout of the software in the memory 46. In a preferred embodiment of the day planner/scheduler program, the JAVA programming language is used to implement most software modules.
  • FIG. 4 illustrates a display screen 64 in which two windows or panes 66a and 66b are defined in accordance with the present invention. These two windows or panes 66a, 66b may also be referred to herein as windows or panes one and two respectively. As will be described hereinafter, the windows or panes 66a and 66b are used by the day planner/scheduler program 60 to convey information to a user in accordance with the principles of the present invention. It should be understood, however, that while the present invention is illustrated herein with reference to a day planner/scheduler application, the principles discussed may also be applicable to other applications.
  • the high level architecture of the day planner/scheduler program 60 can be modeled as a finite state diagram as shown in FIG. 5.
  • a Ml, M2 state 68 indicates that the day planner/scheduler program 60 is displaying month calendar views in both panes 66a and 66b as shown in FIG. 6 A.
  • the Ml, D2 state 72 indicates that the day planner/scheduler program 60 is displaying a month calendar view in pane one 66a and a day diary view in pane two 66b as shown in FIG. 6B.
  • the Dl , M2 state 74 indicates that the day planner/scheduler program 60 is displaying a day diary view in pane one 66a and a month calendar view in pane two 66b as shown in FIG. 6C.
  • the Dl, D2 state 76 indicates that the day planner/scheduler program 60 is displaying day diary views in both panes 66a and 66b as shown in FIG. 6D.
  • the month calendar view may be a view of the weeks and days of a month as shown, for example, in FIG. 6 A. This view may show a relatively small amount of information for each day, such as what day of the week it is, whether a certain day is a holiday, and/or whether the user has an engagement scheduled for that day.
  • the day diary view which is shown in pane two 66b of FIG. 6B, may, for example, comprise a detailed view of a person's schedule for a particular day in which notations can be made for appointments, to-do items, or any other information the user wishes to record. This view can also enable special actions, such as placing a phone call or sending an e-mail message to the person that user has an appointment with. Referring still to FIG. 5, when the day planner/scheduler program 60 is in the
  • Ml, M2 state 68 as shown in FIG. 6A, four events can occur: the user may select the next or previous month to be displayed in pane one 66a by invoking a pair of scrolling arrows 78a or 78b (see FIG. 6A), the user may select the next or previous month to be displayed in pane two 66b by invoking the scrolling arrows 78a or 78b, the user may select a date diary for display from pane two 66b by invoking a day diary icon 82 (see FIG.
  • the day planner/scheduler program 60 remains in the Ml, M2 state 68. If the user selects a day diary from pane two 66b, the day planner/scheduler program 60 transitions to the Dl, M2 state 74, as shown in FIG. 6C. And if the user selects a day diary from pane one 66a, the day planner/scheduler program 60 transitions to the Ml, D2 state 72, as shown in FIG 6B .
  • the user may select the next or previous month to be displayed in pane one 66a by invoking the scrolling arrows 78a or 78b, the user may select the next or previous day to be displayed in pane two 66b by invoking a pair of scrolling arrows 84a or 84b (see FIG. 6B), the user may select a new day diary for display from pane one 66a by invoking the day diary icon 82 or invoking a particular day in the month calendar, the user may select a month for display from pane two 66b by invoking a month calendar icon 86 (see FIG.
  • the user may select a second day diary for display from pane one 66a by invoking the day diary icon 82 and invoking a particular day in the month calendar.
  • the scrolling arrows 84a and 84b are effectively previous day and next day icons respectively. If the user selects the next or previous month to be displayed in pane one 66a or the user selects the next or previous day diary to be displayed in pane two 66b, the day planner/scheduler program 60 remains in the Ml, D2 state 72. Similarly, if the user selects a new day diary from pane one 66a, the day planner/scheduler program 60 remains in the Ml, D2 state 72.
  • the day planner/scheduler program 60 transitions to the Ml, M2 state 68, as shown in FIG. 6A. And if the user selects a second day diary from pane one 66a, the day planner/scheduler program 60 transitions to the Dl, D2 state 76, as shown in FIG. 6D.
  • the user may select the next or previous month to be displayed in pane two 66b by invoking the scrolling arrows 78a or 78b, the user may select the next or previous day to be displayed in pane one 66a by invoking the scrolling arrows 84a or 84b, the user may select a new day diary for display from pane two 66b by invoking the day diary icon 82 or invoking a particular day in the month calendar, the user may select a month for display from pane one 66a by invoking the month calendar icon 86, or the user may select a second day diary for display from pane two 66b by invoking the day diary icon 82 and invoking a particular day in the month calendar.
  • the day planner/scheduler program 60 remains in the Dl, M2 state 74. Similarly, if the user selects a new day diary from pane two 66b, the day planner/scheduler program 60 remains in the Dl, M2 state 74. If the user selects a month for display from pane one 66a, the day planner/scheduler program 60 transitions to the Ml, M2 state 68, as shown in FIG. 6A.
  • the day planner/scheduler program 60 transitions to the Dl, D2 state 76, as shown in FIG. 6D.
  • the day planner/scheduler program 60 is in the Dl, D2 state 76, as shown in FIG.
  • four events can occur: the user may select the next or previous day to be displayed in pane one 66a by invoking the scrolling arrows 84a or 84b, the user may select the next or previous day to be displayed in pane two 66b by invoking the scrolling arrows 84a or 84b, the user may select a month for display from pane two 66b by invoking the month calendar icon 86 in pane two 66b, or the user may select a month for display from pane one 66a by invoking the month calendar icon 86 in pane one 66a.
  • the day planner/scheduler program 60 remains in the Dl, D2 state 76. If the user selects a month for display from pane two 66b, the day planner/scheduler program 60 transitions to the Dl, M2 state 74, as shown in FIG. 6C. And if the user selects a month for display from pane one 66a, the day planner/scheduler program 60 transitions to the Ml, D2 state 72, as shown in FIG. 6B.
  • the present invention is described hereinafter with reference to flowchart illustrations of methods, systems, and computer program products according to an embodiment of the invention.
  • each block of the flowchart illustrations, and combinations of blocks in the flowchart illustrations can be implemented by computer program instructions.
  • These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart block or blocks.
  • These computer program instructions may also be stored in a computer- readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means that implement the function specified in the flowchart block or blocks.
  • the computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions that execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.
  • the day planner/scheduler program 60 can be designed to initialize in any of the four states described above with reference to FIG. 5. For example, it may be desirable to design the day planner/scheduler program 60 to initialize in either the Ml , D2 state 72 or the Dl , M2 state 74 in which today's day diary and the current month are displayed. Alternatively, the day planner/scheduler program 60 may be designed to initialize in the last state that existed before the program was exited. The user may also be allowed to choose a particular initialization state.
  • the process begins at block 92 where a determination is made whether today's date is available in either pane one 66a or pane two 66b. If today's date is available, then the date is highlighted at block 94.
  • an input request is received and processed by the day planner/scheduler program 60. The following steps in the flowchart are based on an evaluation of this input request.
  • pane one 66a month calendar view is updated with the pane two 66b month calendar view currently on display at block 104.
  • the pane two 66b month calendar view is then updated with the month calendar view immediately following the month calendar view currently on display in pane two 66b at block 106.
  • the views displayed in the panes 66a and 66b are arranged in chronological order such that the day diary or month calendar view in pane one 66a does not post date the day diary or month calendar view in pane two 66b.
  • pane one 66a month calendar view is updated with the month calendar view immediately following the month calendar view currently on display in pane one 66a at block 108.
  • next month icon 78b has not been invoked in pane one 66a as determined at block 98, then a determination is made at block 112 whether the previous month icon 78a has been invoked in pane one 66a. If the previous month icon 78a has been invoked in pane one 66a, then connector F is followed to block 114 where the pane one 66a month calendar view is updated with the month calendar view immediately preceding the month calendar view currently on display in pane one 66 a.
  • next month icon 78b has been invoked in pane two 66b.
  • the pane two 66b month calendar view is updated with the month calendar view immediately following the month calendar view currently on display in pane two 66b at block 118. If the next month icon 78b has not been invoked in pane two 66b as determined at block 116, then a determination is made at block 122 whether the previous month icon 78a has been invoked in pane two 66b.
  • pane two 66b is followed to block 124 where a determination is made whether the previous month calendar view requested in pane two 66b is the same as the current month calendar view on display in pane one 66a.
  • the pane two 66b month calendar view is updated with the pane one 66a month calendar view currently on display at block 126.
  • the pane one 66a month calendar view is then updated with the month calendar view immediately preceding the month calendar view currently on display in pane one 66a at block 128.
  • pane two 66b month calendar view is updated with the month calendar view immediately preceding the month calendar view currently on display in pane two 66b by following connector K to block 132.
  • connector L is followed to FIG. 7D where a determination is made at block 134 whether the day diary icon 82 or a specific day from the month calendar view has been invoked in pane one 66a. If the day diary icon 82 or a specific day from the month calendar view has been invoked in pane one 66a, then the day planner/scheduler program 60 transitions to state Ml, D2 72 at block 136 where the day diary view is displayed in pane two 66b for a selected day from the month calendar view on display in pane one 66a.
  • a day may be selected, for example, by clicking on the pane 66a with a stylus to highlight the date and then invoking the day diary icon 82 or by double clicking on the desired date on the pane 66a to bypass the day diary icon 82. Note that if the current date is available in the month calendar view on display in pane one 66 a, it is already highlighted in a preferred embodiment of the present invention and thus the day diary for the current date can be accessed directly by invoking the day diary icon 82.
  • connector M is followed to block 138 where a determination is made whether the day diary icon 82 or a specific day from the month calendar view has been invoked in pane two 66b. If the day diary icon 82 or a specific day from the month calendar view has been invoked in pane two 66b, then the day planner/scheduler program 60 transitions to state Dl , M2 74 at block 142 where the day diary view is displayed in pane one 66a for a selected day from the month calendar view on display in pane two 66b.
  • the day diary icon 82 is invoked in either pane one 66a or pane two 66b, then the day diary view for a highlighted day in the pane in which the icon was invoked could be displayed in that same pane.
  • the day planner/scheduler program 60 transitions to state Dl, M2 where the day diary view for a highlighted day is displayed in pane one 66a.
  • the day plarmer/scheduler program 60 could be made to behave differently depending on whether a day is selected via the day diary icon 82 or by invoking a specific day in the month calendar view.
  • the process begins at block 152 where the date associated with the day diary view on display in pane two 66b is highlighted in pane one 66a.
  • a determination is made whether today's date is available in pane one 66a. If today's date is available, then the date is highlighted at block 156.
  • an input request is received and processed by the day planner/scheduler program 60. The following steps in the flowchart are based on an evaluation of this input request. Following connector B to block 162 a determination is made whether the user has invoked the next month icon 78b (see FIG. 6B) in pane one 66a.
  • next month icon 78b has been invoked in pane one 66a
  • the pane one 66a month calendar view is updated with the pane two 66b day diary view currently on display at block 166.
  • pane one 66a month calendar view is updated with the month calendar view immediately following the month calendar view currently on display in pane one 66a at block 172.
  • a determination is then made at block 174 whether today's date or the date associated with the day diary view on display in pane two 66b is available in pane one 66a. If today's date or the day diary date is available, then the date(s) are highlighted at block 176.
  • next month icon 78b has not been invoked in pane one 66a as determined at block 162
  • a determination is then made at block 184 whether today's date is available in pane one 66a. If today's date is available, then the date is highlighted at block 186.
  • connector E is followed to FIG. 8C where a determination is made at block 188 whether the next day icon 84b has been invoked in pane two 66b. If the next day icon 84b has been invoked in pane two 66b, then connector F is followed to block 192 where a determination is made whether the next day diary view requested in pane two 66b post dates the current month calendar view on display in pane one 66a.
  • pane one 66a is updated with the month calendar view immediately following the month calendar view currently on display in pane one 66a (i.e., the month calendar view associated with the next diary day requested in pane two 66b).
  • Pane two 66b is updated with the day diary view immediately following the day diary view currently on display in pane two 66b at block 196.
  • pane two 66b day diary view is updated with the day diary view immediately following the day diary view currently on display in pane two 66b at block 206.
  • next day icon 84b has not been invoked in pane two 66b as determined at block 188, then connector I is followed where a determination is made at block 208 whether the previous day icon 84a has been invoked in pane two 66b. If the previous day icon 84a has been invoked in pane two 66b, then a determination is made at block 212 whether the previous day diary view requested in pane two 66b pre-dates the current month calendar view on display in pane one 66a.
  • pane one 66a is updated with the month calendar view immediately preceding the month calendar view currently on display in pane one 66a (i.e., the month calendar view associated with the previous day diary requested in pane two 66b).
  • Pane two 66b is updated with the day diary view immediately preceding the day diary view currently on display in pane two 66b at block 216.
  • the date associated with the day diary view on display in pane two 66b is highlighted in pane one 66a.
  • pane two 66b is updated with the day diary view of the new day requested in pane one 66a at block 232.
  • pane two 66b is highlighted in pane one 66a.
  • FIG. 8F a determination is made at block 236 whether a request is made to display two days in the panes 66a and 66b. This can be done in a preferred embodiment of the present invention by invoking the day diary icon 82 and a day from the month calendar view on display in pane one 66a simultaneously. If two day diary views have been requested as determined at block 236, then the day planner/scheduler programs transitions to state Dl, D2 76 at block 238 where the two day diary views are displayed in the panes 66a and 66b. Finally, if a request is not made to display two day diaries in the panes 66a and
  • the process begins at block 252 where the date associated with the day diary view on display in pane one 66a is highlighted in pane two 66b.
  • a determination is made whether today's date is available in pane two 66b. If today's date is available, then the date is highlighted at block 256.
  • an input request is received and processed by the day planner/scheduler program 60. The following steps in the flowchart are based on an evaluation of this input request. Following connector B to block 262 a determination is made whether the user has invoked the previous month icon 78a (see FIG. 6C) in pane two 66b.
  • pane two 66b determines whether the previous month calendar view requested in pane two 66b pre-dates the month associated with the day diary view on display in pane one 66a.
  • the pane two 66b month calendar view is updated with the pane one 66a day diary view currently on display at block 266.
  • the day planner/scheduler program 60 transitions to state Ml, D2 72 at block 268 where pane one 66a is then updated with the month calendar view associated with the previous month requested in pane two 66b.
  • pane two 66b month calendar view is updated with the month calendar view immediately preceding the month calendar view currently on display in pane two 66b at block 272.
  • a determination is then made at block 274 whether today's date or the date associated with the day diary view on display in pane one 66a is available in pane two 66b. If today's date or the day diary date is available, then the date(s) are highlighted at block 276.
  • pane two 66b is updated with the month calendar view immediately preceding the month calendar view currently on display in pane two 66b (i.e., the month calendar view associated with the previous diary day requested in pane one 66a).
  • Pane one 66a is updated with the day diary view immediately preceding the day diary view currently on display in pane one 66a at block 296.
  • the date associated with the day diary view on display in pane one 66a is highlighted in pane two 66b.
  • a determination is then made at block 302 whether today's date is available in pane two 66b. If today's date is available, then connector G is followed to FIG. 9D where the date is highlighted at block 304.
  • pane one 66a day diary view is updated with the day diary view immediately preceding the day diary view currently on display in pane one 66a at block 306.
  • connector I is followed where a determination is made at block 308 whether the next day icon 84b has been invoked in pane one 66a. If the next day icon 84b has been invoked in pane one 66a, then a determination is made at block 312 whether the next day diary view requested in pane one 66a post dates the current month calendar view on display in pane two 66b. If the next day diary view requested in pane one 66a post dates the current month calendar view on display in pane two 66b, then the day diary view is about to cross a month boundary and the month calendar view on display in pane two 66b will be updated to correspond to the new month.
  • pane two 66b is updated with the month calendar view immediately following the month calendar view currently on display in pane two 66b (i.e. , the month calendar view associated with the next day diary requested in pane one 66a).
  • Pane one 66a is updated with the day diary view immediately following the day diary view currently on display in pane one 66a at block 316.
  • the date associated with the day diary view on display in pane one 66a is highlighted in pane two 66b.
  • a determination is then made at block 322 whether today's date is available in pane two 66b. If today's date is available, then the date is highlighted at block 324.
  • pane one 66a day diary view is updated with the day diary view immediately following the day diary view currently on display in pane one 66a at block 326.
  • pane one 66a is updated with the day diary view of the new day requested in pane two 66b at block 332.
  • pane one 66a is updated with the day diary view of the new day requested in pane two 66b at block 332.
  • the date associated with the new day diary view on display in pane one 66a is highlighted in pane two 66b.
  • FIG. 9F a determination is made at block 336 whether a request is made to display two days in the panes 66a and 66b. This can be done in a preferred embodiment of the present invention by invoking the day diary icon 82 and a day from the month calendar view on display in pane two 66b simultaneously. If two day diary views have been requested as determined at block 336, then the day planner/scheduler programs transitions to state Dl, D2 76 at block 338 where the two day diary views are displayed in the panes 66 a and 66b.
  • the process begins at block 352 where an input request is received and processed by the day planner/scheduler program 60.
  • the following steps in the flowchart are based on an evaluation of this input request.
  • pane two 66b day diary view is then updated with the day diary view immediately following the day diary view currently on display in pane two 66b at block 362.
  • the views displayed in the panes 66 a and 66b are arranged in chronological order such that the day diary or month calendar view in pane one 66a does not post date the day diary or month calendar view in pane two 66b.
  • pane one 66a day diary view is updated with the day diary view immediately following the day diary view currently on display in pane one 66a at block 364.
  • next day icon 84b has not been invoked in pane one 66a as determined at block 354, then a determination is made at block 366 whether the previous day icon 84a has been invoked in pane one 66a. If the previous day icon 84a has been invoked in pane one 66a, then connector E is followed to block 368 where the pane one 66a day diary view is updated with the day diary view immediately preceding the day diary view currently on display in pane one 66a. If the previous day icon 84a has not been invoked in pane one 66a as determined at block 366, then a determination is made at block 372 whether the next day icon 84b has been invoked in pane two 66b. Following connector G to FIG. IOC, if the next day icon 84b has been invoked in pane two 66b, then the pane two 66b day diary view is updated with the day diary view immediately following the month calendar view currently on display in pane two 66b at block 374.
  • next day icon 84b has not been invoked in pane two 66b as determined at block 372, then a determination is made at block 376 whether the previous day icon 84a has been invoked in pane two 66b. If the previous day icon 84a has been invoked in pane two 66b, then connector I is followed to block 378 where a determination is made whether the previous day diary view requested in pane two 66b is the same as the current day diary view on display in pane one 66a.
  • pane two 66b day diary view is updated with the pane one 66a day diary view currently on display at block 382.
  • the pane one 66a day diary view is then updated with the day diary view immediately preceding the day diary view currently on display in pane one 66a at block 384.
  • pane two 66b day diary view is updated with the day diary view immediately preceding the day diary view currently on display in pane two 66b by following connector J to block 386. If the previous day icon 84a has not been invoked in pane two 66b as determined at block 376, then connector K is followed to FIG. 10D where a determination is made at block 388 whether the month calendar icon 86 has been invoked in pane one 66a.
  • the day planner/scheduler program 60 transitions to state Ml, D2 72 at block 392 where the month calendar view is displayed in pane one 66b that corresponds with the day diary view previously in pane one 66a.
  • FIGS. 7A - 7D, 8A - 8F, 9A - 9F, and 10A - 10D show the architecture, functionality, and operation of a possible implementation of the day planner/scheduler 60 software.
  • each block represents a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s).
  • the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
  • the day planner/scheduler program 60 described herein provides an easy to use electronic day planner/calendar system. While the present invention is applicable to any size display, it is particularly useful in computing devices having small display screens because it conveys all information via two panes, which are oriented horizontal to one another in a preferred embodiment. It should be further understood that, as stated hereinbefore, the principles of the present invention may also be applicable to other applications. For example, the present invention could be applied to an e-mail application in which a message view and a message list view are defined. The message list view may provide a listing of all the e-mail messages in a particular mailbox by title, sender, or other criteria while the message view provides the text for a particular message.

Abstract

Methods, systems, and computer program products can enable a pair of panes to be displayed on a display screen. A first object, which can be, for example, a month calendar view or a day diary view, is displayed in the first pane. Similarly, a second object, which can also be a month calendar view or a day diary view, is displayed in the second pane. A third object can then be displayed in the first pane while maintaining the second object in the second pane in its current state. Information, such as calendar and/or day diary information, can therefore be conveyed via a pair of panes on a display screen. Thus, while the present invention is applicable to any size display, it may be particularly useful in computing devices having small display screens because information can be conveyed using only two panes. Moreover, the meaning associations between the information presented in the two panes are preserved, which allows a user to navigate between the views in a natural manner.

Description

METHODS, SYSTEMS, AND COMPUTER PROGRAM PRODUCTS FOR CONVEYING INFORMATION THROUGH A MULTIPLE PANE DISPLAY
Field of the Invention
The present invention relates generally to the field of computer display systems, and, more particularly, to conveying information through multiple windows or panes.
Background of the Invention
A new type of computer has been developed and marketed that is smaller than a laptop computer. This new type of computer may be called a personal digital assistant (PDA) or a communicator. These PDA devices or communicators are typically small enough to be held by one hand and include such features as handwriting recognition, communication software for Internet access, and the ability to hook up to a personal computer (PC) to exchange information therewith. FIG. 1 depicts a conventional PDA device 22, which includes a display screen 24, feature access buttons 26a, 26b, and 26c, and a stylus 28. The display screen 24 is typically made using "touch screen" technology, which allows a user to interact with the display screen using, for example, their finger or the stylus 28. As PDA devices evolve their capabilities continue to expand with today's PDAs providing such features as electronic date and address books, e-mail, memo pads (handwriting recognition), Internet browsers, and phone/facsimile access.
Mobile phone technology has also improved such that cellular phones are small enough to fit into the palm of a person's hand. FIG. 2 depicts a typical cellular phone or mobile terminal 32 that includes a display screen 34. To compete with PDAs that provide communication capabilities, such as voice calls, facsimile transmission, Internet access, and e-mail, a new generation of mobile terminals 32, known as smartphones or wireless information devices, now include personal organization features, such as date and address books, to-do lists, and memo pads. A stylus 36 can be used to interact with the display screen 34 to invoke and operate these various features. These smartphones or wireless information devices may also include a foldout keyboard (not shown) that can be used to input information and/or a display screen on the backside of he device opposite the keypad .
Unfortunately, because it is generally desirable to keep the size of both PDAs and mobile terminals small, the display screen size may also be limited.
Consequently, there exists a need to improve the manner in which information, such as a calendar and/or day diary, is displayed to make better use of a limited display screen area.
Summary of the Invention
It is therefore an object of the invention to provide improved information display methods, systems, and computer program products.
It is another object of the invention to provide information display methods, systems, and computer program products that can be used to display information simultaneously via multiple windows or panes.
It is still another object of the present invention to provide improved information display methods, systems, and computer program products for small information devices.
These and other objects, advantages, and features of the present invention are provided by methods, systems, and computer program products that, in a first illustrative embodiment, can enable a pair of panes to be displayed on a display screen. A first object, which can be, for example, a month calendar view or a day diary view, is displayed in the first pane. Similarly, a second object, which can also be a month calendar view or a day diary view, is displayed in the second pane. A third object can then be displayed in the first pane while maintaining the second object in the second pane in its current state. Information, such as calendar and/or day diary information, can therefore be conveyed via a pair of panes on a display screen. Thus, while the present invention is applicable to any size display, it may be particularly useful in computing devices having small display screens because information can be conveyed using only two panes. Moreover, the present invention preserves the meaning associations between the information presented in the two panes, which allows a user to navigate between the views in a natural manner.
In accordance with an aspect of the invention, the first and second objects may comprise various permutations of a month calendar view and a day diary view. For example, the first and second objects may both be month calendar views where the first and second months are either consecutive or non-consecutive. Alternatively, the first and second objects may both be day diary views, or the first object may be a day diary view while the second object is a month calendar view.
In accordance with another aspect of the invention, the month calendar view may include a day diary icon for displaying the day diary view associated with an identified day in the month and previous and next month icons. Similarly, the day diary view may include a month calendar icon for displaying the month calendar view associated with the day diary view and previous and next day icons.
In a second illustrative embodiment of the present invention, methods, systems, and computer program products can enable a pair of panes to be displayed on a display screen. A first object, which can be, for example, a month calendar view or a day diary view, is displayed in the first pane. Similarly, a second object, which can also be a month calendar view or a day diary view, is displayed in the second pane. The month calendar view includes a day diary icon for displaying the day diary view associated with an identified day in the month, a day icon corresponding to each day in the month calendar view for displaying the day diary view associated with that day, and previous and next month icons. Similarly, the day diary view includes a month calendar icon for displaying the month calendar view associated with the day diary and previous and next day icons. In accordance with an aspect of the invention, when the first object is a day diary view for a first day and the second object is a month calendar view for the month associated with the first day, invocation of the next or previous day icons may cause the day diary view to cross a month boundary. In that case, the month calendar view is updated to show the new month corresponding to the month navigated to by the user in the day diary view.
In accordance with another aspect of the invention, the first and second panes may be oriented horizontally on the display screen with the first pane being to the left of the second pane. The first and second objects may be ordered chronologically with the first object being contemporaneous with or preceding the second object in time.
Brief Description of the Drawings Other features of the present invention will be more readily understood from the following detailed description of specific embodiments thereof when read in conjunction with the accompanying drawings, in which:
FIG. 1 illustrates a conventional personal digital assistant device; FIG. 2 illustrates a conventional mobile terminal device that includes a display screen;
FIG. 3 is a block diagram that illustrates methods, systems, and computer program products for conveying information in accordance with the present invention; FIG. 4 illustrates a multiple window or pane display screen in accordance with the present invention; FIG. 5 is a state diagram of the methods, systems, and computer program products of FIG. 3;
FIGS. 6 A - 6D illustrate the display of FIG. 4 for the methods, systems, and computer program products of FIG. 3 in the various states of FIG. 5;
FIGS. 7A - 7D are a flow chart illustrating operations of the methods, systems, and computer program products of FIG. 3 in a first state of FIG. 5;
FIGS. 8A - 8F are a flow chart illustrating operations of the methods, systems, and computer program products of FIG. 3 in a second state of FIG. 5;
FIGS. 9A - 9F are a flow chart illustrating operations of the methods, systems, and computer program products of FIG. 3 in a third state of FIG. 5; and FIGS. 10A - 10D are a flow chart illustrating operations of the methods, systems, and computer program products of FIG. 3 in a fourth state of FIG. 5. Detailed Description of Preferred Embodiments
While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that there is no intent to limit the invention to the particular forms disclosed, but on the contrary, the invention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the invention as defined by the claims. Like reference numbers signify like elements throughout the description of the figures.
As will be appreciated by those skilled in the art, the present invention can be embodied as a method, a computer system, or a computer program product. Accordingly, the present invention can take the form of an entirely hardware embodiment, an entirely software (including firmware, resident software, micro-code, etc.) embodiment, or an embodiment containing both software and hardware aspects. Furthermore, the present invention can take the form of a computer program product on a computer-usable or computer-readable storage medium having computer-usable program code means embodied in the medium for use by or in connection with an instruction execution system. In the context of this document, a computer-usable or computer-readable medium can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with an instruction execution system, apparatus, or device.
The computer-usable or computer-readable medium can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, and a portable compact disc read-only memory (CDROM). Note that the computer-usable or computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via. for instance, optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
Referring now to FIG. 3, the internal architecture of a computing device 42 incorporating an information display system in accordance with the present invention will be described hereafter. Computing device 42 includes a processor 44, which communicates with a memory 46 via an address/data bus 48. The processor 44 can be any commercially available or custom microprocessor suitable for an embedded application. The memory 46 is representative of the overall hierarchy of memory devices containing the software and data used to implement the functionality of the computing device 42. The memory 46 can include, but is not limited to, the following types of devices: cache, ROM, PROM, EPROM, EEPROM, flash, SRAM, and DRAM. As shown in FIG. 3, the memory 46 may hold four major categories of software and data used in the computing device 42: the operating system 52; the application programs 54; the input/output (I/O) device drivers 56; and the application pro gram data 58.
The operating system 52 is typically designed for embedded applications and, preferably, is relatively compact to make the most efficient use of the memory 46. One such example of an operating system meeting these criteria is the LINUX operating system, which is provided as free software by the Free Software Foundation, 59 Temple Place, Suite 330, Boston, MA 0211-1307, through a GNU public license and is used in a preferred embodiment of the present invention. LINUX is typically bundled with other software to form a "distribution," which can then be downloaded from an Internet site or obtained on a diskette or CD-ROM.
The I/O device drivers 56 include software routines that are accessed through the operating system 52 by the application programs 54 to communicate with devices such as a display screen, certain components of the memory 46, and I/O ports such as a serial port or infra red (IR) port for transferring data to another device or system. The static and dynamic data used by the application programs 54 is represented by the application data 58. Finally, the application programs 54 comprise the programs that implement the various features of the computing device 42. The application programs 54 may include software to implement features such as e-mail, Internet access, or word processing. In addition to these programs, information can be conveyed to a user in accordance with the present invention via a day planner/scheduler program 60.
The day planner/scheduler program 60 and the I/O device drivers 56 can be written in a high-level programming language, such as the JAVA programming language sold by Sun Microsystems, Inc., 901 San Antonio Road, Palo Alto, CA 94303, for development convenience. Nevertheless, some code segments of the day planner/scheduler program 60 or the I/O device drivers 56 can be written in assembly or machine language to optimize speed, memory usage, or layout of the software in the memory 46. In a preferred embodiment of the day planner/scheduler program, the JAVA programming language is used to implement most software modules.
Figure 4 illustrates a display screen 64 in which two windows or panes 66a and 66b are defined in accordance with the present invention. These two windows or panes 66a, 66b may also be referred to herein as windows or panes one and two respectively. As will be described hereinafter, the windows or panes 66a and 66b are used by the day planner/scheduler program 60 to convey information to a user in accordance with the principles of the present invention. It should be understood, however, that while the present invention is illustrated herein with reference to a day planner/scheduler application, the principles discussed may also be applicable to other applications. The high level architecture of the day planner/scheduler program 60 can be modeled as a finite state diagram as shown in FIG. 5. In particular, four states are defined: a Ml, M2 state 68, a Ml, D2 state 72, a Dl, M2 state 74, and a Dl, D2 state 76. These states correspond to the information views provided on the display screen 64 shown in FIGS. 6A - 6D. That is, the Ml , M2 state 68 indicates that the day planner/scheduler program 60 is displaying month calendar views in both panes 66a and 66b as shown in FIG. 6 A. The Ml, D2 state 72 indicates that the day planner/scheduler program 60 is displaying a month calendar view in pane one 66a and a day diary view in pane two 66b as shown in FIG. 6B. The Dl , M2 state 74 indicates that the day planner/scheduler program 60 is displaying a day diary view in pane one 66a and a month calendar view in pane two 66b as shown in FIG. 6C. And the Dl, D2 state 76 indicates that the day planner/scheduler program 60 is displaying day diary views in both panes 66a and 66b as shown in FIG. 6D. The month calendar view may be a view of the weeks and days of a month as shown, for example, in FIG. 6 A. This view may show a relatively small amount of information for each day, such as what day of the week it is, whether a certain day is a holiday, and/or whether the user has an engagement scheduled for that day. The day diary view, which is shown in pane two 66b of FIG. 6B, may, for example, comprise a detailed view of a person's schedule for a particular day in which notations can be made for appointments, to-do items, or any other information the user wishes to record. This view can also enable special actions, such as placing a phone call or sending an e-mail message to the person that user has an appointment with. Referring still to FIG. 5, when the day planner/scheduler program 60 is in the
Ml, M2 state 68, as shown in FIG. 6A, four events can occur: the user may select the next or previous month to be displayed in pane one 66a by invoking a pair of scrolling arrows 78a or 78b (see FIG. 6A), the user may select the next or previous month to be displayed in pane two 66b by invoking the scrolling arrows 78a or 78b, the user may select a date diary for display from pane two 66b by invoking a day diary icon 82 (see FIG. 6 A) or invoking a particular day in the month calendar, or the user may select a date diary for display from pane one 66a by invoking the day diary icon 82 or invoking a particular day in the month calendar. Note that the scrolling arrows 78a and 78b are effectively previous month and next month icons respectively. If the user selects the next or previous month to be displayed in either of the panes
66a or 66b, the day planner/scheduler program 60 remains in the Ml, M2 state 68. If the user selects a day diary from pane two 66b, the day planner/scheduler program 60 transitions to the Dl, M2 state 74, as shown in FIG. 6C. And if the user selects a day diary from pane one 66a, the day planner/scheduler program 60 transitions to the Ml, D2 state 72, as shown in FIG 6B .
When the day planner/scheduler program 60 is in the Ml, D2 state 72, as shown in FIG. 6B, five events can occur: the user may select the next or previous month to be displayed in pane one 66a by invoking the scrolling arrows 78a or 78b, the user may select the next or previous day to be displayed in pane two 66b by invoking a pair of scrolling arrows 84a or 84b (see FIG. 6B), the user may select a new day diary for display from pane one 66a by invoking the day diary icon 82 or invoking a particular day in the month calendar, the user may select a month for display from pane two 66b by invoking a month calendar icon 86 (see FIG. 6B), or the user may select a second day diary for display from pane one 66a by invoking the day diary icon 82 and invoking a particular day in the month calendar. Note that the scrolling arrows 84a and 84b are effectively previous day and next day icons respectively. If the user selects the next or previous month to be displayed in pane one 66a or the user selects the next or previous day diary to be displayed in pane two 66b, the day planner/scheduler program 60 remains in the Ml, D2 state 72. Similarly, if the user selects a new day diary from pane one 66a, the day planner/scheduler program 60 remains in the Ml, D2 state 72. If the user selects a month for display from pane two 66b, the day planner/scheduler program 60 transitions to the Ml, M2 state 68, as shown in FIG. 6A. And if the user selects a second day diary from pane one 66a, the day planner/scheduler program 60 transitions to the Dl, D2 state 76, as shown in FIG. 6D.
When the day planner/scheduler program 60 is in the Dl, M2 state 74, as shown in FIG. 6C, five events can occur: the user may select the next or previous month to be displayed in pane two 66b by invoking the scrolling arrows 78a or 78b, the user may select the next or previous day to be displayed in pane one 66a by invoking the scrolling arrows 84a or 84b, the user may select a new day diary for display from pane two 66b by invoking the day diary icon 82 or invoking a particular day in the month calendar, the user may select a month for display from pane one 66a by invoking the month calendar icon 86, or the user may select a second day diary for display from pane two 66b by invoking the day diary icon 82 and invoking a particular day in the month calendar. If the user selects the next or previous month to be displayed in pane two 66b or the user selects the next or previous day diary to be displayed in pane one 66a, the day planner/scheduler program 60 remains in the Dl, M2 state 74. Similarly, if the user selects a new day diary from pane two 66b, the day planner/scheduler program 60 remains in the Dl, M2 state 74. If the user selects a month for display from pane one 66a, the day planner/scheduler program 60 transitions to the Ml, M2 state 68, as shown in FIG. 6A. And if the user selects a second day diary from pane two 66b, the day planner/scheduler program 60 transitions to the Dl, D2 state 76, as shown in FIG. 6D. When the day planner/scheduler program 60 is in the Dl, D2 state 76, as shown in FIG. 6D, four events can occur: the user may select the next or previous day to be displayed in pane one 66a by invoking the scrolling arrows 84a or 84b, the user may select the next or previous day to be displayed in pane two 66b by invoking the scrolling arrows 84a or 84b, the user may select a month for display from pane two 66b by invoking the month calendar icon 86 in pane two 66b, or the user may select a month for display from pane one 66a by invoking the month calendar icon 86 in pane one 66a. If the user selects the next or previous day to be displayed in either of the panes 66a or 66b, the day planner/scheduler program 60 remains in the Dl, D2 state 76. If the user selects a month for display from pane two 66b, the day planner/scheduler program 60 transitions to the Dl, M2 state 74, as shown in FIG. 6C. And if the user selects a month for display from pane one 66a, the day planner/scheduler program 60 transitions to the Ml, D2 state 72, as shown in FIG. 6B. The present invention is described hereinafter with reference to flowchart illustrations of methods, systems, and computer program products according to an embodiment of the invention. It will be understood that each block of the flowchart illustrations, and combinations of blocks in the flowchart illustrations, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart block or blocks. These computer program instructions may also be stored in a computer- readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means that implement the function specified in the flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions that execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.
The operation and features provided by the day planner/scheduler program 60 will be described hereafter with reference to flow charts and with frequent reference to the state diagram of FIG. 5 and display views of FIGS. 6A - 6D. It should be understood that the day planner/scheduler program 60 can be designed to initialize in any of the four states described above with reference to FIG. 5. For example, it may be desirable to design the day planner/scheduler program 60 to initialize in either the Ml , D2 state 72 or the Dl , M2 state 74 in which today's day diary and the current month are displayed. Alternatively, the day planner/scheduler program 60 may be designed to initialize in the last state that existed before the program was exited. The user may also be allowed to choose a particular initialization state.
Ml. M2 State
With reference to the flowchart of FIGS. 7A - 7D, the operation of the day planner/scheduler program 60 in the Ml , M2 state 68, shown in FIG. 6A, will now be described.
The process begins at block 92 where a determination is made whether today's date is available in either pane one 66a or pane two 66b. If today's date is available, then the date is highlighted at block 94. At block 96, an input request is received and processed by the day planner/scheduler program 60. The following steps in the flowchart are based on an evaluation of this input request.
Following connector C to block 98, a determination is made whether the user has invoked the next month icon 78b (see FIG. 6A) in pane one 66a. If the next month icon 78b has been invoked in pane one 66a, then a determination is made at block 102 whether the next month calendar view requested in pane one 66a is the same as the current month calendar view on display in pane two 66b. To avoid confusing the user by displaying the same month calendar view in both panes 66a and 66b, if the next month calendar view requested in pane one 66a is the same as the current month calendar view on display in pane two 66b, then the pane one 66a month calendar view is updated with the pane two 66b month calendar view currently on display at block 104. The pane two 66b month calendar view is then updated with the month calendar view immediately following the month calendar view currently on display in pane two 66b at block 106. Note also that in a preferred embodiment of the day planner/scheduler program, the views displayed in the panes 66a and 66b are arranged in chronological order such that the day diary or month calendar view in pane one 66a does not post date the day diary or month calendar view in pane two 66b.
Following connector D to FIG. 7B, if the next month calendar view requested in pane one 66a is not the same as the current month calendar view on display in pane two 66b, then the pane one 66a month calendar view is updated with the month calendar view immediately following the month calendar view currently on display in pane one 66a at block 108.
If the next month icon 78b has not been invoked in pane one 66a as determined at block 98, then a determination is made at block 112 whether the previous month icon 78a has been invoked in pane one 66a. If the previous month icon 78a has been invoked in pane one 66a, then connector F is followed to block 114 where the pane one 66a month calendar view is updated with the month calendar view immediately preceding the month calendar view currently on display in pane one 66 a.
If the previous month icon 78a has not been invoked in pane one 66a as determined at block 112, then a determination is made at block 116 whether the next month icon 78b has been invoked in pane two 66b. Following connector H to FIG. 7C, if the next month icon 78b has been invoked in pane two 66b, then the pane two 66b month calendar view is updated with the month calendar view immediately following the month calendar view currently on display in pane two 66b at block 118. If the next month icon 78b has not been invoked in pane two 66b as determined at block 116, then a determination is made at block 122 whether the previous month icon 78a has been invoked in pane two 66b. If the previous month icon 78a has been invoked in pane two 66b, then connector J is followed to block 124 where a determination is made whether the previous month calendar view requested in pane two 66b is the same as the current month calendar view on display in pane one 66a. To avoid confusing the user by displaying the same month calendar view in both panes 66a and 66b, if the previous month calendar view requested in pane two 66b is the same as the current month calendar view on display in pane one 66a, then the pane two 66b month calendar view is updated with the pane one 66a month calendar view currently on display at block 126. The pane one 66a month calendar view is then updated with the month calendar view immediately preceding the month calendar view currently on display in pane one 66a at block 128.
If the previous month calendar view requested in pane two 66b is not the same as the current month calendar view on display in pane one 66a, then the pane two 66b month calendar view is updated with the month calendar view immediately preceding the month calendar view currently on display in pane two 66b by following connector K to block 132.
If the previous month icon 78 a has not been invoked in pane two 66b as determined at block 122, then connector L is followed to FIG. 7D where a determination is made at block 134 whether the day diary icon 82 or a specific day from the month calendar view has been invoked in pane one 66a. If the day diary icon 82 or a specific day from the month calendar view has been invoked in pane one 66a, then the day planner/scheduler program 60 transitions to state Ml, D2 72 at block 136 where the day diary view is displayed in pane two 66b for a selected day from the month calendar view on display in pane one 66a. A day may be selected, for example, by clicking on the pane 66a with a stylus to highlight the date and then invoking the day diary icon 82 or by double clicking on the desired date on the pane 66a to bypass the day diary icon 82. Note that if the current date is available in the month calendar view on display in pane one 66 a, it is already highlighted in a preferred embodiment of the present invention and thus the day diary for the current date can be accessed directly by invoking the day diary icon 82. Finally, if the day diary icon 82 or a specific day from the month calendar view has not been invoked in pane one 66a, connector M is followed to block 138 where a determination is made whether the day diary icon 82 or a specific day from the month calendar view has been invoked in pane two 66b. If the day diary icon 82 or a specific day from the month calendar view has been invoked in pane two 66b, then the day planner/scheduler program 60 transitions to state Dl , M2 74 at block 142 where the day diary view is displayed in pane one 66a for a selected day from the month calendar view on display in pane two 66b. Alternatively, if the day diary icon 82 is invoked in either pane one 66a or pane two 66b, then the day diary view for a highlighted day in the pane in which the icon was invoked could be displayed in that same pane. For example, if the day diary icon 82 is invoked in pane one 66a, then the day planner/scheduler program 60 transitions to state Dl, M2 where the day diary view for a highlighted day is displayed in pane one 66a. Thus, the day plarmer/scheduler program 60 could be made to behave differently depending on whether a day is selected via the day diary icon 82 or by invoking a specific day in the month calendar view.
Ml. D2 State
With reference to the flowchart of FIGS. 8A - 8F, the operation of the day planner/scheduler program 60 in the Ml, D2 state 72, shown in FIG. 6B, will now be described.
The process begins at block 152 where the date associated with the day diary view on display in pane two 66b is highlighted in pane one 66a. At block 154, a determination is made whether today's date is available in pane one 66a. If today's date is available, then the date is highlighted at block 156. At block 158, an input request is received and processed by the day planner/scheduler program 60. The following steps in the flowchart are based on an evaluation of this input request. Following connector B to block 162 a determination is made whether the user has invoked the next month icon 78b (see FIG. 6B) in pane one 66a. If the next month icon 78b has been invoked in pane one 66a, then a determination is made at block 164 whether the next month calendar view requested in pane one 66a post dates the month associated with the day diary view on display in pane two 66b. To maintain the chronological ordering between the views displayed in pane one 66a and pane two 66b as discussed hereinbefore, if the next month calendar view requested in pane one 66a post dates the month associated with the day diary view on display in pane two 66b, then the pane one 66a month calendar view is updated with the pane two 66b day diary view currently on display at block 166. Next, the day planner/scheduler program 60 transitions to state Dl , M2 74 at block 168 where pane two 66b is then updated with the month calendar view associated with the next month requested in pane one 66a. WO 00/60514 PCTtUSOO/07187
Following connector C to FIG. 8B, if the next month calendar view requested in pane one 66a does not post date the month associated with the day diary view on display in pane two 66b, then the pane one 66a month calendar view is updated with the month calendar view immediately following the month calendar view currently on display in pane one 66a at block 172. A determination is then made at block 174 whether today's date or the date associated with the day diary view on display in pane two 66b is available in pane one 66a. If today's date or the day diary date is available, then the date(s) are highlighted at block 176.
If the next month icon 78b has not been invoked in pane one 66a as determined at block 162, then a determination is made at block 178 whether the previous month icon 78a has been invoked in pane one 66a. If the previous month icon 78a has been invoked in pane one 66a, then the pane one 66a month calendar view is updated with the month calendar view immediately preceding the month calendar view currently on display in pane one 66a at block 182. A determination is then made at block 184 whether today's date is available in pane one 66a. If today's date is available, then the date is highlighted at block 186.
If the previous month icon 78a has not been invoked in pane one 66a as determined at block 178, then connector E is followed to FIG. 8C where a determination is made at block 188 whether the next day icon 84b has been invoked in pane two 66b. If the next day icon 84b has been invoked in pane two 66b, then connector F is followed to block 192 where a determination is made whether the next day diary view requested in pane two 66b post dates the current month calendar view on display in pane one 66a. If the next day diary view requested in pane two 66b post dates the current month calendar view on display in pane one 66a, then the day diary view is about to cross a month boundary and the month calendar view on display in pane one 66a will be updated to correspond to the new month. Accordingly, at block 194, pane one 66a is updated with the month calendar view immediately following the month calendar view currently on display in pane one 66a (i.e., the month calendar view associated with the next diary day requested in pane two 66b). Pane two 66b is updated with the day diary view immediately following the day diary view currently on display in pane two 66b at block 196. And finally, at block 198, the date associated with the day diary view on display in pane two 66b is highlighted in pane one 66a. A determination is then made at block 202 whether today's date is available in pane one 66a. If today's date is available, then connector G is followed to FIG. 8D where the date is highlighted at block 204.
If the next day diary view requested in pane two 66b does not post date the current month calendar view on display in pane one 66a as determined at block 192, then the pane two 66b day diary view is updated with the day diary view immediately following the day diary view currently on display in pane two 66b at block 206.
If the next day icon 84b has not been invoked in pane two 66b as determined at block 188, then connector I is followed where a determination is made at block 208 whether the previous day icon 84a has been invoked in pane two 66b. If the previous day icon 84a has been invoked in pane two 66b, then a determination is made at block 212 whether the previous day diary view requested in pane two 66b pre-dates the current month calendar view on display in pane one 66a. If the previous day diary view requested in pane two 66b pre-dates the current month calendar view on display in pane one 66a, then the day diary view is about to cross a month boundary and the month calendar view on display in pane one 66a will be updated to correspond to the new month. Accordingly, at block 214, pane one 66a is updated with the month calendar view immediately preceding the month calendar view currently on display in pane one 66a (i.e., the month calendar view associated with the previous day diary requested in pane two 66b). Pane two 66b is updated with the day diary view immediately preceding the day diary view currently on display in pane two 66b at block 216. And finally, at block 218, the date associated with the day diary view on display in pane two 66b is highlighted in pane one 66a. Following connector J to FIG. 8E, A determination is then made at block 222 whether today's date is available in pane one 66a. If today's date is available, then the date is highlighted at block 224. If the next day diary view requested in pane two 66b does not pre-date the current month calendar view on display in pane one 66a as determined at block 212, then the pane two 66b day diary view is updated with the day diary view immediately preceding the day diary view currently on display in pane two 66b at block 226. If the previous day icon 84a has not been invoked in pane two 66b as determined at block 208, then connector L is followed to block 228 where a determination is made whether the day diary icon 82 or a specific day from the month WO 00/60514 PCTtUSOO/07187 calendar view has been invoked in pane one 66a. If the day diary icon 82 or a specific day from the month calendar view has been invoked in pane one 66a, then pane two 66b is updated with the day diary view of the new day requested in pane one 66a at block 232. At block 234 the date associated with the new day diary view on display in pane two 66b is highlighted in pane one 66a.
If the day diary icon 82 or a specific day from the month calendar view has not been invoked in pane one 66a, then connector M is followed to FIG. 8F where a determination is made at block 236 whether a request is made to display two days in the panes 66a and 66b. This can be done in a preferred embodiment of the present invention by invoking the day diary icon 82 and a day from the month calendar view on display in pane one 66a simultaneously. If two day diary views have been requested as determined at block 236, then the day planner/scheduler programs transitions to state Dl, D2 76 at block 238 where the two day diary views are displayed in the panes 66a and 66b. Finally, if a request is not made to display two day diaries in the panes 66a and
66b as determined at block 236, then a determination is made at block 242 whether the month calendar icon 86 is invoked in pane two 66b. If the month calendar icon 86 has been invoked in pane two 66b, then the day planner/scheduler program 60 transitions to state Ml, M2 68 at block 244 where the month calendar view is displayed in pane two 66b for the month associated with the day diary view currently on display in pane two 66b.
Dl, M2 State
With reference to the flowchart of FIGS. 9A - 9F, the operation of the day planner/scheduler program 60 in the D 1 , M2 state 74, shown in FIG. 6C, will now be described.
The process begins at block 252 where the date associated with the day diary view on display in pane one 66a is highlighted in pane two 66b. At block 254, a determination is made whether today's date is available in pane two 66b. If today's date is available, then the date is highlighted at block 256. At block 258, an input request is received and processed by the day planner/scheduler program 60. The following steps in the flowchart are based on an evaluation of this input request. Following connector B to block 262 a determination is made whether the user has invoked the previous month icon 78a (see FIG. 6C) in pane two 66b. If the previous month icon 78a has been invoked in pane two 66b, then a determination is made at block 264 whether the previous month calendar view requested in pane two 66b pre-dates the month associated with the day diary view on display in pane one 66a. To maintain the chronological ordering between the views displayed in pane one 66a and pane two 66b as discussed hereinbefore, if the previous month calendar view requested in pane two 66b pre-dates the month associated with the day diary view on display in pane one 66a, then the pane two 66b month calendar view is updated with the pane one 66a day diary view currently on display at block 266. Next, the day planner/scheduler program 60 transitions to state Ml, D2 72 at block 268 where pane one 66a is then updated with the month calendar view associated with the previous month requested in pane two 66b.
Following connector C to FIG. 9B, if the previous month calendar view requested in pane two 66b does not pre-date the month associated with the day diary view on display in pane one 66a, then the pane two 66b month calendar view is updated with the month calendar view immediately preceding the month calendar view currently on display in pane two 66b at block 272. A determination is then made at block 274 whether today's date or the date associated with the day diary view on display in pane one 66a is available in pane two 66b. If today's date or the day diary date is available, then the date(s) are highlighted at block 276.
If the previous month icon 78a has not been invoked in pane two 66b as . determined at block 262, then a determination is made at block 278 whether the next month icon 78b has been invoked in pane two 66b. If the next month icon 78b has been invoked in pane two 66b, then the pane two 66b month calendar view is updated with the month calendar view immediately following the month calendar view currently on display in pane two 66b at block 282. A determination is then made at block 284 whether today's date is available in pane two 66b. If today's date is available, then the date is highlighted at block 286. If the next month icon 78b has not been invoked in pane two 66b as determined at block 278, then connector E is followed to FIG. 9C where a determination is made at block 288 whether the previous day icon 84a has been invoked in pane one 66a. If the previous day icon 84a has been invoked in pane one 66a, then connector F is followed to block 292 where a determination is made whether the previous day diary view requested in pane one 66a pre-dates the current month calendar view on display in pane two 66b. If the previous day diary view requested in pane one 66a pre-dates the current month calendar view on display in pane two 66b, then the day diary view is about to cross a month boundary and the month calendar view on display in pane two 66b will be updated to correspond to the new month. Accordingly, at block 294, pane two 66b is updated with the month calendar view immediately preceding the month calendar view currently on display in pane two 66b (i.e., the month calendar view associated with the previous diary day requested in pane one 66a). Pane one 66a is updated with the day diary view immediately preceding the day diary view currently on display in pane one 66a at block 296. And finally, at block 298, the date associated with the day diary view on display in pane one 66a is highlighted in pane two 66b. A determination is then made at block 302 whether today's date is available in pane two 66b. If today's date is available, then connector G is followed to FIG. 9D where the date is highlighted at block 304.
If the next day diary view requested in pane one 66a does not pre-date the current month calendar view on display in pane two 66b as determined at block 292, then the pane one 66a day diary view is updated with the day diary view immediately preceding the day diary view currently on display in pane one 66a at block 306.
If the previous day icon 84a has not been invoked in pane one 66a as determined at block 288, then connector I is followed where a determination is made at block 308 whether the next day icon 84b has been invoked in pane one 66a. If the next day icon 84b has been invoked in pane one 66a, then a determination is made at block 312 whether the next day diary view requested in pane one 66a post dates the current month calendar view on display in pane two 66b. If the next day diary view requested in pane one 66a post dates the current month calendar view on display in pane two 66b, then the day diary view is about to cross a month boundary and the month calendar view on display in pane two 66b will be updated to correspond to the new month. Accordingly, at block 314, pane two 66b is updated with the month calendar view immediately following the month calendar view currently on display in pane two 66b (i.e. , the month calendar view associated with the next day diary requested in pane one 66a). Pane one 66a is updated with the day diary view immediately following the day diary view currently on display in pane one 66a at block 316. And finally, at block 318, the date associated with the day diary view on display in pane one 66a is highlighted in pane two 66b. Following connector J to FIG. 9E, A determination is then made at block 322 whether today's date is available in pane two 66b. If today's date is available, then the date is highlighted at block 324.
If the next day diary view requested in pane one 66a does not post date the current month calendar view on display in pane two 66b as determined at block 312, then the pane one 66a day diary view is updated with the day diary view immediately following the day diary view currently on display in pane one 66a at block 326.
If the next day icon 84b has not been invoked in pane one 66a as determined at block 308, then connector L is followed to block 328 where a determination is made whether the day diary icon 82 or a specific day from the month calendar view has been invoked in pane two 66b. If the day diary icon 82 or a specific day from the month calendar view has been invoked in pane two 66b, then pane one 66a is updated with the day diary view of the new day requested in pane two 66b at block 332. At block 334 the date associated with the new day diary view on display in pane one 66a is highlighted in pane two 66b. If the day diary icon 82 or a specific day from the month calendar view has not been invoked in pane one 66b, then connector M is followed to FIG. 9F where a determination is made at block 336 whether a request is made to display two days in the panes 66a and 66b. This can be done in a preferred embodiment of the present invention by invoking the day diary icon 82 and a day from the month calendar view on display in pane two 66b simultaneously. If two day diary views have been requested as determined at block 336, then the day planner/scheduler programs transitions to state Dl, D2 76 at block 338 where the two day diary views are displayed in the panes 66 a and 66b.
Finally, if a request is not made to display two day diaries in the panes 66a and 66b as determined at block 336, then a determination is made at block 342 whether the month calendar icon 86 is invoked in pane one 66a. If the month calendar icon 86 has been invoked in pane one 66a, then the day planner/scheduler program 60 transitions to state Ml, M2 68 at block 344 where the month calendar view is displayed in pane one 66a for the month associated with the day diary view currently on display in pane one 66a.
PL D2 State
With reference to the flowchart of FIGS. 10 A - 10D, the operation of the day planner/scheduler program 60 in the Dl, D2 state 76, shown in FIG. 6D, will now be described.
The process begins at block 352 where an input request is received and processed by the day planner/scheduler program 60. The following steps in the flowchart are based on an evaluation of this input request.
At block 354, a determination is made whether the user has invoked the next day icon 84b (see FIG. 6D) in pane one 66a. If the next day icon 78b has been invoked in pane one 66a, then a determination is made at block 356 whether the next day diary view requested in pane one 66a is the same as the day diary view on display in pane two 66b. To avoid confusing the user by displaying the same day diary view in both panes 66a and 66b, if the next day diary view requested in pane one 66a is the same as the current day diary view on display in pane two όόb, then the pane one 66a day diary view is updated with the pane two 66b day diary view currently on display at block 358. The pane two 66b day diary view is then updated with the day diary view immediately following the day diary view currently on display in pane two 66b at block 362. Recall that in a preferred embodiment of the day planner/scheduler program, the views displayed in the panes 66 a and 66b are arranged in chronological order such that the day diary or month calendar view in pane one 66a does not post date the day diary or month calendar view in pane two 66b.
Following connector C to FIG. 10B, if the next day diary view requested in pane one 66a is not the same as the current day diary view on display in pane two 66b, then the pane one 66a day diary view is updated with the day diary view immediately following the day diary view currently on display in pane one 66a at block 364.
If the next day icon 84b has not been invoked in pane one 66a as determined at block 354, then a determination is made at block 366 whether the previous day icon 84a has been invoked in pane one 66a. If the previous day icon 84a has been invoked in pane one 66a, then connector E is followed to block 368 where the pane one 66a day diary view is updated with the day diary view immediately preceding the day diary view currently on display in pane one 66a. If the previous day icon 84a has not been invoked in pane one 66a as determined at block 366, then a determination is made at block 372 whether the next day icon 84b has been invoked in pane two 66b. Following connector G to FIG. IOC, if the next day icon 84b has been invoked in pane two 66b, then the pane two 66b day diary view is updated with the day diary view immediately following the month calendar view currently on display in pane two 66b at block 374.
If the next day icon 84b has not been invoked in pane two 66b as determined at block 372, then a determination is made at block 376 whether the previous day icon 84a has been invoked in pane two 66b. If the previous day icon 84a has been invoked in pane two 66b, then connector I is followed to block 378 where a determination is made whether the previous day diary view requested in pane two 66b is the same as the current day diary view on display in pane one 66a. To avoid confusing the user by displaying the same day diary view in both panes 66a and 66b, if the previous day diary view requested in pane two 66b is the same as the current day diary view on display in pane one 66a, then the pane two 66b day diary view is updated with the pane one 66a day diary view currently on display at block 382. The pane one 66a day diary view is then updated with the day diary view immediately preceding the day diary view currently on display in pane one 66a at block 384.
If the previous day diary view requested in pane two 66b is not the same as the current day diary view on display in pane one 66a, then the pane two 66b day diary view is updated with the day diary view immediately preceding the day diary view currently on display in pane two 66b by following connector J to block 386. If the previous day icon 84a has not been invoked in pane two 66b as determined at block 376, then connector K is followed to FIG. 10D where a determination is made at block 388 whether the month calendar icon 86 has been invoked in pane one 66a. If the month calendar icon 86 has been invoked in pane one 66a, then the day planner/scheduler program 60 transitions to state Ml, D2 72 at block 392 where the month calendar view is displayed in pane one 66b that corresponds with the day diary view previously in pane one 66a.
Finally, if the month calendar icon 86 has not been invoked in pane one 66a, connector L is followed to block 394 where a determination is made whether the month calendar icon 86 has been invoked in pane two 66b. If the month calendar icon 86 has been invoked in pane two 66b, then the day planner/scheduler program 60 transitions to state Dl, M2 74 at block 396 where the month calendar view is displayed in pane two 66a that corresponds with the day diary view previously in pane two 66b. The flow charts of FIGS. 7A - 7D, 8A - 8F, 9A - 9F, and 10A - 10D show the architecture, functionality, and operation of a possible implementation of the day planner/scheduler 60 software. In this regard, each block represents a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
Thus, the day planner/scheduler program 60 described herein provides an easy to use electronic day planner/calendar system. While the present invention is applicable to any size display, it is particularly useful in computing devices having small display screens because it conveys all information via two panes, which are oriented horizontal to one another in a preferred embodiment. It should be further understood that, as stated hereinbefore, the principles of the present invention may also be applicable to other applications. For example, the present invention could be applied to an e-mail application in which a message view and a message list view are defined. The message list view may provide a listing of all the e-mail messages in a particular mailbox by title, sender, or other criteria while the message view provides the text for a particular message. The various combinations of views could be displayed using two panes in a similar manner to the day planner/scheduler application discussed in the foregoing. In concluding the detailed description, it should be noted that many variations and modifications can be made to the preferred embodiment without substantially departing from the principles of the present invention. All such variations and modifications are intended to be included herein within the scope of the present invention, as set forth in the following claims.

Claims

ClaimsI claim:
1. A method of conveying information via a display screen, comprising the steps of: simultaneously providing first and second panes on the display screen; displaying a first object selected from the group consisting of a month calendar view and a day diary view in the first pane; displaying a second object selected from the group consisting of a month calendar view and a day diary view in the second pane; and displaying a third object selected from the group consisting of a month calendar view and a day diary view in the first pane while maintaining the second object in the second pane after displaying the first and second objects.
2. A method as recited in Claim ϊ , wherein the first object comprises the month calendar view for a first month, the second object comprises the month calendar view for a second month, and the first and second months are not consecutive months.
3. A method as recited in Claim 1 , wherein the first object comprises the month calendar view for a first month the second object comprises the month calendar view for a second month, and the first and second months are consecutive months.
4. A method as recited in Claim 1 , wherein the first object comprises the day diary view for a first day and the second object comprises the day diary view for a second day.
5. A method as recited in Claim 1 , wherein the first object comprises the day diary view for a first day and the second object comprises the month calendar view for a first month associated with the first day. WO 00/60514 PCTtUSOO/07187
6. A method as recited in Claim 1, wherein the month calendar view includes a day diary icon for displaying the day diary view associated with an identified day in the month, a previous month icon for displaying a month calendar view for the immediately preceding month, a next month icon for displaying a month calendar view for the immediately following month, and each day in the month calendar view comprises a day icon for displaying the day diary view associated with that day; and wherein the day diary view includes a month calendar icon for displaying the month calendar view associated with the day diary, a previous day icon for displaying a day diary view for the immediately preceding day, and a next day icon for displaying a day diary view for the immediately following day.
7. A method as recited in Claim 6, wherein the first object comprises the month calendar view for a first month and the displaying the third object step comprises the step of: displaying, responsive to an invocation of the day diary icon in the first pane, the day diary view for an indicated day of the first month in the first pane while maintaining the second object in the second pane.
8. A method as recited in Claim 6, wherein the second object comprises the month calendar view for a first month and the displaying the third object step comprises the step of: displaying, responsive to an invocation of one of the day icons in the second pane, the day diary view in the first pane while maintaining the second object in the second pane.
9. A method as recited in Claim 6, wherein the first object comprises the month calendar view for a first month and the displaying the third object step comprises the step of: displaying, responsive to an invocation of the next month icon in the first pane, the month calendar view for the month immediately following the first month in the first pane while maintaining the second object in the second pane.
10. A method as recited in Claim 6, wherein the first object comprises the month calendar view for a first month and the displaying the third object step comprises the step of: displaying, responsive to an invocation of the previous month icon in the first pane, the month calendar view for the month immediately preceding the first month in the first pane while maintaining the second object in the second pane.
11. A method as recited in Claim 6, wherein the first object comprises the day diary view for a first day and the displaying the third object step comprises the step of: displaying, responsive to an invocation of the month calendar icon in the first pane, the month calendar view in the first pane while maintaining the second object in the second pane.
12. A method as recited in Claim 6, wherein the first object comprises the day diary view for a first day and the displaying the third object step comprises the step of: displaying, responsive to an invocation of the next day icon in the first pane, the day diary view for the day immediately following the first day in the first pane while maintaining the second object in the second pane.
13. A method as recited in Claim 6, wherein the first object comprises the day diary view for a first day and the displaying the third object step comprises the step of: displaying, responsive to an invocation of the previous day icon in the first pane, the day diary view for the day immediately preceding the first day in the first pane while maintaining the second object in the second pane.
14. A method as recited in Claim 6, wherein the first object comprises the month calendar view for a first month and the second object comprises the day diary view for a first day and the displaying the third object step comprises the steps of: displaying, responsive to invocation of both the day diary icon in the first pane and one of the day icons from the month calendar view in the first pane, the day diary view for the day associated with the invoked day icon in the first pane while maintaining the second object in the second pane.
15. A method of conveying information via a display screen, comprising the steps of: simultaneously providing first and second panes on the display screen; displaying a first object selected from the group consisting of a month calendar view and a day diary view in the first pane; and displaying a second object selected from the group consisting of a month calendar view and a day diary view in the second pane; wherein the month calendar view includes a day diary icon for displaying the day diary view associated with an identified day in the month, a previous month icon for displaying a month calendar view for the immediately preceding month, a next month icon for displaying a month calendar view for the immediately following month, and each day in the month calendar view comprises a day icon for displaying the day diary view associated with that day; and wherein the day diary view includes a month calendar icon for displaying the month calendar view associated with the day diary, a previous day icon for displaying a day diary view for the immediately preceding day, and a next day icon for displaying a day diary view for the immediately following day.
16. A method as recited in Claim 15, wherein the first object comprises the day diary view for a first day and the second object comprises the month calendar view for a first month associated with the first day and further comprising the steps of: determining, responsive to an invocation of the previous day icon in the first pane, whether the day immediately preceding the first day is in a second month immediately preceding the first month; and displaying, responsive to determining that the day immediately preceding the first day is in the second month immediately preceding the first month, the month calendar view for the second month in the second pane and the day diary view for the day immediately preceding the first day in the first pane.
17. A method as recited in Claim 15, wherein the first object comprises the day diary view for a first day and the second object comprises the month calendar view for a first month associated with the first day and further comprising the steps of: determining, responsive to an invocation of the next day icon in the first pane, whether the day immediately following the first day is in a second month immediately following the first month; and displaying, responsive to determining that the day immediately following the first day is in the second month immediately following the first month, the month calendar view for the second month in the second pane and the day diary view for the day immediately following the first day in the first pane.
18. A method as recited in Claim 15, wherein the first and second panes are oriented horizontally on the display screen with the first pane being to the left of the second pane and further comprising the step of: ordering the first and second objects chronologically with the first object being contemporaneous with or preceding the second object in time.
19. A method as recited in Claim 18, wherein the first object comprises the month calendar view for a first month and the second object comprises the month calendar view for a second month and further comprising the steps of: determining, responsive to an invocation of the next month icon in the first pane, whether the month immediately following the first month is the second month; and displaying, responsive to determining that the month immediately following the first month is the second month, the month calendar view for the second month in the first pane and the month calendar view for a third month that immediately follows the second month in the second pane.
20. A method as recited in Claim 18, wherein the first object comprises the month calendar view for a first month and the second object comprises the month calendar view for a second month and further comprising the steps of: determining, responsive to an invocation of the previous month icon in the second pane, whether the month immediately preceding the second month is the first month; and displaying, responsive to determining that the month immediately preceding the second month is the first month, the month calendar view for the first month in the second pane and the month calendar view for a fourth month that immediately precedes the first month in the first pane.
21. A method as recited in Claim 18, wherein the first object comprises the day diary view for a first day and the second object comprises the day diary view for a second day and further comprising the steps of: determining, responsive to an invocation of the next day icon in the first pane, whether the day immediately following the first day is the second day; and displaying, responsive to determining that the day immediately following the first day is the second day, the day diary view for the second day in the first pane and the day diary view for a third day that immediately follows the second day in the second pane.
22. A method as recited in Claim 18, wherein the first object comprises the day diary view for a first day and the second object comprises the day diary view for a second day and further comprising the steps of: determining, responsive to an invocation of the previous day icon in the second pane, whether the day immediately preceding the second day is the first day; and displaying, responsive to determining that the day immediately preceding the second day is the first day, the day diary view for the first day in the second pane and the day diary view for a fourth day that immediately precedes the first day in the first pane.
23. A system for conveying information via a display screen, comprising: means for simultaneously providing first and second panes on the display screen; means for displaying a first object selected from the group consisting of a month calendar view and a day diary view in the first pane; means for displaying a second object selected from the group consisting of a month calendar view and a day diary view in the second pane; and means, responsive to the means for displaying a first object and the means for displaying a second object, for displaying a third object selected from the group consisting of a month calendar view and a day diary view in the first pane while maintaining the second object in the second pane.
24. A system as recited in Claim 23, wherein the first object comprises the month calendar view for a first month, the second object comprises the month calendar view for a second month, and the first and second months are not consecutive months.
25. A system as recited in Claim 23, wherein the first object comprises the month calendar view for a first month, the second object comprises the month calendar view for a second month, and the first and second months are consecutive months.
26. A system as recited in Claim 23, wherein the first object comprises the day diary view for a first day and the second object comprises the day diary view for a second day.
27. A system as recited in Claim 23, wherein the first object comprises the day diary view for a first day and the second object comprises the month calendar view for a first month associated with the first day.
28. A system as recited in Claim 23, wherein the month calendar view includes a day diary icon for displaying the day diary view associated with an identified day in the month, a previous month icon for displaying a month calendar view for the immediately preceding month, a next month icon for displaying a month calendar view for the immediately following month, and each day in the month calendar view comprises a day icon for displaying the day diary view associated with that day; and wherein the day diary view includes a month calendar icon for displaying the month calendar view associated with the day diary, a previous day icon for displaying a day diary view for the immediately preceding day, and a next day icon for displaying a day diary view for the immediately following day.
29. A system as recited in Claim 28, wherein the first object comprises the month calendar view for a first month and the means for displaying the third object comprises: means, responsive to an invocation of the day diary icon in the first pane, for displaying the day diary view for an indicated day of the first month in the first pane . while maintaining the second object in the second pane.
30. A system as recited in Claim 28, wherein the second object comprises the month calendar view for a first month and the means for displaying the third object comprises: means, responsive to an invocation of one of the day icons in the second pane, for displaying the day diary view in the first pane while maintaining the second object in the second pane.
31. A system as recited in Claim 28, wherein the first object comprises the month calendar view for a first month and the means for displaying the third object comprises: means, responsive to an invocation of the next month icon in the first pane, for displaying the month calendar view for the month immediately following the first month in the first pane while maintaining the second object in the second pane.
32. A system as recited in Claim 28, wherein the first object comprises the month calendar view for a first month and the means for displaying the third object comprises: means, responsive to an invocation of the previous month icon in the first pane, for displaying the month calendar view for the month immediately preceding the first month in the first pane while maintaining the second object in the second pane.
33. A system as recited in Claim 28, wherein the first object comprises the day diary view for a first day and the means for displaying the third object comprises: means, responsive to an invocation of the month calendar icon in the first pane, for displaying the month calendar view in the first pane while maintaining the second object in the second pane.
34. A system as recited in Claim 28, wherein the first object comprises the day diary view for a first day and the means for displaying the third object comprises: means, responsive to an invocation of the next day icon in the first pane, for displaying the day diary view for the day immediately following the first day in the first pane while maintaining the second object in the second pane.
35. A system as recited in Claim 28, wherein the first object comprises the day diary view for a first day and the means for displaying the third object comprises: means, responsive to an invocation of the previous day icon in the first pane, for displaying the day diary view for the day immediately preceding the first day in the first pane while maintaining the second object in the second pane.
36. A system as recited in Claim 28, wherein the first object comprises the month calendar view for a first month and the second object comprises the day diary view for a first day and the means for displaying the third object comprises: means, responsive to invocation of both the day diary icon in the first pane and one of the day icons from the month calendar view in the first pane, for displaying the day diary view for the day associated with the invoked day icon in the first pane while maintaining the second object in the second pane.
37. A system for conveying information via a display screen, comprising: means for simultaneously providing first and second panes on the display screen; means for displaying a first object selected from the group consisting of a month calendar view and a day diary view in the first pane; and means for displaying a second object selected from the group consisting of a month calendar view and a day diary view in the second pane; wherein the month calendar view includes a day diary icon for displaying the day diary view associated with an identified day in the month, a previous month icon for displaying a month calendar view for the immediately preceding month, a next month icon for displaying a month calendar view for the immediately following month, and each day in the month calendar view comprises a day icon for displaying the day diary view associated with that day; and wherein the day diary view includes a month calendar icon for displaying the month calendar view associated with the day diary, a previous day icon for displaying a day diary view for the immediately preceding day, and a next day icon for displaying a day diary view for the immediately following day.
38. A system as recited in Claim 37, wherein the first object comprises the day diary view for a first day and the second object comprises the month calendar view for a first month associated with the first day and further comprising: means, responsive to an invocation of the previous day icon in the first pane, for determining whether the day immediately preceding the first day is in a second month immediately preceding the first month; and means, responsive to determining that the day immediately preceding the first day is in the second month immediately preceding the first month, for displaying the month calendar view for the second month in the second pane and the day diary view for the day immediately preceding the first day in the first pane.
39. A system as recited in Claim 37, wherein the first object comprises the day diary view for a first day and the second object comprises the month calendar view for a first month associated with the first day and further comprising: means, responsive to an invocation of the next day icon in the first pane, for determining whether the day immediately following the first day is in a second month immediately following the first month; and means, responsive to determining that the day immediately following the first day is in the second month immediately following the first month, for displaying the month calendar view for the second month in the second pane and the day diary view for the day immediately following the first day in the first pane.
40. A system as recited in Claim 37, wherein the first and second panes are oriented horizontally on the display screen with the first pane being to the left of the second pane and further comprising: means for ordering the first and second objects chronologically with the first object being contemporaneous with or preceding the second object in time.
41. A system as recited in Claim 40, wherein the first object comprises the month calendar view for a first month and the second object comprises the month calendar view for a second month and further comprising: means, responsive to an invocation of the next month icon in the first pane, for determining whether the month immediately following the first month is the second month; and means, responsive to determining that the month immediately following the first month is the second month, for displaying the month calendar view for the second month in the first pane and the month calendar view for a third month that immediately follows the second month in the second pane.
42. A system as recited in Claim 40, wherein the first object comprises the month calendar view for a first month and the second object comprises the month calendar view for a second month and further comprising: means, responsive to an invocation of the previous month icon in the second pane, for determining whether the month immediately preceding the second month is the first month; and means, responsive to determining that the month immediately preceding the second month is the first month, for displaying the month calendar view for the first month in the second pane and the month calendar view for a fourth month that immediately precedes the first month in the first pane.
43. A system as recited in Claim 40, wherein the first object comprises the day diary view for a first day and the second object comprises the day diary view for a second day and further comprising: means, responsive to an invocation of the next day icon in the first pane, for determining whether the day immediately following the first day is the second day; and means, responsive to determining that the day immediately following the first day is the second day, for displaying the day diary view for the second day in the first pane and the day diary view for a third day that immediately follows the second day in the second pane.
44. A system as recited in Claim 40, wherein the first object comprises the day diary view for a first day and the second object comprises the day diary view for a second day and further comprising: means, responsive to an invocation of the previous day icon in the second pane, for determining whether the day immediately preceding the second day is the first day; and means, responsive to determining that the day immediately preceding the second day is the first day, for displaying the day diary view for the first day in the second pane and the day diary view for a fourth day that immediately precedes the first day in the first pane.
45. A computer program product for conveying information via a display screen, comprising: a computer readable storage medium having computer readable program code means embodied therein, the computer readable program code means comprising: computer readable program code means for simultaneously providing first and second panes on the display screen; computer readable program code means for displaying a first object selected from the group consisting of a month calendar view and a day diary view in the first pane; computer readable program code means for displaying a second object selected from the group consisting of a month calendar view and a day diary view in the second pane; and computer readable program code means, responsive to the computer readable program code means for displaying a first object and the computer readable program code means for displaying a second object, for displaying a third object selected from the group consisting of a month calendar view and a day diary view in the first pane while maintaining the second object in the second pane.
46. A computer program product as recited in Claim 45, wherein the first object comprises the month calendar view for a first month, the second object comprises the month calendar view for a second month, and the first and second months are not consecutive months.
47. A computer program product as recited in Claim 45, wherein the first object comprises the month calendar view for a first month, the second object comprises the month calendar view for a second month, and the first and second months are consecutive months.
48. A computer program product as recited in Claim 45, wherein the first object comprises the day diary view for a first day and the second object comprises the day diary view for a second day.
49. A computer program product as recited in Claim 45, wherein the first object comprises the day diary view for a first day and the second object comprises the month calendar view for a first month associated with the first day.
50. A computer program product as recited in Claim 45, wherein the month calendar view includes a day diary icon for displaying the day diary view associated with an identified day in the month, a previous month icon for displaying a month calendar view for the immediately preceding month, a next month icon for displaying a month calendar view for the immediately following month, and each day in the month calendar view comprises a day icon for displaying the day diary view associated with that day; and wherein the day diary view includes a month calendar icon for displaying the month calendar view associated with the day diary, a previous day icon for displaying a day diary view for the immediately preceding day, and a next day icon for displaying a day diary view for the immediately following day.
51. A computer program product as recited in Claim 50, wherein the first object comprises the month calendar view for a first month and the computer readable program code means for displaying the third object comprises: computer readable program code means, responsive to an invocation of the day diary icon in the first pane, for displaying the day diary view for an indicated day of the first month in the first pane while maintaining the second object in the second pane.
52. A computer program product as recited in Claim 50, wherein the second object comprises the month calendar view for a first month and the computer readable program code means for displaying the third object comprises: computer readable program code means, responsive to an invocation of one of the day icons in the second pane, for displaying the day diary view in the first pane while maintaining the second object in the second pane.
53. A computer program product as recited in Claim 50, wherein the first object comprises the month calendar view for a first month and the computer readable program code means for displaying the third object comprises: computer readable program code means, responsive to an invocation of the next month icon in the first pane, for displaying the month calendar view for the month immediately following the first month in the first pane while maintaining the second object in the second pane.
54. A computer program product as recited in Claim 50, wherein the first object comprises the month calendar view for a first month and the computer readable program code means for displaying the third object comprises: computer readable program code means, responsive to an invocation of the previous month icon in the first pane, for displaying the month calendar view for the month immediately preceding the first month in the first pane while maintaining the second object in the second pane.
55. A computer program product as recited in Claim 50, wherein the first object comprises the day diary view for a first day and the computer readable program code means for displaying the third object comprises: computer readable program code means, responsive to an invocation of the month calendar icon in the first pane, for displaying the month calendar view in the first pane while maintaining the second object in the second pane.
56. A computer program product as recited in Claim 50, wherein the first object comprises the day diary view for a first day and the computer readable program code means for displaying the third object comprises: computer readable program code means, responsive to an invocation of the next day icon in the first pane, for displaying the day diary view for the day immediately following the first day in the first pane while maintaining the second object in the second pane.
57. A computer program product as recited in Claim 50, wherein the first object comprises the day diary view for a first day and the computer readable program code means for displaying the third object comprises: computer readable program code means, responsive to an invocation of the previous day icon in the first pane, for displaying the day diary view for the day immediately preceding the first day in the first pane while maintaining the second object in the second pane.
58. A computer program product as recited in Claim 50, wherein the first object comprises the month calendar view for a first month and the second object comprises the day diary view for a first day and the computer readable program code means for displaying the third object comprises: computer readable program code means, responsive to invocation of both the day diary icon in the first pane and one of the day icons from the month calendar view in the first pane, for displaying the day diary view for the day associated with the invoked day icon in the first pane while maintaining the second object in the second pane.
59. A computer program product for conveying information via a display screen, comprising: a computer readable storage medium having computer readable program code means embodied therein, the computer readable program code means comprising: computer readable program code means for simultaneously providing first and second panes on the display screen; computer readable program code means for displaying a first object selected from the group consisting of a month calendar view and a day diary view in the first pane; and computer readable program code means for displaying a second object selected from the group consisting of a month calendar view and a day diary view in the second pane; wherein the month calendar view includes a day diary icon for displaying the day diary view associated with an identified day in the month, a previous month icon for displaying a month calendar view for the immediately preceding month, a next month icon for displaying a month calendar view for the immediately following month, and each day in the month calendar view comprises a day icon for displaying the day diary view associated with that day; and wherein the day diary view includes a month calendar icon for displaying the month calendar view associated with the day diary, a previous day icon for displaying a day diary view for the immediately preceding day, and a next day icon for displaying a day diary view for the immediately following day.
60. A computer program product as recited in Claim 59, wherein the first object comprises the day diary view for a first day and the second object comprises the month calendar view for a first month associated with the first day and further comprising: computer readable program code means, responsive to an invocation of the previous day icon in the first pane, for determining whether the day immediately preceding the first day is in a second month immediately preceding the first month; and computer readable program code means, responsive to determining that the day immediately preceding the first day is in the second month immediately preceding the first month, for displaying the month calendar view for the second month in the second pane and the day diary view for the day immediately preceding the first day in the first pane.
61. A computer program product as recited in Claim 59, wherein the first object comprises the day diary view for a first day and the second object comprises the month calendar view for a first month associated with the first day and further comprising: computer readable program code means, responsive to an invocation of the next day icon in the first pane, for determining whether the day immediately following the first day is in a second month immediately following the first month; and computer readable program code means, responsive to determining that the day immediately following the first day is in the second month immediately following the first month, for displaying the month calendar view for the second month in the second pane and the day diary view for the day immediately following the first day in the first pane.
62. A computer program product as recited in Claim 59, wherein the first and second panes are oriented horizontally on the display screen with the first pane being to the left of the second pane and further comprising: computer readable program code means for ordering the first and second objects chronologically with the first object being contemporaneous with or preceding the second object in time.
63. A computer program product as recited in Claim 62, wherein the first object comprises the month calendar view for a first month and the second object comprises the month calendar view for a second month and further comprising: computer readable program code means, responsive to an invocation of the next month icon in the first pane, for determining whether the month immediately following the first month is the second month; and computer readable program code means, responsive to determining that the month immediately following the first month is the second month, for displaying the month calendar view for the second month in the first pane and the month calendar view for a third month that immediately follows the second month in the second pane.
64. A computer program product as recited in Claim 62, wherein the first object comprises the month calendar view for a first month and the second object comprises the month calendar view for a second month and further comprising: computer readable program code means, responsive to an invocation of the previous month icon in the second pane, for determining whether the month immediately preceding the second month is the first month; and computer readable program code means, responsive to determining that the month immediately preceding the second month is the first month, for displaying the month calendar view for the first month in the second pane and the month calendar view for a fourth month that immediately precedes the first month in the first pane.
65. A computer program product as recited in Claim 62, wherein the first object comprises the day diary view for a first day and the second object comprises the day diary view for a second day and further comprising: computer readable program code means, responsive to an invocation of the next day icon in the first pane, for determining whether the day immediately following the first day is the second day; and computer readable program code means, responsive to determining that the day immediately following the first day is the second day, for displaying the day diary view for the second day in the first pane and the day diary view for a third day that immediately follows the second day in the second pane.
66. A computer program product as recited in Claim 62, wherein the first object comprises the day diary view for a first day and the second object comprises the day diary view for a second day and further comprising: computer readable program code means, responsive to an invocation of the previous day icon in the second pane, for determining whether the day immediately preceding the second day is the first day; and computer readable program code means, responsive to determining that the day immediately preceding the second day is the first day, for displaying the day diary view for the first day in the second pane and the day diary view for a fourth day that immediately precedes the first day in the first pane.
PCT/US2000/007187 1999-04-05 2000-03-17 Methods, systems, and computer program products for conveying information through a multiple pane display WO2000060514A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU38974/00A AU3897400A (en) 1999-04-05 2000-03-17 Methods, systems, and computer program products for conveying information through a multiple pane display

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US28627999A 1999-04-05 1999-04-05
US09/286,279 1999-04-05

Publications (3)

Publication Number Publication Date
WO2000060514A1 true WO2000060514A1 (en) 2000-10-12
WO2000060514A8 WO2000060514A8 (en) 2001-03-01
WO2000060514A9 WO2000060514A9 (en) 2001-11-29

Family

ID=23097880

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2000/007187 WO2000060514A1 (en) 1999-04-05 2000-03-17 Methods, systems, and computer program products for conveying information through a multiple pane display

Country Status (2)

Country Link
AU (1) AU3897400A (en)
WO (1) WO2000060514A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8069417B2 (en) 2006-09-29 2011-11-29 Microsoft Corporation Bifocal view: a novel calendar user interface

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5855006A (en) * 1996-03-01 1998-12-29 Humware Personal activity scheduling apparatus

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5855006A (en) * 1996-03-01 1998-12-29 Humware Personal activity scheduling apparatus

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"DAILY AND MONTHLY ICONS ON A WEEKLY CALENDAR", RESEARCH DISCLOSURE,GB,INDUSTRIAL OPPORTUNITIES LTD. HAVANT, no. 345, 1993, pages 24, XP000336479, ISSN: 0374-4353 *
"METHOD FOR 3-DIMENSIONAL SCROLLING", IBM TECHNICAL DISCLOSURE BULLETIN,US,IBM CORP. NEW YORK, vol. 32, no. 8A, 1990, pages 364 - 368, XP000082839, ISSN: 0018-8689 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8069417B2 (en) 2006-09-29 2011-11-29 Microsoft Corporation Bifocal view: a novel calendar user interface

Also Published As

Publication number Publication date
AU3897400A (en) 2000-10-23
WO2000060514A8 (en) 2001-03-01
WO2000060514A9 (en) 2001-11-29

Similar Documents

Publication Publication Date Title
US20210240335A1 (en) Terminal and method for hiding and restoring message
US11003316B2 (en) Dynamic bar oriented user interface
KR101634834B1 (en) Providing selected data through a locked display
US9141218B2 (en) Electronic device and control method thereof
US6462760B1 (en) User interfaces, methods, and computer program products that can conserve space on a computer display screen by associating an icon with a plurality of operations
US7447989B2 (en) Method and system for setting document-linked timed reminders
US8250491B2 (en) Navigation history
US8583090B2 (en) Transferring task completion to another device
US6750850B2 (en) Viewer system for a wireless device
US6496835B2 (en) Methods for mapping data fields from one data set to another in a data processing environment
US20030154207A1 (en) Information processing system
US20100070910A1 (en) Data-Oriented User Interface for Mobile Device
US20040113928A1 (en) Information processing device, information processing method, information processing program, and storage medium having the information processing program
US20150121279A1 (en) Methods and apparatus for a touchscreen user interface
US20030013483A1 (en) User interface for handheld communication device
US20080059881A1 (en) Method and Device for Presenting Calendar Views on Small Displays
KR20020060082A (en) Method of stroing data in a personal information terminal
Björk et al. POWERVIEW Using information links and information views to navigate and visualize information on small displays
WO2000060514A1 (en) Methods, systems, and computer program products for conveying information through a multiple pane display
US20090110173A1 (en) One touch connect for calendar appointments
EP2204728A2 (en) Information product and method for interacting with user
WO2007118228A2 (en) Method for importing, processing and displaying data in spreadsheets
KR20040045771A (en) Portable communication terminal having schedule manager furction for peculiar date recording into a address record and a method operating thereof
Cheng et al. Managing the Mobile Inbox with MoMail
EP2057530A1 (en) Method and device for presenting calendar views on small displays

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AL AM AT AT AU AZ BA BB BG BR BY CA CH CN CU CZ CZ DE DE DK DK EE EE ES FI FI GB GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SK SL TJ TM TR TT UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
AK Designated states

Kind code of ref document: C1

Designated state(s): AE AG AL AM AT AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ CZ DE DE DK DK DM DZ EE EE ES FI FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SK SL TJ TM TR TT UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: C1

Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

CFP Corrected version of a pamphlet front page
CR1 Correction of entry in section i

Free format text: PAT. BUL. 41/2000 UNDER (81) ADD "AG, CR, DM, DZ, GD, MA"; DUE TO LATE TRANSMITTAL BY THE RECEIVINGOFFICE

AK Designated states

Kind code of ref document: C2

Designated state(s): AE AG AL AM AT AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ CZ DE DE DK DK DM DZ EE EE ES FI FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SK SL TJ TM TR TT UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: C2

Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

COP Corrected version of pamphlet

Free format text: PAGES 1/26-26/26, DRAWINGS, REPLACED BY NEW PAGES 1/26-26/26; DUE TO LATE TRANSMITTAL BY THE RECEIVING OFFICE

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase