I am sorry I will changing the topic a little but by reading your reasons to use Flexy and your concerns about it being developed and PHP5 compatible why not take a look at PHPTal. There is a not very recent symofny plugin for it that I took a look at some time ago.
http://tracfort.jp/projects/symfony-phptal/wiki You get all the benefits of using WYSIWYG editors, you get the symfony php helpers, loops, etc. I am personally more into using template engines that do not depend on editors rather than Zend Studio so I am using the template engine I ported from Ruby (http://trac.symfony-project.com/trac/wiki/sfHamlViewPlugin). Again, sorry for the out of topic email :) Kupo commercemeister wrote: > Hello, > > I have a prototype Flexy templating plugin for Symfony. > This is similar to sfSmartyView, but using the Flexy engine: > http://pear.php.net/manual/en/package.html.html-template-flexy.php > > Before making it available (and hence supporting it), I first > want to gauge the interest / response of the community. > > Why a template engine? My company rapidly develops web > applications using "specialists" - our HTML designers > don't usually know a lick of PHP, though they often scream > if the developers get a pixel out of place. > > We used to spend a lot of time "recoding" HTML -> templates, > and that time is better spent on developing the application. > > With Flexy and the right layout file layout, we can actually > use the same .html documents as the templates, with very little > changes - and usually none that stop it from rendering correctly > when viewed "straight" in a browser. > > This is a BIG gain all around for us. > > Why Flexy? > > First, compared to other templating engines, Flexy's syntax > allows us to gain the advantages above. Simple looping can be > handled in the tags themselves, rather than external constructs > (meaning layout don't move out of place when rendering > the template file directly in the browser). > > Like other templating engines, variables are visible to > the browser: {sf_content} > > HTML people get that's a placeholder, and can see it. > > When using generated CRUD, all that has to be done is add > one line to the top of each template to make it "work" > nearly identically to the standard PHP templates. > (Symfony can understand <?php ?> tags, so things "just work") > > This means all the symfony PHP helpers and idioms are still > available to use as necessary. > > What's next? > > The code is definately "prototype" - it works, > but not optimally. > > If there is an interest in using Flexy with symfony, > I'll make a few updates and release the prototype. > I'm still unsure on the best ways to do certain things, > for example make native symfony helpers native to Flexy. > > And there's a lot that can be done to make it integrate even > more tightly, for example add an alternate crud-generation > that would use native Flexy templates. > > I'd like to see this fly, so let me know if you are interested > in either using or helping develop the plugin. > > Thanks, > > Nick > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
