VS2008 Beta 2 and the WPF editor
-
just trying it, is it just me or the editor is far from being usable ? I mean, it's very nice, but when I need to bind events from any control the only thing it can do is bind one event : example, insert a button, then Ctrl+Dbl click adds the click event and this seems the only event that can be managed from the editor...or I'm missing where it can be done ? tried the property window etc etc, windows form editor seems more powerful... what's your experience ?
-
just trying it, is it just me or the editor is far from being usable ? I mean, it's very nice, but when I need to bind events from any control the only thing it can do is bind one event : example, insert a button, then Ctrl+Dbl click adds the click event and this seems the only event that can be managed from the editor...or I'm missing where it can be done ? tried the property window etc etc, windows form editor seems more powerful... what's your experience ?
The visual designer still lacks in depth support for adding event handling methods for elements. IMO that does not render the designer "far from being usable" though. One thing to keep in mind is that whenever you are handling an element's events, consider whether you should be using a Command instead. It's generally better in WPF to handle user interactions via the routed Command system because it promotes a loose coupling between the visuals and application logic. Just my 2 cents.
:josh: My WPF Blog[^] The greatest danger for most of us is not that our aim is too high and we miss it, but that it is too low and we reach it. - Michelangelo (1475-1564)
-
The visual designer still lacks in depth support for adding event handling methods for elements. IMO that does not render the designer "far from being usable" though. One thing to keep in mind is that whenever you are handling an element's events, consider whether you should be using a Command instead. It's generally better in WPF to handle user interactions via the routed Command system because it promotes a loose coupling between the visuals and application logic. Just my 2 cents.
:josh: My WPF Blog[^] The greatest danger for most of us is not that our aim is too high and we miss it, but that it is too low and we reach it. - Michelangelo (1475-1564)
Josh Smith wrote:
It's generally better in WPF to handle user interactions via the routed Command system because it promotes a loose coupling between the visuals and application logic. Just my 2 cents.
Hmm.. your ideas intrigue me, and I would like to subscribe to your newsletter - Err, sorry, channeled Homer Simpson for a second. Any plans on writing an article about routed Commands? :) I've looked at that a little bit but it seemed rather intimidating..
-
Josh Smith wrote:
It's generally better in WPF to handle user interactions via the routed Command system because it promotes a loose coupling between the visuals and application logic. Just my 2 cents.
Hmm.. your ideas intrigue me, and I would like to subscribe to your newsletter - Err, sorry, channeled Homer Simpson for a second. Any plans on writing an article about routed Commands? :) I've looked at that a little bit but it seemed rather intimidating..
That might be a fun topic to write about. I'll think about it. Thanks for the idea...
:josh: My WPF Blog[^] The greatest danger for most of us is not that our aim is too high and we miss it, but that it is too low and we reach it. - Michelangelo (1475-1564)
-
Josh Smith wrote:
It's generally better in WPF to handle user interactions via the routed Command system because it promotes a loose coupling between the visuals and application logic. Just my 2 cents.
Hmm.. your ideas intrigue me, and I would like to subscribe to your newsletter - Err, sorry, channeled Homer Simpson for a second. Any plans on writing an article about routed Commands? :) I've looked at that a little bit but it seemed rather intimidating..
I actually wrote a bit about routed commands on my blog a while back. Here[^] is the link, if you want to check it out.
:josh: My WPF Blog[^] The greatest danger for most of us is not that our aim is too high and we miss it, but that it is too low and we reach it. - Michelangelo (1475-1564)
-
just trying it, is it just me or the editor is far from being usable ? I mean, it's very nice, but when I need to bind events from any control the only thing it can do is bind one event : example, insert a button, then Ctrl+Dbl click adds the click event and this seems the only event that can be managed from the editor...or I'm missing where it can be done ? tried the property window etc etc, windows form editor seems more powerful... what's your experience ?
Am I the only who still can't stop reading WPF as WTF? I know - I need to grow up...
cheers, Chris Maunder
CodeProject.com : C++ MVP
-
Am I the only who still can't stop reading WPF as WTF? I know - I need to grow up...
cheers, Chris Maunder
CodeProject.com : C++ MVP
Chris Maunder wrote:
I know - I need to grow up...
Nah, if you did that this place would be as boring and stuffy as your grandparents' front porch :) I sometimes read it as 'WTF' also and when I first started seeing it, I did think it was a typo.. :doh: :laugh:
-
Josh Smith wrote:
It's generally better in WPF to handle user interactions via the routed Command system because it promotes a loose coupling between the visuals and application logic. Just my 2 cents.
Hmm.. your ideas intrigue me, and I would like to subscribe to your newsletter - Err, sorry, channeled Homer Simpson for a second. Any plans on writing an article about routed Commands? :) I've looked at that a little bit but it seemed rather intimidating..
I just re-read Chapter 7, titled "Actions", in "Essential Windows Presentation Foundation" by Chris Anderson. That is probably the best explanation of routed commands out there. I was going to write an article or blog post about the topic, but after revisiting that chapter I don't see a reason to do so. If you want to understand commands in WPF, just read that chapter.
:josh: My WPF Blog[^] Without a strive for perfection I would be terribly bored.
-
I just re-read Chapter 7, titled "Actions", in "Essential Windows Presentation Foundation" by Chris Anderson. That is probably the best explanation of routed commands out there. I was going to write an article or blog post about the topic, but after revisiting that chapter I don't see a reason to do so. If you want to understand commands in WPF, just read that chapter.
:josh: My WPF Blog[^] Without a strive for perfection I would be terribly bored.
Josh Smith wrote:
If you want to understand commands in WPF, just read that chapter.
Hehe... ok Josh. I generally dislike purchasing programming books because a) writers simply don't know how to present technical material and b) I don't like having obsolete texts on my bookshelf, but I suppose I can make an exception.. ;)