Awesome. good to know. I need to figure out how it manages to work.

On Tue, Feb 15, 2011 at 4:52 PM, Chris Conroy <con...@google.com> wrote:

> Actually, it does work.
>
> On Tue, Feb 15, 2011 at 4:49 PM, Kelly Norton <knor...@google.com> wrote:
> > I could be wrong, but I don't think the xsiframe linker is going to work
> > here.
> >
> > On Tue, Feb 15, 2011 at 4:46 PM, Kelly Norton <knor...@google.com>
> wrote:
> >>
> >> xsiframe is fine if it works. But you'll have to check it because these
> >> are not the normal xs restrictions.
> >>
> >> On Tue, Feb 15, 2011 at 4:28 PM, Unnur Gretarsdottir <unn...@google.com
> >
> >> wrote:
> >>>
> >>> All google3 projects are being switched to xsiframe in a few weeks
> >>> (currently blocked by lack of a Blaze push).  Deprecation/deletions of
> >>> other linkers for regular GWT will soon follow, but to be honest, will
> >>> be a GWT 3.0 thing at the very earliest.
> >>>
> >>> It's not a burning issue, but I do recommend that you do not switch to
> >>> the xs linker at this point. It doesn't install in an iframe, and
> >>> switching from being iframe installed vs. not has proven painful for
> >>> some teams.  Right now - if you're using the std linker (default),
> >>> your compliant with being installed in an iframe, so if you start
> >>> using xs, pick up some code dependencies that assume non-iframe, and
> >>> then need to switch back to iframe based (xsiframe), you may see some
> >>> issues.  Or maybe not....
> >>>
> >>> It's also possible that xs does not support DevMode - I can't remember
> >>> off the top of my head.  If you care about that, then xsiframe
> >>> definitely does support it.
> >>>
> >>> - Unnur
> >>>
> >>> On Tue, Feb 15, 2011 at 1:09 PM, John Tamplin <j...@google.com> wrote:
> >>> > On Tue, Feb 15, 2011 at 4:03 PM, Chris Conroy <con...@google.com>
> >>> > wrote:
> >>> >>
> >>> >> Sorry, didn't see your comment in time for the commit. I just used
> the
> >>> >> same fix Kelly applied in SpeedTracer. I don't think it really
> matters
> >>> >> strongly either way.
> >>> >
> >>> > As I understand it, the xs linker will soon be deprecated since the
> >>> > xsiframe
> >>> > linker provides a superset of its functionality.
> >>> >
> >>> > --
> >>> > John A. Tamplin
> >>> > Software Engineer (GWT), Google
> >>> >
> >>
> >>
> >>
> >> --
> >> If you received this communication by mistake, you are entitled to one
> >> free ice cream cone on me. Simply print out this email including all
> >> relevant SMTP headers and present them at my desk to claim your creamy
> >> treat. We'll have a laugh at my emailing incompetence, and play a game
> of
> >> ping pong. (offer may not be valid in all States).
> >>
> >
> >
> >
> > --
> > If you received this communication by mistake, you are entitled to one
> free
> > ice cream cone on me. Simply print out this email including all relevant
> > SMTP headers and present them at my desk to claim your creamy treat.
> We'll
> > have a laugh at my emailing incompetence, and play a game of ping pong.
> > (offer may not be valid in all States).
> >
> >
>



-- 
If you received this communication by mistake, you are entitled to one free
ice cream cone on me. Simply print out this email including all relevant
SMTP headers and present them at my desk to claim your creamy treat. We'll
have a laugh at my emailing incompetence, and play a game of ping pong.
(offer may not be valid in all States).

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Reply via email to