A More Extensible CoreLoader

This release resolves #43 by opening up the CoreLoader to more useful extension by app level Loaders.

New Features and Composer support

Resolved Issues:
#35
#33
#32
#31

Version 0.9.9 Release

This release provides several bug fixes and enhancements.

• #28 - Controllers now have a configure() method which removes the need to override the inherited constructor
• #22 - The DatabaseRepository interface has been generalized to DataRepository
• #21 - CoreSite getDataRepository() now provides singleton DataRepositories
• #24
  • Generalizes methods in AbstractDatabaseRepository to use only programmatic column names
  • Fix app_http bug by using getpath() to generate it in CoreSite
  • Fix SitePage non-object bug in CoreSite when User is the current Controller
  • ViewRenderer interface now guarantees the presence of setView method
  • HTMLViewRenderer plays more nicely with extending classes
  • Bug fixes and encapsulation refactor for UserCAS
  • The Site context is now injectable into Data Repositories

Loader Refactor

This release includes a restructuring of the initial entry and loading mechanism.

• Introduces the Loader interface and default CoreLoader implementation, responsible for rendering the site.
• Refactors controller configuration parameters into a single $controllerConfig array.

SitePage interface and implementation

• This release includes the new SitePage interface and implementation.
• Structurally, all the basic operations of the framework have been moved to Core implementations. This includes Site, SitePage, SystemMessage and Logger. The App level versions of these still exist for customization purposes and can be activated through the configuration file.

Prep for Open Source Release

Merge pull request #14 from TAMULib/development

remove legacy getControllerPath method and $pages var