On 12-09-01 01:36 AM, Mick Semb Wever wrote:> > Maybe i'm blind [...] visitor pattern [...] add a context to MustacheFactory [...]
Wow wow wow... Just because my one-liner explanation is missing an example doesn't mean you're blind. Forget about MustacheFactory for a while, the point is to implement the algorithm in PartialCode, because it doesn't require the addition of anything. But I agree that lambdas may be the way to go, especially since partials look awkward and invasive in mustache.js, so let's focus on that. > Our first attempt is simply to dump all attributes as a > Map<String,Object> into the request scope under the name "tiles" (in a > subclass of the MustacheRenderer). But this might not work so smoothly > client side. Looks like it's doing the job, though. But I'm not sure exactly what you're trying to achieve with all that "client-side" thingies... you're months ahead of me on that subject. Could you explain a bit? Is this about replacing a part of the web page dynamically after an AJAX call, for instance? And/or about implementing a tiles-like framework on the client side? Could you provide a basic example?
