Or maybe I should just ask, what are the remaining things you can do in Chameleon that you can't do in Mako? I'm interested in the well-formed XML guarantee and Pyramid's Chameleon internationalization support. But on the other hand the Chameleon syntax is so different it's a large learning curve, especially to port inheritance relationships and def's the like. And shoehorning variable assignments and such into tag attributes does look the hyperbole of screwy sometimes, even though I like the idea of if'ing a tag rather than an arbitrary block.
Has Pyramid/Mako's internationalization caught up with Chameleon yet? Should I just give up on XML pre-validation and validate the rendered pages? Am I missing anything else besides not using Chameleon. (Anything in the sense of capabilities, not syntax or speed.) On Fri, May 3, 2013 at 3:48 PM, Mike Orr <[email protected]> wrote: > Are there any good examples around of using Chameleon with a site template > macro? I normally make my sites by inheriting from a Mako template that > provides a standard <head> and header/footer, with the page template > overriding the title, possibly adding stylesheet and Javascript links, > supplying data for the breadcrumbs, etc. I know this can be done with > Chameleon macros and slots and providing the site template in the template > namespace, but does anyone have an example of it that I can borrow the > syntax? Kotti does this but it also has a custom 'api' object in the > template namespace, which I'm not sure if I want to follow. > > -- > Mike Orr <[email protected]> > -- Mike Orr <[email protected]> -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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]. Visit this group at http://groups.google.com/group/pylons-discuss?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
