About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

VuFind Documentation

Site Tools

You are here: start » plug-in_architecture
Trace:
Warning: This page has not been updated in over over a year and may be outdated or deprecated.
plug-in_architecture

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
plug-in_architecture [2011/03/08 15:40] – demiankatzplug-in_architecture [2011/03/11 13:51] – demiankatz
Line 37: Line 37:
  
 [[http://kohanaframework.org|Kohana]] is a PHP framework similar in many ways to Ruby on Rails. [[http://kohanaframework.org|Kohana]] is a PHP framework similar in many ways to Ruby on Rails.
 +
 +==== Borrow ideas from Rails? ====
 +
 +Obviously, VuFind is going to remain a PHP-based project; if you want discovery on Rails, [[http://projectblacklight.org/|Blacklight]] has that territory well covered, and Rails' very heavy dependence on naming conventions would make migration from existing legacy VuFind code unnecessarily complicated.  However, it's not a bad idea to borrow some design principles from Rails.  Here are a couple of ideas that might be helpful to VuFind:
 +
 +  * Render shared page layouts AFTER action-specific page contents -- this way you can pass page-specific details (like title tag contents) from template to template rather than having to embed it in the controller.
 +  * Share the URL routing logic with the templates so that the same logic which resolves incoming requests can also be used to build outgoing links.
 +
 +(feel free to expand this list if you have strong feelings about any other Rails conventions)
  
 ==== Reconsider Smarty? ==== ==== Reconsider Smarty? ====
plug-in_architecture.txt · Last modified: 2015/08/25 15:37 by demiankatz