Browse Prior Art Database

Invoking window size based UI visual layouts via behaviors in WinRT UI applications

IP.com Disclosure Number: IPCOM000234850D
Original Publication Date: 2014-Feb-11
Included in the Prior Art Database: 2014-Feb-11
Document File: 4 page(s) / 46K

Publishing Venue

Microsoft

Related People

James Andrew Canitz: INVENTOR

Abstract

In Microsoft Windows 8.0 and 8.1, the WinRT UI development platform was introduced for application developers wishing to write app-store applications using XAML UI markup backed by C++, Cx, C#, or Visual Basic and other programming languages.

This text was extracted from a Microsoft Word document.
This is the abbreviated version, containing approximately 28% of the total text.

Document Author (alias)

James Andrew Canitz (drewcan)

Defensive Publication Title 

Invoking window size based UI visual layouts via behaviors in WinRT UI applications.

Name(s) of All Contributors

James Canitz

 

 

 

 

Summary of the Defensive Publication/Abstract

In Microsoft Windows 8.0 and 8.1, the WinRT UI development platform was introduced for application developers wishing to write app-store applications using XAML UI markup backed by C++, Cx, C#, or Visual Basic and other programming languages. 

WinRT UI being based on Silverlight UI technologies has many of the same development patterns that can be found in Silverlight and WPF.  One of these key technology concepts is “behaviors” which is a way to define and register application custom properties to the WinRT UI parser and run-time that will invoke an application supplied callback when the value of the custom property changes.  The application callback may contain any logic the application developer desires.  It can even contain complex patterns, register additional callbacks, manipulate local state, etc.

The Windows 8.0+ platform also has the concept of multiple window sizes in which an application can be presented to the user.  It’s up to the application developer to build their application in such a way that it is attractive and useful to the user at different sizes.  One strategy that an application can use is to change its UI layout to optimize for available visual space.  A WinRT UI built in system to control mutually exclusive visual states is called the VisualStateManager.  Within the VisualStateManager the application can define VisualStateGroups which are collections of mutually exclusive VisualStates.  These VisualStates describe to WinRT UI which properties to change on specific controls when the UI is in each individual VisualState.  Using this system an application can force their UI into a VisualState which might hide, resize, rearrange, or otherwise manipulate the controls in the UI.

Applying the “behavior” concept to the VisualStateManager during window size changes is a way that an application can define how their UI will respond to size changes and update its UI by defining this behavior in XAML in a generic way instead of complex and case specific code behind logic.  This document describes an implementation of this behavior called VisualStateWidthRanges.

Description:  Include architectural diagrams and system level data flow diagrams if: 1) they have already been prepared or 2) they are needed to enable another developer to implement your defensive publication. Target 1-2 pages, and not more than 5 pages.  

This document describes a WinRT UI behavior called VisualStateWidthRanges that allows an application developer to define in their XAML how their UI will update in response to window size changes to present the desired experience to the user.

Take for sake of explanation a trivial example, you want to build an application UI for Windows 8.1 using...