Abstract: Technologies are described herein for a health monitor that establishes and monitors a set of alive endpoints to be used as substitutes for a dead working window endpoints. The health monitor periodically monitors substitution endpoints. When a request manager determines that a working window endpoint is dead, the request manager sends a request to the health monitor for a substitute endpoint. The health monitor receives the request and identifies an appropriate substitution endpoint from the health monitor endpoints to provide to the request manager to substitute for the dead endpoint. The health monitor releases the identified substitution endpoint to the request manager.

Abstract: Technologies are described herein for a health monitor that establishes and monitors a set of alive endpoints to be used as substitutes for a dead working window endpoints. The health monitor periodically monitors substitution endpoints. When a request manager determines that a working window endpoint is dead, the request manager sends a request to the health monitor for a substitute endpoint. The health monitor receives the request and identifies an appropriate substitution endpoint from the health monitor endpoints to provide to the request manager to substitute for the dead endpoint. The health monitor releases the identified substitution endpoint to the request manager.

Abstract: Technologies are described herein for a health monitor that establishes and monitors a set of alive endpoints to be used as substitutes for a dead working window endpoints. The health monitor periodically monitors substitution endpoints. When a request manager determines that a working window endpoint is dead, the request manager sends a request to the health monitor for a substitute endpoint. The health monitor receives the request and identifies an appropriate substitution endpoint from the health monitor endpoints to provide to the request manager to substitute for the dead endpoint. The health monitor releases the identified substitution endpoint to the request manager.

Abstract: Concepts and technologies are described herein for progressive loading for web-based spreadsheet applications. In accordance with the concepts and technologies disclosed herein, a user device can access data from a remote source such as a server computer. The user device can determine dimensions of a viewport corresponding to a viewable portion of the data, a window associated with the viewport, and a preloaded area associated with the window. The user device can request the data associated with the window and the preloaded area and store the data in a cache associated with the user device. The cached data can be used by the user device to generate UIs for displaying the spreadsheet. If the user device detects movement of the viewport, the user device can render a new UI in response to the movement. The user device also can be configured to update and/or clean the cache.

Abstract: Various technologies and techniques are disclosed for displaying and managing spreadsheets on mobile devices. An optimized search can be performed. A selection is received from a user to open a spreadsheet. A find selection is received from the use along with keywords for which to the user wishes to search. Any matching keywords are found in the spreadsheet and the cell location of the keywords is retrieved. A results page is constructed that shows search result listings with the keywords along with data surrounding the one or more keywords. The results page is displayed. Navigation options are provided for allowing a user to navigate around the spreadsheet. Right, left, downward, and upward navigation options can be used to change the current view of the spreadsheet by a pre-defined number of cells. Techniques are described for optimizing the display of charts in the spreadsheet.

Abstract: Concepts and technologies are described herein for row and column navigation. In accordance with the concepts and technologies disclosed herein, a user device executes an application program configured to present data in a user interface (“UI”). The user device can execute a navigation controller to detect touch events at the user device. The navigation controller can determine if touch events correspond to input for panning or scrolling the UIs and for implementing the requested panning or scrolling. The navigation controller can include functionality for providing a touch event handler to detect input for panning or scrolling the data and a UI scrolling manager that implements the requested panning or scrolling. The panning or scrolling can be tracked and the data, as modified in accordance with the tracked movement, can be presented to a user in a UI.

Abstract: Technologies are described herein for a health monitor that establishes and monitors a set of alive endpoints to be used as substitutes for a dead working window endpoints. The health monitor periodically monitors substitution endpoints. When a request manager determines that a working window endpoint is dead, the request manager sends a request to the health monitor for a substitute endpoint. The health monitor receives the request and identifies an appropriate substitution endpoint from the health monitor endpoints to provide to the request manager to substitute for the dead endpoint. The health monitor releases the identified substitution endpoint to the request manager.

Abstract: Various technologies and techniques are disclosed for displaying and managing spreadsheets on mobile devices. An optimized search can be performed. A selection is received from a user to open a spreadsheet. A find selection is received from the use along with keywords for which to the user wishes to search. Any matching keywords are found in the spreadsheet and the cell location of the keywords is retrieved. A results page is constructed that shows search result listings with the keywords along with data surrounding the one or more keywords. The results page is displayed. Navigation options are provided for allowing a user to navigate around the spreadsheet. Right, left, downward, and upward navigation options can be used to change the current view of the spreadsheet by a pre-defined number of cells. Techniques are described for optimizing the display of charts in the spreadsheet.

Abstract: Concepts and technologies are described herein for progressive loading for web-based spreadsheet applications. In accordance with the concepts and technologies disclosed herein, a user device can access data from a remote source such as a server computer. The user device can determine dimensions of a viewport corresponding to a viewable portion of the data, a window associated with the viewport, and a preloaded area associated with the window. The user device can request the data associated with the window and the preloaded area and store the data in a cache associated with the user device. The cached data can be used by the user device to generate UIs for displaying the spreadsheet. If the user device detects movement of the viewport, the user device can render a new UI in response to the movement. The user device also can be configured to update and/or clean the cache.

Abstract: Concepts and technologies are described herein for row and column navigation. In accordance with the concepts and technologies disclosed herein, a user device executes an application program configured to present data in a user interface (“UI”). The user device can execute a navigation controller to detect touch events at the user device. The navigation controller can determine if touch events correspond to input for panning or scrolling the UIs and for implementing the requested panning or scrolling. The navigation controller can include functionality for providing a touch event handler to detect input for panning or scrolling the data and a UI scrolling manager that implements the requested panning or scrolling. The panning or scrolling can be tracked and the data, as modified in accordance with the tracked movement, can be presented to a user in a UI.

Abstract: Technologies are described herein for recording user-driven events within a computing system. An interface is established between a recorder application and an input method editor (“IME”) executing on the computer system. Through the use of the interface, the recorder application can obtain and record data identifying user-driven events that are performed within the IME. An interface is also established between the recorder application and a UI control that does not expose data regarding user-driven events through standard system calls. Through the use of the interface, the recorder application can obtain and record data identifying user-driven events detected at the UI control. The recorder application can also provide data identifying the recorded user-driven events directly to a bug tracking application program for inclusion in a bug database.

Abstract: Various technologies and techniques are disclosed for displaying and managing spreadsheets on mobile devices. An optimized search can be performed. A selection is received from a user to open a spreadsheet. A find selection is received from the use along with keywords for which to the user wishes to search. Any matching keywords are found in the spreadsheet and the cell location of the keywords is retrieved. A results page is constructed that shows search result listings with the keywords along with data surrounding the one or more keywords. The results page is displayed. Navigation options are provided for allowing a user to navigate around the spreadsheet. Right, left, downward, and upward navigation options can be used to change the current view of the spreadsheet by a pre-defined number of cells. Techniques are described for optimizing the display of charts in the spreadsheet.

Abstract: Technologies are described herein for recording user-driven events within a computing system. An interface is established between a recorder application and an input method editor (“IME”) executing on the computer system. Through the use of the interface, the recorder application can obtain and record data identifying user-driven events that are performed within the IME. An interface is also established between the recorder application and a UI control that does not expose data regarding user-driven events through standard system calls. Through the use of the interface, the recorder application can obtain and record data identifying user-driven events detected at the UI control. The recorder application can also provide data identifying the recorded user-driven events directly to a bug tracking application program for inclusion in a bug database.