>>>>Hi,
>>>>
>>>>Anyone delved into this library deeply enough to form an opinion ?:
>>>>http://msdn.microsoft.com/en-us/library/cc707890.aspx
>>>
>>>I don't know much about it, but, from what I understand, PRISM is the way to go now. I believe CAL, when compared to PRISM, is too complex and PRISM "simplifies" the process of building loosely coupled layers that are required for such applications. The concept and framework is something we are slowly investigating and there is a *lot* to learn about it. Just Google the PRISM framework and pattern to find out more.
>>
>>Isn't 'Prism' the code-name for "Composite Application Guidance for WPF" - which is just that - guidance. This seems the latest version (Prism2? includes SilverLight):http://msdn.microsoft.com/en-us/library/dd458809.aspx.
>>But, AFAICS, CAL (the Composite Application Library) is MS's version of a framework for implementing the guidance - or, conversely, maybe Prism can be regarded as guidance on using the CAL?
>>
>>I've got the downloads and also watched the videos here:http://channel9.msdn.com/posts/akMSFT/Creating-a-modular-application-using-Prism-V2-Part-1-of-4--Creating-a-shell-and-modules/ but I can see it will take a lot more than that to properly 'come-to-grips' with it.
>>
>>Regards,
>>Viv
>
>
>No kidding that this Composite Application stuff is complex no matter what you call it. This link may help shed some light on it: http://www.tanguay.info/web/index.php?pg=codeExamples&id=105

Hi,

I think I understand the jist of everything by ploughing through the MS sample application - but I'm finding it difficult to translate this into a design that would be work well with the project that I'm currently engaged on. I think this is mainly because my app is very much graphics orientated and doesn't (in large part) lend itself well to the seperation of concerns aimed at by the CAL.....

Maybe for the next app......
Regards,
Viv