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 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 Neil Santos wrote:

[Monday] 02/12/2002 :: 01:20 -- NEWMSG

Hello everyone, I'm new in this list, and I thought I should introduce myself a bit first, before proceeding with the original purpose of this message. My name is, as you may have already guessed, Neil Santos, and I'm from the Philippines. I began tinkering with PHP about a year ago, when I wanted to put up a dynamic Web site (it used to be posted on http://www.sector7bbs.com/aktuation/ but it's dead now). Lately, I've offered to help Sam Williams in redesigning, and ultimately maintaining http://www.faifzilla.org/. I wanted to create an easier way to modify the design of the site, without having to mess with the actual pages. CSS has gone a long way, but I thought I'd try pushing my luck a little further, and make it easier on other people as well, especially Sam. I wanted to create my own CMS (content management system, for those who aren't familiar with the term), since most of the CMSystems out are commercial; something I didn't think was fit for FAIFzilla. I didn't want to create one huge system, centered around one project, so I ended up creating a parser encapsulated in a class. People could then inherit the parser class (which I've taken to calling `Raven'), and just attach the functionality they need and it lacks. While most of the functionality you'd expect in a CMS is done, the project as a whole isn't, and is, in my opinion, far from being so. Raven, however, is usable; in fact, it's responsible for converting what work I've finished on FAIFzilla. I'd like to know is if there is enough interest in the community in seeing a free (in the GNU sense) CMS for me to release it to the public. I'd also like to ask if there is anyone who would be willing to collaborate with me on this project once I've released it, as I am far from being an expert in PHP and could use all the help I'll need. I'd like to be able to submit Raven into the PEAR database, if you, the PEAR developers deem it fit. I've made it a point to make Raven easily modifiable for inclusion into PEAR, and enough structure is in place to make the transition a breeze. At least I hope that's the case. Anyway, I'd be more than happy to answer questions regarding Raven, if you'd send them my way, through this list or directly. If anyone is interested, I'll post what Raven can do at this point as soon as possible. Until then, Later guys. Stay frosty. ------- ``... I don't suppose we shall see them again.''

       -- Frodo, from `The Fellowship of the Ring', by J.R.R. Tolkien

... if (!strcmp(tagline,"humorous")) steal(); else next_msg();