More to the point, to comply, it would end up being a far more rigid development system or it would be entirely unusuable. The only way Microsoft can make Silverlight work on iOS isn't as much an 'adaptation' as 'a complete redesign and implementation in a way that makes it into something entirely other than what it is now'. Silverlight is a system, not an app - inherent in it is the fact that it will require an interpreter, or a local compiler of some sort. Net and Silverlight from day one - and Mono supports both platforms as well and iOS is essentially a stripped down version of MacOS - so Silverlight for iOS already exists (or is close). They've had a MacOS version of both the full. So, no - it's not a question of Microsoft getting around to doing it. The 'must be written in ObjC' restriction put the final nail in the coffin. Net IL to native translator which would have gotten past the 'no interpreted languages' restriction. The Mono group had already released a "Mono for iOS" which embedded a lightweight version of the. Net and Mono (the open source version of. Worse, they also added a requirement that any app MUST be written in ObjC and compile to native code. While it's generally agreed that this was a direct shot at Adobe Flash, it had the side effect of taking out Silverlight and Java. Apple made a policy change with iOS 4.0 that expressly forbade any kind of interpreted language or virtual machine on iOS devices (other than ones they themselves wrote, of course).
0 kommentar(er)
