Search and locate event on calendar with timeline

Abstract

Searching and locating an event on a calendar with a timeline is provided. An application such as a calendar application detects a search on the calendar or the timeline. One or more events are located on the calendar or on the timeline that match a search term of the search. The search term on the one or more events is highlighted. The one or more events with the search term that is highlighted are displayed on the calendar or the timeline.

Description

BACKGROUND

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.

SUMMARY

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 searching and locating an event on a calendar with a timeline. In some example embodiments, a calendar application may detect a search on the calendar. One or more events may be located on the calendar that match a search term of the search. The search term may be highlighted on the one or more events. The one or more events may be displayed with the search term that is highlighted on the calendar.

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.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a conceptual diagram illustrating an example of searching and locating an event on a calendar with a timeline, according to embodiments;

FIG. 2 illustrates an example of a search on a calendar, according to embodiments;

FIG. 3 illustrates an example of a search on a timeline, according to embodiments;

FIG. 4 illustrates an example of an event peek on a search result displayed on a timeline, according to embodiments;

FIG. 5 is a simplified networked environment, where a system according to embodiments may be implemented;

FIG. 6 illustrates a general purpose computing device, which may be configured to search and locate an event on a calendar with a timeline; and

FIG. 7 illustrates a logic flow diagram for a process to search and locate an event on a calendar with a timeline, according to embodiments.

DETAILED DESCRIPTION

As briefly described above, an event may be searched and located on a calendar with a timeline by a calendar application. The calendar application may detect a search on the calendar. One or more events may be located on the calendar that match a search term of the search. The search term may be highlighted on the one or more events. The one or more events may be displayed with the search term that is highlighted on the calendar.

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 search and locate 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 searching and locating an event on a calendar with a timeline, according to embodiments.

In a diagram 100, 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 also be presented as a stand-alone component. 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 search and locate an event. The event may be displayed on the calendar and duplicated on the timeline 120.

While the example system in 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 search on a calendar, according to embodiments.

In a diagram 200, a calendar application 202 that displays a calendar 222 used to search and locate an event may be described. The calendar application 202 may display a search tool 204 to allow a user to conduct a search on the calendar 222. The search tool may provide text box to receive a search term 203. The search tool 204 may also provide a search control to initiate the search. The search term 203 may include a title, a subject, a summary, a description, a label, among other attributes associated with one or more events displayed on the calendar 222. The search term 203 may include one or more categories, one or more attendees, one or more groups, a content of one or more documents associated with one or more events displayed on the calendar 222.

In response to an activation of the search control, the calendar application 202 may match the search term 203 (input by an external entity) in the search tool 204 to an attribute of one or more events in the calendar 222. Events (216, 218) may have subjects that include the search term 203. The calendar application 202 may match the search term to the events (216, 218). The search term 203 may be highlighted on the events (216, 218). The events (216, 218) that match the search term 203 may be displayed with the search term 203 highlighted on the events (216, 218) Other events such as an event 214 that do not match the search term 203 may be hidden. The calendar application 202 may render the event 214 as transparent compared to the events (216, 218) to emphasize the event 214 failing to match the search term 203.

The search term 203 may be shared with an authorized external entity. The authorized external entity may include a user, a social network, a service, an application, among others. The events (216, 218) that match the search term 203 may also be shared with the external entity. An example scenario may include insertion of the events (216, 218) into a web page associated with an authorized web application to provide the events (216, 218) to authorized external entities that access the web page.

The calendar application 202 may also display additional controls associated with the calendar 222. A date picker component 205 may allow a user to select a date from a displayed range. The selected date may be displayed in the calendar 222 that shows the date within a date range that is configurable. The date range of the calendar 222 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 222 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 222 to show one or more events that last during a time unit such as a day.

The calendar 222 may also 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.

FIG. 3 illustrates an example of a search on a timeline, according to embodiments.

In a diagram 300, a calendar application 302 may display a timeline 320 to provide events in a linear presentations. The timeline 320 may be displayed stand-alone or in conjunction with a calendar. The events displayed in the timeline 320 may be duplicates of events stored in the calendar. In addition, the timeline 320 may display a date range of events that may be scrollable through a scroll control 324. The date range may be presented with a date range label 322. The date range may be partitioned based on time units such as an hour, a day 328, 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 calendar application 302 may provide a search control 304 that provides a text box to input a search term and a search control to initiate the search. In response to an activation of the search control, the search term may be matched to attributes of the events displayed on the timeline 320. The events (316, 318) that match the search term may be displayed with the search term highlighted on the events (316, 318). Events that fail to match to search term may be hidden through a transparent rendering or another scheme. A current date label 314 may also be displayed on the timeline 320 in response to a detection that a date range of the events (316, 318), that match the search term, may include a current date. The search term and the events (316, 318) may be shared with an authorized external entity that includes a user, a social network, a service, an application, among others.

