Sponsored By Aspose - File Format APIs for .NET

Aspose are the market leader of .NET APIs for file business formats – natively work with DOCX, XLSX, PPT, PDF, MSG, MPP, images formats and many more!

Presentation Patterns for Virtual ALT.NET in August: You pick the topics

I will be presenting at the Virtual ALT.NET meetings during the first two weeks of August.  I would like to present preliminary work from my book on Presentation Patterns, but the VAN administrators and I would like you to select the specific topics.  I re-enabled comments this morning, so vote in the comments for one or more of these topics (feel free to write in other topics around desktop applications):

  1. Separated Presentation patterns.  You know, what are your options, why are they different, and when would you choose one or another for a particular scenario.  Model View Presenter variants and Presentation Model (MVVM). 
  2. “Screen Activation Lifecycle” — Design patterns and the system responsibilities for systems composed of multiple screens
  3. DSL development within a desktop application.
  4. Test Automation strategies.  How testability impacts design
  5. Event Aggregation
  6. Managing the application shell
  7. Using an IoC tool within a desktop application for extensibility

Thank you, and I’ll virtually see you in August.

 

If you’re not familiar with the “VAN” yet, here’s an introduction from Zachariah Young.

About Jeremy Miller

Jeremy is the Chief Software Architect at Dovetail Software, the coolest ISV in Austin. Jeremy began his IT career writing "Shadow IT" applications to automate his engineering documentation, then wandered into software development because it looked like more fun. Jeremy is the author of the open source StructureMap tool for Dependency Injection with .Net, StoryTeller for supercharged acceptance testing in .Net, and one of the principal developers behind FubuMVC. Jeremy's thoughts on all things software can be found at The Shade Tree Developer at http://codebetter.com/jeremymiller.
This entry was posted in Uncategorized. Bookmark the permalink. Follow any comments here with the RSS feed for this post.
  • Jean-Francois Cantin

    I vote for 1, 2 and 6

  • http://devlicio.us/blogs/christopher_bennage/ Christopher Bennage

    1,2,6,5

  • Brad Mead

    1, 4 and 6

    Look forward to it!

  • David Fauber

    Oh man, #2 would be a god-send for me right now.

  • http://http//addwatch.wordpress.com/ José Filipe

    1. Separated Presentation patterns.

    2. “Screen Activation Lifecycle”

  • Eyston

    4. Test Automation strategies. How testability impacts design

    5. Event Aggregation

    ditto for those.

  • Bill

    These aren’t among your listed topics but I’d love to see a discussion of:

    * Common code smells (and associated refactorings) you’ve encountered specifically when using Separated Presentation (big presenters, etc.)

    * Using Separated Presentation patterns for complicated views.

  • Gabriel Schenker

    4. Test Automation strategies
    7. Using and IoC container (advanced context based scenarios)

  • http://jonkruger.com/blog Jon Kruger

    4. Test Automation strategies. How testability impacts design

    … particularly if you talk about testing other than writing unit tests (e.g. functional testing).

  • http://codebetter.com/members/Robbie-Courtney/default.aspx Robbie Courtney

    1. “Screen Activation Lifecycle” — Design patterns and the system responsibilities for systems composed of multiple screens

    2. Test Automation strategies. How testability impacts design

    3. Managing the application shell

  • Siim

    1. Separated Presentation patterns. You know, what are your options, why are they different, and when would you choose one or another for a particular scenario. Model View Presenter variants and Presentation Model (MVVM).
    2. Event Aggregation
    3. “Screen Activation Lifecycle” — Design patterns and the system responsibilities for systems composed of multiple screens
    Test Automation strategies. How testability impacts design

  • Valeriu Caraulean

    I’d like hear you speaking about:
    2. Screen Activation Lifecycle
    7. Using an IoC tool within a desktop application for extensibility

    Thanks

  • Brian Chiasson

    1. Separated Presentation patterns.
    2. “Screen Activation Lifecycle”

  • http://codebetter.com/members/mcnamara/default.aspx mcnamara

    Hi

    I am interesting in the following ones:

    1. Separated Presentation patterns. Model View Presenter variants and Presentation Model (MVVM).
    2. “Screen Activation Lifecycle” — Design patterns and the system responsibilities for systems composed of multiple screens
    6. Managing the application shell

  • http://sharpoverride.blogspot.com Mihai

    3.DSL development within a desktop application.
    5.Managing the application shell

  • http://jason.lostechies.com Jason Meridth

    4. Test Automation strategies. How testability impacts design
    5. Event Aggregation

    are the 2 that I’d be most interested in.

    Also your knowledge on what a good API looks likes/should look like.