Hello developers and designers,
I am very willing to learn WPF in which i use C# as the logic code.
Or i ‘try’ to anyway.
I have written a 2-page long code-behind in Forms-style though, so i know some syntaxes.
But that was a really cumbersome way of doing it.
The problem is that i am still lingering around the area of understanding at least the basic concept of object oriented programming. But 9 out of 10 times i am not getting the example-codes entirely because of that ‘1 little thing of which i don’t even know what it’s called’.
How do you even know if there is a command for the function you want to express and more importantly…. how it’s called and where it located in what namespace?
Even the best video-examples aren’t doing it for me, because when any code is typed, they never explain how the code exactly works. And most of the times it just doesn’t even add up to what i know of logic code (of course i’m wrong).
In the early days i learned the Commodore64’s Basic no problem.
Learning and writing Actionscript (Flash), within 2 months creating a 2D-shoot’em up
Learning and writing CMD, within 3 months writing 5000+ lines of code for all sorts of functions.
Why in Merlin’s beard is WPF so hard?
Watching the “simplest” tutorial-video’s are becoming more and more de-motivational.
Anyone recognizes this?
Thanks for reading,
Danny
Regarding WPF the articles I’ve found to be most useful are the overviews on MSDN, they might take quite some time to work through but they are concise and in-depth, see this page for a master-overview.
Why WPF is hard is a good question, one primary cause might be that it is simply huge, at least i perceive it that way. Aside from having all the code you also now have XAML markup which is a world of its own.
Someone from Microsoft who did a presentation on F# in 2008 said that if you know three of the keywords,
let,fun&|>, you know the whole language, which is not even that much of an overstatement. WPF on the other hand is not a language, it is a sub-framework. If F# can be likened to 3 nanotechnology building blocks then WPF is a 50 meter workbench stacked with tools (the controls) and a dozen heavy duty machines (WPF mechanisms like dependency properties, data binding, commanding, data templating, etc.), and all of those come with a manual. So if you are facing a problem you pretty much need to know what all the tools and machines do so you know which to use, and then of course you also need to know how to use them, apart from their basic functionality each may even have its own kinks and peculiarities which are important to keep in mind.So learning WPF requires a lot of raw knowledge of the framework but also experience so you know what is the best approach in a given situation and to get a feeling for what can be done and what cannot.