Freigeben über

Windows Phone 7 Guides for IT Pros (and Developers)

  • Artikel

I just stumbled across these guides on the download centre and I must say there’s some great information in there for developers as well as IT Pros.

I found the “Internet Explorer”, “Security Model” and “Device Update” documents to be of particular interest. And the “Root Certificates” document contains a list of all the root certificates that come pre-installed on Windows Phone 7.

Comments

  • Anonymous
    January 16, 2011
    I was pleased to see the link to "Windows Internet Explorer Mobile on Windows Phone 7" just to be very disappointed by the grave omissions in the content. The document calls the browser "optimized for touch" when it doesn't even fire the usual touch events. It forgets to mention that the window Object is disabled in Javascript, as are various useful debugging functions such as alert(). It also forgets to mention that Internet Explorer supports only 16bit color depths ("thousands of colors") even when running on devices with a higher color count. And these are just the things I uncovered after working with Internet Explorer for WP7 for one day. It makes me wonder how you arrived at the conclusion that this guide contains "great information [...] for developers".

  • Anonymous
    January 17, 2011
    @jonemo I don't think you can dispute that the browser is optimised for touch? The touch user-experience with the browser on WP7 is fantastic. These are documents intended for IT Pros but, as I said, I certainly found a lot of the information interesting and useful as a developer. There is a lot of useful material in the IE Mobile document for developers - perhaps it's not exhaustive but there's still a lot of good material in there. Same goes for the Security Model document. This was information I'd not seen written down elsewhere. Best regards, Mike.

  • Anonymous
    January 18, 2011
    I don't dispute that the information in the document is a useful starting point. But I stand by my point that it omits a lot of important information and by doing so misleads and over-promises. Maybe I just haven't found the right source yet, but I see this as symptomatic for the overall lack of information about IE for WP7. Let me explain through an example: On my first WP7 project I agreed to adjust a webapp to work on WP7. I had read all the documentation I could find and was confident I could do the job. IE for WP7 was described as standard IE7 with a list of restrictions (mostly identical to the one in the document you link to). When the devices came out, I was surprised to find that IE falls back to 16bit color depth on 24bit capable screens. If such a major constraint goes unmentioned in the documentation, working on web apps for WP7 is very risky. Behind every corner lies an undocumented pitfall that could be a show stopper. This means feasibility of projects cannot be judged before completing the project - clearly an undesirable situation that no IT professional or developer wants to be in. This is why, for now, I stopped doing work on WP7. The same problem of over-promising applies for touch optimization. When a smartphone OS is advertised as being touch-optimized I read this information in the context of other similar platforms I worked with, such as HP webOS, Android and iOS. From a touch-optimized browser in 2011 one would expect that one can give a developer the job to create a touch based web app for it. But I can't because not only has the browser the same shortcomings that most other mobile browsers have (e.g. no events available to read finger positions during multi-touch), it goes further by omitting touch-events completely.