Standard Windows Forms to Windows 8

Metro Style porting tool Group No: 12-111

Introduction

Why Switch to Windows 8?

• Targets Touch Based Devices• New User Experience• Fast And Fluid• Programming Flexibility• Better Hardware Utilization

Why use Metro Style?• Full screen applications tailored for user needs

and the device they run on

• Optimized for Touch interaction and to the windows user interface

• Eliminates the Windows Chrome such as ribbons and tool bars, giving an uncluttered UI

Windows Forms vs. Metro Style

• Windowed• Not much Touch Friendly• Fills the screen with

toolbars and chrome• .NET 4/4.5 (Win32) and

earlier

• Full screen• Touch Friendly• No chrome, more space

for the application• .NET 4.5 (WinRT)• Charms

Objective : Can this conversion be done?, how?, if so a tool to help

Windows Forms vs. Metro Style

• Why the change ?– Microsoft is moving for the tablet market– One application, one job• Fullscreen – No interference from other applications• No MDIs - Simple work flow

– More space for the application interface– Simplify the user interaction

Why porting is required?• To reduce the cost of developing applications

from the scratch. • Keep the logical functionality of the current

application intact even with the new technology.

User Requirements

What the system should do?

• Convert the GUI• Convert the code behind• Convert the solution and folder structures• Help the user throughout the conversion

process

What the system should do

Windows Forms Application

Metro Style Application

Convert the GUI

Convert code

behind

Convert solution file and folder

structure

What the system should do- Use Case

User Characteristics• Student : Low Technical Background– To learn– To play around– Little or no knowledge on WinRT and Metro

• Developer : High Technical Background– Knows what he/she’s doing– Good knowledge on WinRT and Metro

User Interface – What the user need

• A window where we can set what to convert/port, and to check whether it is possible

• A wizard that would guide the user through the porting process.

• Help when the user needs it

Software Interfaces• Roslyn Project – Get service from the compiler.• Windows 8 – Platform on which the output

application runs on• .NET 4.5 (WinRT) – Framework the output

application runs on• .NET 4.0 – Framework the system and the input

application runs on

Operations• Interactive Operations– Set input application– Set basic settings– Select capabilities– Select charms– Modify defaults– Monitor porting process

• Unattended Operations– None

Product Functions• Analyze code• Set options• Port Code• View log• Change application settings• View help• Customize conversion rules

System Requirements

The System – Class diagram

The User InterfacesMain Window• Used to Provide the input

project to be ported• Analyzes the input for

integrity and compatibility• If everything is ok, transfer

control to the porting wizard

The User InterfacesPorting Wizard -Introduction• The starting point of the

porting wizard• Give a brief description on the

porting process which follows

The User InterfacesPorting Wizard - Application UI• Set basic application

properties

The User InterfacesPorting Wizard - Capabilities• What the application has

access to• Help user make the correct

choice

The User InterfacesPorting Wizard - Charms• New Feature introduced in

Windows 8• Provides access to

functionalities in • Provides the user with the

option to select preferred charms

The User InterfacesPorting Wizard – User Modifications• Ability to change the

generated code• Override defaults

The User InterfacesPorting Wizard – Analysis Report• What happened during the

porting process• Errors, Warnings

The Requirements• Functional– Convert the User Interface– Convert the Code behind– Convert the Solution files and folder structure

The Requirements• Non Functional– Maintainability• Should be easily updatable

– User friendliness• Must be easily to use

– Portability• Application must be able to run on different computer

which meets the minimum requirements– Usability• Must be easy to learn and master

The Requirements• Non Functional– Performance• Use resources efficiently• Get the porting process done as fast as possible

Questions?

Thank you!

References• http

://www.hongkiat.com/blog/evolution-of-microsoft-windows-1985-2009/

• http://en.wikipedia.org/wiki/Porting