Re: CMSystem written in PHP

> Like everyone else has said, putting a whole CMS into PEAR is not really > the aim of PEAR, although the package manager may make your life easier. > > It doesnt mean that the code you have is not suited to PEAR, it just > means that PEAR would need to digest them in smaller (independant) parts. > Generally the components of a CMS: > 1) URL->Object (or file) mapper > 2) Display engine (eg. Templating system) > 3) Data Store (libraries that deal with managing the data) > 4) Display objects (or files).. the bits that merge input with the data > store and create output data (either directly or via templates). > > at the moment, PEAR has > 1) - none > 2) - a few like IT, Smarty?, Flexy/Simple Smarty is not in pear because there would be too much work putting it to Coding Standards. There is a package.xml though which eases the install process. > 3) - DB, DB_DataObject, some of the XML classes > 4) - QuickForms... etc. > > for 3&4) - the data design of your eventual CMS is usually very > specific.. - so only generic pieces are re-usable. > > Anyway - Hopefully some food for though > Regards > Alan