Stephen, Prism would divert and solve my whole loading problem. Trouble is that I started this app when Prism was still in nappies and I decided to write my own mini-CAB which used the View-Controller pattern. I spent several weeks writing a demo in CAB and it was monstrous overkill for a team of one and half people. It made more work than it solved. I figured the same would happen with Prism, however I would now consider using it for any new large SL project, or perhaps the MVVM-lite that I saw last week.
I was rather irritated that I followed the CAB pattern, and then last year everyone goes into a frenzy of MVVM and binding everything to everything else. Due to peer group pressure, over the last few months I've refactored my app to use binding in the MVVM style. Now my app is mostly MVVM with some remnants of View-Controller where I found the binding so mind-bogglingly difficult to implement that I skipped it for now. I find that using pure binding is like building a delicate crystal palace made out of puzzle pieces. Binding is a clever invention, but it was released before anyone looked at the big picture of how to use it consistently and productively. I spend more time tweaking bound classes, properties and XML than I do writing code. Now we've got people advocating binding for method calls using wrapper classes and attached properties and I'm still not sure what's the best way of doing it. It's like it's being invented on the run. Greg
_______________________________________________ ozsilverlight mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
