On Fri, 2012-08-31 at 10:14 -0400, Nicolas LE BAS wrote: > It's some extra work at coding, but it doesn't interfere with the > loading of the initial template, so the testing and debugging should be > easier.
It sounds about right yes. I'll take a closer look at DeferringMustacheFactory. We're still working our way through things (it's important that including partials by tiles attribute names works both client and server side), it may well be that we use lambdas instead of partials... and that leads to implementing an autotag implementation against lambdas. But regardless of the partials we do want a way where resource loading goes through the application context, and we also don't create a very specific set of mustache classes that can only be used. But this relates back to your discussion in (3/3) where often only one use-case can be supported. ~mck -- “The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore, all progress depends on the unreasonable man.” - George Bernard Shaw | http://github.com/finn-no | http://tech.finn.no |
signature.asc
Description: This is a digitally signed message part
