title: Any pattern for "one class per one action/page"?
body: <p>MVC is a really good pattern, but sometimes it is really boring to put everything into Controller's methods. Controller is constantly growing and it takes time to get rid of thousands of code lines. Some people highly recommends to put as much as possible into Model, but I prefer to keep Model clean (I don't put controller oriented methods into Model).</p>
  
  <p>The idea is to put each Controller's action into own class...</p>
  
  <pre><code>class Post_Add {}
  class Post_Remove {}
  class Post_View {}
  </code></pre>
  
  <p>All code, which is common for all action classes we're putting into <code>class Post_Parent</code> and passing it's instance into action constructor.</p>
  
  <p>So, calling action will look like...</p>
  
  <pre><code>$parent = new Post_Parent();
  $action = new Post_Add($parent);
  $action-&gt;run();
  </code></pre>
  
  <p>So, what we have?</p>
  
  <ul>
  <li>Each action is in separated class, so
  we can add as much private methods,
  vars, constants as we want.</li>
  <li>All common code is separated into
  parent class (<code>Post_Parent</code>) and can
  be accessed from action classes. It
  is very good for organizing ACL etc.-</li>
  </ul>
  
  <p>Is this idea worth living? Is there any similar design patterns for this?</p>
  
  <p>Thank you.</p>