Hey Guys,
While working on a php port of the java shindig version, i noticed
that in ParsedGadgetSpec, it supports having a <Content> block per
view., and it stores the content data in an map with a [view name] =>
[content data or contentHref] relationship.
It also supports a content type, either html or url based.
However if shindig / opensocial supports those 2 things, you would
expect as a gadget writer that you could mix those 2 types (html and
url), and have a url block for say 'default', and a html content block
for <whatever views will be defined by the social gadget spec>
However looking at the code, it stores the its contentType and
contentHref in single vars, which is overwritten every time by
processContent(). So it assumes that the last content type and/or href
it sees in the xml document is the contentType and contentHref for
every view, thus making it impossible to mixing multiple type's in a
gadget, and impossible to use the multiple view support with anything
but <Content type="html" /> blocks.
Is this intended and will-be-documented behavior or, as i suspect, a
bug?
oh ps, i also noticed in the GadgetSpecParser that it's perfectly ok
with having a gadget xml document without any <Content> blocks ... was
wondering if that was intended, or if maybe that should throw an
SpecParserException too.
Thanks,
-- Chris
