Re: Why are .Net UIs slower than C++ or classic VB?

The new Windows Presentation Foundation stuff looks much better than the
UI stuff we currently have for .Net.

It's at the core of Vista's new look and is promised as an upgrade for XP
and 2003 Servers.

You are right Jim!

Just wish we had it now.....I'd hate to think I have to redo these apps
all over again a year (or so) from now.

Thats why we tier apps right?

Cheers,

Greg


"Jim Hubbard" <reply@xxxxxxxxxxxxx> wrote in message
news:NVn5g.3403$QU3.607@xxxxxxxxxxxxxxxxxxxxxxxxx

"Barry Kelly" <barry.j.kelly@xxxxxxxxx> wrote in message
news:ifob52pc8iuud90d1621g4pcbn2hrvg16b@xxxxxxxxxx
"Jim Hubbard" <reply@xxxxxxxxxxxxx> wrote:

I've noticed (for quite some time now) that .Net UIs are not as
responsive
(see Franklin Covey's PlanPlus for Windows XP or Symantec's .Net Norton
Antivirus or even the .Net version of Paint done by Washington
University vs
good old Paint UIs for examples).

They are also not as professional looking as the older applications and
the
reaction times of the UIs is not professional looking at all.

Why do you think this is? Is it bad programming or is there something
else
going on here?

I agree. I think (and hope) it's a lot to do with GDI+ not being
accelerated (and it probably will never be, as WPF approaches).
Something I've especially noticed is that resize logic for forms with
lots of nested containers is especially expensive. Very laggy resizing
of 16 or so nested containers of different kinds shouldn't slow a 3GHz
machine to a crawl, but it can and does!

-- Barry

The new Windows Presentation Foundation stuff looks much better than the
UI stuff we currently have for .Net.

Take a look at the demos for Windows Expression at
http://www.microsoft.com/products/expression/en/default.mspx. In the
demos, the UIs look fast and smooth. Not at all jerky or slow!

It's at the core of Vista's new look and is promised as an upgrade for XP
and 2003 Servers.

Just wish we had it now.....I'd hate to think I have to redo these apps
all over again a year (or so) from now.

Jim



.

Relevant Pages

  • Re: NT4 to Win 03
    ... Easies is to upgrade your existing PDC. ... you have to set the AD domain in Native mode. ... If you upgrade you do not have to set your AD domain in native mode. ... > assume i will install the new 2003 servers one at a time. ...
    (microsoft.public.windows.server.migration)
  • Re: Graphical Interfaces
    ... A sampling of the things that Microsoft has never really understood: ... - You can't reboot servers to install software. ... you can't upgrade anything in less than two years. ... - Internal documentation of software is a good thing, especially for tech support. ...
    (comp.os.linux)
  • Tech directions for Delphi?
    ... Current development tools and languages are quite inconvenient when doing multithreading, not only because of thread safety, but because load balancing and true parallelism is really hard to achieve (even on a dual core, try making a mere "search and replace"... ... Quad-core will be available by the end of the year, and will be mainstream by the end of 2007, at that point, 16 core servers won't be such alien encounters. ... Here is an opportunity to leapfrog MS: while they're busy refining .Net and presentation layers, build the development platform that will process, compute and manage all the /data/. ...
    (borland.public.delphi.non-technical)
  • Re: Tech directions for Delphi?
    ... More CPUs on an entry-level desktop machines than most servers ever had. ... on a quad core can already involve hellish stuff). ... There are specialty languages and arcane tools, ... Here is an opportunity to leapfrog MS: ...
    (borland.public.delphi.non-technical)
  • Re: NT4 to Win 03
    ... > users access to NT 4.0 file/application servers, ... In other words, if I upgrade my ... replication between NT 4.0 BDCs and AD DCs in the same domain. ... > the NT domain to the AD domain, or upgrade, by upgrading the NT PDC first. ...
    (microsoft.public.windows.server.migration)