search for: dryness

I''m finding that I''m writing sets of very similar scenarios to check access permissions for each of my actions. Does anyone have suggestions on how to dry this up: Given an existing Account And a logged in Admin When the user visits account/manage Then he should get access Given an existing Account And a logged in Manager When the user visits account/manage Then he should get

All, I have a form with the following field interaction rules. Given checkbox A, text field B text field C If checkbox A is checked then make text field C equal to the value of text field B and disable field C. If checkbox A is unchecked then enable field C. In order to display a form where I''m manipulating an already existing object, I have something like this in my RHTML template

Hello, I''m a novice to ferret, so far only used it via acts_as_ferret. My question is about a recommended pattern for an ''advanced search'', which would be searching by all fields of a model and some fields from related models, with range search, expression search and wildcards. The kind of search in which a user is presented with a huge form that allows them to set

There are datatypes that need to be converted back and forth from a string representation: they need to be parsed both coming from the database, and coming from elsewhere like views. Dates are an example, and I recently needed to implement a more forgiving converter for decimal numbers. So we have here at least two flows of execution, for example: post.date = "22-jan-2007"

In a model I have following validates_format_of. Is there an easy way to DRY this up? It seems to be rather repetitive. validates_format_of :expiration_date, :with => /^[0-9]{4}[-][0-9]{2}[-][0-9]{2}$/ validates_format_of :activation_date, :with => /^[0-9]{4}[-][0-9]{2}[-][0-9]{2}$/ validates_format_of :some_other_date, :with =>

...w FormBuilder but then I have to stub the text_field method which is what i''m actually spec''ing. I''d appreciate any suggestions on how to accomplish this without having to repeat the same basic form information and buttons over multiple forms. Something about sacrificing DRYness to achieve BDD seems off. I''d imagine you can have both and I''m just not hitting the mark. Thanks in advance. RSL

I''m rewriting the code to my first app. I want to reuse a lot of it, but tidy it up a lot. The first thing I will tackle is my nav-bar. Throughout a user''s experience on my app, I want it to reload as little as possible (I''ll have about 7 or 8 controllers with about 70 actions). So, I''ve thought of a few ways of doing it, and was wondering if you guys

I am curious what you find is good and bad MVC design. Let''s use the find and find_by_sql methods as examples. Currently I have these spread out all over the place... View: here I have some find methods when I am for example populating a select list with choices in a form. Controller: here I have the simpler find methods. Model: here I have the more complicated find methods (usually

I was thinking today, it would be nice if a view could tell a model how to format it''s data for that particular view. Kind of like, the view is bestowing instant, and temporary knowledge on the model for the duration of the views run. It seemed to me that this would be more objecty than say a helper that formats a string format_my_string( my_string ) Instead, in my view. Lets assume I