On Mon, 2003-09-29 at 19:10, Chris L wrote: > [EMAIL PROTECTED] (Robert Cummings) wrote in > news:[EMAIL PROTECTED]: > > > Regardless of the framework or library or whatever you choose, you > > WILL have to adapt to it to some degree. Whether that be style-wise or > > just learning the the API. The more power, and flexibility you want, > > the more you will probably have to learn. These things usually come at > > the price of learning a very specific way to do something, but once > > learned, becomes extremely quick to implement and adapt. > > I'm not averse to learning a methodology-- I learned Fusebox in just this > situation when I was using Cold Fusion. However, when I made that choice > there wasn't much to choose from and the basic model made sense. > > With PHP there is a LARGE number of frameworks to choose from, some of > which seem amazingly complex, some of which appear to be seeking > theoretical ends rather than practical solutions. > > Templating solutions have never been my thing, so I have a bit of a built- > in resistance to that concept, and I'm not programming for IBM, so I don't > necessarily need a framework that is suitable to the largest enterprise. > I'm not even particularly worried about interoperability with parts of > program A and program B, which seems to add a lot of overhead to, for > instance, the fusebox model, where they are trying hard to make each fuse > portable.
*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. -- .------------------------------------------------------------. | InterJinn Application Framework - http://www.interjinn.com | :------------------------------------------------------------: | An application and templating framework for PHP. Boasting | | a powerful, scalable system for accessing system services | | such as forms, properties, sessions, and caches. InterJinn | | also provides an extremely flexible architecture for | | creating re-usable components quickly and easily. | `------------------------------------------------------------' -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
