> > Thanks, that was my next question...I was told to look at PEAR from > the beginning. All I can say is PEAR looks very exciting for me. > > Some good coding structure ideas that have been brought into the > Lasso developer circles over the years: > > 1) FrameWork...(incredible piece of work) I have friend that is > working on porting it to PHP. > http://www.fwpro.com/ > > 2) Corral (basically a cascading includes system) > Appear to be offline at the moment: http://www.corralmethodology.com/ > > 3) One-File (basically similar to FuseBox, but without the "black > box") Stems from corral. I know I have seen a lot of PHP developers > develop with this style, such as ?page=1, etc... > --
I tend to follow the pear standards in many ways but i dont build classes for pear maybe i should ? I pretty much follow all the naming conventions, code commenting and structuring standards. For webpage apps i use a file for each section with a main include which includes all my classes, functions and constants and database connections. For content management systems i use a system similar to fusebox, i use a switch case method with an action ie action=edit, action=update, action=insert, but each section has its own file. And i put my code within these parts, i also use a templating system called phemplate because it seemed to be the most efficient, simple and non bloatware system out there. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
