|
Show off
Snake BOA
Street ST
BOAST
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
We have a winner!
98.4% of statistics are made up on the spot.
|
|
|
|
|
D'oh! I was trying to work out how BOARD meant show off. Some days you just know things aren't going well.
|
|
|
|
|
That's round the corner on Snake Road! 
98.4% of statistics are made up on the spot.
|
|
|
|
|
I want to know that why c# developer choose WPF 
|
|
|
|
|
Because you can do things in WPF that aren't easily achievable in Windows Forms. For instance, restyling a TextBox in WPF is incredibly trivial (say, you want it to have rounded edges). Oh, and the binding engine is vastly superior in WPF to Windows Forms.
This space for rent
|
|
|
|
|
can i shift from Win Forms to WPF, if i dont have working knowledge of WPF
|
|
|
|
|
Yes, start by learning WPF.
|
|
|
|
|
How to successfully turn into WPF if i don't know the WPF but i know Win Forms, both are similar to learn or totally new?
|
|
|
|
|
WPF uses XAML, which is a declarative language (similar to HTML) to handle the UI. It is vastly different to WinForms.
This space for rent
|
|
|
|
|
@Pete O'Hanlon can you give Code Project WPF article link, Thanks For Taking interest.
|
|
|
|
|
To show you what WPF looks like, and to get you in the declarative mindset, try this[^] article. The excellent @sacha-barber also wrote a fantastic series starting here[^].
This space for rent
|
|
|
|
|
Apart from what Pete suggested, you can have a look at WPF related stuff here on Codeproject[^]
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning
|
|
|
|
|
But the learning curve is something akin to photoshop.
If they would upgrade GDI+ and allow it to use graphic card capability, now that would back awesome.
|
|
|
|
|
windows forms vs wpf[^]
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning
|
|
|
|
|
|
My experience of WPF as others have previously commented is that it makes what seems complicated easy and what seems easy as complicated.
There are some real advantages when it comes to design of the UI and how the UI binds to the data.
Some things are not straightforward.
It's a steep learning curve and it's not something you can pick up from scratch without doing a fair amount of reading first.
That said when things go well with WPF you can design some really nice applications.
I would also add that I think that as an exercise in itself it's worth learning, because it will introduce you to MVP within a non web environment and the challenge of learning new architectural patterns can in itself have its own value.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
Dunno. I use WinForms when I need a GUI. I'm more about function than form.
|
|
|
|
|
I don't. Partly because WPF has, and continues to be, voodoo to me.
That said, if I'm going to learn something obtuse, confusing, and poorly documented, I might as well dive straight into web development, which IMHO is where everything is going (or has gone), so that's where I've focused my learning energies.
If I ever end up doing mobile development, yeah, there's XAML and Xamarin, but at the moment, any work there hasn't escaped the event horizon.
|
|
|
|
|
Personally I choose it because I am way more productive in it.
It was a pain to learn. I kept trying to do thing the WinForm way, and it took a lot of code. For example I had a tree-view with 50 lines of code to change the selected item.... simply because I did not understand "if you are not databinding it, you are doing it wrong." And indeed the 50 lines of code was replaced with databinding to a simple property... it just worked.
Now I have learned it, I just "think MVVM and databinding" if I need a UI - and everything else is taking me too long and turn into too much spaghetti keeping the UI controls updated.
If I just need something small, I still do WPF but might skip the model - let the view model deal with the mess. It is easy to refactor out if it turns out the model would be useful after all.
And it makes it easy to keep up to date on the latest and greatest HTML UI frameworks and trends -
after all, they are just slowly trying to implement WPF without having the fundamentals right.
I do not really use the superior rendering capabilities of WPF. I suck at design, so tend to stick to default look in both WPF and WinForm.
|
|
|
|
|
lmoelleb wrote: I kept trying to do thing the WinForm way, and it took a lot of code. For example I had a tree-view with 50 lines of code to change the selected item.... simply because I did not understand "if you are not databinding it, you are doing it wrong." And indeed the 50 lines of code was replaced with databinding to a simple property... it just worked
That describes how I learned both WPF, and to be honest, .NET. I kept thinking I had to do all of this 'plumbing', when in fact I really just needed to drink the damned Kool-Aid™ already and believe.
Software Zen: delete this;
|
|
|
|
|
Exactly! The reason why WPF was intuitive to me was that the old cut&paste/replace idiom became the method to leverage any method used; short of learning a language like XML (XAML) and why all the stuff it enables one to do is a language itself.
So I guess it's the ease with which one is able throw big blocks of nonesense at a test platform and see the results all at once (or failures) that makes WPF so appealing.
But I am an eggheaded maunderer, so don't listen to me.
|
|
|
|
|
Imagine being held at gunpoint (bear with me) by a literate animal, and the only hope of rescue (BEAR WITH ME) is posting an encoded message online.
|
|
|
|
|
I can't bear to think how you would get out of this.
Perhaps you should address the situation, and we could arrange to swat him?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Sounds like a grizzly situation you are in 
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
