http://www.napcsweb.com/blog/2010/03/15/making-as-strin-alternate-attribute-readers/ professional web development and consulting Mon, 22 Aug 2011 18:56:36 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://www.napcsweb.com/blog/2010/03/15/making-as-strin-alternate-attribute-readers/comment-page-1/#comment-27708 Jon Thu, 25 Mar 2010 18:58:06 +0000 http://www.napcsweb.com/blog/?p=152#comment-27708 Thanks for this elegant solution Brian! And @grosser, why would you ever think that complex view logic that you have to maintain with find and replace is better than having a single place to define your behavior that is easily testable? Thanks for this elegant solution Brian! And @grosser, why would you ever think that complex view logic that you have to maintain with find and replace is better than having a single place to define your behavior that is easily testable?

]]> http://www.napcsweb.com/blog/2010/03/15/making-as-strin-alternate-attribute-readers/comment-page-1/#comment-27674 grosser Mon, 22 Mar 2010 21:34:12 +0000 http://www.napcsweb.com/blog/?p=152#comment-27674 Seem overkill to me, why would i do all this crazy meta-madness only to go from x.active? ? 'x' : 'y' to x.active_as_string('x','y'), first one is easier to type, understand and maintain (e.g. search for active? and replace it, instead of having to know that there can be some active_as_xxx) Seem overkill to me, why would i do all this crazy meta-madness only to go from x.active? ? ‘x’ : ‘y’ to x.active_as_string(‘x’,'y’), first one is easier to type, understand and maintain (e.g. search for active? and replace it, instead of having to know that there can be some active_as_xxx)

]]>