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.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
plug-in_architecture [2011/04/08 14:25] – demiankatz | plug-in_architecture [2014/06/13 13:14] – external edit 127.0.0.1 | ||
---|---|---|---|
Line 55: | Line 55: | ||
PHP 6 is going to introduce namespace support -- might this be helpful for differentiating between VuFind core and local modifications in a straightforward, | PHP 6 is going to introduce namespace support -- might this be helpful for differentiating between VuFind core and local modifications in a straightforward, | ||
+ | |||
+ | |||
===== Redesign Goals ===== | ===== Redesign Goals ===== | ||
+ | |||
+ | As of 4/8/11, these are Demian' | ||
* Maintain existing URL routes for compatibility, | * Maintain existing URL routes for compatibility, | ||
* Maintain compatibility with existing configuration files (either directly or via an upgrade script) | * Maintain compatibility with existing configuration files (either directly or via an upgrade script) | ||
- | * Replace existing controller model with something more flexible (for example, well-designed context switching would be helpful for your JSON/XML suggestions) | + | * Replace existing controller model with something more flexible (for example, well-designed context switching would be helpful for providing alternate API-style views) |
* Replace Smarty views with something PHP-based | * Replace Smarty views with something PHP-based | ||
* Reduce external dependencies on obsolete code (i.e. deprecated PEAR libraries) | * Reduce external dependencies on obsolete code (i.e. deprecated PEAR libraries) |
plug-in_architecture.txt · Last modified: 2015/08/25 15:37 by demiankatz