MVP Award...
in [MFC]
|
Prev: CMenu class and menu object
Next: need some class help
From: Hector Santos on 26 Feb 2010 09:14 David Lowndes wrote: >>> VS2010 editor was completely rewritten using WPF, >> Great. Thats a big endorsement for WPF. > > But not for the bugs they've (re)introduced into the editor > functionality ;) So much for the Black Box, Plug and Play theory :) -- HLS
From: Joseph M. Newcomer on 26 Feb 2010 11:44 Or the fact that they basically re-implemented what was already a flawed design. joe On Fri, 26 Feb 2010 13:49:03 +0000, David Lowndes <DavidL(a)example.invalid> wrote: >>> VS2010 editor was completely rewritten using WPF, >> >>Great. Thats a big endorsement for WPF. > >But not for the bugs they've (re)introduced into the editor >functionality ;) > >Dave Joseph M. Newcomer [MVP] email: newcomer(a)flounder.com Web: http://www.flounder.com MVP Tips: http://www.flounder.com/mvp_tips.htm
From: David Lowndes on 26 Feb 2010 12:10 >Or the fact that they basically re-implemented what was already a flawed design. From a couple of the issues I noticed, I have a suspicion they reimplemented it from an early version before bugs were fixed (a long time ago). Dave
From: James Juno on 26 Feb 2010 12:21 Funny thing. My shop specializes in scientific data visualization using OpenGL. We've replaced some of the MFC controls with in-house (and superior) equivalents rendered in an OpenGL context. I guess in a sort of bastardized way, this is similar to WPF. Still, we're unlikely to consider using WPF anytime in the near future. Our toolset is too highly integrated into the more battle-tested and mature (or, depending on your agenda, "legacy and obsolete") technology. -JJ "Ajay Kalra" <ajaykalra(a)yahoo.com> wrote in message news:37b06edd-73d5-4b4a-8f4d-d20207ea8dd1(a)k17g2000yqb.googlegroups.com... On Feb 25, 2:58 pm, "James Juno" <j...(a)noplace.fake> wrote: > Your post hits the nail on the head. I've been fanatical about UI > responsiveness for many years, through several companies and now in my own > shop. It's one of the reasons I quickly dismissed .NET for any serious UI > work (this was several years ago -- I have no idea how well the managed > paradigm performs now nor do I care -- I'm an old codger locked in his > ways). Just the startup time for even the simplest of the .NET samples was > horrible. I remember colleagues being delighted with the new language and > "my god the programming tools are manna from heaven," but I held steadfast > to my belief that none of that matters one wit to the user who, whether he > knows it or not, expects things to get done RIGHT NOW, from program > start-up > to its use to its shutdown. I won't bother expressing my feelings toward > these so-called browser-based apps. I used MFC for 10 years and have been using C#/.Net for over 4 years. Startup time is probably an issue(not if you use NGEN) but thats no reason to dismiss it. .Net is significantly ahead of older technologies. Our apps are trading apps in real world where performance is of extreme importance and it works fine. -- Ajay
From: Ajay Kalra on 26 Feb 2010 12:43
On Feb 26, 12:21 pm, "James Juno" <j...(a)noplace.fake> wrote: > Funny thing. My shop specializes in scientific data visualization using > OpenGL. We've replaced some of the MFC controls with in-house (and > superior) equivalents rendered in an OpenGL context. I guess in a sort of > bastardized way, this is similar to WPF. Still, we're unlikely to consider > using WPF anytime in the near future. Our toolset is too highly integrated > into the more battle-tested and mature (or, depending on your agenda, > "legacy and obsolete") technology. I am certain I will call OpenGL as obsolete technology(May DirectX is now better; dont know). There is no agenda here but for vanilla UI apps not requring any specialization, .Net is far superior IMO. Even with apps requiring specialization, .Net can coexist comfortably. The problem is not about embracing a newer technology, its about the cost of migrating over existing system to newer one. Normally there is no reason to do it and its a waste of resources without any real benefits. However for new apps, these rules dont apply. -- Ajay |