Felice Pollano Blog

The Official Fatica Labs Blog

About the author

Author Name is someone.
E-mail me Send mail

Recent comments

Authors

    Disclaimer

    The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

    © Copyright 2008

    The future of CAB for rich clients: the MVC libraries scenario

    An interesting post here. Unfortunately there aren't a wide scope solution that could target easily both WPF and Winform.

    Some ineteresting links about this topic:

    Prism : targets WPF. Some features are:

    • "Enabled TFS Integration for releases
    • IMetadataInfo removed from the Prism framework. The application developer is now responsible for providing a model in order for the headers to bind to. We provide guidance on how to accomplish this in the RI though. Reason: flexibility.
    • MultiDispatchCommand renamed to CompositeCommand
    • DelegateCommand is now generic for compile time check of the parameter type (not at the XAML level though)
    • Bootstrapper refactored for unit testing. Added module initialize.
    • Random market feeds updates the UI continuously.
    • Ability to add named views to regions that you can easily retrieve later.
    • Added logger interface and default enterprise libary logger implementation
    • Several more refactorings and consistency fixes (lots!).
    • New UI Composition QuickStart. Demonstrates shell, global, local regions, and views. Note: This Quickstart uses a branch of the Prism framework source. We will be merging into the main."

    Caliburn : targets WPF. Some features are:

    • Improved asynchronous programming experience for actions.
    • Asynchronous module loading
    • Eager and lazy loaded modules with lazy loaded commands/presenters.
    • New isolation options for modules: None or Container-based.
    • Scoped UI composition and data storage.
    • Two different mechanisms for event aggregation; take your pick.  Choose a string-based mechanism similar to CAB or a strongly-typed message-based mechanism.
    • Support for triggering actions with routed events.
    • Support for action message forwarding.
    • IActionMessageHandler for advanced action message scenarios.
    • Support for Windsor/StructureMap/Spring.NET and now Unity containers.
    • Various bug fixes, including several that caused (the feeble) VS designer to break 

    Smart Client Software Factory – April 2008 : The CAB evolution on Visual Studio 2008.

    behind the scenes some projects as Acropolis disappear, and the WPF Composite Client seems not so active even if here we read that something shoul ship at the end of2008.

     

    Be the first to rate this post

    • Currently 0/5 Stars.
    • 1
    • 2
    • 3
    • 4
    • 5

    Tags: , ,
    Posted by Felice on Tuesday, May 13, 2008 11:31 AM
    Permalink | Comments (0) | Post RSSRSS comment feed

    Related posts

    Add comment


    (Will show your Gravatar icon)  

      Country flag




    Live preview

    Friday, November 21, 2008 7:06 PM

    Gravatar