If you are an experienced PureMVC developer, you will now have less to explain to your coworkers who are not; just loan them the book (or show them where to buy it). If you are just starting out, then hopefully this book has given you an adequate understanding of what the PureMVC development process is like and the important points in the mindset for mastering it. As you seek to expand your skill with PureMVC, here are a few more tidbits to help you along your way.
Here is a short overview of the benefits of PureMVC from a debugging perspective. If you have never used your IDE’s debugger, it’s really simple, and I will show the basic steps here. If you are seasoned at debugging, I am sure you will appreciate the benefits of PureMVC’s underlying organization of your application as soon as you set your first breakpoint and inspect the variables. As you may know, often, when setting breakpoints in your application, you cannot see stuff that the class you have breakpointed does not have a reference to, so while you can tell the state of your breakpointed class, it is hard to know what is going on elsewhere without setting breakpoints all over the place like roadblocks on Christmas Eve.
In PureMVC, setting a breakpoint on any executing line of any
Proxy gives you a reference to the
Facade, which in turn gives you references to
Controller. They, in turn, give you references
to all your
Proxy and ...