☂ general awesomeness for klein.Plating

[glyph]

Here are some things that should be added to klein.Plating to make it really complete, which were left out of the initial implementation (#118) to keep it compact:

• Support for different types of templates
  • the ones from twisted; XMLFile support XMLFile loader for klein.Plating #121
  • and XMLString as implied by "plating" decorator for quickly constructing simple sites #89's basic prototype support XMLString loader for klein.Plating #122
  • HTML5Lib html5lib loader for klein.Plating #123
• Deferred support deferred support for HTML portions of klein.Plating #131
• including some kind of solution for asynchronous JSON serialization asynchronous JSON serialization for klein.Plating #124
• More documentation, particularly for how to use widgets documentation for widgets in klein.Plating #125
• Something on the input side, for conveniently parsing JSON post bodies and handling form data submission - something that doesn't involve handling state in memory, by the way, since that doesn't scale. (Is there even a way in werkzeug's routing syntax to extract a query arg as a python parameter, or doe sit only accept path segments?) form handling #126
• attr.s support - specifically, automatically invoking asdict so applications can work entirely in terms of nice data structures and not manually decompose things into dicts and lists attr.s support for klein.plating #127
• pluggable renderer support. the example even has a great use-case: latitude and longitude are conventionally presented as "east" and "west", "north" and "south", not positive and negative numbers. We may want to present an individual serializable value in a different way. I think that the way to do this might be @plating.renderer("blub") def blubrender(plated_data, request, tag): "..." to stuff things into a specific renderer's element. Still not sure how to do composition / renderer libraries nicely, but at the very least you could write a function and then do add_utility_renderers(my_plating) pluggable renderers for klein.Plating #128 and "common navigation" rendering for klein.Plating #130 - closely related, possibly resolvable with the same implementation
• datetime serialization (what even is the best practice for this in JSON) datetime rendering for klein.Plating #129
• real content-type negotiation real content-type negotiation for klein.Plating #132
• support for methods support for methods in klein.Plating #133 (oops)
• allow for nesting within :list renderer :list renderer in klein.Plating should support dictionaries, and fill slots with their values #161

[wsanchez]

Perhaps this ticket should be a milestone instead?