Personally I don't see why you would even bother with symfony then. The whole point is that symfony is an MVC, not just M and half a C. Sure, you probably could just use the bits you want but if your not using symfony's view/templating system why not just use Propel on its own, tack on your own "actions" class, etc and let that HTML you are talking about do the rest. Then you don't have to worry about hacking symfony up to do half its job.
On Mon, Sep 28, 2009 at 5:55 PM, Simon Cast <[email protected]> wrote: > > Hi, > > I'm working on a project where we are going to not use the presenation/ > view layer of symfony to render pages. All the actions, business > logic and database access will be handled by Symfony but the > presenation/page generation will be handled using straight HTML/JS > (don't ask). Symfony in effect manages API calls. > > Does any one have advice or tips on potential pitfalls? > > One pitfall that I haven't resolved is how the HTML/JS pages and > Symfony are going to site on the same server and play nice together. > I could see problems with going to www.example.com and Symfony > index.php taking over but that is probably resolved by changing the > htmldocs directory. > > On a similar note, does anyone know if there will be problems with > calling actions straight without first going through the index.php? > > Thanks for any pointers. > > Regards, > > Simon > > > -- Gareth McCumskey http://garethmccumskey.blogspot.com twitter: @garethmcc --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" 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/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
