stevo_ said:magicalclick said:*snip*
Uh you could do that in c++, both will need platform abstraction layers... but you wouldn't want to do that because the UI / experience of a phone is different to a desktop.. the core of the rendering engine should be re-used, and that would have significantly less dependencies than a UI would..
Also AndyC, that example doesn't mean you should do it in .NET, it just means there needs to be a better way to interop the drawing layers in WPF and native.. maybe they already do have a good way but the web browser control just isn't compat..
But I'm pretty sure they could make that work faster than it would for them to write an entirely new browser..
.NET is great, I solely program .NET, in-fact I've had such a brief time in native world that I hardly remember it, but I at least know that native isn't obsolete to .NET - and that I can't see any reason why they wouldn't instead- write an entirely new browser in native..
steveo_ said:Also AndyC, that example doesn't mean you should do it in .NET, it just means there needs to be a better way to interop the drawing layers in WPF and native.. maybe they already do have a good way but the web browser control just isn't compat..
Unlikely, doing that would mean pretty much redeveloping large parts of Win32, since it is fundamental Win32 decisions that lead to the limitations involved. And that in itself would be not only an enormous job, but a compatibility nightmare. And even after all that it might not even be fixable without breaking basic Win32 assumptions - remember it's not necessarily just layering, but the ability to truly treat it as a WPF control, including applying transformations, animations or embedding the control onto a 3D surface whilst remaining functional.
Given that Trident no longer has any actual dependencies on real Win32 controls, it would probably be easier to port that into WPF via C++/CLI if they wanted to fix that. It's questionable whether that would have any benefit for Microsoft though, given it's not something they necessarily need themselves. I still think it would be a useful third party control though.