3 ms·

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

by sudont 16y ago

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.

kenjackson 16y ago
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 the list... Win8Touch needs to be able to run WP7 Silverlight apps. The market needs to be seeded with touch apps in order for the tablet to take off. This was THE most important thing Apple did for the iPad (followed very closely by incredible battery life).
- sudont 16y ago
  It's possible with the iPad. I'm thinking it's partially the right form-factor. I initially dismissed the iPad as junk, but after picking one up I was a little more convinced that it had a lot of value. 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.