I liked the part where a section of a template could get a name and be used in another template, or within the same, without needing an include function. The ".extends" command type i can live without, though i like the .block one...
On Oct 5, 10:11 pm, Andy Chu <[email protected]> wrote: > On Mon, Oct 5, 2009 at 1:57 PM, Steven Roussey <[email protected]> wrote: > > > I was wondering if the blocks concept might get native treatment in > > json-template? > > I don't think so -- it doesn't appear necessary. The 2 template > solution described here has worked for me in real apps, and more > cleanly than an inheritance solution: > > http://json-template.googlecode.com/svn/trunk/doc/On-Design-Minimalis... > > It might take a little "figuring" depending on what web framework > you're working within. Some of them are a little inflexible and may > not let you have this 2-level thing. > > Also I'm working on something called "JSON Config" (a 3rd one, after > JSON Pattern) that will allow you to put multiple template fragments > in a single text file. So some people might want to use it for this > "base template" thing, and it can also be used for the recursive > templates -- what we talked about for formatting trees. In general I > try to have features solve more than one problem, and not just do > one-offs. > > Andy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JSON Template" 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/json-template?hl=en -~----------~----~----~----~------~----~------~--~---
