It's applicable to the current trunk, and you should be able to apply it to
fairly recent extracts of trunk as well.


Michael Beaver
IBM Lotus
919-254-7007 (T/L 444)


|------------>
| From:      |
|------------>
  
>--------------------------------------------------------------------------------------------------------------------------------------------------|
  |Rob Keane <[email protected]>                                              
                                                                     |
  
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To:        |
|------------>
  
>--------------------------------------------------------------------------------------------------------------------------------------------------|
  |"[email protected]" <[email protected]>                            
                                                                     |
  
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Cc:        |
|------------>
  
>--------------------------------------------------------------------------------------------------------------------------------------------------|
  |"[email protected]" <[email protected]>                            
                                                                     |
  
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date:      |
|------------>
  
>--------------------------------------------------------------------------------------------------------------------------------------------------|
  |09/29/2011 09:33 AM                                                          
                                                                     |
  
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject:   |
|------------>
  
>--------------------------------------------------------------------------------------------------------------------------------------------------|
  |Re: Inline rendering and 3.0 Release                                         
                                                                     |
  
>--------------------------------------------------------------------------------------------------------------------------------------------------|





Is the 3.0 patch meant to be applied to a tag? A point in time on the
trunk?

Thanks!



On Sep 28, 2011, at 3:19 PM, Michael Beaver <[email protected]> wrote:

> Hey, Kevin.  I've attached 2 versions of the inline patch to the jira
site for inline: https://issues.apache.org/jira/browse/SHINDIG-1402
>
>
> We're currently developing the mixin approach (inline.patch) but for
completeness I also included the original approach that was ported from the
2.0.2 version (inline-initial-port.patch).
>
> Thanks!
>
> Michael Beaver
> IBM Lotus
> 919-254-7007 (T/L 444)
>
> Rob Keane ---09/23/2011 03:44:03 PM---Very cool, I will be checking that
out.  On Sep 23, 2011, at 3:40 PM, "Dan Dumont" <[email protected]
>
>
> From:
>
> Rob Keane <[email protected]>
>
> To:
>
> "[email protected]" <[email protected]>
>
> Date:
>
> 09/23/2011 03:44 PM
>
> Subject:
>
> Re: Inline rendering and 3.0 Release
>
>
>
> Very cool, I will be checking that out.
>
>
>
> On Sep 23, 2011, at 3:40 PM, "Dan Dumont" <[email protected]> wrote:
>
> > You may also want to consider some work that's been recently committed
to
> > allow all views of a gadget to share a reference to a single iframe on
the
> > page that code can be loaded in and shared between all instances of
that
> > gadget (regardless of view rendering).
> >
> > https://reviews.apache.org/r/1749/
> >
> > This allows you to leverage the safety of browser sandboxing while also

> > allowing you to keep all of your code in a single, persistent window.
> > This code will be expanded soon in a new feature that allows several
> > gadgets to share in the use of a single shared-script-frame, even when
> > rendering with locked domains.
> >
> >
> >
> > From:   Rob Keane <[email protected]>
> > To:     "[email protected]" <[email protected]>,
> > Cc:     "[email protected]" <[email protected]>
> > Date:   09/23/2011 03:36 PM
> > Subject:        Re: Inline rendering and 3.0 Release
> >
> >
> >
> > 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.
> >>
> >
> >
> >
>
>

Reply via email to