It looks like we're both looking for the same goals out of this project. The number one feature for us is to reuse the Radiant layouts to keep that DRY. And that's where this project will be going next.
As for the rails portion of the site, the other thing this extension allows for, is to be able to use the traditional RAILS_ROOT/app/ [controllers|helpers|models|views] folders instead of burying everything into /vendor/extensions. I think this also helps to create a cleaner split between Rails and Radiant code and also makes it easier to integrate Radiant into an existing Rails app. Matt Parrish http://www.pearware.org On May 30, 2007, at 2:01 PM, Mario T. Lanza wrote: >> I'm also very interested in allowing Rails pages to leverage Radiant >> layouts, and that is the next thing I plan to work on. > > I'm very happy to see this project forming. After tossing around many > ideas for integrating custom Rails views within a Radiant site, I've > formulated a pattern. > > I simply create an extension and build the functionality exactly like > I'm building a Rails app. I modify the routes in the extension > initializer being careful to differentiate between back-end > functionality (for the admin interface) and front-end functionality > (for > the sites users). Admin functionality is put in "admin" subfolders > just > as is already done with the Radiant admin stuff. For example, here > are > the routes I currently use for an in-progress extension that has both > front-end and back-end interfaces. > > define_routes do |map| > > #back-end interfaces > map.admin_event 'admin/event/:action/:id', :controller => > 'admin/event' > map.admin_offering 'admin/offering/:action/:id', :controller => > 'admin/offering' > > #front-end interfaces > map.offering 'offering/:action/:id', :controller => 'offering' > map.event 'event/:action/:id', :controller => 'event' > map.registration 'registration/:action/:id', :controller => > 'registration' > map.invitation 'invitation/:action/:id', :controller => 'invitation' > map.evite 'evite/:action/:id', :controller => 'invitation' > > end > > There models are common, but there is a distinction between the > front-end and back-end controllers and views. > > I find this is a very natural means of doing just what I have been > attempting to do all along. The only piece that I am missing is the > ability to take advantage of Radiant from the Rails side, which > apparently is a much sought-after piece that is now in the works. > > At this point I am creating Rails layouts that are identical to their > Radiant counterparts. It's not DRY, but it is workable for the time > being. > > I'm eagerly anticipating seeing this extension so I can DRY things up. > > Mario > > > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > Radiant mailing list > Post: [email protected] > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
