Windows 8下的WPF和Silverlight的未来是什么? [英] What will the future be for WPF and Silverlight under Windows 8?

查看:202
本文介绍了Windows 8下的WPF和Silverlight的未来是什么?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

查看,但Win32 API尚未被删除,使用传统应用程序执行环境的旧应用程序将继续按预期工作。



< Joe Stegman在BUILD会议上发表的演讲详细介绍了预期会发生什么变化。




  • 这是一回事,只是现在是原生的,现在在Windows 8上发货。

  • C ++,C#,VB:XAML的一流编程语言

  • XAML控件是本机WinRT API

  • 在Silverlight和WPF中你曾经做过的事情与你将来在做什么之间真的是一致的Windows 8。



所以,仍然会支持现有技术。但是,为了利用新技术,您必须在WinRT上构建。使用XAML与您已经习惯的不同。






Windows 8(BUILD)的开发博客揭示了背景和设计决策。



Windows 8新的Metro风格用户界面是一次彻底的改造,在设计之前考虑到了全新的体验。


我们在2009年夏天开始计划Windows 8(在Windows 7发售
之前)。从一开始,我们的方法就是重新构想
Windows,并开放重新审视用户模型,平台和API以及我们b $ b支持的体系结构的最基本元素
。我们的目标是不妥协的设计。



...如果你想永久地沉浸在Metro世界中,你将
永远不会看到桌面 - 我们甚至不会加载它(字面上代码将
不加载)除非你明确选择去那里!这是
Windows重新构想。


然而,Windows 8的开发团队认识到需要继续支持现有的桌面界面和应用程序,甚至将继续改进它。正如他们在后续帖子,Metro风格与传统桌面之间的差距尽可能和谐。


但是,如果您确实看到桌面体验的价值 - 精确控制,强大的窗口和文件管理
,与
数十万现有程序和设备兼容,支持
您的商业软件,这些功能也在您的
指尖。



基本上,您可以将Windows桌面视为另一个应用程序。



所以,即使我们相信随着时间的推移,很多场景将是由Metro风格的应用程序提供的优惠服务,在可预见的未来,
桌面即将推出继续在许多人的b $ b生活中发挥关键作用。所以我们要改进它。


Metro风格的界面试图替换适合的现有界面,但传统的桌面在哪里可以提供更好的体验,它仍然可以。


我们的设计目标很明确:没有任何妥协。如果你愿意,你可以
在Metro风格的应用程序和改进的Windows
桌面之间无缝切换。现有的应用程序,设备和工具都在Windows 8中保留并改进了
。另一方面,如果您更喜欢让自己沉浸在
Metro风格的应用程序(和平台)以及新的用户体验中,你
也可以做到这一点!开发人员可以针对他们希望提供的软件定位有意义的API


关于现有技术是否会仍然受到支持,他们提到了以下内容


我们将展示允许您编写Metro风格的全新工具$ b HTML5 / JavaScript,C / C ++和/或C#/ XAML中的$ b应用程序。
您作为开发人员使用所有这些语言进行的投资
结转Windows 8,它允许您选择如何最好地使用Windows 8系统服务
。我们谈到Windows 8是最终用户的
a无妥协操作系统,对于开发人员而言,它也是一个不妥协的
平台。


来自微软的Jon DeVaan的评论更让人放心:


WPF和Silverlight继续保持桌面不变。
的新功能Windows 8能够利用您的WPF和Silverlight
知识(以及带有一些更改的代码)来创建Metro Style
应用程序。



Seeing the first announcement of the HTML5/JS Windows 8 GUI, plenty of WPF and Silverlight developers panicked.

What is the future for these technologies? How will the new and old technologies be able to cooperate? Should we all start developing using an entirely new framework pretty soon?

Does anyone have official sources clarifying the situation a bit?

解决方案

In the keynote of the build conference they demonstrated the following platform diagram:

WinRT is an object-oriented replacement for Win32, but the Win32 API has not been removed and older applications using the traditional application execution environment will continue to work as expected.

This talk by Joe Stegman at the BUILD conference goes into detail about what to expect.

  • "It's the same thing, just now native and now shipping in-box on Windows 8."
  • C++, C#, VB: first class programming languages for XAML
  • XAML controls are "native" WinRT APIs
  • "Things are really consistent between what you're used to doing in Silverlight and WPF and what you may be doing in the future in Windows 8."

So yes, the existing technologies will still be supported. However, in order to make use of the new technologies you will have to build upon WinRT. Using XAML won't differ much from what you are already used to.


The development blog of Windows 8 (BUILD) sheds some light on the background and design decisions.

The new Metro-style user interface of Windows 8 is a complete overhaul, designed up front with a new experience in mind.

We started planning Windows 8 during the summer of 2009 (before Windows 7 shipped). From the start, our approach has been to reimagine Windows, and to be open to revisiting even the most basic elements of the user model, the platform and APIs, and the architectures we support. Our goal was a no compromise design.

... if you want to stay permanently immersed in that Metro world, you will never see the desktop—we won’t even load it (literally the code will not be loaded) unless you explicitly choose to go there! This is Windows reimagined.

However, the development team of Windows 8 recognizes the need to continue supporting the existing desktop interface and applications, and will even continue to improve it. As they discuss in a follow-up post, the gap between Metro style and the traditional desktop is made as harmonious as possible.

But if you do see value in the desktop experience—in precise control, in powerful windowing and file management, in compatibility with hundreds of thousands of existing programs and devices, in support of your business software, those capabilities are right at your fingertips as well.

Essentially, you can think of the Windows desktop as just another app.

So, even if we believe that over time many scenarios will be well-served by Metro style apps, for the foreseeable future, the desktop is going to continue to play a key role in many people’s lives. So we are going to improve it.

The Metro-style interface tries to replace the existing interface where suitable, but where the traditional desktop can provide a better experience, it still can.

Our design goal was clear: no compromises. If you want to, you can seamlessly switch between Metro style apps and the improved Windows desktop. Existing apps, devices, and tools all remain and are improved in Windows 8. On the other hand, if you prefer to immerse yourself in only Metro style apps (and platform) and the new user experience, you can do that as well! Developers can target the APIs that make sense for the software they wish to deliver.

As to whether the existing technologies will still be supported, they mentioned the following:

We will show the brand new tools that allow you to code Metro style applications in HTML5/JavaScript, C/C++, and/or C#/XAML. The investments you have made as developers in all of these languages carry forward for Windows 8, which lets you choose how to best make use of the Windows 8 system services. We talked about Windows 8 being a no-compromise OS for end-users, and it is also a no-compromise platform for developers.

The comment by Jon DeVaan from Microsoft is even more reassuring:

WPF and Silverlight continue unchanged for the desktop. New to Windows 8 is the ability to leverage your WPF and Silverlight knowledge (and code with some changes) to create Metro Style applications.

这篇关于Windows 8下的WPF和Silverlight的未来是什么?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