gadgets.rpc isn't the solution that you need -- we still have no way of messaging the parent container to the type=url gadget, thus you're stuck in the same bind (you have to hard code the parent url).
On Feb 18, 2008 11:10 PM, Neo Anderson <[EMAIL PROTECTED]> wrote: > Zhen implemented rpc. How to use dynamic height with with <Content > type="url" href="xxxxxxxxxxx.jsp" /> using this rpc? > > On Feb 14, 2008 1:09 PM, Kevin Brown <[EMAIL PROTECTED]> wrote: > > > On Wed, Feb 13, 2008 at 11:12 PM, Neo Anderson < > > [EMAIL PROTECTED]> wrote: > > > > > I have a gadget with <Content type="url" href="xxxxxxxxxxx.jsp" /> in > > xml > > > file. > > > > > > I want to use dynamic-height feature. As it is a jsp(or any other > server > > > side technology like ASP, PHP) page, I may not be able to place my > code > > > inside this content tag (Can I place server side code here?). In this > > > case, > > > how can I use dynamic-height feature? Can I place > > _IG_AdjustIFrameHeight() > > > method in that *xxxxxxxxxxx.jsp *page? Will it work? > > > > > > You should use gadgets.window.adjustHeight and it'll work -- however > > there's > > one outstanding issue with Shindig today which is that you have no way > of > > knowing what the parent page is (and thus where to get the appropriate > > javascript from). > > > > In general, libraries should be emitted by inspecting the libs parameter > > that is passed to your server and using that as the root for generating > > your > > iframe source. Unfortunately, this has one major outstanding flaw which > is > > that you don't know what host it came from (before open sourcing this > > technology, google simply had authors point to www.gmodules.com/..< > http://www.gmodules.com/>., > > but the > > javascript served there is not completely compatible with shindig). > We're > > working on a solution. > > > > In the interim, you'll want to generate something like this (PHP > example): > > > > $scriptPath = $containerUrl.strip_tags($_GET['libs']); > > echo '<script src="'.$scriptPath.'"></script>'; > > > > where $containerUrl points to the container page. I *think* you can get > > this > > value from the "parent" parameter, but I'm not completely sure that this > > path is accurate (and you still need to white list containers that you > > trust, since otherwise you're opening the door for XSS attacks). > > > > > > > > -- > > ~Kevin > > > > If you received this email by mistake, please delete it, cancel your > mail > > account, destroy your hard drive, silence any witnesses, and burn down > the > > building that you're in. > > > -- ~Kevin If you received this email by mistake, please delete it, cancel your mail account, destroy your hard drive, silence any witnesses, and burn down the building that you're in.
