WPF--a threat to WinForms?

  • Thread starter Thread starter raylopez99
  • Start date Start date
not_a_commie said:
Holy crap, dude. Is this a joke? Come out of the closet. Plug your
computer into the internet. You seem like the kind of person who
doesn't deal with change well, which would make a job as a programmer
particularly difficult for you.
Click to expand...

How did you cope with change a year and a day before you started
coding in WPF, Commie? Projection noted...

WPF has been pushed with Vista for
several years now. API info on it has been available for at least
three years. WinForms goes back 7 years, although the format of the
WinForms library is similar to GUI APIs available years before that.
WPF is the technology intended to replace WinForms. You can file bugs
on WinForms with MS, but they won't get fixed. The future is WPF. And
it rocks, really. I've been coding WPF for a year and loving it. WPF
has some issues, but WinForms has ISSUES. WPF has had a lot of design
work. And overall I think it has come together quite well.
Notwithstanding that, I assure that the WinForms API won't disappear
any time soon.
Click to expand...

Well, I guess ISSUES > "some issues", but I'd be curious as to what
these issues are.
I have no idea what you are talking about here. Well, actually, I
think you're talking about XAML. However, I think you're comparing
apples and oranges.
Click to expand...

No, I was comparing storing your data in binary form rather than XML
(text based) form. There's a writeup in Albahari's book on it.
Binary > text for all but 'interoperability' (internet messaging
between disparate programs). Ever notice how bloated XML based files
are? Kind of like storing binary data in base 64.

Hey Commie, I'm almost as good a coder as you after only studying
WinForms for 6 weeks! What does that say about the depth of your
field? And no I don't code for a living...

Happy coding....

RL
 
Flicker is solved by Double Buffering (checking a property box) in
WinForms, but you're right, the GDI+ graphics in WinForms is very
slow*, then again in MFC they used to only Paint 'invalid' regions
that had been moved, so I guess it's an improvement.

Looking forward to dipping my toe in WPF to see how much better it is
than WinForms, which I kind of like (compared to MFC).

RL

* to see how slow, just resize a Winform window by dragging a border
back and forth; even on the fastest multicore core machine it will
cause the microprocessor 'speedometer' to shoot way up, indicating
valuable processing power and lots of clock cycles are being wasted on
resizing the window.
 
Flicker is solved by Double Buffering

Only in extremely rare cases. The double buffering likely won't effect
your control unless you draw the thing entirely yourself.
 
Flicker is solved by Double Buffering (checking a property box) in
WinForms, but you're right, the GDI+ graphics in WinForms is very
slow*, then again in MFC they used to only Paint 'invalid' regions
that had been moved, so I guess it's an improvement.

Looking forward to dipping my toe in WPF to see how much better it is
than WinForms, which I kind of like (compared to MFC).

RL

* to see how slow, just resize a Winform window by dragging a border
back and forth; even on the fastest multicore core machine it will
cause the microprocessor 'speedometer' to shoot way up, indicating
valuable processing power and lots of clock cycles are being wasted on
resizing the window.
Click to expand...

Here is a video by Billy Hollis which shows (to me anyway) an
impressive UI built with WPF. Doing the same thing with WinForms
would be much more difficult.

http://www.dnrtv.com/default.aspx?showNum=115

Chris
 
Back
Top