[EMAIL PROTECTED] (Robert Cummings) wrote in news:[EMAIL PROTECTED]:
> *heh* I like being able to look at project 2 and say to myself, hmm > needs an authentication just like project 1, but with a different > look. Or wants a news feed, like project 1, buyt the data source is > different, I'll just re-use the renderer and logic and recode the data > retriever. I guess it depends on preference. I find I can do fully > customized management projects from scratch with serious backend and > front end functionality in very short time (weeks). And when I can > re-use a component or module, I just shave off more time. The nice > thing about re-using components and modules too, is that I know it > works, the testing has been done, let alone the coding. > > Cheers, > Rob. I like that idea too-- I just don't like having to learn what amounts to a third language to do it. Does one have to have a templating engine in order to achieve this? I find reusability to be, largely, a theoretical mantra, templates or not. In general, between applications, so much changes that even the same basic idea means that the most reusable part are SQL queries and such, and I already keep THOSE separate. And I've been looking for good examples of code on the web-- examples that exemplify forethought and reusability. I must be looking in the wrong places :) c -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