The calendar application 302 may also display one or more people selection controls 306 that select a subset of events displayed on the timeline associated with one or more users. Each one of the one or more people selection controls may correspond to a user associated with the calendar application 302. The calendar application 302 may detect an activation of one of the people selection controls 306. A subset of the events (316, 318) may be displayed on the timeline 320, where the subset is associated with the user represented by the selected people selection control. A remaining or non-selected subset of the events may be hidden through a transparency rendering, or another scheme. Alternatively, an activation of one of the people selection controls 306 may cause the calendar application 302 to share the events (316, 318) that match the search term and the search term with the user associated with the activated people selection control.

The calendar application 302 may also display a time range control 308. The time range control 308 may allow for input of a start date and end date of a date range to display on the timeline 320. In response to detecting input of an expansionary time range on the time range control 308, the search may be expanded to include additional events based on the time range encompassing the events (316, 318) and additional events outside the dates of the events (316, 318). In response to detecting input of a contractionary time range on the time range control 308, the search may be narrowed to include a subset of the events (316, 318) based on which of the events (316, 318) are encompassed by the contractionary time range.

FIG. 4 illustrates an example of an event peek on a search result displayed on a timeline, according to embodiments.

In a diagram 400, an event peek 404 may be displayed in response to a selection of an event 418 by the calendar application 402. The events (416, 418) may be displayed with a search term highlighted to illustrate the matched events. The calendar application 402 may detect a selection action on an event 418 that matches the search term. The event peek display 404 may be displayed in response to the selection action. A title of the event 418, a location of the event 418, a time of the event 418, a description of the event 418, a creator of the event 418, among other attributes of the event 418 may be displayed on the event peek 404. A map of the location of the event 418 may also be displayed in the event peek 404.

The event peek 404 may be displayed based on a duration of the selection action. An example may include displaying the event peek 404 during a hover action by a mouse input, a touch based input, among other input types. Alternatively, the event peek 404 may be displayed in a persistent state that may be dismissed by an additional input.

The technical advantage of searching and locating an event on a calendar with a timeline may be improved usability and enhanced reliability of display devices in providing event search, and location, among other features compared to static event presentation based solutions.

The example scenarios and schemas in FIG. 1 through 4 are shown with specific components, data types, and configurations. Embodiments are not limited to systems according to these example configurations. Searching and locating 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 4 and their subcomponents may be implemented in a similar manner with other values using the principles described herein.

FIG. 5 is an example networked environment, where embodiments may be implemented. A calendar application configured to search and locate an event on a calendar with a timeline may be implemented via software executed over one or more servers 514 such as a hosted service. The platform may communicate with client applications on individual computing devices such as a smart phone 513, a laptop computer 512, or desktop computer 511 (‘client devices’) through network(s) 510.

Client applications executed on any of the client devices 511-513 may facilitate communications via application(s) executed by servers 514, or on individual server 516. A calendar application may search and locate one or more events of a calendar or a timeline that match a search term of a search. One or more events with the search term may be displayed with the search term highlighted on the one or more events. The calendar application may store data associated with the calendar and the timeline in data store(s) 519 directly or through database server 518.

Network(s) 510 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) 510 may include secure networks such as an enterprise network, an unsecure network such as a wireless open network, or the Internet. Network(s) 510 may also coordinate communication over other networks such as Public Switched Telephone Network (PSTN) or cellular networks. Furthermore, network(s) 510 may include short range wireless networks such as Bluetooth or similar ones. Network(s) 510 provide communication between the nodes described herein. By way of example, and not limitation, network(s) 510 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 search and locate an event on a calendar with a timeline. Furthermore, the networked environments discussed in FIG. 5 are for illustration purposes only. Embodiments are not limited to the example applications, modules, or processes.

FIG. 6 illustrates a general purpose computing device, which may be configured to search and locate an event on a calendar with a timeline, arranged in accordance with at least some embodiments described herein.

For example, the computing device 600 may be used to search and locate an event on a calendar with a timeline. In an example of a basic configuration 602, the computing device 600 may include one or more processors 604 and a system memory 606. A memory bus 608 may be used for communication between the processor 604 and the system memory 606. The basic configuration 602 may be illustrated in FIG. 6 by those components within the inner dashed line.

Depending on the desired configuration, the processor 604 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 604 may include one more levels of caching, such as a level cache memory 612, a processor core 614, and registers 616. The processor core 614 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 618 may also be used with the processor 604, or in some implementations, the memory controller 618 may be an internal part of the processor 604.

