Viewing effects of proposed change in document before committing change

A tweak and view mode may be used by a user to see an effect of a proposed change to a document before the change is committed to the document. The application may automatically navigate to different portions of the document and/or display different sections of the document. Instead of the user having to search for the portion of the document affected by the change, the changed portions are determined for the user. The portions may be automatically displayed to the user and/or the user may determine when to move to each different portion that changed as a result of the proposed change. The proposed change may be accepted/rejected by the user. For example, a User Interface (UI) element may be selected by the user to either accept the change or reject the change.

BACKGROUND

Viewing the effects of possible changes to a document (e.g. a spreadsheet) can be difficult. For example, if a user wants to see how a possible change affects a document, the user may make a copy of the document and make a change to the copy of the document to see how changes affect a document. Viewing proposed changes to a document that is shared between users can be even more challenging.

SUMMARY

A tweak and view mode may be used by a user to see an effect of a proposed change on a document before the change is committed to the document. The change may affect one or more portions of the document. For example, a change to a value in a cell of a spreadsheet may affect one or more charts, cells and/or other objects that are associated with the spreadsheet. Instead of the user having to search for the portion(s) of the document affected by the change, the changed portions may be determined for the user. The portions may be automatically displayed to the user and/or the user may determine when to move to each different portion that changed as a result of the proposed change. For example, in response to changing one or more values within one portion of the document, the application may show one or more graphs that changed and/or show a comparison of each portion. The proposed change may be accepted/rejected by the user. For example, a User Interface (UI) element may be selected by the user to either accept the change or reject the change.

DETAILED DESCRIPTION

Referring now to the drawings, in which like numerals represent like elements, various embodiment will be described.

FIG. 1shows a system for using a tweak and view mode before committing a change to a document. As illustrated, system100includes application110, change manager26and touch screen input display115.

In order to facilitate communication with the change manager26, one or more callback routines, may be implemented. According to an embodiment, application110is a business productivity application, such as a spreadsheet application, that is configured to receive input from a touch-sensitive input display115and/or keyboard input (e.g. a physical keyboard and/or SIP) and/or other types of input (e.g. speech and/or some other input sensing). For example, change manager26may provide information to application110in response to a user's input such as editing a cell, selecting an element to edit a value, and the like.

System100as illustrated comprises a touch screen input display115that detects when a touch input has been received (e.g. a finger touching or nearly touching the touch screen). Display115may detect input, such as: a pinch gesture; a stretch gesture; a select gesture (e.g. a tap action on a displayed element); a select and hold gesture (e.g. a tap and hold gesture received on a displayed element); a swiping action and/or dragging action and/or double tap; and the like. Any type of touch screen may be utilized that detects a user's touch input. For example, the touch screen may include one or more layers of capacitive material that detects the touch input. Other sensors may be used in addition to or in place of the capacitive material. For example, Infrared (IR) sensors may be used. According to an embodiment, the touch screen is configured to detect objects that in contact with or above a touchable surface. Although the term “above” is used in this description, it should be understood that the orientation of the touch panel system is irrelevant. The term “above” is intended to be applicable to all such orientations. The touch screen may be configured to determine locations of where touch input is received (e.g. a starting point, intermediate points and an ending point). Actual contact between the touchable surface and the object may be detected by any suitable means, including, for example, by a vibration sensor or microphone coupled to the touch panel. A non-exhaustive list of examples for sensors to detect contact includes pressure-based mechanisms, micro-machined accelerometers, piezoelectric devices, capacitive sensors, resistive sensors, inductive sensors, laser vibrometers, and LED vibrometers.

Change manager26is configured to enter/exit a tweak and view mode that may be used by a user to see an effect of a proposed change on a document before the change is committed to the document. The change may affect one or more portions of the document.

In the current example, display115shows that the “Tweak and View Mode is Enabled” that provides an indication to the user that any changes made to the current spreadsheet, are not committed (e.g. saved) to the spreadsheet until a confirmation of commitment is received. As illustrated, a user has changed three cells to include values 0.01, 0.14, and 0.20. The changed values may/may not be distinguished from unchanged values (e.g. bolded, highlighted, line drawn around values, . . . ). When the user would like to see how the changes affected other parts of the spreadsheet, the user may select to view the changes (e.g. selecting a user interface element, saying a command, performing a gesture, and the like). For example, a change to a value in a cell of the spreadsheet may affect one or more charts and/or other objects that are associated with the spreadsheet. Instead of the user having to search for the portion of the document affected by the change, the changed portions may be determined for the user.

