Hello.
Should it be possible right now to use JsInterop to use the facebook
Javascript sdk?
The call I want to use is FB.XFBML.parse
So I created 2 interfaces:
@JsType
public interface FB {
@JsProperty XFBML getXFBML();
}
@JsType
public interface XFBML {
void parse();
}
I get FB through
Btw, when calling parse() out of jsni or in the browser console, it works
fine. So the Javascript side is ok.
--
You received this message because you are subscribed to the Google Groups "GWT
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email
t
Did you enable jsinterop?
If you did, take a look at the generated javascript and see if it makes
sense.
On Tue, Sep 30, 2014 at 3:55 AM, Michael Vogt wrote:
> Hello.
>
> Should it be possible right now to use JsInterop to use the facebook
> Javascript sdk?
>
> The call I want to use is FB.XFB
Just a thought, the folks that forget to update Java 1.6 to Java 1.7 in
their project and run SDM (super dev mode) will have issues. A warning
could be useful for those trying to run SDM with Java 1.6 otherwise the
warning is an exception of no significance. I'm tempted to ask the IDES to
add o
1.7 was mostly required for GSS and that is no longer planned for 2.7
release so we can probably fix this breakage (recently introduced) instead
of a warning.
On Tue, Sep 30, 2014 at 10:50 AM, Brandon Donnelson wrote:
> Just a thought, the folks that forget to update Java 1.6 to Java 1.7 in
> t
I'm not sure whats going on yet, but I've got some recompile issue coming
up when trying to start dev mode. (This isn't using in browser recompile
button)
After moving to Java 1.7 because of a Java 1.6 error I got stuck with this
error. Not sure whats going on yet, but I thought I'd post it for
By adding the -XjsInteropMode JS option, the thing should work.
Le mardi 30 septembre 2014 12:55:57 UTC+2, Michael Vogt a écrit :
>
> Hello.
>
> Should it be possible right now to use JsInterop to use the facebook
> Javascript sdk?
>
> The call I want to use is FB.XFBML.parse
>
> So I create
Oops. This particular bug shouldn't be hard to fix.
On Tue, Sep 30, 2014 at 10:50 AM, Brandon Donnelson wrote:
> Just a thought, the folks that forget to update Java 1.6 to Java 1.7 in
> their project and run SDM (super dev mode) will have issues. A warning
> could be useful for those trying to
Actually, that particular stack trace should be fixed by this uncommitted
patch:
https://gwt-review.googlesource.com/#/c/9361/
However, I haven't tested it on Java 1.6.
On Tue, Sep 30, 2014 at 11:48 AM, Brian Slesinsky
wrote:
> Oops. This particular bug shouldn't be hard to fix.
>
> On Tue, S
I can explain what's going here I think.
Incremental compile is made possible by storing and reusing data in a new
object called a MinimalRebuildCache. Since some of the analysis that
incremental compilation is much simpler when there is only one permutation
being compiled and since the contents o
Thinking about it, we should probably make superDevMode opt-out instead of
opt-in and make it work out of the box for existing users instead of asking
them to add the -superDevMode.
So what do you think about making superDevMode the default for dev-mode in
2.7 release?
PS: BTW, if you haven't alr
Yeah I kind of agree.
If DevMode support is removed in Chrome soon after the 2.7 release, we'll
be wishing we'd made DevMode launches default to turning superDevMode on.
On Tue, Sep 30, 2014 at 11:54 AM, 'Goktug Gokdogan' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wr
I was looking at this when updating the feature for GPE and thought this
might change in 3.0, but would be easy to adjust in GPE, I'm testing the
preview build now and things are working good.
But on the other hand if this changes, what do you think would happen, b/c
I would need to deal with
Just curious where the GWT 2.6.1+ DocType dtd http location should be?
I would suspect here:
https://gwt.googlesource.com/gwt/+/2.6.1/distro-source/core/src/gwt-module.dtd,
although this location serves up some wrapper ui. I wonder if there is a
way to get a raw file from gittiles?
https://gwt
On Tue, Sep 30, 2014 at 12:06 PM, Brandon Donnelson wrote:
> I was looking at this when updating the feature for GPE and thought this
> might change in 3.0, but would be easy to adjust in GPE, I'm testing the
> preview build now and things are working good.
>
>
The only thing I care here is tryin
>
> Is there any way to get raw files out of gittiles?
>
Currently not: https://code.google.com/p/gitiles/issues/detail?id=7
IMHO the file should be deployed to gwtproject.org along with a nightly one
for SNAPSHOT users.
-- J.
--
You received this message because you are subscribed to the Go
Fwiw, we made it the default in the gwt-maven-plugin.
--
You received this message because you are subscribed to the Google Groups "GWT
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit-contributors+unsubscr...@googlegroup
Should I make this default behavior in GPE? On by default?
On Tuesday, September 30, 2014 3:40:15 PM UTC-7, Thomas Broyer wrote:
>
> Fwiw, we made it the default in the gwt-maven-plugin.
--
You received this message because you are subscribed to the Google Groups "GWT
Contributors" group.
To un
The GWT team thinks that this should be the default behaviour going forward.
On Tue, Sep 30, 2014 at 4:21 PM, Brandon Donnelson
wrote:
> Should I make this default behavior in GPE? On by default?
>
> On Tuesday, September 30, 2014 3:40:15 PM UTC-7, Thomas Broyer wrote:
>>
>> Fwiw, we made it the
We've got quite a few downstream changes to fixup if the flag changes to
turn on DevMode then. When do you think we can get that in so I can adjust
GPE program args. :)
On Tuesday, September 30, 2014 4:22:24 PM UTC-7, Daniel Kurka wrote:
>
> The GWT team thinks that this should be the default be
Goktug mentioned that he thinks the option should be on be default in GWT,
which would mean no change necessary in GPE. And I agree.
On Tue, Sep 30, 2014 at 4:21 PM, Brandon Donnelson
wrote:
> Should I make this default behavior in GPE? On by default?
>
> On Tuesday, September 30, 2014 3:40:15 P
Gotcha. Well, I baked in -superDevMode program arg switch, and this is also
backported in an embedded jar. I would have to take into account some
switch to turn back on DevMode. I was hoping to alleviate the pain of
changing the program args by hand.
On Tuesday, September 30, 2014 4:28:18 PM U
Brandon and I talked a bit about if offline and just the summarize:
If we want to accomplish "making SuperDevMode on as the default behavior in
the DevMode launcher in GPE" it is going to require some changes in
Brandon's work regardless of whether we do it via updating the default
value of the fl
The 'test runner' in this case is just the name of a regular module file,
which happens to be used for running lots of tests, most of which look like
EntryPoints. Nothing too magic going on here, and I've gotten this error by
running modules for more 'normal' gwt apps as well, typically when I s
24 matches
Mail list logo
