[stringtemplate-interest] Group Syntax extension for ModelAdapter and Renderer
parrt at cs.usfca.edu
Thu Jun 30 11:30:25 PDT 2011
Hi Gang, thanks for the excellent discussion.
Udo had a nice suggestion to look first at the native group then requesting group in a reverse polymorphism.
The Sams suggested that perhaps templates not renderers are what is needed.
Udo points out that we need to escape lots of things like " in strings, */ in javadoc etc...
One of the Sams suggested a single renderer for strings that knows more escapes. I think that is a fine solution since we are really saying we need to render strings in both cases. Why not group together:
I think we should stick to something super simple. I don't like String having two renderers in system at once. BUT, we currently allow you to set renderers PER group so what does that mean? For non-imported groups, it's obvious. For imports, any renderer set on import group is ignored even when using import template. I guess I'm ok with that. Set the renderer on the main group you use (or all to be sure). I look at import groups as "helpers" that should give me templates and nothing else.
Udo: can you live with making one uber-string-renderer?
More information about the stringtemplate-interest