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 revisionNext revisionBoth sides next revision | ||
plug-in_architecture [2011/03/11 13:51] – demiankatz | plug-in_architecture [2011/04/08 14:26] – demiankatz | ||
---|---|---|---|
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 ===== | ||
+ | |||
+ | As of 4/8/11, these are Demian' | ||
+ | |||
+ | * Maintain existing URL routes for compatibility, | ||
+ | * 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 Smarty views with something PHP-based | ||
+ | * Reduce external dependencies on obsolete code (i.e. deprecated PEAR libraries) | ||
+ | * Make file organization and class naming more consistent (i.e. sort out the current web/sys quagmire) | ||
+ | * Ensure that everything (models, views, controllers, | ||
+ | |||
---- struct data ---- | ---- struct data ---- | ||
---- | ---- | ||
plug-in_architecture.txt · Last modified: 2015/08/25 15:37 by demiankatz