[ANN] PageFactory 2.0

Dobai-Pataky_BSSSSl · December 2, 2010, 6:09pm

If anyone wants to jump on the bleeding edge, I think the next
generation of PageFactory is ready for public use. It works pretty much
like PageFactory 1, but drops the PageFactory::Base class. Instead, all
part management is done directly on your Page subclasses:

class EmployeePage < Page
    part "first name"
    part "last name"
    part "department"
end

PageFactory 2 also adds management of Page Fields.

Everything is on the 2.0 branch, so you’ll have to install the extension
and manually check out the new branch. It will probably remain as a
vendored extension until we see another release of Radiant.

As always, comments, questions, and bug reports welcomed and
appreciated.

j

Joshua_Danger_Frenc · December 2, 2010, 8:06pm

On Thu, Dec 2, 2010 at 12:08 PM, Joshua Danger French
[email protected] wrote:

Everything is on the 2.0 branch, so you’ll have to install the extension and
manually check out the new branch. It will probably remain as a vendored extension
until we see another release of Radiant.

As always, comments, questions, and bug reports welcomed and appreciated.

j

This idea was too good not to include in the main project.

On edge, Radiant will call new_with_defaults when creating a new page:

github.com

radiant/radiant/blob/master/app/controllers/admin/pages_controller.rb#L21


      
          responses do |r|
            r.plural.js do
              @level = params[:level].to_i
              @template_name = 'index'
              self.models = Page.find(params[:page_id]).children.all
              response.headers['Content-Type'] = 'text/html;charset=utf-8'
              render :action => 'children.html.haml', :layout => false
            end
          end
          
          
def index
            @homepage = Page.find_by_parent_id(nil)
            response_for :plural
          end
          
          
def new
            @page = self.model = model_class.new_with_defaults(config)
            assign_page_attributes
            response_for :new
          end

That allows your Page subclasses to initialize their parts and fields.

The core doesn’t, however, have things like descriptions for parts or
rake tasks to sync things up.

Does that simplify PageFactory in any way? (I haven’t tried it in a
while)