Hi,
I have a dilemma. I don't know in which api should I write games(WinRT or Win32). I want to target on Xbox One and PC.
It is possible, that XBOX will use WinRT?
It is difference(in speed) between Metro and Desktop?
It is better(in PC) stayed on Win32 or focus on WinRT?
Is WinRT a waste of time?
Worrying about this is a waste of time. Wrap WIn32 (or RT) in your own API wrapper, and target that. Modifying the wrapper at a later date will be trivial...
Thank you for quick answer. I just want to know which api is better to use.
Worrying about this is a waste of time. Wrap WIn32 (or RT) in your own API wrapper, and target that. Modifying the wrapper at a later date will be trivial...
Yes, I used wrapper in every project I have created
Frankly a UI layer most likely wont be available on XBox One. You will be expected to roll your own, or use a 3rd party service like WinForms.
Also, I bet you just about any money Metro is dead as a dodo within 4 years, just like WPF before it.
I believe that the c++ in WinRT is very different than standard c++. You didn't specify what language you are using.
It's called c++/cx http://en.wikipedia.org/wiki/C%2B%2B/CX
C++/CX is totally optional, you can use standard C++ with WRL instead. Not that you need to even with a crossplatform project the C++/CX bits can be compartmentalized, and even Microsoft recommends it's usage this way on MSDN (though their code examples do not demonstrate this).
Frankly a UI layer most likely wont be available on XBox One. You will be expected to roll your own, or use a 3rd party service like WinForms.
Also, I bet you just about any money Metro is dead as a dodo within 4 years, just like WPF before it.
I like Metro. So hearing say that makes me sad. Actually, what really makes me sad, is that you may be right.
I like Metro. So hearing say that makes me sad. Actually, what really makes me sad, is that you may be right.
The same was said about XNA. This platform did die, luckily the MonoXna project was started by some open-source developers with foresight. Soon the renamed MonoGame project might even provide the final parts of the content pipeline 
Personally I am working on my open-source Unity clone (mutiny) because I feel the same will happen with Unity (and .NET / C# in general).
So if anyone wants to attempt writing a C++/cx compiler and Metro system libraries, perhaps in 5-6 years developers can still use these platforms that they have invested their precious time in learning.
Otherwise, stick with good ol' boring C/C++ and OpenGL which is almost guaranteed to outlive existing tech ;)
Frankly a UI layer most likely wont be available on XBox One. You will be expected to roll your own, or use a 3rd party service like WinForms.
Also, I bet you just about any money Metro is dead as a dodo within 4 years, just like WPF before it.
I am so confused by this lol
Why would Microsoft allow people to use WinForms UI and not XAML lol? Do you have a source for this. Doing a quick search brought up some "Desktop dead" and "PC dead" links which was somewhat amusing
Personally I like all the XAML technologies but that's just me, I doubt VS would move onto WPF if it were dead or close to dying, besides what are the options for 'super quick' desktop development if it were.
No idea if metro will die in 4 years, but the next few years are going to be a lot of fun, so far ASP.NET MVC, DirectX, PC or Desktops in general and now metro are 'expected' to die, I don't really see any of them dying but lets wait and see.
On a serious note though, why is there very little info on Xbox One development, there is some crap about dev kits but nothing really informative