In response to selecting to view the changes, display115is updated as shown in display115′. The portions showing the changed portion(s) may be automatically displayed to the user and/or the user may determine when to move to each different portion that changed as a result of the proposed change. In the current example, change manager26instructs the application to show a comparison of the data before the change (Profit(old) in table120and graph122) to data after the change (Profit(new) in table120and graph124). Other display methods may be used to show the changed portions. For example, each portion of the document affected by the change may be shown independently without a comparison of data. According to an embodiment, a ordering is made as to what portion of the document was affected by the change more than other portions of the document. The ordering may be used when displaying the changed portions to the user.

The proposed change(s) may be accepted/rejected by the user. For example, a User Interface (UI) element126may be selected by the user to either accept the change or reject the change. More details and examples regarding the tweak and view mode are provided below.

FIG. 2shows making and viewing proposed changes using a comparison view while in a tweak and view mode. As illustrated,FIG. 2includes three different displays (210,220and230) that illustrate before making a proposed change(s), making a proposed change(s) and viewing the proposed change(s) while in tweak and view mode.

The displays may be shown on displays having a standard/large display (e.g. displays larger than 12 inches) as well as a device having a limited display size (e.g. a cell phone having a display of approximately 2 by 3 inches, a slate/tablet having approximately a 7-10 inch display, and/or other devices having other display sizes (e.g. 4, 5, 6, . . . ). The displays may also be shown on a touch screen.

Display210shows a display of content (e.g. spreadsheet data) before a proposed change is entered (e.g. a first version state). In the current example, the user has entered the tweak and view mode (e.g. by saying a command, selecting a UI element, performing a gesture, . . . ) but has not yet made a proposed change.

Display220shows the display of spreadsheet data after proposed changes are made (e.g. a second version state). In the current example, the user has changed value 0.02 to 0.01, value 0.15 to 0.14 and value 0.08 to 0.20 in the predicted sales column. More/fewer changes may be made. Proposed changes may also be made in portions of the document not currently shown on the display. The proposed changes may/may not be distinguished from the other data in the document (e.g. bolded, highlighted, line drawn around values, . . . ). In the current example, the proposed changes are bolded. Data affected by the change(s) may also be indicated. For example, the cell including the Profit221that is affected by the change may be displayed differently to show that it is affected by the proposed change.

Display230shows a view of different portion of the document showing the proposed changes. Display230shows a comparison of the data before the change (Profit(old) in table231and graph232) to data after the change (Profit(new) in table231and graph233). Other display methods may be used to show the changed portions (e.g. SeeFIGS. 3 and 4). According to an embodiment, the use selects UI element222to show the changes.

The user may commit the changes to the document or decide not to commit the changes to the document. According to an embodiment, the user make a selection on UI element234to either save the changes or not save the changes. Other methods may be used to commit the changes (e.g. voice command, gesture, . . . ).

FIG. 3shows making and viewing proposed changes while in a tweak and view mode. As illustrated,FIG. 3includes five different displays (310,320,330,335and340) that illustrate before making a proposed change(s), making a proposed change(s) and viewing the proposed change(s) while in tweak and view mode.

Display310shows a display of content (e.g. spreadsheet data) before a proposed change is entered. In the current example, the user has entered the tweak and view mode (e.g. saying a command, selecting a UI element, performing a gesture, . . . ) but has not yet made a proposed change.

Display320shows the display of spreadsheet data after proposed changes are made. In the current example, the user has changed value 0.02 to 0.01, value 0.15 to 0.14 and value 0.08 to 0.20 in the predicted sales column. Profit has changed from $250,000 to $300,000.

Display330shows a portion of the document showing affected by the proposed changes. Display330shows a Predicted Sales graph that changed as a result of the proposed changes.

According to an embodiment, a user may select UI element334to see how the chart appeared before the proposed change was made. Selecting UI element334(or receiving some other command) shows display335that shows the graph before the proposed changes were used. A user may return to the view showing the proposed changes (e.g. UI element337) or save the changes (e.g. UI element336).

A user may also access the next change view (when there are further changed portions to be shown) from display330using Access Next Change332(or receiving some other command) When the access next change is commanded, the display changes to display340.

A user may also access the previous change view (to access a previous change) from display330using Access Previous Change333(or receiving some other command).

Display340shows another portion of the document showing affected by the proposed changes. Display340shows a Profit by Quarter graph that changed as a result of the proposed changes. According to an embodiment, an indication is displayed that there are no further changes. A user may select UI element342According to another embodiment, as discussed with regard to display330, a user view how the graph appeared before the proposed change was made. A user may return to the changes (e.g. UI element337) or save the changes (e.g. UI element336).

FIG. 4shows making and viewing proposed changes while in a tweak and view mode. As illustrated,FIG. 4includes five different displays (410,420,430,435and440) that illustrate before making a proposed change(s), making a proposed change(s) and viewing the proposed change(s) while in tweak and view mode.

Display410shows a display of content (e.g. spreadsheet data) before a proposed change is entered. In the current example, the user has entered the tweak and view mode (e.g. saying a command, selecting a UI element, performing a gesture, . . . ) but has not yet made a proposed change.

Display420shows the display of spreadsheet data after proposed changes are made. In the current example, the user has changed value 0.02 to 0.01, value 0.15 to 0.14 and value 0.08 to 0.20 in the predicted sales column.

Display430shows an overview of different portions of the document showing affected by the proposed changes. Display430shows four different sheets (Sheet 1, Sheet 3, Sheet 5 and Sheet 6) that changed as a result of the proposed changes. According to an embodiment, each thumbnail represents a sheet of a spreadsheet workbook that includes at least one portion affected by the proposed change. According to another embodiment, each thumbnail represents a portion of the content (e.g. 50%, 33%, 16% and the like). The content that is displayed in the thumbnail may be a zoomed out view of the content without changing the actual content, a zoomed out view of a modified view of the content, and/or a representation of the content. When there are larger thumbnails displayed, the content may actually be a zoomed out view of the content. As there are more thumbnails displayed in the view and the thumbnails are smaller, the level of detail in the thumbnail changes. For example, when a bar chart is converted into a thumbnail that occupies roughly half of a limited display device, the display is a zoomed out view without changing the content displayed in the thumbnail. When the size of the thumbnail goes down further, the actual content, which is a chart in this example, is replaced with a graphical icon replacing the content.

While different sheets are shown in display430, the portions of the content may relate to different content. For example, display435shows another example display of portions of a document showing changes.

Display435shows thumbnails for different portions of the document affected by the proposed changes. As shown, each thumbnail includes a representation of the portion of the document. For example, portion1shows data, portion2shows a graph, and portion3shows a graph.

A user may select one of the thumbnails to see a more detailed view of the proposed change. For example, a user may select Sheet 1 in display430by tapping on the sheet. In response to selecting the thumbnails, the display changes to the selected portion.

Display440shows a Predicted Sales graph that is updated in response to the proposed changes. A user may decide to save the changes and/or return to the overview display (e.g. display430/435).

According to an embodiment, a user may perform other gestures to move between the displays. For example, a user may perform a pinch gesture by pulling together his or her index finger and thumb to create a pinching action in order to move from display440to display430/435. A user may perform a stretch gesture by spreading his or her index finger and thumb to create a stretching action in order to move from a thumbnail on display430/435to display440.

FIG. 5shows an illustrative process for making and viewing proposed changes before the changes are committed to the document. When reading the discussion of the routines presented herein, it should be appreciated that the logical operations of various embodiments are implemented (1) as a sequence of computer implemented acts or program modules running on a computing system and/or (2) as interconnected machine logic circuits or circuit modules within the computing system. The implementation is a matter of choice dependent on the performance requirements of the computing system implementing the invention. Accordingly, the logical operations illustrated and making up the embodiments described herein are referred to variously as operations, structural devices, acts or modules. These operations, structural devices, acts and modules may be implemented in software, in firmware, in special purpose digital logic, and any combination thereof.

After a start operation, the process moves to operation510, where content is displayed. The content displayed may be different types of contents. For example, the content may be a spreadsheet, a document, a presentation, images, files, and the like. According to an embodiment, the content is a spreadsheet document that may include one or more sheets in a workbook.

Moving to operation520, a tweak and view mode is entered. Different methods may be used to enter/exit the tweak and view mode. For example, a UI element may be selected, a user may say a command, a user may perform a gesture, and the like. While in the tweak and view mode, a user may make proposed changes and view the portions of the document that are affected by the changes before committing the proposed changes to the document.

Flowing to operation530, one or more proposed changes are received. The proposed change(s) may affect one or more portions of the document. For example, a user may change a value in the document that affected a calculation performed in another portion of the document and also changes how two different objects (e.g. chart/graph/picture) are displayed in other portions of the document. According to an embodiment, the changes are changes to at least one value within a spreadsheet.

Transitioning to operation540, a determination is made as to what portion(s) of the document are affected by the change. The proposed change may affect one or more portions of the document. For example, the proposed changes may affect data in one or more portions of the document as well as one or more graphical objects in one or more portions of the document. According to an embodiment, a calculation is automatically performed that determines an ordering of the portions of the document ranging from more affected to least affected. A portion of a document may be considered to be more affected based on various criteria (e.g. number of data values changed, a size of a displayed object affected by the change (e.g. chart/graph/picture), and the like. According to an embodiment, a user may define an ordering method used (e.g. a graph object before a table object, a table object before data values, and the like). According to an embodiment, the determined ordering is used when displaying the changed portions of the document to the user.

Moving to operation550, the portion(s) of the document affected by the proposed changes are displayed. According to an embodiment, a user input is received indicating that they would like to view the changed portions of the document. The portion(s) may be automatically/manually displayed. For example, a user may manually select/advance through each of the different portions. The application may also automatically display the portions affected by the proposed changes (e.g. predetermined logic). A combination of automatic/manual navigation through the changed portions may also be used. For example, an initial display may be shown from which point specific user commands are received to navigate through the different portions affected by the change.

Flowing to operation560, the user may accept/reject the proposed change(s). For example, a user may select a “save” UI element to commit the changes to the document or select a “do not save” UI element so that the changes are not committed to the document. According to an embodiment, a user may indicate to commit/not commit the proposed changes using other methods (e.g. verbal command, gesture, and the like.

Transitioning to decision operation570, a determination is made as to whether to exit the tweak and view mode. For example, a UI element may be selected, a user may say a command, a user may perform a gesture, and the like to exit the tweak and view mode. When the determination is to not exit the tweak and view mode, the process returns to operation530to receive further proposed change(s). When the determination is to exit the tweak and view mode, the process moves to operation580.

At operation580, the tweak and view mode is exited. When not in tweak and view mode, changes made to the document are committed to the document.

The process then flows to an end operation and returns to processing other actions.

FIG. 6illustrates an exemplary system that may use a tweak and view mode to view proposed changes. As illustrated, system1000includes service1010, data store1045, touch screen input device1050(e.g. a slate), smart phone1030, and display device1080(e.g. monitor/television, . . . ).

Each device (e.g. device1050, smart phone1030, display device) may be configured to receive input from one or more sensing devices. The sensing device may be a part of the device and/or separate from the device. The sensing device may be configured to capture user input using various input methods. A sensing device may include one or more microphones to capture spoken input (e.g. words) and one or more cameras to detect movement of a user (e.g. pictures/videos). The sensing device may also be configured to capture other inputs from a user such as by a keyboard and/or mouse (not pictured). For example, the sensing device may be a MICROSOFT KINECT® device comprising a plurality of cameras and a plurality of microphones

As illustrated, service1010is a cloud based and/or enterprise based service that may be configured to provide spreadsheet services. The service may be configured to be interacted with using different types of input/output. For example, a user may use speech input, touch input, hardware based input, and the like. The service may provide speech output and/or sound effects. Functionality of one or more of the services/applications provided by service1010may also be configured as a client/server based application.

As illustrated, service1010is a multi-tenant service that provides resources1015and services to any number of tenants (e.g. Tenants 1-N). Multi-tenant service1010is a cloud based service that provides resources/services1015to tenants subscribed to the service and maintains each tenant's data separately and protected from other tenant data.

System1000as illustrated comprises a touch screen input device1050(e.g. a slate/tablet device) and smart phone1030that detects when a touch input has been received (e.g. a finger touching or nearly touching the touch screen). Any type of touch screen may be utilized that detects a user's touch input. For example, the touch screen may include one or more layers of capacitive material that detects the touch input. Other sensors may be used in addition to or in place of the capacitive material. For example, Infrared (IR) sensors may be used. According to an embodiment, the touch screen is configured to detect objects that in contact with or above a touchable surface. Although the term “above” is used in this description, it should be understood that the orientation of the touch panel system is irrelevant. The term “above” is intended to be applicable to all such orientations. The touch screen may be configured to determine locations of where touch input is received (e.g. a starting point, intermediate points and an ending point). Actual contact between the touchable surface and the object may be detected by any suitable means, including, for example, by a vibration sensor or microphone coupled to the touch panel. A non-exhaustive list of examples for sensors to detect contact includes pressure-based mechanisms, micro-machined accelerometers, piezoelectric devices, capacitive sensors, resistive sensors, inductive sensors, laser vibrometers, and LED vibrometers.

According to an embodiment, smart phone1030, touch screen input device1050and device1080are configured with multimodal applications (1031,1051,1081). While the application is illustrated as part of the device, the application may be a network application (e.g. included as part of service1010) that is stored externally from the device.

As illustrated, touch screen input device1050, smart phone1030and display device1080shows exemplary displays1052/1032/1082showing the use of an application that utilize multimodal input/output (e.g. speech/graphical displays/gestures (touch/non-touch)). Data may be stored on a device (e.g. smart phone1030, device1050and/or at some other location (e.g. network data store1045). Data store1054may be used to store spreadsheet data used by the service. The applications used by the devices may be client based applications, server based applications, cloud based applications and/or some combination.

Change manager26is configured to perform operations relating to using a tweak and view mode as described herein. While manager26is shown within service1010, the all/part of the functionality of the manager may be included in other locations (e.g. on smart phone1030, device1050and/or display device1080).

The embodiments and functionalities described herein may operate via a multitude of computing systems, including wired and wireless computing systems, mobile computing systems (e.g., mobile telephones, tablet or slate type computers, laptop computers, etc.). In addition, the embodiments and functionalities described herein may operate over distributed systems, where application functionality, memory, data storage and retrieval and various processing functions may be operated remotely from each other over a distributed computing network, such as the Internet or an intranet. User interfaces and information of various types may be displayed via on-board computing device displays or via remote display units associated with one or more computing devices. For example user interfaces and information of various types may be displayed and interacted with on a wall surface onto which user interfaces and information of various types are projected. Interaction with the multitude of computing systems with which embodiments of the invention may be practiced include, keystroke entry, touch screen entry, voice or other audio entry, gesture entry where an associated computing device is equipped with detection (e.g., camera) functionality for capturing and interpreting user gestures for controlling the functionality of the computing device, and the like.

FIGS. 7, 8 and 9and the associated descriptions provide a discussion of a variety of operating environments in which embodiments of the invention may be practiced. However, the devices and systems illustrated and discussed with respect toFIGS. 7, 8 and 9are for purposes of example and illustration and are not limiting of a vast number of computing device configurations that may be utilized for practicing embodiments of the invention, described herein.

FIG. 7is a block diagram illustrating example physical components of a computing device1100with which embodiments of the invention may be practiced. The computing device components described below may be suitable for the computing devices described above. In a basic configuration, computing device1100may include at least one processing unit1102and a system memory1104. Depending on the configuration and type of computing device, system memory1104may comprise, but is not limited to, volatile (e.g. random access memory (RAM)), non-volatile (e.g. read-only memory (ROM)), flash memory, or any combination. System memory1104may include operating system1105, one or more programming modules1106, and may include a web browser application1120. Operating system1105, for example, may be suitable for controlling computing device1100's operation. In one embodiment, programming modules1106may include a change manager26, as described above, installed on computing device1100. Furthermore, embodiments of the invention may be practiced in conjunction with a graphics library, other operating systems, or any other application program and is not limited to any particular application or system. This basic configuration is illustrated inFIG. 7by those components within a dashed line1108.

Computing device1100may have additional features or functionality. For example, computing device1100may also include additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. Such additional storage is illustrated by a removable storage1109and a non-removable storage1110.

As stated above, a number of program modules and data files may be stored in system memory1104, including operating system1105. While executing on processing unit1102, programming modules1106, such as the manager may perform processes including, for example, operations related to methods as described above. The aforementioned process is an example, and processing unit1102may perform other processes. Other programming modules that may be used in accordance with embodiments of the present invention may include electronic mail and contacts applications, word processing applications, spreadsheet applications, database applications, slide presentation applications, drawing or computer-aided application programs, etc.

Embodiments of the invention, for example, may be implemented as a computer 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 media readable by a computer system and encoding a computer program of instructions for executing a computer process.

The term computer readable media as used herein may include computer storage media. 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. System memory1104, removable storage1109, and non-removable storage1110are all computer storage media examples (i.e., memory storage). Computer storage media may include, but is not limited to, RAM, ROM, electrically erasable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store information and which can be accessed by computing device1100. Any such computer storage media may be part of device1100. Computing device1100may also have input device(s)1112such as a keyboard, a mouse, a pen, a sound input device, a touch input device, etc. Output device(s)1114such as a display, speakers, a printer, etc. may also be included. The aforementioned devices are examples and others may be used.

A camera and/or some other sensing device may be operative to record one or more users and capture motions and/or gestures made by users of a computing device. A sensing device may be further operative to capture spoken words, such as by a microphone and/or capture other inputs from a user such as by a keyboard and/or mouse (not pictured). The sensing device may comprise any motion detection device capable of detecting the movement of a user. For example, a camera may comprise a MICROSOFT KINECT® motion capture device comprising a plurality of cameras and a plurality of microphones.

FIGS. 8A and 8Billustrate a suitable mobile computing environment, for example, a mobile telephone, a smartphone, a tablet personal computer, a laptop computer, and the like, with which embodiments of the invention may be practiced. With reference toFIG. 8A, an example mobile computing device1200for implementing the embodiments is illustrated. In a basic configuration, mobile computing device1200is a handheld computer having both input elements and output elements. Input elements may include touch screen display1205and input buttons1210that allow the user to enter information into mobile computing device1200. Mobile computing device1200may also incorporate an optional side input element1215allowing further user input. Optional side input element1215may be a rotary switch, a button, or any other type of manual input element. In alternative embodiments, mobile computing device1200may incorporate more or less input elements. For example, display1205may not be a touch screen in some embodiments. In yet another alternative embodiment, the mobile computing device is a portable phone system, such as a cellular phone having display1205and input buttons1210. Mobile computing device1200may also include an optional keypad1235. Optional keypad1235may be a physical keypad or a “soft” keypad generated on the touch screen display.

Mobile computing device1200incorporates output elements, such as display1205, which can display a graphical user interface (GUI). Other output elements include speaker1225and LED1220. Additionally, mobile computing device1200may incorporate a vibration module (not shown), which causes mobile computing device1200to vibrate to notify the user of an event. In yet another embodiment, mobile computing device1200may incorporate a headphone jack (not shown) for providing another means of providing output signals.

Although described herein in combination with mobile computing device1200, in alternative embodiments the invention is used in combination with any number of computer systems, such as in desktop environments, laptop or notebook computer systems, multiprocessor systems, micro-processor based or programmable consumer electronics, network PCs, mini computers, main frame computers and the like. Embodiments of the invention 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; programs may be located in both local and remote memory storage devices. To summarize, any computer system having a plurality of environment sensors, a plurality of output elements to provide notifications to a user and a plurality of notification event types may incorporate embodiments of the present invention.

FIG. 8Bis a block diagram illustrating components of a mobile computing device used in one embodiment, such as the computing device shown inFIG. 8A. That is, mobile computing device1200can incorporate system1202to implement some embodiments. For example, system1202can be used in implementing a “smart phone” that can run one or more applications similar to those of a desktop or notebook computer such as, for example, spreadsheet applications, presentation applications, browser, e-mail, scheduling, instant messaging, and media player applications. In some embodiments, system1202is integrated as a computing device, such as an integrated personal digital assistant (PDA) and wireless phoneme.

One or more application1266may be loaded into memory1262and run on or in association with operating system1264. Examples of application programs include phone dialer programs, e-mail programs, PIM (personal information management) programs, word processing programs, spreadsheet programs, presentation/slideshow programs, Internet browser programs, messaging programs, and so forth. System1202also includes non-volatile storage1268within memory1262. Non-volatile storage1268may be used to store persistent information that should not be lost if system1202is powered down. Applications1266may use and store information in non-volatile storage1268, such as spreadsheet content, document content, e-mail or other messages used by an e-mail application, and the like. A synchronization application (not shown) may also reside on system1202and is programmed to interact with a corresponding synchronization application resident on a host computer to keep the information stored in non-volatile storage1268synchronized with corresponding information stored at the host computer. As should be appreciated, other applications may be loaded into memory1262and run on the device1200, including the change manager26, described above.

System1202has a power supply1270, which may be implemented as one or more batteries. Power supply1270might further include an external power source, such as an AC adapter or a powered docking cradle that supplements or recharges the batteries.

System1202may also include a radio1272that performs the function of transmitting and receiving radio frequency communications. Radio1272facilitates wireless connectivity between system1202and the “outside world,” via a communications carrier or service provider. Transmissions to and from radio1272are conducted under control of OS1264. In other words, communications received by radio1272may be disseminated to application1266via OS1264, and vice versa.

This embodiment of system1202is shown with two types of notification output devices; LED1220that can be used to provide visual notifications and an audio interface1274that can be used with speaker1225to provide audio notifications. These devices may be directly coupled to power supply1270so that when activated, they remain on for a duration dictated by the notification mechanism even though processor1260and other components might shut down for conserving battery power. LED1220may be programmed to remain on indefinitely until the user takes action to indicate the powered-on status of the device. Audio interface1274is used to provide audible signals to and receive audible signals from the user. For example, in addition to being coupled to speaker1225, audio interface1274may also be coupled to a microphone to receive audible input, such as to facilitate a telephone conversation. In accordance with embodiments of the present invention, the microphone may also serve as an audio sensor to facilitate control of notifications, as will be described below. System1202may further include video interface1276that enables an operation of on-board camera1230to record still images, video stream, and the like.

A mobile computing device implementing system1202may have additional features or functionality. For example, the device may also include additional data storage devices (removable and/or non-removable) such as, magnetic disks, optical disks, or tape. Such additional storage is illustrated inFIG. 8Bby storage1268. 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.

Data/information generated or captured by the device1200and stored via the system1202may be stored locally on the device1200, as described above, or the data may be stored on any number of storage media that may be accessed by the device via the radio1272or via a wired connection between the device1200and a separate computing device associated with the device1200, for example, a server computer in a distributed computing network such as the Internet. As should be appreciated such data/information may be accessed via the device1200via the radio1272or via a distributed computing network. Similarly, such data/information may be readily transferred between computing devices for storage and use according to well-known data/information transfer and storage means, including electronic mail and collaborative data/information sharing systems.

FIG. 9illustrates a system architecture for a system as described herein.

Components managed via the change manager26may be stored in different communication channels or other storage types. For example, components along with information from which they are developed may be stored using directory services1322, web portals1324, mailbox services1326, instant messaging stores1328and social networking sites1330. The systems/applications26,1320may use any of these types of systems or the like for enabling management and storage of components in a store1316. A server1332may provide communications and services relating to the tweak and view mode as described herein. Server1332may provide services and content over the web to clients through a network1308. Examples of clients that may utilize server1332include computing device1302, which may include any general purpose personal computer, a tablet computing device1304and/or mobile computing device1306which may include smart phones. Any of these devices may obtain display component management communications and content from the store1316.