﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Christopher Bennage commented on Concepts &amp; Features in NH Prof: Filtering</title><description>@Michael We use an attribute for the display name because we don't instantiate the filters in order to list them in the UI. The list of _available_ filters is just a list of types, and the only addition metadata we needed was the display name.
</description><link>http://ayende.com/4144/concepts-features-in-nh-prof-filtering#comment7</link><guid>http://ayende.com/4144/concepts-features-in-nh-prof-filtering#comment7</guid><pubDate>Mon, 31 Aug 2009 15:20:22 GMT</pubDate></item><item><title>Ayende Rahien commented on Concepts &amp; Features in NH Prof: Filtering</title><description>Kyle,
  
I am leaning toward must not. 
</description><link>http://ayende.com/4144/concepts-features-in-nh-prof-filtering#comment6</link><guid>http://ayende.com/4144/concepts-features-in-nh-prof-filtering#comment6</guid><pubDate>Wed, 26 Aug 2009 04:07:28 GMT</pubDate></item><item><title>Ayende Rahien commented on Concepts &amp; Features in NH Prof: Filtering</title><description>Mike,
  
I would say that CRUD is a concept and a CRUD screen is a feature in this concept
</description><link>http://ayende.com/4144/concepts-features-in-nh-prof-filtering#comment5</link><guid>http://ayende.com/4144/concepts-features-in-nh-prof-filtering#comment5</guid><pubDate>Wed, 26 Aug 2009 03:54:42 GMT</pubDate></item><item><title>Mike Minutillo commented on Concepts &amp; Features in NH Prof: Filtering</title><description>@Kyle - I would assume that Should Not would quickly devolve into usually does which becomes always does. Then the lines between Concepts &amp; Features blur and your app becomes a big ball again making it difficult to add new features to your app.
  
  
@Ayende - I like this approach a lot. Would you consider this a valid approach for simple CRUD apps or is this overkill? I've done something like that before where you'd call a concept one of the standard actions (create, list, edit/update, delete, view) and each feature is essentially a new screen with UI and a presenter that dictates where the data comes from/goes.
</description><link>http://ayende.com/4144/concepts-features-in-nh-prof-filtering#comment4</link><guid>http://ayende.com/4144/concepts-features-in-nh-prof-filtering#comment4</guid><pubDate>Tue, 25 Aug 2009 23:33:48 GMT</pubDate></item><item><title>Kyle Szklenski commented on Concepts &amp; Features in NH Prof: Filtering</title><description>Just a quick clarification: When you say, "May not involve", do you mean CANNOT, or should not? I'm assuming the former because it's you posting, but the latter seems more likely, just given systems I've seen. :)
</description><link>http://ayende.com/4144/concepts-features-in-nh-prof-filtering#comment3</link><guid>http://ayende.com/4144/concepts-features-in-nh-prof-filtering#comment3</guid><pubDate>Tue, 25 Aug 2009 16:06:14 GMT</pubDate></item><item><title>Michael commented on Concepts &amp; Features in NH Prof: Filtering</title><description>Nice post again.
  
Could you explain why you have defined display name as an attribute and not as a read-only property?
  
</description><link>http://ayende.com/4144/concepts-features-in-nh-prof-filtering#comment2</link><guid>http://ayende.com/4144/concepts-features-in-nh-prof-filtering#comment2</guid><pubDate>Tue, 25 Aug 2009 14:53:30 GMT</pubDate></item><item><title>Set commented on Concepts &amp; Features in NH Prof: Filtering</title><description>When I see the code base I inherited to maintain and this blog entry, it looks like magic :(
</description><link>http://ayende.com/4144/concepts-features-in-nh-prof-filtering#comment1</link><guid>http://ayende.com/4144/concepts-features-in-nh-prof-filtering#comment1</guid><pubDate>Tue, 25 Aug 2009 05:54:13 GMT</pubDate></item></channel></rss>