My thoughts behind the templating issue is that I personally prefer to use PHP-style templates (I like Cake's implementation), but I also would like to provide support for other template styles, as many people often have a Smarty-style theme created (so it would be simpler for the user's theme to migrate from smarty on some other application to smarty using my app)
I think smarty is good when there is a need to reduce the amount of sometimes lengthy php variable references, because changing in/out of HTML to PHP can be quite confusing if it's heavily intermixed (often a situation that comes out of not keeping MVC-strict, but it happens) I'd definitely like to see what you've done with Drake & a sample application, if you don't mind :-) One thing that seems nice about the bridges to CMSes, is that you could develop a must-have application that can easily run across multiple CMSes, something that is usually a feat to accomplish... That'd be nice On 6/11/07, Joshua Benner <[EMAIL PROTECTED]> wrote: > > > In response to > http://groups.google.com/group/cake-php/msg/838c013d48104b7e > > I kinda felt like we were hijacking the thread, so here's my response to > your message. > > So far we've only developed small applications for internal use. I have > no problem sharing them, but I don't know if they'll hold much meaning > for you since they will be outside of our context. If you want me to > send a sample, just let me know. I'm also willing to share the changes I > made to Drake -- just ask. > > You mentioned that you were considering integrating Smarty with Cake. > I've seen some minor flames shoot up over using Smarty or just PHP, and > I feel like I can talk as someone who's walked both sides of that fence. > I've used Smarty for a long time in many projects, and finally abandoned > it when I started using Cake. While I liked that way Smarty did a great > job separating display logic from business logic (which was the biggest > argument for using it), Cake does a great job at that by itself without > a templating system. Additionally, I was always extending Smarty and I > found myself spending an unacceptable amount of time forcing my template > system to do the advanced things I wanted it to. > > In all honesty, PHP _is_ a templating system by itself... probably one > of the best there is. Granted, the advanced programming features > available in display logic tempts a programmer to put business logic > there, but that's nothing a little discipline and adherence to Cake > standards doesn't cure. > > I would never fault somebody for using something like Smarty -- it > really is great (and nice if you're going to expose it to end users -- > carefully), but I'd encourage people to use pure PHP, as its more > powerful, faster, and in the end, seems to save (me) time vs Smarty when > working on a project. > > > -- > Joshua Benner > http://bennerweb.com > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
