What is the future of these technologies? How can new and old technologies work together? Should we start using a whole new framework soon?
Does anyone have an official source to clarify the situation?
WinRT is an object-oriented replacement to Win32, but the Win32 API has not been deleted, and old applications that use the traditional application execution environment will continue to work as expected.
Joe Stegman’s at the BUILD conference This talk details the expectations.
> “This is the same thing, right now, and is now shipping boxed on Windows 8.”
> C, C#, VB: XAML first class The programming language
> XAML control is “native” WinRT API
>”The content you are used to using in Silverlight and WPF is consistent with what you may be doing in the future in Windows 8.”
So yes, existing technologies will still be supported. However, in order to take advantage of these new technologies, you will have to be based on WinRT. Using XAML is different from what you are used to,
development blog of Windows 8 ( BUILD) shines in the background and design decisions.
The new Metro style user interface of Windows 8 is a comprehensive overhaul, and a new experience is designed in the front.
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 permanen tly 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 Windows 8 development team recognized the need to continue to support existing desktop interfaces and applications, and even continue to improve. As they discussed in April 2007, The gap between Metro style and traditional desktop is 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 attempts to replace the existing interface with a suitable interface, but the traditional desktop can provide a better experience, but it still works.
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 for whether the existing technology is still 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 Wind ows 8 being
a no-compromise OS for end-users, and it is also a no-compromise
platform for developers.
Microsoft Jon DeVaan’s comments are even more impressive Rest assured:
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.
See the first announcement of the HTML5/JS Windows 8 GUI, a large number of WPF and Silverlight developers panicked.
What is the future of these technologies? How can new and old technologies work together? Should we start using a whole new framework soon?
Does anyone have an official source to clarify the situation?
In the keynote of the build conference, they showed the following platform diagram:
WinRT is an object-oriented replacement for Win32 , But the Win32 API has not been deleted, and old applications that use the traditional application execution environment will continue to work as expected.
Joe Stegman’s This talk at the BUILD conference detailed the expectations.
< p>>”This is the same thing, right now, and now it is shipped boxed on Windows 8.”
> C, C#, VB: XAML’s first-class programming language
> XAML controls are “native “WinRT API
>”The content you are accustomed to using in Silverlight and WPF is consistent with what you may be doing in the future in Windows 8.”
Then yes, the existing technology will still be supported But, in order to take advantage of these new technologies, you will have to be based on WinRT. Using XAML is different from what you are used to,
development blog of Windows 8 (BUILD) shines in the background and design decisions.
Windows 8’s new Metro style user interface is a comprehensive overhaul, with a new experience designed in front.
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 d esktop—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 Windows 8 development team recognized the need to continue to support the existing desktop interface and applications, and even continue to improve. As they discussed in April 2007, the gap between Metro style and traditional desktop is 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.< /p>
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.
Metro style interface tries to replace the existing interface with a suitable interface, but traditional desktops can provide better Experience, but still ok.
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 for whether the existing technology is still supported, they mentioned the following:
p>
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-compromis e
platform for developers.
Microsoft Jon DeVaan’s comments are more reassuring:
WPF and Silverlight continue New to Windows 8 is the ability to leverage your WPF and Silverlight knowledge (and code with some changes) to create Metro Style applications. unchanged for the desktop.