Earlier quoted context omitted.
That's a good plan. I doubt Microsoft would ever implement it. And most of what you wrote is what Apple did with iOS, it's actually just Mac OS X with the GUI torn off completely. Really, a touch API for .NET would go a long way for promoting it in tech circles. The problem is that the bosses are in love with iPads. Mono for Android, maybe.
Really, a touch API for .NET would go a long way for promoting it in tech circles. WPF 4.0 has touch support, and seems pretty full-featured as far as I can tell. The problem I have building .NET apps is that I don't know anyone with a Windows touch device. It's hard for me to want to add touch support, given I have no customers for it. Although if MS paid me for my time... :-) Which reminds me of one more thing for…
And heh, looks like Microsoft took a little bit of direction from cocoa touch in naming their classes "UIElement"
.NET apps would be a lot more valuable for in-house applications, although, Apple's 299/yr enterprise license takes a bit of air out of that.