- From: François REMY <francois.remy.dev@outlook.com>
- Date: Mon, 1 Jul 2013 13:22:25 +0200
- To: "Robin Berjon" <robin@w3.org>
- Cc: <public-nextweb@w3.org>
> Say if you're embedding Photoshop to edit an image with it, then the embed > page just shows the picture and Photoshop is launched as usual. (And you > can get it to cooperate without it knowing it by watching the file and > sending events every time it's saved — imperfect but hey, we have to work > in steps.) Okay but what's the point? How is that better than leaving the UA do the hard work of displaying the app the way is the most natural to the platform? On Windows 8, the Share charm is displayed the same way every time and is totally outside of control of the share initiator, and that's absolutely awesome because this uniformity brings a lot of potential for innovation to the platform instead of to the app. They added new sharing possibilities to Windows 8.1 with no need for any change in the apps because Microsoft was in total control of the experience. If it was up to apps to choose the size and location the sharing control, maybe some would have fitted the box in a way that made it impossible for the OS to show more on-screen content. Also, the user looses the benefits of consitency. (however, this should probably be discussed inside the TAG group as it's all about API design, I'm not sure it's really linked to the charter of this working group)
Received on Monday, 1 July 2013 11:22:52 UTC