Microsoft Technology Licensing, LLC

Kyle Thomas Brady

Mehmet Iyigun

Hari R Pulapaka

Benjamin M Schultz

Frederick Justus Smith

Ross Nathaniel Luengen

John Carroll Gordon

Gregory Thomas Mattox, Jr

William Joseph Devereux

Kenneth Martin Tubbs, Jr

Morakinyo Korede Olugbade

Paul Bozzay

Ali Hajy

Rose Elizabeth Higgins

Laurent Etienne Gilbert Mouton

Jessica Mary Hallett-Hook

Embodiments described herein are directed to simultaneously displaying proxy windows for application windows and/or tabs included in such application windows via a graphical user interface of an operating system. For instance, an application programming interface (API) associated with an application that supports a tabbed document interface (TDI) provides information associated with each tab opened within an application window associated with the application. An API of the operating system receives and utilizes such information to generate and display a proxy window for each tab. The proxy windows for the tabs may be displayed alongside proxy windows of application windows for other applications. The proxy windows may be generated and displayed in response to user invocation of various features of the operating system graphical user interface, including, but not limited to, a task switcher feature, a taskbar feature, or a window snap feature.

Systems and methods for providing tab previews via an operating system user interface

Different containers are used for different usage sessions, a container referring to a virtualization layer for a computing device and used for isolation as well as hardware resource partitioning. A usage session refers to the time span beginning when one or more users begin to use the computing device, and ending when the one or more users cease using the computing device. During a particular usage session that uses a container, all interaction with the computing device is maintained in the container. The container is deleted when the usage session ends, leaving no data from the usage session behind after the usage session ends. Additionally, some usage sessions need not be run in containers, so data generated during such usage sessions is maintained after usage session ends. The host operating system automatically determines which usage sessions to run in containers and which usage sessions to run separate from any containers.

Selective container use for device usage sessions

A container for one or more scheduled meeting is pre-built for the meeting prior to the meeting occurring. The container can be built in a variety of manners, including using both static and dynamic techniques. Dynamic techniques for building a container allows a pre-build system to include more pertinent data in the container whereas static techniques reduce computing workload and allow for pre-building containers for unscheduled meetings. A combination of static and dynamic building techniques can be applied using a layer repository. Alternately, a static base layer can be used and customized for scheduled meetings.

Pre-building containers

Growing community of inventors

Seattle, WA, United States of America

Kyle Thomas Brady