`Template#file()` seems extra to me, because it breaks ISP. `Engine` also looks very non-segregated to me. Could you elaborate on the usage of `Context`? I couldn't understand how it could be used. I use an interop context in the form of `ContainerInterface`.
On Tuesday, September 26, 2017 at 1:34:22 AM UTC+2, David Lundgren wrote: > > Greetings, > > This may seem like shameless self-promotion, but I had an idea similar to > this last year, that has sort of fallen by the wayside. I am happy that > someone brought it up on this list, and I would love to move the idea > forward. > > In the same way that http-interop did, I created an output-interp > organization on github, https://github.com/output-interop > > The spec that is currently published was founded on the work that Giuseppe > Mazzapica started with Foil PHP https://github.com/FoilPHP/Foil as I > found it an excellent basis for a rendering system. > > I do have some code that I wrote that allowed me to switch between Twig, > Smarty, php, Blade, with the primary differences being render syntax of > variables. > > Dave > > On Monday, September 25, 2017 at 12:45:34 AM UTC-5, Rasmus Schultz wrote: >> >> Granted, the majority of template engines use a template file-name and a >> set of name/value pairs. >> >> This template engine uses neither: >> >> https://github.com/mindplay-dk/kisstpl >> >> I'm sure you won't care because it's not popular or well-known ;-) >> >> We use this at work because: >> >> 1. code-sniffer inspections and plain PHP templates are a requirement - >> view data dictionaries get in the way of that, and >> >> 2. dynamic template-selection is a requirement (enabling template >> overrides across modules etc.) and hard-coding template paths gets in the >> way of that. >> >> I know this is not the mainstream approach to templates ;-) >> >> -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/fe5904c5-b525-434b-a43d-fb093ecbe8be%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
