1. Ink Input John Ruble

2. Motivation / Goal Implement information organization in GUI Add Microsoft.Ink input and storage Make tablet-friendly (no keyboard necessary) Facilitate future milestones

3. Previous / Related Work Many apps save/load ink – Journal, OneNote/GoBinder Ink AniEd - http://www.leweyg.com/anied/ Ink animation programhttp://www.leweyg.com/anied/ Saves ink with regard to time

4. Ink AniEd

5. Challenges Moving from one GUI to another How to save ink? (Ink doesn’t natively serialize) Safety –Prevention of overwriting events –Prevention of duplicating events

6. Challenges – GUI transplant Differences in GUIs –Start/stop paradigm –Editing existing events

7. Challenges – Ink Serialization Microsoft.Ink doesn’t implement System.Runtime.Serialization.Iserializable interface

8. Challenges - Safety What do you do when asked to add an AnnotationEvent with the same start time or overlapping time duration? This goes hand-in-hand with facilitating future milestones : minimize preconditions other developers must meet

9. Approach – GUI transplant Systematic approach – per-button MSDEV’s powerful runtime debugger

10. Approach – Ink Serialization Microsoft.Ink does provide.Save(PersistenceFormat…) function By storing this in a byte[ ], serialization proceeds

11. Approach – Safety Lots of checking Descriptive errors for unhandled events GUI feature disabling to prevent unhandled events from occuring

12. Demo

13. Questions GUI – How can it be easier/faster? What other ‘safety’ issues might occur?