Chris Meller wrote: > > I also like the idea of moving handlers and their sub-items out of the > generic classes directory, regardless of what the eventual structure is. > They're more like controllers than libraries, so it's never made much > sense to have them lumped all together, it was just easy.
This change seems to mesh well with implementing SPL autoload and the bootstrap stuff we were talking about on IRC. For those not present, we were discussing how it would be nice if you could include the Habari system without it actually processing the output. A potential solution is to create a system/bootstrap directory in which a series of purpose-related modules could include their components. Example components include running the installer, initializing the database, and loading plugins. The index.php file would be reduced to a series of includes that pull from that bootstrap directory. Other applications could create their own index.php-like files that include only the desired components of Habari by including just those bootstrap files. This would make it easier to, for example, embed Habari functionality within some other page or application. SPL autoload would simply use the SPL autoload features directly insteda of implying them like we do now. It would also need to be augmented to support loading handlers from a different place than class libraries. Owen --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
