I'm back coding WPF today. Whoopie!
I think you're all overly romanticising WPF. It's not a difficult as you portray, except perhaps for someone who has been coding WinForms for years and suddenly has XAML thrust into their faces (I doubt if there many many left in that position). So the main point of contention is development speed. I claim it takes me 5 times longer to write XAML/WPF than it does WinForms. Others here claim that WPF is far more productive. How is this possible? As I sit down now I have to look forward to writing more XAML by hand, with VS2010 on the left screen and Blend 4 on the right screen. I have to have the help open at all times because I can't find or remember all of the properties, classes, methods and elements. I just wrote some cryptic code to convert ICO files into ImageSources, jeezeuz! How are you so productive in WPF? How have you built your nirvana? Another point I made has been largely ignored: standard UI behaviour. What's happened to the UI design guidelines from Microsoft? I also love the way WPF gives you complete and utter freedom to create almost any UI you can think of, but as I said "who wants that?". I wasn't kidding when I said that my customers want a familiar and friendly UI with menus, toolbar, status bar, navigation, etc. WPF can give you a bit of wow factor as something transforms into view, a picture carousel, or a lovely templated grid. These wow things would be great in an app for the general public, but with specialised in-house apps they don't add much value. Oh well, perhaps another day of concentrated WPF coding will help boost my overall speed. Greg
_______________________________________________ ozwpf mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozwpf
