Make metro a windowed program, that would work better on desktop.
metro in a window is an obvious solution. Esp from the perspective of user choice. What is the Microsoft reasoning for not allowing a metro app to display in a window on the desktop?
Comments
-
-
Congrats. But, just my opinion, C9 was much better back in the day. Anders was always great. Scoble and Rory were fun and seemed honest. Microsoft needs a public advocate, someone on the inside who speaks to the legitimate complaints of users and programmers. C9 should have someone challenging the Bing team on why their search engine is not growing in popularity, for example.
-
but in practice Tianyu, you end up getting some inscrutable compile errors.
Find the error in this code. Note the bullshit compile error.
void Tester2( unique_ptr<std::wstring> pString ) { } void CallTester2( ) { unique_ptr<std::wstring> pString ; Tester2( pString ) ; }4 IntelliSense: "std::unique_ptr<_Ty, _Dx>::unique_ptr(const std::unique_ptr<_Ty, _Dx>::_Myt &) [with _Ty=std::wstring, _Dx=std::default_delete<std::wstring>]" (declared at line 1447 of "C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\include\memory") is inaccessible c:\SkyDrive\democpp\Tester\Tester.cpp 379 14 Tester
Error 3 error C2248: 'std::unique_ptr<_Ty>::unique_ptr' : cannot access private member declared in class 'std::unique_ptr<_Ty>' c:\skydrive\democpp\tester\tester.cpp 382 1 Tester -
Why is const needed anyway? C# does not have the concept.
Another C++ request ... enum class. Have a built in ToString method or enable enum class to have member functions, or add extension methods to the language. The purpose being to enable enum specific code, like Parse and ToString, to be called using dot notation from an enum instance.
enum class Colors { red, white, blue } ;
Colors color = Colors::red ;
auto textColorName = color.ToString( )
auto anotherColor = Colors::Parse( textColorName ) ;Bigger picture. Give me a native version of C#. Or enhance the struct handling capabilites of C#. ( C# cannot efficiently handle PIDLs used by windows shell. ) Microsoft to this day says that windows shell code written in C# is unsupported. A C# like native code language would be awesome.
-
does c++11 provide yield return and extension methods as we know them from C#? Does it do away with header files?
-
-
1 hour ago, bkuhns wrote
*snip*
Watch Bjarne's presentation from Going Native 2012, "C++11 Style". He shows how strong abstractions can be built using C++11 that are clean and modern.
Well, I doubt I will find a satisfactory way to organize my C++ code because I have to code in both .h and .cpp files. I like the way my C# code is organized with each class in a .cs file and those files are in folders organized along namespace lines. I like being able to return Tuples from C# methods and adding extension methods. Granted these are my little tics, but it still makes a lot of sense to me that the native language used by MSFT should be as similar to C# as possible and focused on doing what you need a native language to do - run with low overhead.
-
22 hours ago, Charles wrote
*snip*
Really? With C++, you're given very sharp knives to cut through computational complexity. As such, you need to learn how to use them wisely (and effectively). When has this not been the case for C++? Further, C++ is language that affords great efficiency and performance across the hardware spectrum and with high level modern programming abstractions. ...
See, I thought we simply needed a language to write efficient native code. Kind of like C with modern programming constructs like namespaces, classes, interfaces, extension methods, tuples, lambdas, collections, ... To write large apps I will use C#. For energy efficient, quick starting standalone apps give me a native language with a familiar syntax.
-
2 hours ago, STL wrote
> Still do not understand why C++, with all the additions being throw at it, is retaining the #include header file thing.
That's being worked on ("modules") for a future C++ Standard.
I am really not a complainer, but I wish MSFT would just forge ahead and do modules on their own. From my recent experience with C++ it is very difficult to organize your code when you have to split things between .h and .cpp files. Esp when I bring my C# practices to a C++ project. Filters are not a substitute for C# folders.
thanks for the explanations.
-
Scott lost me almost as quickly as MSDN magazine does every time I try to read it. I have never seen && in c++ code. I am not completely certain about rvalue and lvalue. The r and l stand for right and left side of the expression, right? Other than that I am lost.
Still do not understand why C++, with all the additions being throw at it, is retaining the #include header file thing. That is the aspect of the language that to me makes it difficult to use and structure your code files.
