>> On Fri, Jan 21, 2011 at 8:22 AM, Michael MacFadden <
>> [email protected]> wrote:
>>> Any ideas why when a gadget is added to the blip it seems to have a
height
>>> of 20px, rather than the heigh specified in the gadget definition?

I'm seeing this height problem with urls like
http://blah.appspot.com/wave/sudoku/sudoku.xml. This Url sizes correctly on
Google wave. I couldn't find an issue logged for this. Should I log one? Are
others seeing this happen?

Also, is there any information about using existing Google gadgets? Well,
for example, would it be okay to create a catalog of gadgets like Google
wave has? I imagine if the gadget were used as is without any change the
gadget creator would be okay with it. But, what are the legal/logistical
issues involved?

Thanks,
Scott


On Thu, Jan 20, 2011 at 10:45 PM, Paul Lindner <[email protected]> wrote:

> You might try adding a call to
>
> gadgets.window.adjustHeight()
>
> in your initialize function (and anytime you change the viewport sizing)
>
>
> On Thu, Jan 20, 2011 at 7:37 PM, Michael MacFadden
> <[email protected]> wrote:
> > It' happening to some, but not to this one for example.. it could be my
> gadget.
> >
> > http://wave.macfadden.org/poly-map.xml
> >
> >
> > On Jan 20, 2011, at 7:07 PM, David Hearnden wrote:
> >
> >> As to why the height is 20px, it's the default height constant in
> >> GadgetWidgetUi.  When the iframe gets constructed, that's the height it
> >> gets.
> >> When I add a gadget to a wave, the height does gets adjusted to the
> correct
> >> height after the gadget loads.  Does that not happen for you?
> >>
> >> (Gadgets do seem to have an ugly border around them for some reason).
> >>
> >> -Dave
> >>
> >> On Fri, Jan 21, 2011 at 8:22 AM, Michael MacFadden <
> >> [email protected]> wrote:
> >>
> >>> All,
> >>>
> >>> Any ideas why when a gadget is added to the blip it seems to have a
> height
> >>> of 20px, rather than the heigh specified in the gadget definition?
> >>>
> >>> Michael
> >
> >
>
>
>
> --
> Paul Lindner -- [email protected] -- linkedin.com/in/plindner
>

Reply via email to