Hi Mark, I'd recommend you switch to Cake as soon as possible, it'll really make your code easy to manage.
It won't be easy to 'port' to Cake, I won't lie. For most, you'll be recoding the entire basic setup of your website. You'll be able to use the basic code-set (like say some library functions that you use throughout your code) by dumping them into your 'vendors' folder in Cake, but otherwise, it's best you remake the website in Cake rather than copy-paste code into Cake's structure. It should take you much lesser time than it took you to make the website, since you have a basic idea of how things to work (not to mention design!), so don't worry about devtime. Good luck! On Sep 22, 3:00 am, mark kelly <[email protected]> wrote: > Hi > I developed a site last year in php and mysql in a procedural manner > (I did not use MVC model or object oriented programming). The project > is being developed further along with 2 new programmers. As we have > got some investment and it looks like this application (market place > style website) will be going for a few years, I would like to apply > Best Practices to the existing code. This means using the MVC model > and OOP. I feel its best to do this now where the website is at a > manageable(ish) 300 files rather than a year down the line when its a > mess.. > > Do ye think its a good idea to use the cakePHP framework to force a > sort of structure on the code? So we would not be doing a lot of new > coding, instead we'd be using the framework to enforce good practices > of OOP and MVC. Also, any estimates on if this would take long (300 > files) and whether cakePHP is right for this? Or if it's worth doing > at all? > Thanks > Mark -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
