About Features Downloads Getting Started Documentation Events Support GitHub

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

Site Tools


Warning: This page has not been updated in over over a year and may be outdated or deprecated.
developers_call:minutes20140916

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
developers_call:minutes20140916 [2014/09/16 14:29] – [VuFind Developers Call Minutes: September 16, 2014] demiankatzdevelopers_call:minutes20140916 [2014/09/16 14:38] – [2. Development Planning] demiankatz
Line 54: Line 54:
  
 Note one significant exception to the rule: right now, most Search\Options, Search\Params and Search\Results objects are constructed through AbstractPluginFactory classes rather than through explicit configuration. Assuming we decide to eliminate the majority of abstract factories, should we reconfigure this, or continue to use the abstract factories in this special case? Note one significant exception to the rule: right now, most Search\Options, Search\Params and Search\Results objects are constructed through AbstractPluginFactory classes rather than through explicit configuration. Assuming we decide to eliminate the majority of abstract factories, should we reconfigure this, or continue to use the abstract factories in this special case?
 +
 +There was no objection to the basic idea, so Demian will put together a pull request for review and submit it to vufind-tech before merging it to master.
  
 === Should we split out stand-alone libraries? === === Should we split out stand-alone libraries? ===
developers_call/minutes20140916.txt · Last modified: 2016/04/07 15:14 by milenakrakowiy