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/01/25 16:09] – demiankatzplug-in_architecture [2011/03/08 15:40] – demiankatz
Line 12: Line 12:
  
 Feel free to add to this section -- the idea is currently to list possible solutions and evaluate advantages and disadvantages. Feel free to add to this section -- the idea is currently to list possible solutions and evaluate advantages and disadvantages.
 +
  
  
Line 32: Line 33:
  
 This project advertises itself as both a CMS and an application framework.  The CMS element might be a nice bonus feature, but at the same time, tying VuFind to a particular CMS might become an obstacle to adoption (the same argument goes for Drupal). This project advertises itself as both a CMS and an application framework.  The CMS element might be a nice bonus feature, but at the same time, tying VuFind to a particular CMS might become an obstacle to adoption (the same argument goes for Drupal).
 +
 +=== Kohana ===
 +
 +[[http://kohanaframework.org|Kohana]] is a PHP framework similar in many ways to Ruby on Rails.
  
 ==== Reconsider Smarty? ==== ==== Reconsider Smarty? ====
plug-in_architecture.txt · Last modified: 2015/08/25 15:37 by demiankatz