Windows 8 下的 WPF 和 Silverlight 的未来会怎样？

发布于 2024-11-14 01:34:33 字数 305 浏览 3 评论 0原文

请参阅HTML5/JS Windows 8 GUI 的首次公告，许多WPF 和 Silverlight 开发人员感到恐慌。

这些技术的未来是什么？新旧技术如何协同？我们是否应该尽快开始使用全新的框架进行开发？

有没有人有官方消息来源澄清一下情况？

原文

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

二手情话 2024-11-21 01:34:33

在构建会议的主题演讲中，他们演示了以下平台图：

Windows 8 平台和工具

WinRT 是一个Win32 的面向对象替代品，但 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 以及我们的架构
支持。我们的目标是不妥协的设计。
...如果你想永远沉浸在地铁世界中，你会
永远不会看到桌面——我们甚至不会加载它（实际上代码将
不会被加载）除非你明确选择去那里！这是
Windows 重新构想。

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

但是，如果您确实看到了桌面体验的价值——精确控制，
强大的窗口和文件管理功能，兼容
数十万个现有程序和设备，以支持
您的商业软件，这些功能就在您身边
指尖也是如此。
本质上，您可以将 Windows 桌面视为另一个应用程序。
所以，即使我们相信随着时间的推移，许多场景都会发生
Metro 风格的应用程序提供良好的服务，在可预见的未来，
桌面将继续在许多人的生活中发挥关键作用
生活。所以我们要改进它。

Metro风格的界面试图在合适的地方取代现有的界面，但在传统桌面可以提供更好体验的地方，它仍然可以。

我们的设计目标很明确：不妥协。如果你愿意，你可以
Metro 风格应用程序和改进的 Windows 之间无缝切换
桌面。现有的应用程序、设备和工具均保留并得到改进
在 Windows 8 中。另一方面，如果您喜欢沉浸在
只有 Metro 风格的应用程序（和平台）和新的用户体验，您
也可以这样做！开发人员可以针对有意义的 API
他们希望提供的软件。

至于是否仍支持现有技术，他们提到了以下内容：

我们将展示允许您编写 Metro 风格代码的全新工具
HTML5/JavaScript、C/C++ 和/或 C#/XAML 中的应用程序。
您作为所有这些语言的开发人员所做的投资
Windows 8 的继承，让您可以选择如何最好地制作
使用Windows 8系统服务。我们谈到 Windows 8
对于最终用户来说，它是一个不妥协的操作系统，也是一个不妥协的操作系统
开发者平台。

微软的 Jon DeVaan 的评论更让人放心：

桌面版的 WPF 和 Silverlight 保持不变。新来的
Windows 8 能够利用 WPF 和 Silverlight
创建 Metro 风格的知识（以及经过一些更改的代码）
应用程序。

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

Windows 8 Platform and tools

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.

回复收藏 0 原文