How many of you use WPF
-
I'm thinking of just boycotting the technology. Why should I have to learn something new and complicated just for the sake of being up to date? I don't like WPF and how it makes thinks seem messy and more complicated. I should not have to write XML and hoolaguh boolahuh to make a button on a form. WinForms, GDI/+, OpenGL, and DirectX is all we need! Who is with me on this?
The Digital World. It is an amazing place in which we primitive humans interact. Our flesh made this synthetic machine. You see, we are so smart, we know a lot of stuff. We were grown from cells that came from the universe, which the matter and physics I'm typing in it is amazing how the universe is working. Human life is very amazing. How I experience this sh*t its like wow.
This reminds me of a time I complained on this message board about the technology moving too fast for me to keep up. .NET 2.0 had been out for about a year, it seemed, when they started releasing 3.0. I complained on here that they need to wait much longer before releasing another major version as I haven't even come close to learning what is already out there (.NET 2.0 in this case). Another person responded by saying I was stupid for thinking that innovation was bad (in so many words). Hmmm. Now, just because a new version of an existing product is released with some new things, doesn't necessarily mean its pure innovation, right? In any case, I haven't taken much time to look into WPF, or WCF or, what's the other one, ...; I'm still too busy learning .NET 2.0! :)
-
I think ReSharper screwed it up, but even after disabling ReSharper and reverting to VS Intellisense, it still no longer works. I'm sure nothing short of a complete re-install will fix it.
Pits fall into Chuck Norris.
Take a look at Karl Shiflett's blog - he details a fix there.
Deja View - the feeling that you've seen this post before.
-
Mustafa Ismail Mustafa wrote:
You don't develop for a living do you?
He said the other day what he does for a living. http://www.codeproject.com/script/Forums/View.aspx?fid=2605&msg=2529900[^]
-
Dude, you should go back to my original post. I said, "Fortunately, I am still on XP along with my customer base. I don't have to worry so much about silly new three letter acronyms.". You are the one that said "WPF runs on XP". You are the one that brought up WPF in response to my post. So you can run around telling me I am wrong about WPF? Give me a break. I suggest you reread this thread and put some fiber in your diet.
CodeWiz51 -- Life is not a spectator sport. I came to play. Code's Musings | Code's Articles
CodeWizard1951 wrote:
I said, "Fortunately, I am still on XP along with my customer base. I don't have to worry so much about silly new three letter acronyms.".
Yes, and that was a silly thing to say, because WPF is equally an option in XP as it is in Vista.
CodeWizard1951 wrote:
You are the one that said "WPF runs on XP".
Correct. It does. Perhaps what you meant is that you expect your XP user base to be ignorant of WPF and therefore you have no pressure on you to learn a new technology that provides seriously powerful, flexible and cool UI.
CodeWizard1951 wrote:
You are the one that brought up WPF in response to my post.
So, you posted in a thread on WPF, mentioned 'silly three letter acronyms', but I brought up WPF ?
Christian Graus Please read this if you don't understand the answer I've given you "also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it ) ( spaces added for the benefit of people running at < 1280x1024 )
-
CodeWizard1951 wrote:
I said, "Fortunately, I am still on XP along with my customer base. I don't have to worry so much about silly new three letter acronyms.".
Yes, and that was a silly thing to say, because WPF is equally an option in XP as it is in Vista.
CodeWizard1951 wrote:
You are the one that said "WPF runs on XP".
Correct. It does. Perhaps what you meant is that you expect your XP user base to be ignorant of WPF and therefore you have no pressure on you to learn a new technology that provides seriously powerful, flexible and cool UI.
CodeWizard1951 wrote:
You are the one that brought up WPF in response to my post.
So, you posted in a thread on WPF, mentioned 'silly three letter acronyms', but I brought up WPF ?
Christian Graus Please read this if you don't understand the answer I've given you "also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it ) ( spaces added for the benefit of people running at < 1280x1024 )
>>So, you posted in a thread on WPF, mentioned 'silly three letter acronyms', but I brought up WPF ? Yep, that's about the size of it. I posted in a thread asking "How many of you use WPF". I said I wasn't worrying about TLA's. This wasn't a highly technical thread and you managed to turn it into me claiming that WPF had to be used on Vista, which I did not claim at all. I simply said that WPF is far less preferred on XP than on Vista, which is still my opinion. You went on the tell me how I could use C if I wanted to create a user interface on Vista. (Which, by the way I wouldn't want to do. I find dialog resources far more convenient to utilize than building an interface in code from scratch. I built enough of those apps back in the days of Windows 3.1 and I have no desire to return to that regime.) I am eternally grateful to you for letting me know that C can be utilized, as I thought VS 2008 no longer supported MFC, WTL, ATL or any other native technology when programming in Vista. In fact, I thought everyone had to use Iron Python when programming on Vista. Thanks for the repartee. It was real and it was fun, but it wasn't real fun.
CodeWiz51 -- Life is not a spectator sport. I came to play. Code's Musings | Code's Articles
-
Gary R. Wheeler wrote:
You do if the image on the button must remain proportional to the size of the button, the button size can change, and you want it to look decent. Such as in my application which represents components in a piece of equipment using buttons.
If you are using images then vector graphics wont help you any.
The Digital World. It is an amazing place in which we primitive humans interact. Our flesh made this synthetic machine. You see, we are so smart, we know a lot of stuff. We were grown from cells that came from the universe, which the matter and physics I'm typing in it is amazing how the universe is working. Human life is very amazing. How I experience this sh*t its like wow.
The images on the buttons are drawn using vector graphics :rolleyes:.
Software Zen:
delete this;
Fold With Us![^] -
Kevin McFarlane wrote:
I don't use it myself but our application (software for controlling an industrial print machine) uses it.
Why couldn't you design the application without the use of such controls? In the world of programming and application design there are many possibilities to accomplish the goal. I believe a simple bitmap would be a better solution that a 3d rendered control.
The Digital World. It is an amazing place in which we primitive humans interact. Our flesh made this synthetic machine. You see, we are so smart, we know a lot of stuff. We were grown from cells that came from the universe, which the matter and physics I'm typing in it is amazing how the universe is working. Human life is very amazing. How I experience this sh*t its like wow.
We could have done. But WPF happens to enable a richer UI in our case (it's not just WPF versions of standard UI elements, such as buttons). So we've decided to use it. Why use anything new? Why not write all our code in assembler? I agree we shouldn't use new just for newness' sake. But if there is some advantage to it why not?
Kevin
-
I'm on your side mister, the GUI just needs to enable the user to work efficiently with as little mouse clicks and movements as possible. And it needs to feel natural and logical. Ofcourse it helps if it's not butt ugly too, if you have to stare at it all day it gets kinda tiring if it's bright purple + green.
Wout
-
Darn! I just did my whole site (and wardrobe in fuscia and lime... now you tell me that won't be nice to look at all day? What's a programmer to do?
Me thinks you are kidding us! ;P You are going over pretty old thread by the way!
Wout
-
No more or less than it is on Vista.
Christian Graus Please read this if you don't understand the answer I've given you "also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it ) ( spaces added for the benefit of people running at < 1280x1024 )
-
Yeah, except which app developer wants to force his users to download the huge runtimes for the framework in XP? I find it to be a deal killer.
My app comes with 3 gig of content, on a DVD. I agree, for downloadable apps, the frameworks ( .NET and WPF ) are an issue.
Christian Graus Please read this if you don't understand the answer I've given you "also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it ) ( spaces added for the benefit of people running at < 1280x1024 )
-
I'm thinking of just boycotting the technology. Why should I have to learn something new and complicated just for the sake of being up to date? I don't like WPF and how it makes thinks seem messy and more complicated. I should not have to write XML and hoolaguh boolahuh to make a button on a form. WinForms, GDI/+, OpenGL, and DirectX is all we need! Who is with me on this?
The Digital World. It is an amazing place in which we primitive humans interact. Our flesh made this synthetic machine. You see, we are so smart, we know a lot of stuff. We were grown from cells that came from the universe, which the matter and physics I'm typing in it is amazing how the universe is working. Human life is very amazing. How I experience this sh*t its like wow.
If you are not interested in WPF then you don't have to learn it. WPF, in its current state, reminds me of the real old days of HTML programming. The tools, while getting better, are still way to immature to be overly useful. As a result you do spend a lot of time in the XML realm. But this isn't the way it will always be. Sort of like ASP.NET today or even WinForms, eventually you'll be building UIs via the designers and not thinking about the code behind the scenes. At the end of the day every UI framework ultimately is nothing more of a facade over the real format. WinForms is nothing more than hiding code. ASP.NET is nothing more than HTML. Even Win32 dialogs are nothing more than structures in memory. WPF does open up a lot of flexibility that Win32/WinForms just doesn't have. Ultimately whether WPF succeeds or not depends upon how much people want non-standard UIs over standard ones. It is ironic that for the past couple of decades MS has pushed consistent UIs (except anything related to music, go figure). Now WPF comes along to introduce non-standard UIs. WPF also eliminates many of the headaches of Win32/WinForms programming. Rather than messages going to a target window they can be bounced up and down the window hierarchy with ease. This makes taking over child controls a lot easier than in Win32/WInForms where you would have to use hacks. My definition of a good UI is one that the user can easily pick up and understand without the need for training or help. It is intuitive and all core functionality is easily accessible to keep efficiency up. Whether the UI is a listbox and a button or a complex form doesn't matter. It is in how users will use it that determines a good UI. WPF doesn't make it any easier to develop good UIs. It allows you to accomplish certain things easier. Many of the canonical examples that you'll see for WPF involve animating buttons or displaying videos in controls. Honestly these are to show off what is possible with WPF rather than examples of how you will commonly use it. More likely uses for WPF would involve the ability to theme the entire app and allow users to change it (something that is doable, but not easy, in WinForms). For people with color blindness or sensitive eyes this is a blessing. WPF also has some hooks for better architecture such as command routing (sorely missed in WinForms). WPF has its usages but it isn't right for everyone or every project. Right now I'm working on a project where users can design their own screens
-
I'm thinking of just boycotting the technology. Why should I have to learn something new and complicated just for the sake of being up to date? I don't like WPF and how it makes thinks seem messy and more complicated. I should not have to write XML and hoolaguh boolahuh to make a button on a form. WinForms, GDI/+, OpenGL, and DirectX is all we need! Who is with me on this?
The Digital World. It is an amazing place in which we primitive humans interact. Our flesh made this synthetic machine. You see, we are so smart, we know a lot of stuff. We were grown from cells that came from the universe, which the matter and physics I'm typing in it is amazing how the universe is working. Human life is very amazing. How I experience this sh*t its like wow.