Depending on the desired configuration, the system memory 606 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 606 may include an operating system 620, a calendar application 622, and a program data 624. The calendar application 622 may search and locate one or more events of a calendar or a timeline that match a search term of a search. One or more events with the search term may be displayed with the search term highlighted on the one or more events. Components of the calendar application 622 (such as a user interface) may also be displayed on a display device associated with the computing device 600. An example of the display device may include a hardware screen that may be communicatively coupled to the computing device 600. 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 622 such as the calendar and the timeline, displayed by the touch based device. The program data 624 may include, among other data, a timeline data 628, or the like, as described herein. The timeline data 628 may include the event, subject name of the event, the event date, among others.

The computing device 600 may have additional features or functionality, and additional interfaces to facilitate communications between the basic configuration 602 and any desired devices and interfaces. For example, a bus/interface controller 630 may be used to facilitate communications between the basic configuration 602 and one or more data storage devices 632 via a storage interface bus 634. The data storage devices 632 may be one or more removable storage devices 636, one or more non-removable storage devices 638, 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 606, the removable storage devices 636, and the non-removable storage devices 638 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 600. Any such computer storage media may be part of the computing device 600.

The computing device 600 may also include an interface bus 640 for facilitating communication from various interface devices (for example, one or more output devices 642, one or more peripheral interfaces 644, and one or more communication devices 666) to the basic configuration 602 via the bus/interface controller 630. Some of the example output devices 642 may include a graphics processing unit 648 and an audio processing unit 650, which may be configured to communicate to various external devices, such as a display or speakers via one or more A/V ports 652. One or more example peripheral interfaces 644 may include a serial interface controller 654 or a parallel interface controller 656, 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 658. An example communication device 666 may include a network controller 660, which may be arranged to facilitate communications with one or more other computing devices 662 over a network communication link via one or more communication ports 664. The one or more other computing devices 662 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 600 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 600 may also be implemented as a personal computer including both laptop computer and non-laptop computer configurations.

Example embodiments may also include searching and locating 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. 7 illustrates a logic flow diagram for a process to search and locate an event on a calendar with a timeline, according to embodiments. Process 700 may be implemented on a calendar application.

Process 700 begins with operation 710, where a search on the calendar may be detected. At operation 720, one or more events on the calendar may be located that match a search term of the search. The search term on the one or more events may be highlighted at operation 730. At operation 740, the one or more events with the search term that is highlighted may be displayed on the calendar.

The operations included in process 700 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 search and locate an event on a calendar with a timeline may be described. The method may include detecting a search on the calendar, locating one or more events on the calendar that match a search term of the search, highlighting the search term on the one or more events, and displaying the one or more events with the search term that is highlighted on the calendar.

According to other examples, the method may further include detecting the search term to include one or more from a set of: one or more categories, one or more attendees, one or more groups, a content of one or more documents associated with the one or more events. The search term may be matched to one or more from a set of: a title, a subject, a summary, a description, and a label of the one or more events. Other events that do not match the search term may be detected and the other events may be hidden. A time range control may be provided to expand the search to include additional events based on the time range encompassing the one or more events and the additional events. A time range control may be provided to narrow the search to include a subset of the one or more events based on the time range encompassing the subset. The search term may be shared with an authorized external entity that includes one or more from a set of: a user, a social network, a service, and an application and the one or more events may be shared with the authorized external entity.

According to further examples, the method may further include locating one or more events on a timeline of the calendar that match the search term of the search, wherein the one or more events on the timeline are duplicates of the one or more events on the calendar. The search term may be highlighted on the one or more events on the timeline and the one or more events may be displayed on the timeline with the search term that is highlighted. A current date may be displayed label on the timeline, in response to detecting the one or more events on the timeline to be within a date range of the timeline that includes a current date. Other events may be detected on the timeline that do not match the search term of the search and the other events may be hidden on the timeline.

According to some examples, a computing device to search and discover 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 detect a search on the calendar, locate one or more events on the calendar and one or more events on a timeline of the calendar that match a search term of the search, wherein the one or more events on the timeline are duplicates of the one or more events on the calendar, highlight the search term on the one or more events on the calendar and the one or more events on the timeline, and display the one or more events on the calendar and the one or more events on the timeline with the search term that is highlighted on the calendar, on the display device.

According to other examples, the calendar application is further configured to detect a selection action on one of the one or more events on the timeline, display an event peek, on the display device, and display one or more from a set of: a title of the event, a location of the event, a time of the event, a description of the event, and a creator of the event in the event peek, on the display device. One or more people selection controls that select a subset of the one or more events on the timeline associated with a user may be displayed, on the display device. The calendar application is further configured to detect an activation of one of the one or more people selection controls, display the subset of the one or more events on the timeline, wherein the subset is associated with the user represented by the people selection control, and hide a non-selected subset of the one or more events. The calendar application is further configured to detect an activation of one of the one or more people selection controls and share the subset of the one or more events on the timeline associated with the user represented by the people selection control.

According to some examples, a computer-readable memory device with instructions stored thereon to search and locate 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 detecting a search on the calendar, a means for locating one or more events on the calendar that match a search term of the search, a means for highlighting the search term on the one or more events, and a means for displaying the one or more events with the search term that is highlighted on the calendar.

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

1. A method executed on a computing device to search and locate an event on a calendar with a timeline, the method comprising: providing a user interface displaying a calendar view and a scrollable timeline, the calendar view displaying a plurality of events within a grid representation of a first plurality of dates and the scrollable timeline displaying at least one of the plurality of events within a linear representation of a second plurality of dates, wherein the first plurality of dates is different from the second plurality of dates;providing a search tool with a text input element;detecting an input of a search term into the text input element; andin response to detecting the input of the search term, locating an event included in the plurality of events matching the search term, wherein one or more of a title, a subject, a summary, a description, or a label of the event matches the search term, andtransforming the user interface, wherein the transformation comprises highlighting the search term on the located event as displayed on both the calendar view and the scrollable timeline.

2. The method of claim 1, further comprising: detecting the search term to include one or more from a set of a category, an attendee, a group, a content of a document associated with the event.

3. The method of claim 1, further comprising, in response to detecting the input of the search term: detecting a second event included in the plurality of events that does not match the search term; andtransforming the user interface to hide the second event within both the calendar view and the scrollable timeline.

4. The method of claim 1, further comprising: providing a time range control to set a time range for locating the event.

5. The method of claim 1, further comprising: sharing the search term with an authorized external entity that includes one or more from a set of: a user, a social network, a service, and an application; andsharing the event with the authorized external entity.

6. The method of claim 1, further comprising: providing a current date label on the scrollable timeline.

7. A computing device to search and locate an event, the computing device comprising: a memory;a processor coupled to the memory, the processor, via executing a calendar application in conjunction with instructions stored in the memory, configured to:provide a user interface displaying a calendar view and a scrollable timeline, the calendar view displaying a plurality of events within a grid representation of a first plurality of dates and the scrollable timeline displaying at least one of the plurality of events within a linear representation of a second plurality of dates, wherein the first plurality of dates is different from the second plurality of dates;provide a search tool with a text input element;detect an input of a search term into the text input element; andin response to detecting the input of the search term, locate a first event included in the plurality of events matching the search term, wherein one or more of a title, a subject, a summary, a description, or a label of the first event matches the search term;detect a second event included in the plurality of events falling within at least one of the first plurality of dates and the second plurality of dates that does not match the search term, andtransform the user interface, wherein the transformation comprises highlighting the search term on the located first event as displayed on both the calendar view and the scrollable timeline, and the detected second event is hidden from at least one of the calendar view and the scrollable timeline on the transformed user interface.

8. The computing device of claim 7, wherein the processor is further configured to: detect a selection action on the first event on the scrollable timeline; andprovide an event peek in response to the selection action.

9. The computing device of claim 8, wherein the processor is further configured to: provide one or more from a set of: the title of the first event, a location of the first event, a time of the first event, the description of the first event, and a creator of the first event in the event peek.

10. The computing device of claim 7, wherein the processor is further configured to: provide a person selection control.

11. The computing device of claim 10, wherein the processor is further configured to: detect an activation of the person selection control; andin response to detecting the activation of the person selection control, provide the first event on the scrollable timeline when the first event is associated with the user represented by the person selection control.

12. The computing device of claim 10, wherein the processor is further configured to: detect an activation of the person selection control; andin response to detecting the activation of the person selection control, share the first event with a user represented by the person selection control.

13. A non-transitory computer-readable memory device with instructions stored thereon to search and locate an event, the instructions comprising: providing a user interface displaying a calendar view and a scrollable timeline, the calendar view displaying a plurality of events within a grid representation of a first plurality of dates and the scrollable timeline displaying at least one of the plurality of events within a linear representation of a second plurality of dates, wherein the first plurality of dates is different from the second plurality of dates;providing a search tool with a text input element;detecting an input of a search term into the text input element;locating an event included in the plurality of events matching the search term, wherein one or more of a title, a subject, a summary, a description, or a label of the event matches the search term;transforming the user interface, wherein the transformation comprises highlighting the search term on the located event as displayed on both the calendar view and the scrollable timeline;detecting an activation of a people selection control; andin response to detecting the activation of the people selection control, sharing the located event with one or more users associated with the people selection control.

14. The non-transitory computer-readable memory device of claim 13, wherein the instructions further comprise: detecting a selection action on the event on the scrollable timeline; andin response to detecting the selection action, providing one or more from a set of: the title of the event, a location of the event, a time of the event, the description of the event, and a creator of the event in an event peek.

15. The non-transitory computer-readable memory device of claim 13, wherein the instructions further comprise: providing a time range control to set a time range for locating the event matching the search term.