ModulePrefs are already exposed in the Gadget / GadgetSpec object. We expect that most containers will use this library directly to get access to this meta data. Doing all of this in javascript is extraordinarily cumbersome, and in the long run probably isn't necessary. We could certainly implement this in pure JS, but I don't think that will be practical for real implementations due to the cost of iframe->container communication.
On Jan 16, 2008 5:30 AM, Martin Webb <[EMAIL PROTECTED]> wrote: > On 15/01/2008, Kevin Brown <[EMAIL PROTECTED]> wrote: > > > > > > We could put a hack in for the reference container that forces use of > set > > height, but that's not very clean either. > > > Can we not put a hack in to return all the ModulePrefs as an object, so > that > the container can opt to make use of it? If so where would that hack go? > > Martin >
