US20150370440A1 - Managing event on calendar with timeline - Google Patents
Managing event on calendar with timeline Download PDFInfo
- Publication number
- US20150370440A1 US20150370440A1 US14/518,425 US201414518425A US2015370440A1 US 20150370440 A1 US20150370440 A1 US 20150370440A1 US 201414518425 A US201414518425 A US 201414518425A US 2015370440 A1 US2015370440 A1 US 2015370440A1
- Authority
- US
- United States
- Prior art keywords
- event
- timeline
- calendar
- date
- displayed
- Prior art date
- Legal status (The legal status 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 status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input 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/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0481—Interaction 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
- G06F3/0482—Interaction with lists of selectable items, e.g. menus
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/903—Querying
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/953—Querying, e.g. by the use of web search engines
- G06F16/9535—Search customisation based on user profiles and personalisation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input 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/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
- G06F3/04842—Selection of displayed objects or displayed text elements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input 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/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
- G06F3/04847—Interaction techniques to control parameter settings, e.g. interaction with sliders or dials
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input 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/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
- G06F3/0485—Scrolling or panning
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input 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/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
- G06F3/0485—Scrolling or panning
- G06F3/04855—Interaction with scrollbars
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input 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/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
- G06F3/0486—Drag-and-drop
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input 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/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0487—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
- G06F3/0488—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures
- G06F3/04883—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures for inputting data by handwriting, e.g. gesture or text
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
- G06Q10/1093—Calendar-based scheduling for persons or groups
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/07—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
- H04L51/08—Annexed information, e.g. attachments
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Definitions
- Legacy calendar views in scheduling applications provide limited information. Alternatively, the legacy calendar views in scheduling applications provide excessive information. Legacy calendar views are usually used in detailed configurations for daily and weekly actions. However, users are underserved in long term synapsis of associated actions in legacy calendar views. Addition of actions and other items into legacy calendar views prove challenging for long term synapsis of associated actions.
- Embodiments are directed to managing an event on a calendar with a timeline.
- a calendar application may display a first context menu that includes a create control on the calendar, in response to a first selection action of the event displayed on the calendar.
- the event may be presented on the timeline, in response to an activation of the create control.
- a second context menu, that includes a delete control may be displayed on the timeline, in response to a second selection action of the event displayed on the timeline.
- the event may be removed from the timeline, in response to an activation of the delete control.
- FIG. 1 is a conceptual diagram illustrating an example of managing an event on a calendar with a timeline, according to embodiments
- FIG. 2 illustrates an example of a create action to create an event within a timeline, according to embodiments
- FIG. 3 illustrates an example of a removal action to delete an event from a timeline, according to embodiments
- FIG. 4 illustrates an example of a drag and drop action to copy an event on a calendar into the timeline, according to embodiments
- FIG. 5 illustrates an example of a touch and drag action to change a date and time of an event on a calendar, according to embodiments
- FIG. 6 illustrates an example of a hover action to display a tooltip below the timeline, according to embodiments
- FIG. 7 illustrates an example of an event peek associated with an event displayed on the timeline, according to embodiments
- FIG. 8 illustrates an example of managing events that conflict on a timeline, according to embodiments
- FIG. 9 is a simplified networked environment, where a system according to embodiments may be implemented.
- FIG. 10 illustrates a general purpose computing device, which may be configured to manage an event on a calendar with a timeline
- FIG. 11 illustrates a logic flow diagram for a process to manage an event on a calendar with a timeline, according to embodiments.
- an event on a calendar with a timeline may be managed by a calendar application.
- a first context menu that includes a create control may be displayed on the calendar, in response to a first selection action of the event displayed on the calendar.
- the event may be presented on the timeline, in response to an activation of the create control.
- a second context menu, that includes a delete control may be displayed on the timeline, in response to a second selection action of the event displayed on the timeline.
- the event may be removed from the timeline, in response to an activation of the delete control.
- program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types.
- embodiments may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and comparable computing devices.
- Embodiments may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network.
- program modules may be located in both local and remote memory storage devices.
- Embodiments may be implemented as a computer-implemented process (method), a computing system, or as an article of manufacture, such as a computer program product or computer readable media.
- the computer program product may be a computer storage medium readable by a computer system and encoding a computer program that comprises instructions for causing a computer or computing system to perform example process(es).
- the computer-readable storage medium is a computer-readable memory device.
- the computer-readable memory device includes a hardware device that includes a hard disk drive, a solid state drive, a compact disk, a memory chip, among others.
- the computer-readable storage medium can for example be implemented via one or more of a volatile computer memory, a non-volatile memory, a hard drive, and a flash drive.
- platform may be a combination of software and hardware components to manage an event on a calendar with a timeline.
- platforms include, but are not limited to, a hosted service executed over a plurality of servers, an application executed on a single computing device, and comparable systems.
- server generally refers to a computing device executing one or more software programs typically in a networked environment. However, a server may also be implemented as a virtual server (software programs) executed on one or more computing devices viewed as a server on the network. More detail on these technologies and example embodiments may be found in the following description.
- FIG. 1 is a conceptual diagram illustrating an example of managing an event on a calendar with a timeline, according to embodiments.
- a computing device 104 may execute a calendar application 102 .
- the computing device may include a tablet device, a laptop computer, a desktop computer, a smart phone, among others.
- the computing device 104 may display the calendar application 102 to a user 106 .
- the user 106 may be allowed to interact with the calendar application 102 through an input device or touch enabled display component of the computing device 104 .
- the user 106 may interact with the calendar application 102 with a keyboard based input, a mouse based input, a voice based input, a pen based input, a gesture based input, among others.
- the gesture based input may include one or more touch based actions such as a touch action, a swipe action, a combination of each, among others.
- the calendar application 102 may include a timeline 120 as a component placed adjacent to and below a calendar.
- the timeline 120 may include a linear presentation of events during a time period divided based on a time unit such as a day. Events presented on the timeline may be duplicates of the events on the calendar displayed by the calendar application 102 .
- a user 106 may be allowed to interact with the calendar and the timeline 120 to manage an event. The event may be displayed on the calendar and duplicated on the timeline 120 .
- FIG. 1 has been described with specific components including the computing device 104 , the calendar application 102 , the timeline 120 , embodiments are not limited to these components or system configurations and can be implemented with other system configuration employing fewer or additional components.
- FIG. 2 illustrates an example of a create action to create an event within a timeline, according to embodiments.
- a calendar application 202 that displays a calendar 226 and a timeline 220 used to create an event may be described.
- the calendar application 202 may display a context menu 216 on the calendar 226 in response to a selection action on an event 214 .
- the selection action may include a click event associated with a mouse input, a tap action associated with a touch based input, among others.
- the context menu 216 may be displayed in proximity to the event 214 , adjacent to the event 214 or superimposed on the event 214 .
- the calendar application 202 may display one or more controls on the context menu 216 .
- One of the controls may include a create control 218 to create the event on the timeline 220 .
- the event 214 may be copied to the timeline on a date of the event.
- the timeline may be scrolled to a date range that includes the date of the event.
- the event may be displayed on the date of the event on the timeline 220 .
- the calendar application 202 may also display additional controls associated with the calendar 226 .
- the date picker component 204 may allow a user to select a date from a displayed range.
- the selected date may be displayed in the calendar 226 that shows the date within a date range that is configurable.
- the date range of the calendar 226 may include a day, a week, a month, a year, among others.
- a current date range may be illustrated with a date range label 208 .
- the date range may also be partitioned vertically based on a time unit such as a day 210 .
- the time units may be scrollable.
- the calendar 226 may also be partitioned horizontally based on an hour based unit 212 .
- the hour based units may be scrollable.
- An “all day” unit may persist on a top section of the calendar 226 to show one or more events that last during a time unit such as a day.
- the calendar 226 may be selectable through a calendar selection control 206 .
- the calendar application 202 may display one or more calendars that may be selectable through the calendar selection control 206 and other calendar selection controls displayed adjacent to the calendar selection control 206 .
- the timeline 220 may display a linear presentation of events on the calendar 226 .
- the timeline 220 may display a date range of events that may be scrollable through a scroll control 224 .
- the date range may be presented with a date range label 222 .
- the date range may be partitioned based on time units such as an hour, a day 228 , a week, a month, a year, among others.
- the date range may be selectable based on a selection of the range by a user through a range selection control such as “weekly,” among others.
- the event 214 on the calendar 226 may be duplicated on the timeline 220 using the create control 218 or through another operation to copy the event 214 to the timeline 220 .
- FIG. 3 illustrates an example of a removal action to delete an event from a timeline, according to embodiments.
- a calendar application 302 may display a context menu superimposed on the event 304 , in response to a selection action detected on the event 304 .
- the selection action may include a click event associated with a mouse input, a tap action associated with a touch based input, among others.
- the context menu 306 may also be displayed adjacent to or in proximity to the event 304 displayed on the timeline 320 .
- a distance between the event 304 and the context menu 306 may be determined based on an application attribute or dynamically based on other components of the calendar application 302 , when displaying the context menu 306 in proximity to the event 304 .
- the event 304 may also be a duplication of the event 314 .
- the event 304 may be displayed on a date of the timeline 320 that corresponds to an event date of the event 314 .
- the context menu 306 may provide one or more controls to manage the event 304 displayed on the timeline 320 .
- the context menu 306 may include a delete control 308 to remove the event from the timeline 320 .
- the event 304 may be removed from the timeline 320 .
- the delete control 308 may not remove the event 314 from the calendar.
- An additional operation may be initiated by a user to remove the event 314 from the calendar.
- An example may include a selection action of the event 314 to display a new context menu on the calendar.
- Another delete control on the new context menu may be activated to remove the event 314 from the calendar.
- FIG. 4 illustrates an example of a drag and drop action to copy an event on a calendar into the timeline, according to embodiments.
- a drag and drop action on an event 414 may be detected by the calendar application 402 .
- the drag and drop action may include a click and hold event by a mouse input, a tap and hold event by a touch based action, among others on the event 414 .
- the calendar application 402 may detect a direction of the drag and drop action.
- a message 404 may be overlaid on the timeline 420 to guide the drag and drop action to conclude on the timeline.
- the timeline may also be minimized during the drag and drop action.
- the timeline may be restored to an original size prior to a minimization operation.
- a message to guide the drag and drop action to conclude on the timeline 420 may be displayed on the timeline 420 .
- an event 406 may be detected as dropped on the timeline.
- the event 406 may be a copy of the event 414 in transit from the calendar to the timeline 420 during the drag and drop action.
- the timeline 420 may be scrolled to a display a time period that includes a date of the event 414 .
- the event 406 may be placed on a date on the timeline that corresponds to the date of the event 414 .
- FIG. 5 illustrates an example of a touch and drag action to change a date and time of an event on a calendar, according to embodiments.
- a calendar application 502 may detect a touch and drag action to change a date and a time of an event 514 .
- a touch and drag action may start with a tap and hold action 512 on an event 514 .
- the touch and drag action may be detected to conclude at a new date and a new time in response to a drop action 518 .
- An event 516 may be placed at the new date and new time based on detecting a location of the drop action 518 that corresponds to the new date and new time on the calendar.
- the event 514 may be removed from the calendar.
- the event 516 may be displayed on the new date and new time.
- An event 504 may also be moved in response to the touch and drag action on the event 514 .
- the event 504 may be a duplicate of the event 514 , on the timeline 520 .
- the event 504 may be moved to a new date that corresponds to the date of event 516 , on the timeline 520 .
- the event 504 may be removed from an original date.
- the event 504 may be placed on the new date on the timeline 520 that corresponds to the date of the event 516 .
- FIG. 6 illustrates an example of a hover action to display a tooltip below the timeline, according to embodiments.
- a hover action 602 may be detected on a section of a timeline 620 .
- a tooltip 606 may be displayed below the section.
- the tooltip 606 may display a date associated with the section.
- the calendar application may also display an event 604 within the section where the hover action may be detected.
- the hover action 602 may be detected as a result of a mouse input or touch based input, among others.
- FIG. 7 illustrates an example of an event peek associated with an event displayed on the timeline, according to embodiments.
- a calendar application 702 may display an event peek 706 in response to a selection action on an event 704 displayed on a timeline 720 .
- the selection action may be a hover action detected on the event 704 .
- the hover action may be provided through a mouse input, through a touch based input, among others.
- the event 704 may be a duplicate of an event 714 displayed on a calendar.
- the event peek 706 may display attributes associated with the event 704 .
- the attributes may include an event subject, an event title, a date of the event, a time of the event, a creation timestamp, a summary of the event, among others.
- One or more controls, that includes an edit control 708 may also be provided through the event peek 706 to edit the event 704 .
- the event peek 706 may be displayed by the calendar application 702 in a persistent mode and a user may be allowed to edit the attributes of the event 704 on the event peek 706 .
- a cancel control may also be provided to stop editing the attributes of the event 704 and undo any edits that were not saved.
- the edits of the attributes may be saved on the event 704 .
- the edits of the attributes may also be saved on an event 714 on the calendar because the event 704 is a duplicate of the event 714 .
- FIG. 8 illustrates an example of managing events that conflict on a timeline, according to embodiments.
- a calendar application may detect a conflict between events when more than one event is added to a timeline 820 while overlapping a timeslot of the timeline 820 .
- a new event such as an event 804 may be placed above existing events such as an event 806 and an event 808 to resolve the conflict.
- number of events overlapping a timeslot may lead to exceeding a vertical height of the timeline 820 while stacking the events.
- the calendar application may detect the events ( 804 , 806 , and 808 ) on a date of the timeline 820 to exceed the vertical height of the timeline. As a result, part of the events ( 804 , 806 , and 808 ) may be hidden from view. To provide access to the events ( 804 , 806 , and 808 ) the calendar application may increase the vertical height of the timeline to encompass the events ( 804 , 806 , and 808 ). The calendar application may also detect the events ( 804 , 806 , and 808 ) exceeding a vertical height threshold of the timeline 820 .
- the vertical height threshold may be configured by a user or a device setting such as available screen estate.
- a vertical scroll control 810 may be presented on a vertical edge of the timeline 820 , such as a right edge or a left edge, to allow for scrolling through the events ( 804 , 806 , and 808 ), in response to detecting the events ( 804 , 806 , and 808 ) exceeding the vertical height threshold of the timeline 820 .
- an insertion action may be detected on the timeline 820 to insert an initial deadline on a date of the timeline.
- the initial deadline may be displayed on the date.
- Another insertion action may also be detected to insert a second deadline on the date of the initial deadline.
- the second deadline may be displayed on the date.
- a label of the second deadline may be superimposed on a label of the initial deadline.
- the technical advantage of managing an event on a calendar with a timeline may be improved usability and enhanced reliability of display devices in providing event creation, editing, management, and display, among other features compared to static event presentation based solutions.
- FIG. 1 through 8 are shown with specific components, data types, and configurations. Embodiments are not limited to systems according to these example configurations. Managing an event on a calendar with a timeline may be implemented in configurations employing fewer or additional components in applications and user interfaces. Furthermore, the example schema and components shown in FIG. 1 through 8 and their subcomponents may be implemented in a similar manner with other values using the principles described herein.
- FIG. 9 is an example networked environment, where embodiments may be implemented.
- a calendar application configured to manage an event on a calendar with a timeline may be implemented via software executed over one or more servers 914 such as a hosted service.
- the platform may communicate with client applications on individual computing devices such as a smart phone 913 , a laptop computer 912 , or desktop computer 911 (‘client devices’) through network(s) 910 .
- client devices desktop computer 911
- Client applications executed on any of the client devices 911 - 913 may facilitate communications via application(s) executed by servers 914 , or on individual server 916 .
- a calendar application may display a context menu that includes a create control on an event of the calendar. The event may be presented on the timeline in response to an activation of the create control.
- the calendar application may store data associated with the timeline in data store(s) 919 directly or through database server 918 .
- Network(s) 910 may comprise any topology of servers, clients, Internet service providers, and communication media.
- a system according to embodiments may have a static or dynamic topology.
- Network(s) 910 may include secure networks such as an enterprise network, an unsecure network such as a wireless open network, or the Internet.
- Network(s) 910 may also coordinate communication over other networks such as Public Switched Telephone Network (PSTN) or cellular networks.
- PSTN Public Switched Telephone Network
- network(s) 910 may include short range wireless networks such as Bluetooth or similar ones.
- Network(s) 910 provide communication between the nodes described herein.
- network(s) 910 may include wireless media such as acoustic, RF, infrared and other wireless media.
- FIG. 10 illustrates a general purpose computing device, which may be configured to manage an event on a calendar with a timeline, arranged in accordance with at least some embodiments described herein.
- the computing device 1000 may be used to manage an event on a calendar with a timeline.
- the computing device 1000 may include one or more processors 1004 and a system memory 1006 .
- a memory bus 1008 may be used for communication between the processor 1004 and the system memory 1006 .
- the basic configuration 1002 may be illustrated in FIG. 10 by those components within the inner dashed line.
- the processor 1004 may be of any type, including, but not limited to, a microprocessor ( ⁇ P), a microcontroller ( ⁇ C), a digital signal processor (DSP), or any combination thereof.
- the processor 1004 may include one more levels of caching, such as a level cache memory 1012 , a processor core 1014 , and registers 1016 .
- the processor core 1014 may include an arithmetic logic unit (ALU), a floating point unit (FPU), a digital signal processing core (DSP Core), or any combination thereof.
- a memory controller 1018 may also be used with the processor 1004 , or in some implementations, the memory controller 1018 may be an internal part of the processor 1004 .
- the system memory 1006 may be of any type including but not limited to volatile memory (such as RAM), non-volatile memory (such as ROM, flash memory, etc.), or any combination thereof.
- the system memory 1006 may include an operating system 1020 , a calendar application 1022 , and a program data 1024 .
- the calendar application 1022 may display a context menu that includes a create control on an event of the calendar. The event may be presented on the timeline in response to an activation of the create control.
- Components of the calendar application 1022 (such as a user interface) may also be displayed on a display device associated with the computing device 1000 .
- An example of the display device may include a hardware screen that may be communicatively coupled to the computing device 1000 .
- the display device may include a touch based device that detects gestures such as a touch action.
- the display device may also provide feedback in response to detected gestures (or any other form of input) by transforming one or more user interfaces of the calendar application 1022 such as the timeline, displayed by the touch based device.
- the program data 1024 may include, among other data, a timeline data 1028 , or the like, as described herein.
- the timeline data 1028 may include the event, subject name of the event, the event date, among others.
- the computing device 1000 may have additional features or functionality, and additional interfaces to facilitate communications between the basic configuration 1002 and any desired devices and interfaces.
- a bus/interface controller 1030 may be used to facilitate communications between the basic configuration 1002 and one or more data storage devices 1032 via a storage interface bus 1034 .
- the data storage devices 1032 may be one or more removable storage devices 1036 , one or more non-removable storage devices 1038 , or a combination thereof.
- Examples of the removable storage and the non-removable storage devices may include magnetic disk devices, such as flexible disk drives and hard-disk drives (HDD), optical disk drives such as compact disk (CD) drives or digital versatile disk (DVD) drives, solid state drives (SSD), and tape drives, to name a few.
- Example computer storage media may include volatile and nonvolatile, removable, and non-removable media implemented in any method or technology for storage of information, such as computer-readable instructions, data structures, program modules, or other data.
- the system memory 1006 , the removable storage devices 1036 , and the non-removable storage devices 1038 may be examples of computer storage media.
- Computer storage media may include, but may not be limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD), solid state drives, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which may be used to store the desired information and which may be accessed by the computing device 1000 . Any such computer storage media may be part of the computing device 1000 .
- the computing device 1000 may also include an interface bus 1040 for facilitating communication from various interface devices (for example, one or more output devices 1042 , one or more peripheral interfaces 1044 , and one or more communication devices 1066 ) to the basic configuration 1002 via the bus/interface controller 1030 .
- interface devices for example, one or more output devices 1042 , one or more peripheral interfaces 1044 , and one or more communication devices 1066 .
- Some of the example output devices 1042 may include a graphics processing unit 1048 and an audio processing unit 1050 , which may be configured to communicate to various external devices, such as a display or speakers via one or more A/V ports 1052 .
- One or more example peripheral interfaces 1044 may include a serial interface controller 1054 or a parallel interface controller 1056 , which may be configured to communicate with external devices, such as input devices (for example, keyboard, mouse, pen, voice input device, touch input device, etc.) or other peripheral devices (for example, printer, scanner, etc.) via one or more I/O ports 1058 .
- An example communication device 1066 may include a network controller 1060 , which may be arranged to facilitate communications with one or more other computing devices 1062 over a network communication link via one or more communication ports 1064 .
- the one or more other computing devices 1062 may include servers, client equipment, and comparable devices.
- the network communication link may be one example of a communication media.
- Communication media may be embodied by computer-readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and may include any information delivery media.
- a “modulated data signal” may be a signal that has one or more of the modulated data signal characteristics set or changed in such a manner as to encode information in the signal.
- communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), microwave, infrared (IR), and other wireless media.
- RF radio frequency
- IR infrared
- the term computer-readable media, as used herein, may include both storage media and communication media.
- the computing device 1000 may be implemented as a part of a general purpose or specialized server, mainframe, or similar computer, which includes any of the above functions.
- the computing device 1000 may also be implemented as a personal computer including both laptop computer and non-laptop computer configurations.
- Example embodiments may also include managing an event on a calendar with a timeline.
- These methods may be implemented in any number of ways, including the structures described herein. One such way may be by machine operations, using devices of the type described in the present disclosure. Another optional way may be for one or more of the individual operations of the methods to be performed in conjunction with one or more human operators performing some of the operations while other operations may be performed by machines. These human operators need not be co-located with each other, but each may be with a machine that performs a portion of the program. In other examples, the human interaction may be automated such as by pre-selected criteria that may be machine automated.
- FIG. 11 illustrates a logic flow diagram for a process to manage an event on a calendar with a timeline, according to embodiments.
- Process 1100 may be implemented on a calendar application of the cloud based service.
- Process 1100 begins with operation 1110 , where a first context menu that includes a create control may be displayed on the calendar, in response to a first selection action of the event displayed on the calendar.
- the event may be presented on the timeline, in response to an activation of the create control.
- a second context menu, that includes a delete control may be displayed on the timeline, in response to a second selection action of the event displayed on the timeline at operation 1130 .
- the event may be removed from the timeline, in response to an activation of the delete control.
- process 1100 is for illustration purposes.
- a calendar application according to embodiments may be implemented by similar processes with fewer or additional steps, as well as in different order of operations using the principles described herein.
- a method that is executed on a computing device to manage an event on a calendar with a timeline may be described.
- the method may include displaying a first context menu that includes a create control on the calendar, in response to a first selection action of the event displayed on the calendar, presenting the event on the timeline, in response to an activation of the create control, displaying a second context menu, that includes a delete control, on the timeline, in response to a second selection action of the event displayed on the timeline, and removing the event from the timeline, in response to an activation of the delete control.
- the method may further include presenting the first context menu on a location that includes one from a set of: in proximity to, adjacent to, and superimposed on the event displayed on the calendar and presenting the second context menu on another location that includes one from a set of: in proximity to, adjacent to, and superimposed on the event displayed on the timeline.
- the method may further include detecting a drag and drop action on the event displayed on the calendar, overlaying a message on the timeline to guide the drag and drop action to conclude on the timeline, detecting the drag and drop action that concludes on the timeline, scrolling the timeline to a date range that includes a date of the event, and displaying the event within the date on the timeline
- the method may further include detecting a touch and drag action on the event displayed on the calendar to move the event from an original date and an original time to a new date and a new time, displaying the event at the new date and the new time on the calendar, removing the event on the timeline at the original date, scrolling the timeline to a date range that includes the new date, and displaying the event on the timeline at the new date.
- a hover action may be detected on a section of the timeline and a tooltip may be displayed below the section that shows a date associated with the section.
- the method may further include detecting a third selection action on the event displayed on the timeline, displaying an event peek on the timeline, presenting one or more attributes from a set of: an event subject, an event title, a date of the event, a time of the event, a creation timestamp, and a summary of the event in the event peek, and providing an edit control in the event peek to allow one or more edit operations to modify the one or more attributes.
- the event and other events may be detected on a date of the timeline that exceed a vertical height threshold of the timeline and a vertical scroll control may be presented on a vertical edge of the timeline to allow for scrolling through the event and the other events.
- the event and other events may be detected on a date of the timeline that exceed a vertical height of the timeline and the vertical height of the timeline may be increased to encompass the event and the other events.
- a computing device to manage an event on a calendar with a timeline may be described.
- the computing device may include a display device, a memory, a processor coupled to the memory and the display device.
- the processor may be configured to execute a calendar application in conjunction with instructions stored in the memory.
- the calendar application may be configured to display a first context menu that includes a create control on the calendar, on the display device, in response to a first selection action of the event displayed on the calendar, where the first context menu is displayed superimposed on the event, present the event on the timeline, on the display device, in response to an activation of the create control, display a second context menu, that includes a delete control, on the timeline, on the display device, in response to a second selection action of the event displayed on the timeline, where the second context menu is displayed superimposed on the event, and remove the event from the timeline, on the display device, in response to an activation of the delete control.
- the calendar application is further configured to detect an insertion action to insert a first deadline on a date of the timeline, display the first deadline on the date, on the display device, detect another insertion action to insert a second deadline on the date, and display the second deadline on the date, on the display device, where a label of the second deadline is superimposed on a label of the first deadline.
- the calendar application is further configured to detect a second event added to the timeline, where the second event overlaps one or more dates associated with the event, display the second event above the event on the timeline, on the display device, detect a third event added to the timeline, where the third event overlaps one or more dates associated with the event and the second event, increase a vertical height of the timeline to encompass the event, the second event, and the third event, and display the third event above the second event on the timeline, on the display device.
- a drag and drop action may be detected on the event displayed on the calendar, the timeline may be minimized, and a message may be overlaid on the timeline to guide the drag and drop action to conclude on the minimized timeline, on the display device.
- a computer-readable memory device with instructions stored thereon to manage an event on a calendar with a timeline may be described.
- the instructions may include actions that are similar to the method described above.
- a means to manage an event on a calendar with a timeline may be described.
- the means to manage an event on a calendar with a timeline may include a means for displaying a first context menu that includes a create control on the calendar, in response to a first selection action of the event displayed on the calendar, a means for presenting the event on the timeline, in response to an activation of the create control, a means for displaying a second context menu, that includes a delete control, on the timeline, in response to a second selection action of the event displayed on the timeline, and a means for removing the event from the timeline, in response to an activation of the delete control.
Abstract
Description
- This applications claims the benefit of U.S. Provisional Patent Application Ser. No. 62/015,350 filed on Jun. 20, 2014. The disclosure of the provisional application is incorporated herein in its entirety.
- Legacy calendar views in scheduling applications provide limited information. Alternatively, the legacy calendar views in scheduling applications provide excessive information. Legacy calendar views are usually used in detailed configurations for daily and weekly actions. However, users are underserved in long term synapsis of associated actions in legacy calendar views. Addition of actions and other items into legacy calendar views prove challenging for long term synapsis of associated actions.
- This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This summary is not intended to exclusively identify key features or essential features of the claimed subject matter, nor is it intended as an aid in determining the scope of the claimed subject matter.
- Embodiments are directed to managing an event on a calendar with a timeline. In some example embodiments, a calendar application may display a first context menu that includes a create control on the calendar, in response to a first selection action of the event displayed on the calendar. The event may be presented on the timeline, in response to an activation of the create control. A second context menu, that includes a delete control, may be displayed on the timeline, in response to a second selection action of the event displayed on the timeline. The event may be removed from the timeline, in response to an activation of the delete control.
- These and other features and advantages will be apparent from a reading of the following detailed description and a review of the associated drawings. It is to be understood that both the foregoing general description and the following detailed description are explanatory and do not restrict aspects as claimed.
-
FIG. 1 is a conceptual diagram illustrating an example of managing an event on a calendar with a timeline, according to embodiments; -
FIG. 2 illustrates an example of a create action to create an event within a timeline, according to embodiments; -
FIG. 3 illustrates an example of a removal action to delete an event from a timeline, according to embodiments; -
FIG. 4 illustrates an example of a drag and drop action to copy an event on a calendar into the timeline, according to embodiments; -
FIG. 5 illustrates an example of a touch and drag action to change a date and time of an event on a calendar, according to embodiments; -
FIG. 6 illustrates an example of a hover action to display a tooltip below the timeline, according to embodiments; -
FIG. 7 illustrates an example of an event peek associated with an event displayed on the timeline, according to embodiments; -
FIG. 8 illustrates an example of managing events that conflict on a timeline, according to embodiments; -
FIG. 9 is a simplified networked environment, where a system according to embodiments may be implemented; -
FIG. 10 illustrates a general purpose computing device, which may be configured to manage an event on a calendar with a timeline; and -
FIG. 11 illustrates a logic flow diagram for a process to manage an event on a calendar with a timeline, according to embodiments. - As briefly described above, an event on a calendar with a timeline may be managed by a calendar application. A first context menu that includes a create control may be displayed on the calendar, in response to a first selection action of the event displayed on the calendar. The event may be presented on the timeline, in response to an activation of the create control. A second context menu, that includes a delete control, may be displayed on the timeline, in response to a second selection action of the event displayed on the timeline. The event may be removed from the timeline, in response to an activation of the delete control.
- In the following detailed description, references are made to the accompanying drawings that form a part hereof, and in which are shown by way of illustrations specific embodiments or examples. These aspects may be combined, other aspects may be utilized, and structural changes may be made without departing from the spirit or scope of the present disclosure. The following detailed description is therefore not to be taken in a limiting sense, and the scope of the present invention is defined by the appended claims and their equivalents.
- While the embodiments will be described in the general context of program modules that execute in conjunction with an application program that runs on an operating system on a computing device, those skilled in the art will recognize that aspects may also be implemented in combination with other program modules.
- Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that embodiments may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and comparable computing devices. Embodiments may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
- Embodiments may be implemented as a computer-implemented process (method), a computing system, or as an article of manufacture, such as a computer program product or computer readable media. The computer program product may be a computer storage medium readable by a computer system and encoding a computer program that comprises instructions for causing a computer or computing system to perform example process(es). The computer-readable storage medium is a computer-readable memory device. The computer-readable memory device includes a hardware device that includes a hard disk drive, a solid state drive, a compact disk, a memory chip, among others. The computer-readable storage medium can for example be implemented via one or more of a volatile computer memory, a non-volatile memory, a hard drive, and a flash drive.
- Throughout this specification, the term “platform” may be a combination of software and hardware components to manage an event on a calendar with a timeline. Examples of platforms include, but are not limited to, a hosted service executed over a plurality of servers, an application executed on a single computing device, and comparable systems. The term “server” generally refers to a computing device executing one or more software programs typically in a networked environment. However, a server may also be implemented as a virtual server (software programs) executed on one or more computing devices viewed as a server on the network. More detail on these technologies and example embodiments may be found in the following description.
-
FIG. 1 is a conceptual diagram illustrating an example of managing an event on a calendar with a timeline, according to embodiments. - In a diagram 100, a
computing device 104 may execute acalendar application 102. The computing device may include a tablet device, a laptop computer, a desktop computer, a smart phone, among others. Thecomputing device 104 may display thecalendar application 102 to auser 106. Theuser 106 may be allowed to interact with thecalendar application 102 through an input device or touch enabled display component of thecomputing device 104. Theuser 106 may interact with thecalendar application 102 with a keyboard based input, a mouse based input, a voice based input, a pen based input, a gesture based input, among others. The gesture based input may include one or more touch based actions such as a touch action, a swipe action, a combination of each, among others. - The
calendar application 102 may include atimeline 120 as a component placed adjacent to and below a calendar. Thetimeline 120 may include a linear presentation of events during a time period divided based on a time unit such as a day. Events presented on the timeline may be duplicates of the events on the calendar displayed by thecalendar application 102. Auser 106 may be allowed to interact with the calendar and thetimeline 120 to manage an event. The event may be displayed on the calendar and duplicated on thetimeline 120. - While the example system in
FIG. 1 has been described with specific components including thecomputing device 104, thecalendar application 102, thetimeline 120, embodiments are not limited to these components or system configurations and can be implemented with other system configuration employing fewer or additional components. -
FIG. 2 illustrates an example of a create action to create an event within a timeline, according to embodiments. - In a diagram 200, a
calendar application 202 that displays acalendar 226 and atimeline 220 used to create an event may be described. Thecalendar application 202 may display acontext menu 216 on thecalendar 226 in response to a selection action on anevent 214. The selection action may include a click event associated with a mouse input, a tap action associated with a touch based input, among others. Thecontext menu 216 may be displayed in proximity to theevent 214, adjacent to theevent 214 or superimposed on theevent 214. - The
calendar application 202 may display one or more controls on thecontext menu 216. One of the controls may include a createcontrol 218 to create the event on thetimeline 220. In response to an activation of the createcontrol 218, theevent 214 may be copied to the timeline on a date of the event. The timeline may be scrolled to a date range that includes the date of the event. The event may be displayed on the date of the event on thetimeline 220. - The
calendar application 202 may also display additional controls associated with thecalendar 226. Thedate picker component 204 may allow a user to select a date from a displayed range. The selected date may be displayed in thecalendar 226 that shows the date within a date range that is configurable. The date range of thecalendar 226 may include a day, a week, a month, a year, among others. A current date range may be illustrated with adate range label 208. The date range may also be partitioned vertically based on a time unit such as aday 210. The time units may be scrollable. Thecalendar 226 may also be partitioned horizontally based on an hour basedunit 212. The hour based units may be scrollable. An “all day” unit may persist on a top section of thecalendar 226 to show one or more events that last during a time unit such as a day. - The
calendar 226 may be selectable through acalendar selection control 206. Thecalendar application 202 may display one or more calendars that may be selectable through thecalendar selection control 206 and other calendar selection controls displayed adjacent to thecalendar selection control 206. - The
timeline 220 may display a linear presentation of events on thecalendar 226. Thetimeline 220 may display a date range of events that may be scrollable through ascroll control 224. The date range may be presented with adate range label 222. The date range may be partitioned based on time units such as an hour, aday 228, a week, a month, a year, among others. The date range may be selectable based on a selection of the range by a user through a range selection control such as “weekly,” among others. Theevent 214 on thecalendar 226 may be duplicated on thetimeline 220 using the createcontrol 218 or through another operation to copy theevent 214 to thetimeline 220. -
FIG. 3 illustrates an example of a removal action to delete an event from a timeline, according to embodiments. - In a diagram 300, a
calendar application 302 may display a context menu superimposed on theevent 304, in response to a selection action detected on theevent 304. The selection action may include a click event associated with a mouse input, a tap action associated with a touch based input, among others. Thecontext menu 306 may also be displayed adjacent to or in proximity to theevent 304 displayed on thetimeline 320. A distance between theevent 304 and thecontext menu 306 may be determined based on an application attribute or dynamically based on other components of thecalendar application 302, when displaying thecontext menu 306 in proximity to theevent 304. Theevent 304 may also be a duplication of theevent 314. Theevent 304 may be displayed on a date of thetimeline 320 that corresponds to an event date of theevent 314. - The
context menu 306 may provide one or more controls to manage theevent 304 displayed on thetimeline 320. Thecontext menu 306 may include adelete control 308 to remove the event from thetimeline 320. In response to an activation of thedelete control 308, theevent 304 may be removed from thetimeline 320. Thedelete control 308 may not remove theevent 314 from the calendar. An additional operation may be initiated by a user to remove theevent 314 from the calendar. An example may include a selection action of theevent 314 to display a new context menu on the calendar. Another delete control on the new context menu may be activated to remove theevent 314 from the calendar. -
FIG. 4 illustrates an example of a drag and drop action to copy an event on a calendar into the timeline, according to embodiments. - In a diagram 400, a drag and drop action on an
event 414 may be detected by thecalendar application 402. The drag and drop action may include a click and hold event by a mouse input, a tap and hold event by a touch based action, among others on theevent 414. Thecalendar application 402 may detect a direction of the drag and drop action. In response to detecting the direction of the drag and drop action to point towards atimeline 420, amessage 404 may be overlaid on thetimeline 420 to guide the drag and drop action to conclude on the timeline. The timeline may also be minimized during the drag and drop action. - In response to detecting the drag and drop action to move an
event 406 over thetimeline 420, the timeline may be restored to an original size prior to a minimization operation. A message to guide the drag and drop action to conclude on thetimeline 420 may be displayed on thetimeline 420. In response to detecting a conclusion of the drag and drop action on thetimeline 420, anevent 406 may be detected as dropped on the timeline. Theevent 406 may be a copy of theevent 414 in transit from the calendar to thetimeline 420 during the drag and drop action. Thetimeline 420 may be scrolled to a display a time period that includes a date of theevent 414. Theevent 406 may be placed on a date on the timeline that corresponds to the date of theevent 414. -
FIG. 5 illustrates an example of a touch and drag action to change a date and time of an event on a calendar, according to embodiments. - In a diagram 500, a
calendar application 502 may detect a touch and drag action to change a date and a time of anevent 514. A touch and drag action may start with a tap and holdaction 512 on anevent 514. The touch and drag action may be detected to conclude at a new date and a new time in response to adrop action 518. Anevent 516 may be placed at the new date and new time based on detecting a location of thedrop action 518 that corresponds to the new date and new time on the calendar. Theevent 514 may be removed from the calendar. Theevent 516 may be displayed on the new date and new time. - An
event 504 may also be moved in response to the touch and drag action on theevent 514. Theevent 504 may be a duplicate of theevent 514, on thetimeline 520. As such, theevent 504 may be moved to a new date that corresponds to the date ofevent 516, on thetimeline 520. Upon conclusion of the touch and drag action, theevent 504 may be removed from an original date. Theevent 504 may be placed on the new date on thetimeline 520 that corresponds to the date of theevent 516. -
FIG. 6 illustrates an example of a hover action to display a tooltip below the timeline, according to embodiments. - In a diagram 600, a hover
action 602 may be detected on a section of atimeline 620. Atooltip 606 may be displayed below the section. Thetooltip 606 may display a date associated with the section. The calendar application may also display anevent 604 within the section where the hover action may be detected. The hoveraction 602 may be detected as a result of a mouse input or touch based input, among others. -
FIG. 7 illustrates an example of an event peek associated with an event displayed on the timeline, according to embodiments. - In a diagram 700, a
calendar application 702 may display anevent peek 706 in response to a selection action on anevent 704 displayed on a timeline 720. The selection action may be a hover action detected on theevent 704. The hover action may be provided through a mouse input, through a touch based input, among others. Theevent 704 may be a duplicate of anevent 714 displayed on a calendar. - The
event peek 706 may display attributes associated with theevent 704. The attributes may include an event subject, an event title, a date of the event, a time of the event, a creation timestamp, a summary of the event, among others. One or more controls, that includes anedit control 708, may also be provided through theevent peek 706 to edit theevent 704. In response to an activation of theedit control 708, theevent peek 706 may be displayed by thecalendar application 702 in a persistent mode and a user may be allowed to edit the attributes of theevent 704 on theevent peek 706. A cancel control may also be provided to stop editing the attributes of theevent 704 and undo any edits that were not saved. In response to a completion of edit operations, the edits of the attributes may be saved on theevent 704. The edits of the attributes may also be saved on anevent 714 on the calendar because theevent 704 is a duplicate of theevent 714. -
FIG. 8 illustrates an example of managing events that conflict on a timeline, according to embodiments. - In a diagram 800, a calendar application may detect a conflict between events when more than one event is added to a
timeline 820 while overlapping a timeslot of thetimeline 820. A new event such as anevent 804 may be placed above existing events such as anevent 806 and anevent 808 to resolve the conflict. However, number of events overlapping a timeslot may lead to exceeding a vertical height of thetimeline 820 while stacking the events. - The calendar application may detect the events (804, 806, and 808) on a date of the
timeline 820 to exceed the vertical height of the timeline. As a result, part of the events (804, 806, and 808) may be hidden from view. To provide access to the events (804, 806, and 808) the calendar application may increase the vertical height of the timeline to encompass the events (804, 806, and 808). The calendar application may also detect the events (804, 806, and 808) exceeding a vertical height threshold of thetimeline 820. The vertical height threshold may be configured by a user or a device setting such as available screen estate. Avertical scroll control 810 may be presented on a vertical edge of thetimeline 820, such as a right edge or a left edge, to allow for scrolling through the events (804, 806, and 808), in response to detecting the events (804, 806, and 808) exceeding the vertical height threshold of thetimeline 820. - In addition, an insertion action may be detected on the
timeline 820 to insert an initial deadline on a date of the timeline. The initial deadline may be displayed on the date. Another insertion action may also be detected to insert a second deadline on the date of the initial deadline. The second deadline may be displayed on the date. A label of the second deadline may be superimposed on a label of the initial deadline. - The technical advantage of managing an event on a calendar with a timeline may be improved usability and enhanced reliability of display devices in providing event creation, editing, management, and display, among other features compared to static event presentation based solutions.
- The example scenarios and schemas in
FIG. 1 through 8 are shown with specific components, data types, and configurations. Embodiments are not limited to systems according to these example configurations. Managing an event on a calendar with a timeline may be implemented in configurations employing fewer or additional components in applications and user interfaces. Furthermore, the example schema and components shown inFIG. 1 through 8 and their subcomponents may be implemented in a similar manner with other values using the principles described herein. -
FIG. 9 is an example networked environment, where embodiments may be implemented. A calendar application configured to manage an event on a calendar with a timeline may be implemented via software executed over one ormore servers 914 such as a hosted service. The platform may communicate with client applications on individual computing devices such as asmart phone 913, alaptop computer 912, or desktop computer 911 (‘client devices’) through network(s) 910. - Client applications executed on any of the client devices 911-913 may facilitate communications via application(s) executed by
servers 914, or onindividual server 916. A calendar application may display a context menu that includes a create control on an event of the calendar. The event may be presented on the timeline in response to an activation of the create control. The calendar application may store data associated with the timeline in data store(s) 919 directly or throughdatabase server 918. - Network(s) 910 may comprise any topology of servers, clients, Internet service providers, and communication media. A system according to embodiments may have a static or dynamic topology. Network(s) 910 may include secure networks such as an enterprise network, an unsecure network such as a wireless open network, or the Internet. Network(s) 910 may also coordinate communication over other networks such as Public Switched Telephone Network (PSTN) or cellular networks. Furthermore, network(s) 910 may include short range wireless networks such as Bluetooth or similar ones. Network(s) 910 provide communication between the nodes described herein. By way of example, and not limitation, network(s) 910 may include wireless media such as acoustic, RF, infrared and other wireless media.
- Many other configurations of computing devices, applications, data sources, and data distribution systems may be employed to manage an event on a calendar with a timeline. Furthermore, the networked environments discussed in
FIG. 9 are for illustration purposes only. Embodiments are not limited to the example applications, modules, or processes. -
FIG. 10 illustrates a general purpose computing device, which may be configured to manage an event on a calendar with a timeline, arranged in accordance with at least some embodiments described herein. - For example, the
computing device 1000 may be used to manage an event on a calendar with a timeline. In an example of a basic configuration 1002, thecomputing device 1000 may include one ormore processors 1004 and asystem memory 1006. A memory bus 1008 may be used for communication between theprocessor 1004 and thesystem memory 1006. The basic configuration 1002 may be illustrated inFIG. 10 by those components within the inner dashed line. - Depending on the desired configuration, the
processor 1004 may be of any type, including, but not limited to, a microprocessor (μP), a microcontroller (μC), a digital signal processor (DSP), or any combination thereof. Theprocessor 1004 may include one more levels of caching, such as alevel cache memory 1012, aprocessor core 1014, and registers 1016. Theprocessor core 1014 may include an arithmetic logic unit (ALU), a floating point unit (FPU), a digital signal processing core (DSP Core), or any combination thereof. Amemory controller 1018 may also be used with theprocessor 1004, or in some implementations, thememory controller 1018 may be an internal part of theprocessor 1004. - Depending on the desired configuration, the
system memory 1006 may be of any type including but not limited to volatile memory (such as RAM), non-volatile memory (such as ROM, flash memory, etc.), or any combination thereof. Thesystem memory 1006 may include anoperating system 1020, acalendar application 1022, and aprogram data 1024. Thecalendar application 1022 may display a context menu that includes a create control on an event of the calendar. The event may be presented on the timeline in response to an activation of the create control. Components of the calendar application 1022 (such as a user interface) may also be displayed on a display device associated with thecomputing device 1000. An example of the display device may include a hardware screen that may be communicatively coupled to thecomputing device 1000. The display device may include a touch based device that detects gestures such as a touch action. The display device may also provide feedback in response to detected gestures (or any other form of input) by transforming one or more user interfaces of thecalendar application 1022 such as the timeline, displayed by the touch based device. Theprogram data 1024 may include, among other data, atimeline data 1028, or the like, as described herein. Thetimeline data 1028 may include the event, subject name of the event, the event date, among others. - The
computing device 1000 may have additional features or functionality, and additional interfaces to facilitate communications between the basic configuration 1002 and any desired devices and interfaces. For example, a bus/interface controller 1030 may be used to facilitate communications between the basic configuration 1002 and one or moredata storage devices 1032 via a storage interface bus 1034. Thedata storage devices 1032 may be one or moreremovable storage devices 1036, one or morenon-removable storage devices 1038, or a combination thereof. Examples of the removable storage and the non-removable storage devices may include magnetic disk devices, such as flexible disk drives and hard-disk drives (HDD), optical disk drives such as compact disk (CD) drives or digital versatile disk (DVD) drives, solid state drives (SSD), and tape drives, to name a few. Example computer storage media may include volatile and nonvolatile, removable, and non-removable media implemented in any method or technology for storage of information, such as computer-readable instructions, data structures, program modules, or other data. - The
system memory 1006, theremovable storage devices 1036, and thenon-removable storage devices 1038 may be examples of computer storage media. Computer storage media may include, but may not be limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD), solid state drives, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which may be used to store the desired information and which may be accessed by thecomputing device 1000. Any such computer storage media may be part of thecomputing device 1000. - The
computing device 1000 may also include an interface bus 1040 for facilitating communication from various interface devices (for example, one ormore output devices 1042, one or moreperipheral interfaces 1044, and one or more communication devices 1066) to the basic configuration 1002 via the bus/interface controller 1030. Some of theexample output devices 1042 may include agraphics processing unit 1048 and an audio processing unit 1050, which may be configured to communicate to various external devices, such as a display or speakers via one or more A/V ports 1052. One or more exampleperipheral interfaces 1044 may include aserial interface controller 1054 or aparallel interface controller 1056, which may be configured to communicate with external devices, such as input devices (for example, keyboard, mouse, pen, voice input device, touch input device, etc.) or other peripheral devices (for example, printer, scanner, etc.) via one or more I/O ports 1058. Anexample communication device 1066 may include anetwork controller 1060, which may be arranged to facilitate communications with one or moreother computing devices 1062 over a network communication link via one ormore communication ports 1064. The one or moreother computing devices 1062 may include servers, client equipment, and comparable devices. - The network communication link may be one example of a communication media. Communication media may be embodied by computer-readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and may include any information delivery media. A “modulated data signal” may be a signal that has one or more of the modulated data signal characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), microwave, infrared (IR), and other wireless media. The term computer-readable media, as used herein, may include both storage media and communication media.
- The
computing device 1000 may be implemented as a part of a general purpose or specialized server, mainframe, or similar computer, which includes any of the above functions. Thecomputing device 1000 may also be implemented as a personal computer including both laptop computer and non-laptop computer configurations. - Example embodiments may also include managing an event on a calendar with a timeline. These methods may be implemented in any number of ways, including the structures described herein. One such way may be by machine operations, using devices of the type described in the present disclosure. Another optional way may be for one or more of the individual operations of the methods to be performed in conjunction with one or more human operators performing some of the operations while other operations may be performed by machines. These human operators need not be co-located with each other, but each may be with a machine that performs a portion of the program. In other examples, the human interaction may be automated such as by pre-selected criteria that may be machine automated.
-
FIG. 11 illustrates a logic flow diagram for a process to manage an event on a calendar with a timeline, according to embodiments.Process 1100 may be implemented on a calendar application of the cloud based service. -
Process 1100 begins withoperation 1110, where a first context menu that includes a create control may be displayed on the calendar, in response to a first selection action of the event displayed on the calendar. Atoperation 1120, the event may be presented on the timeline, in response to an activation of the create control. A second context menu, that includes a delete control, may be displayed on the timeline, in response to a second selection action of the event displayed on the timeline atoperation 1130. Atoperation 1140, the event may be removed from the timeline, in response to an activation of the delete control. - The operations included in
process 1100 are for illustration purposes. A calendar application according to embodiments may be implemented by similar processes with fewer or additional steps, as well as in different order of operations using the principles described herein. - According to some examples, a method that is executed on a computing device to manage an event on a calendar with a timeline may be described. The method may include displaying a first context menu that includes a create control on the calendar, in response to a first selection action of the event displayed on the calendar, presenting the event on the timeline, in response to an activation of the create control, displaying a second context menu, that includes a delete control, on the timeline, in response to a second selection action of the event displayed on the timeline, and removing the event from the timeline, in response to an activation of the delete control.
- According to other examples, the method may further include presenting the first context menu on a location that includes one from a set of: in proximity to, adjacent to, and superimposed on the event displayed on the calendar and presenting the second context menu on another location that includes one from a set of: in proximity to, adjacent to, and superimposed on the event displayed on the timeline. The method may further include detecting a drag and drop action on the event displayed on the calendar, overlaying a message on the timeline to guide the drag and drop action to conclude on the timeline, detecting the drag and drop action that concludes on the timeline, scrolling the timeline to a date range that includes a date of the event, and displaying the event within the date on the timeline
- According to further examples, the method may further include detecting a touch and drag action on the event displayed on the calendar to move the event from an original date and an original time to a new date and a new time, displaying the event at the new date and the new time on the calendar, removing the event on the timeline at the original date, scrolling the timeline to a date range that includes the new date, and displaying the event on the timeline at the new date. A hover action may be detected on a section of the timeline and a tooltip may be displayed below the section that shows a date associated with the section.
- According to further examples, the method may further include detecting a third selection action on the event displayed on the timeline, displaying an event peek on the timeline, presenting one or more attributes from a set of: an event subject, an event title, a date of the event, a time of the event, a creation timestamp, and a summary of the event in the event peek, and providing an edit control in the event peek to allow one or more edit operations to modify the one or more attributes. The event and other events may be detected on a date of the timeline that exceed a vertical height threshold of the timeline and a vertical scroll control may be presented on a vertical edge of the timeline to allow for scrolling through the event and the other events. The event and other events may be detected on a date of the timeline that exceed a vertical height of the timeline and the vertical height of the timeline may be increased to encompass the event and the other events.
- According to some examples, a computing device to manage an event on a calendar with a timeline may be described. The computing device may include a display device, a memory, a processor coupled to the memory and the display device. The processor may be configured to execute a calendar application in conjunction with instructions stored in the memory. The calendar application may be configured to display a first context menu that includes a create control on the calendar, on the display device, in response to a first selection action of the event displayed on the calendar, where the first context menu is displayed superimposed on the event, present the event on the timeline, on the display device, in response to an activation of the create control, display a second context menu, that includes a delete control, on the timeline, on the display device, in response to a second selection action of the event displayed on the timeline, where the second context menu is displayed superimposed on the event, and remove the event from the timeline, on the display device, in response to an activation of the delete control.
- According to other examples, the calendar application is further configured to detect an insertion action to insert a first deadline on a date of the timeline, display the first deadline on the date, on the display device, detect another insertion action to insert a second deadline on the date, and display the second deadline on the date, on the display device, where a label of the second deadline is superimposed on a label of the first deadline. The calendar application is further configured to detect a second event added to the timeline, where the second event overlaps one or more dates associated with the event, display the second event above the event on the timeline, on the display device, detect a third event added to the timeline, where the third event overlaps one or more dates associated with the event and the second event, increase a vertical height of the timeline to encompass the event, the second event, and the third event, and display the third event above the second event on the timeline, on the display device. A drag and drop action may be detected on the event displayed on the calendar, the timeline may be minimized, and a message may be overlaid on the timeline to guide the drag and drop action to conclude on the minimized timeline, on the display device.
- According to some examples, a computer-readable memory device with instructions stored thereon to manage an event on a calendar with a timeline may be described. The instructions may include actions that are similar to the method described above.
- According to some examples, a means to manage an event on a calendar with a timeline may be described. The means to manage an event on a calendar with a timeline may include a means for displaying a first context menu that includes a create control on the calendar, in response to a first selection action of the event displayed on the calendar, a means for presenting the event on the timeline, in response to an activation of the create control, a means for displaying a second context menu, that includes a delete control, on the timeline, in response to a second selection action of the event displayed on the timeline, and a means for removing the event from the timeline, in response to an activation of the delete control.
- The above specification, examples and data provide a complete description of the manufacture and use of the composition of the embodiments. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims and embodiments.
Claims (20)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/518,425 US20150370440A1 (en) | 2014-06-20 | 2014-10-20 | Managing event on calendar with timeline |
TW104113082A TW201600980A (en) | 2014-06-20 | 2015-04-23 | Manage event on calendar with timeline |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201462015350P | 2014-06-20 | 2014-06-20 | |
US14/518,425 US20150370440A1 (en) | 2014-06-20 | 2014-10-20 | Managing event on calendar with timeline |
Publications (1)
Publication Number | Publication Date |
---|---|
US20150370440A1 true US20150370440A1 (en) | 2015-12-24 |
Family
ID=54869630
Family Applications (8)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/494,404 Abandoned US20150370462A1 (en) | 2014-06-20 | 2014-09-23 | Creating calendar event from timeline |
US14/518,425 Abandoned US20150370440A1 (en) | 2014-06-20 | 2014-10-20 | Managing event on calendar with timeline |
US14/518,664 Active 2036-01-11 US10656789B2 (en) | 2014-06-20 | 2014-10-20 | Locating event on timeline |
US14/519,035 Active 2036-06-20 US11416115B2 (en) | 2014-06-20 | 2014-10-20 | Search and locate event on calendar with timeline |
US14/519,089 Active US9746997B2 (en) | 2014-06-20 | 2014-10-20 | Share timeline of calendar |
US14/518,515 Abandoned US20150370463A1 (en) | 2014-06-20 | 2014-10-20 | Event visualization on calendar with timeline |
US14/518,824 Abandoned US20150370422A1 (en) | 2014-06-20 | 2014-10-20 | Manage event with content on calendar with timeline |
US14/520,293 Abandoned US20150370464A1 (en) | 2014-06-20 | 2014-10-21 | Manage recurring event on calendar with timeline |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/494,404 Abandoned US20150370462A1 (en) | 2014-06-20 | 2014-09-23 | Creating calendar event from timeline |
Family Applications After (6)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/518,664 Active 2036-01-11 US10656789B2 (en) | 2014-06-20 | 2014-10-20 | Locating event on timeline |
US14/519,035 Active 2036-06-20 US11416115B2 (en) | 2014-06-20 | 2014-10-20 | Search and locate event on calendar with timeline |
US14/519,089 Active US9746997B2 (en) | 2014-06-20 | 2014-10-20 | Share timeline of calendar |
US14/518,515 Abandoned US20150370463A1 (en) | 2014-06-20 | 2014-10-20 | Event visualization on calendar with timeline |
US14/518,824 Abandoned US20150370422A1 (en) | 2014-06-20 | 2014-10-20 | Manage event with content on calendar with timeline |
US14/520,293 Abandoned US20150370464A1 (en) | 2014-06-20 | 2014-10-21 | Manage recurring event on calendar with timeline |
Country Status (5)
Country | Link |
---|---|
US (8) | US20150370462A1 (en) |
EP (2) | EP3158516A1 (en) |
CN (2) | CN106796684A (en) |
TW (8) | TW201602930A (en) |
WO (7) | WO2015196004A1 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20180150650A1 (en) * | 2015-01-30 | 2018-05-31 | The Diary Corporation | System and method for controlling permissions for selected recipients by owners of data |
US10656789B2 (en) | 2014-06-20 | 2020-05-19 | Microsoft Technology Licensing, Llc | Locating event on timeline |
Families Citing this family (43)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3564891A1 (en) | 2009-06-04 | 2019-11-06 | Joshua Feuerstein | Method and system for electronic advertising |
US8423088B2 (en) * | 2009-07-22 | 2013-04-16 | Microsoft Corporation | Aggregated, interactive communication timeline |
US11410129B2 (en) | 2010-05-01 | 2022-08-09 | Monday.com Ltd. | Digital processing systems and methods for two-way syncing with third party applications in collaborative work systems |
WO2021099839A1 (en) | 2019-11-18 | 2021-05-27 | Roy Mann | Collaborative networking systems, methods, and devices |
WO2021161104A1 (en) | 2020-02-12 | 2021-08-19 | Monday.Com | Enhanced display features in collaborative network systems, methods, and devices |
US10241654B2 (en) * | 2013-12-20 | 2019-03-26 | Dassault Systemes Americas Corp. | Computer method and apparatus for automated scheduling |
USD775142S1 (en) | 2015-02-20 | 2016-12-27 | State Farm Mutual Automobile Insurance Company | Display screen with a graphical user interface for automobile repair estimation and recommendation |
US11030584B2 (en) * | 2015-07-17 | 2021-06-08 | Adp, Llc | System and method for managing events |
US20170024104A1 (en) * | 2015-07-24 | 2017-01-26 | Successfactors, Inc. | Erasure gesture |
US10692533B2 (en) * | 2015-10-07 | 2020-06-23 | Google Llc | Storyline experience |
CN107203389B (en) * | 2016-03-18 | 2021-01-22 | 百度在线网络技术(北京)有限公司 | Control display method and device |
US10222441B2 (en) | 2016-04-03 | 2019-03-05 | Q Bio, Inc. | Tensor field mapping |
US20180018063A1 (en) | 2016-07-14 | 2018-01-18 | Intent Media, Inc. | Graphical user interface and system for viewing landing page content |
US20180219810A1 (en) * | 2016-08-29 | 2018-08-02 | Mezzemail Llc | Transmitting tagged electronic messages |
US11348072B2 (en) | 2016-09-26 | 2022-05-31 | Microsoft Technology Licensing, Llc | Techniques for sharing electronic calendars between mailboxes in an online application and collaboration service |
US20180095938A1 (en) * | 2016-09-30 | 2018-04-05 | Sap Se | Synchronized calendar and timeline adaptive user interface |
US11250028B2 (en) * | 2017-01-31 | 2022-02-15 | Bank Of America Corporation | Data aggregator |
US10936180B2 (en) * | 2017-03-16 | 2021-03-02 | Q Bio, Inc. | User interface for medical information |
US10922661B2 (en) * | 2017-03-27 | 2021-02-16 | Microsoft Technology Licensing, Llc | Controlling a computing system to generate a pre-accept cache for calendar sharing |
US10650033B2 (en) * | 2017-06-08 | 2020-05-12 | Microsoft Technology Licensing, Llc | Calendar user interface search and interactivity features |
CN107844950A (en) * | 2017-10-27 | 2018-03-27 | 珠海市魅族科技有限公司 | A kind of calendar event creation method, apparatus, computer installation and storage medium |
CN107817938B (en) * | 2017-11-23 | 2020-01-14 | 平安科技(深圳)有限公司 | Method, device and equipment for realizing selection list scrolling and readable storage medium |
CA3085101A1 (en) * | 2017-12-08 | 2019-06-13 | Chronthat, Inc. | Electronic chronology |
CN108647067A (en) * | 2018-04-12 | 2018-10-12 | 青岛真时科技有限公司 | A kind of schedule display methods and device |
US11436359B2 (en) | 2018-07-04 | 2022-09-06 | Monday.com Ltd. | System and method for managing permissions of users for a single data type column-oriented data structure |
US11698890B2 (en) | 2018-07-04 | 2023-07-11 | Monday.com Ltd. | System and method for generating a column-oriented data structure repository for columns of single data types |
CN110968224A (en) * | 2018-09-28 | 2020-04-07 | 北京国双科技有限公司 | Time information display method and related device |
US11663557B2 (en) * | 2018-12-18 | 2023-05-30 | Rubrik, Inc. | Snapshot calendar view interfaces |
US11354586B2 (en) | 2019-02-15 | 2022-06-07 | Q Bio, Inc. | Model parameter determination using a predictive model |
US11131735B2 (en) | 2019-09-27 | 2021-09-28 | Q Bio, Inc. | Maxwell parallel imaging |
US11614509B2 (en) | 2019-09-27 | 2023-03-28 | Q Bio, Inc. | Maxwell parallel imaging |
CN111026472A (en) * | 2019-10-28 | 2020-04-17 | 珠海格力电器股份有限公司 | Calendar configuration and date selection method and device, storage medium and electronic equipment |
CN111124400B (en) * | 2019-11-14 | 2023-08-29 | 深圳震有科技股份有限公司 | Calendar component implementation method and device, computer equipment and medium |
US20210150135A1 (en) | 2019-11-18 | 2021-05-20 | Monday.Com | Digital processing systems and methods for integrated graphs in cells of collaborative work system tables |
US11829953B1 (en) | 2020-05-01 | 2023-11-28 | Monday.com Ltd. | Digital processing systems and methods for managing sprints using linked electronic boards |
US11501255B2 (en) | 2020-05-01 | 2022-11-15 | Monday.com Ltd. | Digital processing systems and methods for virtual file-based electronic white board in collaborative work systems |
US11277361B2 (en) | 2020-05-03 | 2022-03-15 | Monday.com Ltd. | Digital processing systems and methods for variable hang-time for social layer messages in collaborative work systems |
US11687216B2 (en) | 2021-01-14 | 2023-06-27 | Monday.com Ltd. | Digital processing systems and methods for dynamically updating documents with data from linked files in collaborative work systems |
US11614508B1 (en) | 2021-10-25 | 2023-03-28 | Q Bio, Inc. | Sparse representation of measurements |
US11741071B1 (en) | 2022-12-28 | 2023-08-29 | Monday.com Ltd. | Digital processing systems and methods for navigating and viewing displayed content |
US11886683B1 (en) | 2022-12-30 | 2024-01-30 | Monday.com Ltd | Digital processing systems and methods for presenting board graphics |
US11893381B1 (en) | 2023-02-21 | 2024-02-06 | Monday.com Ltd | Digital processing systems and methods for reducing file bundle sizes |
US11829708B1 (en) * | 2023-04-28 | 2023-11-28 | Dell Products L.P. | Communicating context for messages between users in copy management systems |
Citations (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040109137A1 (en) * | 2002-12-04 | 2004-06-10 | Bubie Walter C. | Streamlined methods and systems for scheduling and handling digital cinema content in a multi-theatre environment |
US20050108253A1 (en) * | 2003-11-17 | 2005-05-19 | Nokia Corporation | Time bar navigation in a media diary application |
US20050262450A1 (en) * | 2004-05-21 | 2005-11-24 | Volker Sauermann | System and method for controlling a display of data |
US20060279628A1 (en) * | 2003-09-12 | 2006-12-14 | Fleming Hayden G | Streaming non-continuous video data |
US20070182763A1 (en) * | 1991-12-20 | 2007-08-09 | Venolia Daniel S | Zooming controller |
US20070209019A1 (en) * | 2002-06-06 | 2007-09-06 | Maria Kaval | Method and device for displaying data |
US20080034047A1 (en) * | 2006-08-07 | 2008-02-07 | Rosenberg Gregory A | Calendar event, notification and alert bar embedded within mail |
US20080082925A1 (en) * | 2006-09-29 | 2008-04-03 | Microsoft Corporation | Bifocal view: a novel calendar user interface |
US20110167369A1 (en) * | 2010-01-06 | 2011-07-07 | Van Os Marcel | Device, Method, and Graphical User Interface for Navigating Through a Range of Values |
US20110202879A1 (en) * | 2010-02-15 | 2011-08-18 | Research In Motion Limited | Graphical context short menu |
US20110252351A1 (en) * | 2010-04-09 | 2011-10-13 | Calamander Inc. | Systems and methods for consuming, sharing, and synchronizing time based information |
US20120262472A1 (en) * | 2011-04-13 | 2012-10-18 | Honeywell International Inc. | Heatmap timeline for visualization of time series data |
US20130024206A1 (en) * | 2011-07-21 | 2013-01-24 | D & R Software Ii, Llc | Method, apparatus, and system for reading, processing, presenting, and/or storing electronic medical record information |
US20130055106A1 (en) * | 2010-12-16 | 2013-02-28 | Sony Ericsson Mobile Communications Ab | Calendar Application for Communication Devices |
US20140033025A1 (en) * | 2007-12-06 | 2014-01-30 | Adobe Systems Incorporated | Displaying a text-based description of digital content in a sub-frame |
US20140082536A1 (en) * | 2011-09-16 | 2014-03-20 | Ciprian Costa | Scheduling Events on an Electronic Calendar Utilizing Fixed-positioned Events and a Draggable Calendar Grid |
Family Cites Families (131)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5745110A (en) | 1995-03-10 | 1998-04-28 | Microsoft Corporation | Method and apparatus for arranging and displaying task schedule information in a calendar view format |
US5649182A (en) | 1995-03-17 | 1997-07-15 | Reitz; Carl A. | Apparatus and method for organizing timeline data |
US6016478A (en) | 1996-08-13 | 2000-01-18 | Starfish Software, Inc. | Scheduling system with methods for peer-to-peer scheduling of remote users |
US5898431A (en) | 1996-12-31 | 1999-04-27 | International Business Machines Corporation | Database graphical user interface with calendar view |
US6957191B1 (en) | 1999-02-05 | 2005-10-18 | Babcock & Brown Lp | Automated financial scenario modeling and analysis tool having an intelligent graphical user interface |
US6369840B1 (en) | 1999-03-10 | 2002-04-09 | America Online, Inc. | Multi-layered online calendaring and purchasing |
US6360217B1 (en) | 1999-04-21 | 2002-03-19 | Microsoft Corporation | Method and computer program product for calculating event occurrences |
US7263667B1 (en) | 1999-06-09 | 2007-08-28 | Microsoft Corporation | Methods, apparatus and data structures for providing a user interface which facilitates decision making |
US6603489B1 (en) | 2000-02-09 | 2003-08-05 | International Business Machines Corporation | Electronic calendaring system that automatically predicts calendar entries based upon previous activities |
US6678698B2 (en) | 2000-02-15 | 2004-01-13 | Intralinks, Inc. | Computerized method and system for communicating and managing information used in task-oriented projects |
US7721210B2 (en) | 2000-11-29 | 2010-05-18 | Nokia Corporation | Electronic calendar system |
US20020161756A1 (en) * | 2001-02-28 | 2002-10-31 | Fesq William Mcbride | System and method for performing local searhces across user defined events |
US20020186252A1 (en) | 2001-06-07 | 2002-12-12 | International Business Machines Corporation | Method, apparatus and computer program product for providing context to a computer display window |
US7340691B2 (en) * | 2001-06-25 | 2008-03-04 | International Business Machines Corporation | Method, system, and program for accessing calendar information for shadowed users from a database |
US8032561B1 (en) | 2001-08-16 | 2011-10-04 | Altera Corporation | System and method for scheduling and arbitrating events in computing and networking |
US7016909B2 (en) | 2002-06-04 | 2006-03-21 | Microsoft Corporation | Method and system for expansion of recurring calendar events |
US20040181425A1 (en) | 2003-03-14 | 2004-09-16 | Sven Schwerin-Wenzel | Change Management |
US7149810B1 (en) * | 2003-05-30 | 2006-12-12 | Microsoft Corporation | System and method for managing calendar items |
US9715678B2 (en) | 2003-06-26 | 2017-07-25 | Microsoft Technology Licensing, Llc | Side-by-side shared calendars |
US7069003B2 (en) | 2003-10-06 | 2006-06-27 | Nokia Corporation | Method and apparatus for automatically updating a mobile web log (blog) to reflect mobile terminal activity |
US20050105374A1 (en) | 2003-11-17 | 2005-05-19 | Nokia Corporation | Media diary application for use with digital device |
FI116764B (en) | 2003-12-22 | 2006-02-15 | Nokia Corp | Method for Sharing Calendar Content in a Communication System, a Communication System, and a Terminal |
US7349920B1 (en) | 2004-02-13 | 2008-03-25 | Microsoft Corporation | Simultaneous display of multiple calendar systems |
US7487441B2 (en) | 2004-03-11 | 2009-02-03 | Yahoo!Inc. | Method and system of enhanced messaging |
US7370282B2 (en) | 2004-04-06 | 2008-05-06 | Cary James C | Grouping and displaying multiple tasks within an event object of an electronic calendar |
US7660904B2 (en) | 2004-05-11 | 2010-02-09 | Microsoft Corporation | Providing keys to share data within an instant messaging session |
US8463872B2 (en) | 2004-07-02 | 2013-06-11 | Broadsoft Casabi, Llc | Method and apparatus for a family center |
US8850330B2 (en) | 2004-07-26 | 2014-09-30 | International Business Machines Corporation | Editing repeating calendar events |
US20060028917A1 (en) | 2004-08-05 | 2006-02-09 | International Business Machines Corp. | Milestone bar calender |
US8127229B2 (en) * | 2004-08-31 | 2012-02-28 | Access Co., Ltd. | Controlling focus, and movement of the focus, between focus items in a multi-frame document |
US7747966B2 (en) * | 2004-09-30 | 2010-06-29 | Microsoft Corporation | User interface for providing task management and calendar information |
US7921026B2 (en) | 2005-03-01 | 2011-04-05 | Microsoft Corporation | Method and system for generating a timeline associated with a project schedule |
US20060236269A1 (en) | 2005-04-18 | 2006-10-19 | Amir Borna | Method and an apparatus for displaying calendar information to a user |
US8751279B2 (en) | 2005-05-23 | 2014-06-10 | Blackberry Limited | System and method for preventing the lapse of a recurring event using electronic calendar system |
CN1786852A (en) | 2005-06-18 | 2006-06-14 | 代龙云 | Geometric world clock and watch |
US20070027938A1 (en) | 2005-07-26 | 2007-02-01 | Scribe Software Inc. | Detecting data changes |
US7502798B2 (en) | 2005-08-03 | 2009-03-10 | Novell, Inc. | System and method of searching for information based on prior user actions |
US20070038494A1 (en) | 2005-08-15 | 2007-02-15 | Cognetics Corporation | Team management system and method |
US20090100010A1 (en) | 2005-10-26 | 2009-04-16 | Zimbra, Inc. | System and method for seamlessly integrating separate information systems within an application |
US7805676B2 (en) | 2005-12-21 | 2010-09-28 | Vmware, Inc. | Enhanced calendaring functionality in a collaboration suite |
US8074175B2 (en) | 2006-01-06 | 2011-12-06 | Microsoft Corporation | User interface for an inkable family calendar |
BRPI0709548A2 (en) | 2006-03-15 | 2011-07-19 | Google Inc | automatic display of reframed images |
US7636779B2 (en) | 2006-04-28 | 2009-12-22 | Yahoo! Inc. | Contextual mobile local search based on social network vitality information |
US7757181B2 (en) | 2006-05-05 | 2010-07-13 | Microsoft Corporation | Agenda and day hybrid calendar view |
JP4662481B2 (en) | 2006-06-28 | 2011-03-30 | ソニー・エリクソン・モバイルコミュニケーションズ株式会社 | Information processing device, information processing method, information processing program, and portable terminal device |
US7933955B2 (en) | 2006-07-11 | 2011-04-26 | Igor Khalatian | One-click universal screen sharing |
US7999810B1 (en) | 2006-08-30 | 2011-08-16 | Boice Gina L | System and method for animated computer visualization of historic events |
US20080082578A1 (en) * | 2006-09-29 | 2008-04-03 | Andrew Hogue | Displaying search results on a one or two dimensional graph |
US7673248B2 (en) | 2006-11-06 | 2010-03-02 | International Business Machines Corporation | Combining calendar entries with map views |
US7870194B2 (en) | 2006-11-14 | 2011-01-11 | Microsoft Corporation | Sharing calendar information |
US8578301B2 (en) | 2006-11-22 | 2013-11-05 | Skadool, Inc. | Hierarchical events |
US8209613B2 (en) | 2006-12-05 | 2012-06-26 | Research In Motion Limited | Method and device for scheduling follow-up events |
US8082276B2 (en) * | 2007-01-08 | 2011-12-20 | Microsoft Corporation | Techniques using captured information |
US20080195455A1 (en) | 2007-02-09 | 2008-08-14 | Research In Motion Limited | Electronic device and method of scheduling calendar events |
US8249906B2 (en) | 2007-02-12 | 2012-08-21 | Pma Technologies, Llc | Interactive graphics-based planning systems |
US7711717B2 (en) | 2007-03-20 | 2010-05-04 | Microsoft Corporation | Achieving recurring item recordings from calendaring applications over LOB systems |
US20080294663A1 (en) * | 2007-05-14 | 2008-11-27 | Heinley Brandon J | Creation and management of visual timelines |
US20080294994A1 (en) | 2007-05-18 | 2008-11-27 | Justin David Kruger | Event management system and method with calendar interface |
US20080307323A1 (en) * | 2007-06-10 | 2008-12-11 | Patrick Lee Coffman | Calendaring techniques and systems |
US8122362B2 (en) | 2007-07-20 | 2012-02-21 | Microsoft Corporation | Control and visibility for digital calendar sharing |
US9773525B2 (en) | 2007-08-16 | 2017-09-26 | Adobe Systems Incorporated | Timeline management |
US20090063947A1 (en) | 2007-08-17 | 2009-03-05 | Dma Ink | Calendar and spreadsheet user interfaces |
US20090138307A1 (en) | 2007-10-09 | 2009-05-28 | Babcock & Brown Lp, A Delaware Limited Partnership | Automated financial scenario modeling and analysis tool having an intelligent graphical user interface |
US8510123B2 (en) | 2007-12-17 | 2013-08-13 | Smooth Productions Inc. | Communications system and method for serving electronic content |
US8245153B2 (en) * | 2008-01-24 | 2012-08-14 | International Business Machines Coporation | System and method for displaying gantt charts with other project management tools |
US20090196123A1 (en) | 2008-02-05 | 2009-08-06 | Rajesh Gautam | Collaborative Appointment and Reminder System |
US20090240611A1 (en) | 2008-03-21 | 2009-09-24 | Augustine Nancy L | Systems and methods for displaying a data modification timeline |
US20090241048A1 (en) | 2008-03-21 | 2009-09-24 | Augustine Nancy L | Systems and methods for displaying a data modification timeline |
US8091033B2 (en) * | 2008-04-08 | 2012-01-03 | Cisco Technology, Inc. | System for displaying search results along a timeline |
US9715679B2 (en) | 2008-05-07 | 2017-07-25 | Novell, Inc. | System and method for displaying multiple time zones in an online calendar view |
US20090292690A1 (en) * | 2008-05-23 | 2009-11-26 | Daniel Jason Culbert | Method and System for Automatic Event Administration and Viewing |
US7961087B2 (en) | 2008-10-28 | 2011-06-14 | Bahman Hoveida | Holistic alarm monitoring |
US20100223089A1 (en) | 2009-02-27 | 2010-09-02 | Research In Motion Limited | Electronic device and method for creating calendar event records |
US20100262926A1 (en) | 2009-04-13 | 2010-10-14 | Gupta Pawan | Customizing recurring calendar events |
US20100313151A1 (en) | 2009-06-04 | 2010-12-09 | Microsoft Corporation | Representing data on configurable timeline with filter |
US20100318398A1 (en) | 2009-06-15 | 2010-12-16 | Xerox Corporation | Natural language interface for collaborative event scheduling |
US8200693B2 (en) * | 2009-06-26 | 2012-06-12 | Fair Isaac Corporation | Decision logic comparison and review |
US8423088B2 (en) | 2009-07-22 | 2013-04-16 | Microsoft Corporation | Aggregated, interactive communication timeline |
US9779386B2 (en) | 2009-08-31 | 2017-10-03 | Thomson Reuters Global Resources | Method and system for implementing workflows and managing staff and engagements |
EP2478476A4 (en) * | 2009-09-20 | 2013-09-18 | Blackberry Ltd | Mobile application for calendar sharing and scheduling |
US8606242B2 (en) | 2009-10-30 | 2013-12-10 | Sap Ag | Systems and methods to provide context information for mobile communication devices |
US9524493B2 (en) | 2009-11-24 | 2016-12-20 | International Business Machines Corporation | Chronologically navigating among time-based entries |
US8793611B2 (en) | 2010-01-06 | 2014-07-29 | Apple Inc. | Device, method, and graphical user interface for manipulating selectable user interface objects |
US8346590B2 (en) | 2010-01-27 | 2013-01-01 | Google Inc. | Automatically schedule and re-schedule meetings through search interface |
US8930841B2 (en) | 2010-02-15 | 2015-01-06 | Motorola Mobility Llc | Methods and apparatus for a user interface configured to display event information |
US10262301B2 (en) * | 2010-02-15 | 2019-04-16 | Sarah Photowat | Methods and systems for calendaring, social networking and planning for users, including, vendors, consumers and enterprises |
US8346229B2 (en) * | 2010-02-26 | 2013-01-01 | Research In Motion Limited | Scheduling and delivering ad meetings |
US20120047421A1 (en) | 2010-03-15 | 2012-02-23 | Holman Enterprises, LLC | System and method for creating and displaying a timeline presentation |
US20110239146A1 (en) * | 2010-03-23 | 2011-09-29 | Lala Dutta | Automatic event generation |
US9230224B2 (en) | 2010-05-11 | 2016-01-05 | Salesforce.Com, Inc. | Providing a timeline control in a multi-tenant database environment |
US9158444B2 (en) * | 2010-05-26 | 2015-10-13 | Avaya Inc. | User interface for managing communication sessions |
US8407075B2 (en) | 2010-06-25 | 2013-03-26 | International Business Machines Corporation | Merging calendar entries |
US8577959B2 (en) | 2010-07-01 | 2013-11-05 | Microsoft Corporation | Managing recurring appointments |
US9799004B2 (en) | 2010-07-30 | 2017-10-24 | Avaya Inc. | System and method for multi-model, context-aware visualization, notification, aggregation and formation |
US8634662B2 (en) | 2010-08-25 | 2014-01-21 | Apple Inc. | Detecting recurring events in consumer image collections |
US20130018667A1 (en) | 2011-07-11 | 2013-01-17 | ClearCare, Inc. | Measuring Outcomes Via Telephony |
US20120150784A1 (en) | 2010-12-11 | 2012-06-14 | Microsoft Corporation | Immersive Planning of Events Including Vacations |
US20120331378A1 (en) | 2011-06-22 | 2012-12-27 | Digitalviews, Inc. | System and method for timeline visualization and interaction |
US10984387B2 (en) | 2011-06-28 | 2021-04-20 | Microsoft Technology Licensing, Llc | Automatic task extraction and calendar entry |
US20130010575A1 (en) | 2011-07-07 | 2013-01-10 | International Business Machines Corporation | Systems and methods of managing electronic calendar applications |
US9424393B2 (en) * | 2011-07-21 | 2016-08-23 | Emergent Health Care Solutions, Llc | Method, apparatus, and system for reading, processing, presenting, and/or storing electronic medical record information |
US9292521B1 (en) * | 2011-10-20 | 2016-03-22 | Amazon Technologies, Inc. | Archiving and querying data updates associated with an electronic catalog system |
US10504561B2 (en) | 2011-12-12 | 2019-12-10 | Corel Corporation | Media editing system and method with linked storyboard and timeline |
US20130159875A1 (en) | 2011-12-14 | 2013-06-20 | Microsoft Corporation | Graphical user interface to facilitate selectable presentation point of message list |
US20130159198A1 (en) | 2011-12-19 | 2013-06-20 | Oracle International Corporation | Project mapper |
US20130227462A1 (en) * | 2012-02-24 | 2013-08-29 | Htc Corporation | Dual time zone view and weather application in electronic device |
US20150205491A1 (en) | 2012-04-18 | 2015-07-23 | Google Inc. | Systems and methods for emphasizing calendar events |
US20130335419A1 (en) | 2012-06-13 | 2013-12-19 | Bank Of America | Consumer history graphics |
US20140012574A1 (en) | 2012-06-21 | 2014-01-09 | Maluuba Inc. | Interactive timeline for presenting and organizing tasks |
US20140101189A1 (en) | 2012-10-04 | 2014-04-10 | EuroSmartz Ltd. | Using calendar events to modify notification and alert behavior, system and method |
US9288275B2 (en) | 2012-10-11 | 2016-03-15 | ThistleWorks | Computer implemented event-centric social networking platform |
US9250781B2 (en) | 2012-10-17 | 2016-02-02 | Sap Se | Method and device for navigating time and timescale using movements |
WO2014064863A1 (en) | 2012-10-22 | 2014-05-01 | Necカシオモバイルコミュニケーションズ株式会社 | Device for processing information, and method and program for managing chronological information |
US10387480B2 (en) | 2012-11-08 | 2019-08-20 | Lance M. King | Systems and methods for a scalable, collaborative, real-time, graphical life-management interface |
US9268833B2 (en) | 2012-12-05 | 2016-02-23 | Microsoft Technology Licensing, Llc | Recurring calendar item master and instance synchronization |
KR102085225B1 (en) | 2012-12-05 | 2020-03-05 | 삼성전자주식회사 | User terminal apparatus and contol method thereof |
US9009803B2 (en) | 2012-12-20 | 2015-04-14 | Capsoole, Inc. | Method and system for planning and management of digital events |
US8537983B1 (en) | 2013-03-08 | 2013-09-17 | Noble Systems Corporation | Multi-component viewing tool for contact center agents |
GB2513836A (en) * | 2013-03-15 | 2014-11-12 | Taptron Ltd | Automated diary population II |
US10255573B2 (en) | 2013-03-15 | 2019-04-09 | WebINTENSIVE Software, LLC | Systems, methods, and media for presenting interactive checklists |
US20140310045A1 (en) | 2013-04-16 | 2014-10-16 | Go Daddy Operating Company, LLC | Generating and Displaying a Calendar Event Recurrence Preview |
US9773231B2 (en) | 2013-05-29 | 2017-09-26 | Evernote Corporation | Content associations and sharing for scheduled events |
US20140365107A1 (en) * | 2013-06-08 | 2014-12-11 | Apple Inc. | Specifying Travel Times for Calendared Events |
US10915868B2 (en) * | 2013-06-17 | 2021-02-09 | Microsoft Technology Licensing, Llc | Displaying life events while navigating a calendar |
US20150178260A1 (en) * | 2013-12-20 | 2015-06-25 | Avaya, Inc. | Multi-layered presentation and mechanisms for collaborating with the same |
US9691105B2 (en) | 2014-04-16 | 2017-06-27 | Sap Se | Analyzing calendar to generate financial information |
US11200542B2 (en) * | 2014-05-30 | 2021-12-14 | Apple Inc. | Intelligent appointment suggestions |
US10037512B2 (en) | 2014-05-30 | 2018-07-31 | Apple Inc. | Calendar event completion |
US20150370462A1 (en) | 2014-06-20 | 2015-12-24 | Microsoft Corporation | Creating calendar event from timeline |
US10650033B2 (en) * | 2017-06-08 | 2020-05-12 | Microsoft Technology Licensing, Llc | Calendar user interface search and interactivity features |
WO2019178676A1 (en) * | 2018-03-23 | 2019-09-26 | Avigilon Corporation | Method and system for interfacing with a user to facilitate an image search for an object-of-interest |
-
2014
- 2014-09-23 US US14/494,404 patent/US20150370462A1/en not_active Abandoned
- 2014-10-20 US US14/518,425 patent/US20150370440A1/en not_active Abandoned
- 2014-10-20 US US14/518,664 patent/US10656789B2/en active Active
- 2014-10-20 US US14/519,035 patent/US11416115B2/en active Active
- 2014-10-20 US US14/519,089 patent/US9746997B2/en active Active
- 2014-10-20 US US14/518,515 patent/US20150370463A1/en not_active Abandoned
- 2014-10-20 US US14/518,824 patent/US20150370422A1/en not_active Abandoned
- 2014-10-21 US US14/520,293 patent/US20150370464A1/en not_active Abandoned
-
2015
- 2015-04-22 TW TW104112935A patent/TW201602930A/en unknown
- 2015-04-23 TW TW104113083A patent/TW201602889A/en unknown
- 2015-04-23 TW TW104113082A patent/TW201600980A/en unknown
- 2015-05-20 TW TW104116122A patent/TW201602932A/en unknown
- 2015-05-20 TW TW104116092A patent/TW201601081A/en unknown
- 2015-05-20 TW TW104116127A patent/TW201606663A/en unknown
- 2015-05-20 TW TW104116117A patent/TW201602931A/en unknown
- 2015-05-20 TW TW104116135A patent/TW201606664A/en unknown
- 2015-06-19 WO PCT/US2015/036564 patent/WO2015196004A1/en active Application Filing
- 2015-06-19 CN CN201580033344.5A patent/CN106796684A/en not_active Withdrawn
- 2015-06-19 WO PCT/US2015/036571 patent/WO2015196009A1/en active Application Filing
- 2015-06-19 WO PCT/US2015/036569 patent/WO2015196007A1/en active Application Filing
- 2015-06-19 CN CN201580033143.5A patent/CN106462834B/en active Active
- 2015-06-19 EP EP15733972.2A patent/EP3158516A1/en not_active Withdrawn
- 2015-06-19 WO PCT/US2015/036563 patent/WO2015196003A1/en active Application Filing
- 2015-06-19 WO PCT/US2015/036565 patent/WO2015196005A1/en active Application Filing
- 2015-06-19 WO PCT/US2015/036568 patent/WO2015196006A2/en active Application Filing
- 2015-06-19 EP EP15736089.2A patent/EP3158517A1/en not_active Ceased
- 2015-06-19 WO PCT/US2015/036570 patent/WO2015196008A1/en active Application Filing
Patent Citations (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070182763A1 (en) * | 1991-12-20 | 2007-08-09 | Venolia Daniel S | Zooming controller |
US20070209019A1 (en) * | 2002-06-06 | 2007-09-06 | Maria Kaval | Method and device for displaying data |
US20040109137A1 (en) * | 2002-12-04 | 2004-06-10 | Bubie Walter C. | Streamlined methods and systems for scheduling and handling digital cinema content in a multi-theatre environment |
US20060279628A1 (en) * | 2003-09-12 | 2006-12-14 | Fleming Hayden G | Streaming non-continuous video data |
US20050108253A1 (en) * | 2003-11-17 | 2005-05-19 | Nokia Corporation | Time bar navigation in a media diary application |
US20050262450A1 (en) * | 2004-05-21 | 2005-11-24 | Volker Sauermann | System and method for controlling a display of data |
US20080034047A1 (en) * | 2006-08-07 | 2008-02-07 | Rosenberg Gregory A | Calendar event, notification and alert bar embedded within mail |
US20080082925A1 (en) * | 2006-09-29 | 2008-04-03 | Microsoft Corporation | Bifocal view: a novel calendar user interface |
US20140033025A1 (en) * | 2007-12-06 | 2014-01-30 | Adobe Systems Incorporated | Displaying a text-based description of digital content in a sub-frame |
US20110167369A1 (en) * | 2010-01-06 | 2011-07-07 | Van Os Marcel | Device, Method, and Graphical User Interface for Navigating Through a Range of Values |
US20110202879A1 (en) * | 2010-02-15 | 2011-08-18 | Research In Motion Limited | Graphical context short menu |
US20110252351A1 (en) * | 2010-04-09 | 2011-10-13 | Calamander Inc. | Systems and methods for consuming, sharing, and synchronizing time based information |
US20130055106A1 (en) * | 2010-12-16 | 2013-02-28 | Sony Ericsson Mobile Communications Ab | Calendar Application for Communication Devices |
US20120262472A1 (en) * | 2011-04-13 | 2012-10-18 | Honeywell International Inc. | Heatmap timeline for visualization of time series data |
US20130024206A1 (en) * | 2011-07-21 | 2013-01-24 | D & R Software Ii, Llc | Method, apparatus, and system for reading, processing, presenting, and/or storing electronic medical record information |
US20140082536A1 (en) * | 2011-09-16 | 2014-03-20 | Ciprian Costa | Scheduling Events on an Electronic Calendar Utilizing Fixed-positioned Events and a Draggable Calendar Grid |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10656789B2 (en) | 2014-06-20 | 2020-05-19 | Microsoft Technology Licensing, Llc | Locating event on timeline |
US11416115B2 (en) | 2014-06-20 | 2022-08-16 | Microsoft Technology Licensing, Llc | Search and locate event on calendar with timeline |
US20180150650A1 (en) * | 2015-01-30 | 2018-05-31 | The Diary Corporation | System and method for controlling permissions for selected recipients by owners of data |
Also Published As
Publication number | Publication date |
---|---|
TW201602931A (en) | 2016-01-16 |
EP3158516A1 (en) | 2017-04-26 |
TW201602889A (en) | 2016-01-16 |
US20150370904A1 (en) | 2015-12-24 |
WO2015196004A1 (en) | 2015-12-23 |
US20150370464A1 (en) | 2015-12-24 |
WO2015196007A1 (en) | 2015-12-23 |
TW201606664A (en) | 2016-02-16 |
WO2015196009A1 (en) | 2015-12-23 |
EP3158517A1 (en) | 2017-04-26 |
CN106462834B (en) | 2020-10-02 |
US10656789B2 (en) | 2020-05-19 |
WO2015196003A1 (en) | 2015-12-23 |
TW201601081A (en) | 2016-01-01 |
TW201600980A (en) | 2016-01-01 |
TW201606663A (en) | 2016-02-16 |
WO2015196008A1 (en) | 2015-12-23 |
WO2015196006A2 (en) | 2015-12-23 |
US20150372829A1 (en) | 2015-12-24 |
US11416115B2 (en) | 2022-08-16 |
TW201602930A (en) | 2016-01-16 |
US20150370462A1 (en) | 2015-12-24 |
US20150370422A1 (en) | 2015-12-24 |
WO2015196006A3 (en) | 2016-02-18 |
US9746997B2 (en) | 2017-08-29 |
US20150370463A1 (en) | 2015-12-24 |
WO2015196005A1 (en) | 2015-12-23 |
TW201602932A (en) | 2016-01-16 |
CN106796684A (en) | 2017-05-31 |
US20150370421A1 (en) | 2015-12-24 |
CN106462834A (en) | 2017-02-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20150370440A1 (en) | Managing event on calendar with timeline | |
US10725622B2 (en) | Providing attachment control to manage attachments in conversation | |
US10198411B2 (en) | Storing additional document information through change tracking | |
US20160140139A1 (en) | Local representation of shared files in disparate locations | |
US20160173541A1 (en) | Presentation of content from within spreadsheet application | |
AU2012302454B2 (en) | Schedule managing method and apparatus | |
CN107408242B (en) | Providing interactive previews of content within communications | |
US11275486B2 (en) | Restructuring view of messages based on configurable persistence | |
US20180374057A1 (en) | Interaction with and visualization of conflicting calendar events | |
US9571595B2 (en) | Employment of presence-based history information in notebook application | |
US10296190B2 (en) | Spatially organizing communications | |
US20170168654A1 (en) | Organize communications on timeline |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: MICROSOFT CORPORATION, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:JOSHI, NEEL;BOONE, JEANNINE;LI, JOAN;AND OTHERS;SIGNING DATES FROM 20141012 TO 20141014;REEL/FRAME:033982/0909 |
|
AS | Assignment |
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034819/0001 Effective date: 20150123 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |