Excellent! IFrames come with a decent amount of overhead and we'd love to be able to share common libraries and CSS between gadgets without loading them over and over again individually.
Those issues have caused some undesirable performance hits on older browsers and hardware. On Sep 23, 2011, at 11:51 AM, Michael Beaver <[email protected]> wrote: > Hi, Rob. > > We're planning on submitting a preview of our inline work early next week to > the community and would love to work with you on assessing the approach. > There are a number of items we're still working on but feel that it would be > beneficial to get some feedback from the community while it's still in > progress. The 3.0 approach is different from the inline patch that was based > on 2.0.2, and instead operates as a container mixin to avoid massive > modification of core container code. The result is a significantly cleaner > approach. > > Also, we'd really like to understand what requirements and functionality your > company is interested in for rendering gadgets inline, so hopefully this > early preview can be used to help drive that discussion. > > > Thanks! > > Michael Beaver > IBM Lotus > 919-254-7007 (T/L 444) > > Rob Keane ---09/22/2011 01:46:18 PM---My company is very interested in inline > rendering and the 3.0 release. Will this feature be include > > > From: > > Rob Keane <[email protected]> > > To: > > "[email protected]" <[email protected]> > > Date: > > 09/22/2011 01:46 PM > > Subject: > > Inline rendering and 3.0 Release > > > > My company is very interested in inline rendering and the 3.0 release. > > Will this feature be included in the release, will it be in a beta release if > so? > > Is there any rough timeline for the 3.0 release? > > Apologies if these questions have already been addressed, I was unable to > find an answer. >
