Some Shindigers demoed shindig with caja support at the hackathon
today. It doesn't currently display Caja error messages or warnings
(from com.google.caja.reporting.MessageQueue).
Cassie (CCed) and I bandied about a couple ideas:
(1) Since GadgetRewriter takes a gadget spec and returns a gadget
spec, put the messages after or in place of the <Content>:
<Error level="WARNING" location="foo.js:42"
>is_not_assigned is used before first assignment</Error>
(2) Have shindig grab the message queue and use it.
I'm leaning towards (1) because:
* having one output (content | content with warnings | errors) will
make it easier on many clients
* it would make it easy for us to provide more structured error
messages in the future without having to update clients
Any other options or arguments for or against either option?
cheers,
mike
