NYCPHP Meetup

[Eric K.]

I think the tie in is simply because, at the end of the day, when you
are done designing coding and testing (the part that the framework is
most useful for), most php applications will need to spit out
html/images/etc (content) which warrants the need for an
html/images/etc (content) management system of some kind...

I'd say install/try out the framework and ignore as much of the CMS as
you need to, to get your app done. The benefits of reusing the
framework code and the inherent coding methods will be an improvement
from coding the straight PHP way.

On 6/29/05, Anthony Papillion <papillion at gmail.com> wrote:
> Hello Everyone,
>  
>  In light of today's discussions about frameworks I think now is a good time
> for me to ask a question that's prevented me from using frameworks in the
> past and doing everything the "straight PHP" way:
>  
>  It seems that all of the frameworks I've run across are somehow tied to
> CMS's. In my mind, and perhaps wrongly, this limits their usefulness to
> creating CMS software. What about people who are creating other type of
> software? And does it also mean that one has to install a complete CMS just
> to have acess to the API's? This seems like a lot of overkill to me.
>  
>  Perhaps, and probably, I am wrong. I am very eager to work with a framework
> since they really seem to eliminate a lot of work. Can anyone tae a little
> time to shed some light on these issues for me?
>  
>  Thanks!
> 
> -- 
> Anthony M. Papillion
> Quality Technical Services and Support
> Phone: (918) 926-0139
> Email:  papillion at gmail.com 
> _______________________________________________
> New York PHP Talk Mailing List
> AMP Technology
> Supporting Apache, MySQL and PHP
> http://lists.nyphp.org/mailman/listinfo/talk
> http://www.nyphp.org
> 
>