Sounds right to me. I seem to recall discussions around this in previous spec iterations, so I'd check the archives as well.
Cheers, John On Tue, Jul 13, 2010 at 3:17 PM, Michael Young <[email protected]>wrote: > Ok, this makes sense, however at this time it doesn't seem there is a > standard way to do this per the OpenSocial spec. In other words if I grab a > random gadget and execute it in my container, it won't grab the parent's > styling. > > I'm guessing this is something that should be proposed to the spec > committee. > > - Mike > -- > Liferay West Coast Symposium > September 8-9, 2010 > Anaheim, CA > www.liferay.com/wcs > -- > Follow us on Twitter: liferay > > On Jul 13, 2010, at 3:04 PM, John Hjelmstad wrote: > > > That does make sense. The API support for this is pretty thin at the > moment: > > JS API: > > > http://svn.apache.org/repos/asf/shindig/trunk/features/src/main/javascript/features/skins/ > > > > All this does essentially is invent (another) way to pass a string/string > > map to an API for consumption by gadgets as they wish. There's a few > > standard keys with implied correlated value types, but not too many. > > > > On the server side, we implement "hangman" variable substitution as well: > > __SKIN_foo__ resolves to the same value as > gadgets.skins.getProperty("foo") > > -- but this isn't implemented in Shindig. > > > > --j > > > > On Tue, Jul 13, 2010 at 2:56 PM, Michael Young < > [email protected]>wrote: > > > >> Is there an API to pass styling from the parent container to the gadget > >> iframe? For example, we'd like for background colors to match. Does this > >> even make sense? > >> > >> - Mike > >> -- > >> Liferay West Coast Symposium > >> September 8-9, 2010 > >> Anaheim, CA > >> www.liferay.com/wcs > >> -- > >> Follow us on Twitter: liferay > >> > >> > >
