Re: Unicode setting question
"Tom Serface" <tom.nospam@camaswood.com> wrote in message
news:7274ECAC-28E9-4426-B147-715E16E0DA49@microsoft.com...
I find it confusing too that we get lots of things in the C#/WinForms
resource editor (like the ability to set tooltips, colors, fonts, etc.)
that we can't seem to get in the MFC resource editor even after all this
time. You'd think the same UI would work for both and it would just be a
matter of programming to connect the dots. If native does die it will be
because the "other stuff" has better tools imo not because the "other
stuff" is necessarily any better.
When you stop to think about it, when has the stuff with the best tools not
become the industry standard? It's a self-fulfilling circle. The best
programmers want to use the best tools, so they go there and create the best
products, which encourage people to develop even better tools for the
biggest dev market, and the cycle continues. The same is true of the
documentation. Windows has the best documentation (though not perfect), in
no small part to unauthorized reverse engineering and source code leakage
such as when Win2K source code was posted on the Internet, etc. But MS is
slowly letting more and more people look at their source code, the code to
key parts of the .NET framework was released, etc. So MS also is better
supporting an already well-documented ecosystem.
Anyway, it all starts with the best tools.
-- David