Depends on your needs. TextButton was basically a CellWidget with a
TextButtonCell; but you might also just use a Button widget.
On Friday, October 24, 2014 7:57:49 AM UTC+2, Stefan Lecho wrote:
Thanks for pointing me to the source code. If I want to use v2.7.0-beta1,
with which classes
It seems that the com.google.gwt.widget.client.TextButton class is no
longer packaged in the v2.7.0-beta1 of gwt-user.jar. Where can I find this
class ?
On Saturday, 18 October 2014 19:54:40 UTC+2, Daniel Kurka wrote:
Hi all,
since we are adding major features to GWT, we decided to change
com.google.gwt.widget.* was deprecated and removed in the 2.7 release.
You can get a copy of the files here:
https://code.google.com/p/google-web-toolkit/source/browse/trunk/user/src/com/google/gwt/widget/client?r=9884
On Thu, Oct 23, 2014 at 7:57 AM, Stefan Lecho stle...@gmail.com wrote:
It
Thanks for pointing me to the source code. If I want to use v2.7.0-beta1,
with which classes should I replace them ?
On Friday, 24 October 2014 07:01:27 UTC+2, Goktug Gokdogan wrote:
com.google.gwt.widget.* was deprecated and removed in the 2.7 release.
You can get a copy of the files here:
Hello guys,
we're in the process of trying out GWT 2.7 in our massive application.
Currently we get an error during compile for one module. It worked with GWT
2.6.1.
Any ideas on this one? I'm not sure but the problem might be that we can't
create a JSO using new ..Jso().
But the big question
You can not create a JSO using new in Java. If this has worked with GWT
2.6.1 it is just a bug and should not have worked in the first place.
-Daniel
On Tue, Oct 21, 2014 at 12:46 PM, Jan Thewes janthe...@gmail.com wrote:
Hello guys,
we're in the process of trying out GWT 2.7 in our massive
Ok thx. This is what I assumed.
Will fix this and see how far we can go with 2.7.
Am Dienstag, 21. Oktober 2014 12:51:45 UTC+2 schrieb Daniel Kurka:
You can not create a JSO using new in Java. If this has worked with GWT
2.6.1 it is just a bug and should not have worked in the first place.
IIRC, there was a bug in compiler where is you call GWT.create on JSO (e.g.
when you inject it via GIN), it will generate a new MyJso call (which
shouldn't work normally as the constructor is protected.)
On Tue, Oct 21, 2014 at 4:06 AM, Jan Thewes janthe...@gmail.com wrote:
Ok thx. This is what
I'm seeing what looks like a regression in my project. I get the following
error when running GWT compilation from Gradle after upping the version.
The error doesn't seem very helpful except that it's possibly related to
code generation and UiBinder:
Compiling module com.MyModule
Does adding inherit to c.g.gwt.uibinder.UiBinder fix the issue?
We broke many cyclic dependencies around c.g.gwt.user.User. In this
process, I dropped many unneeded dependencies to User from smaller modules.
As most developers directly depend on User that doesn't have any affect.
However if they
Doesn't seem to help. I did already have a dependency on User. Here's the
full list of inherits from my gwtxml:
inherits name='com.google.gwt.user.User'/
inherits name='com.google.gwt.uibinder.UiBinder'/
inherits name=com.google.gwt.logging.Logging/
inherits
I don't have any other ideas. If you can provide us a simpler repro case,
it would be very helpful.
On Sun, Oct 19, 2014 at 3:11 PM, Erik Kuefler ekuef...@gmail.com wrote:
Doesn't seem to help. I did already have a dependency on User. Here's the
full list of inherits from my gwtxml:
inherits
Is GPE support still pending? I just did a quick test in Kepler. I set
this as my default GWT SDK, then attempted to GWT Compile my project; it
died immediately with this stack trace:
Compiling module com.basis.bbj.web.gwt.EnglishOnly
[ERROR] Unexpected internal compiler error
This looks like an issue with your gwt-unitCache. Can you clear it and
retry?
-Daniel
On Sat, Oct 18, 2014 at 8:17 PM, Jim Douglas jdou...@basis.com wrote:
Is GPE support still pending? I just did a quick test in Kepler. I set
this as my default GWT SDK, then attempted to GWT Compile my
Crap, I knew that, but it's been a few years since it last tripped me up,
so I forgot; retrying now.
On Saturday, October 18, 2014 11:21:23 AM UTC-7, Daniel Kurka wrote:
This looks like an issue with your gwt-unitCache. Can you clear it and
retry?
-Daniel
On Sat, Oct 18, 2014 at 8:17 PM,
No difference...this is the stack trace after erasing gwt-unitCache and
retrying.
Compiling module com.basis.bbj.web.gwt.EnglishOnly
[ERROR] Unexpected internal compiler error
java.lang.IncompatibleClassChangeError: class
com.google.gwt.dev.javac.asm.CollectMethodData has interface
Not trying to run either dev mode, just trying to GWT Compile the package.
On Saturday, October 18, 2014 11:31:44 AM UTC-7, Brandon Donnelson wrote:
There is no special GPE support needed to run GWT 2.7.0-beta1. The same
launch configs can be used.
Although if you want to run dev mode, use
The org.ow2.asm dependency has moved, and I see asm in the class above I
wonder you're dependency configuration look like?
Have a good day,
Brandon Donnelson
+Follow Me https://plus.google.com/u/0/111739836936169749229/posts
On Sat, Oct 18, 2014 at 11:41 AM, Jim Douglas jdou...@basis.com wrote:
I suspect you may need an exclusion or library sort so gwt has a higher
priority in the dependency order.
Have a good day,
Brandon Donnelson
+Follow Me https://plus.google.com/u/0/111739836936169749229/posts
On Sat, Oct 18, 2014 at 11:43 AM, Brandon Donnelson branflake2...@gmail.com
wrote:
No difference...this is the stack trace after erasing gwt-unitCache and
retrying.
Does it work if you put ASM 5.0.3 on class
path? http://forge.ow2.org/projects/asm/
-- J.
--
You received this message because you are subscribed to the Google Groups GWT
Contributors group.
To
Eureka! (Or not quite, but that was much closer to working.) Apparently
our overall project is dependent on asm-all-3.1.jar, and GWT 2.7.0 has a
newer dependency than GWT 2.6.1 (and the APIs are inompatible). Ok,
swapping in asm-all-5.0.3.jar introduces a flood of build errors in another
Process output
Compiling
Compiling permutation 1...
[ERROR] An internal compiler exception occurred
com.google.gwt.dev.jjs.InternalCompilerException: Could not find property
compiler.max.vars.per.var
Hm thats strange. The variable is defined in
Hmm. We do have this in our project.gwt.xml file:
set-configuration-property name='compiler.max.vars.per.var' value='-1'/
I inherited ownership of this project; I'm not sure why that was added.
Removing it does correct that crash. That leaves me with a few
new-for-2.7 linker errors:
On Saturday, October 18, 2014 9:27:20 PM UTC+2, Jim Douglas wrote:
Eureka! (Or not quite, but that was much closer to working.) Apparently
our overall project is dependent on asm-all-3.1.jar, and GWT 2.7.0 has a
newer dependency than GWT 2.6.1 (and the APIs are inompatible).
Prior to
FYI, I'm releasing 2.7.0-beta1 of the gwt-maven-plugin (website is
uploading as I write, then sync to Central could take a few hours too).
On Saturday, October 18, 2014 7:54:40 PM UTC+2, Daniel Kurka wrote:
Hi all,
since we are adding major features to GWT, we decided to change our
release
Invoking Linker Cross-Site-Iframe
[ERROR] The Cross-Site-Iframe linker does not support script tags
in the gwt.xml files, but the gwt.xml file (or the gwt.xml files which it
includes) contains the following script tags:
html2canvas.min.js
jquery-1.11.1.min.js
Because ASM 4+ guarantees API compatibility, when we switched to 5.0.3 (to
support Java 8) we decided to use it directly without rebasing.
Maybe we should bundle ASM 5 in the SDK zip file and let GPE add it to the
class path if no dependency management tool is used. Otherwise beginners
Is there any fundamental reason why we don't support script tags for
Cross-Site-IFrame?
On Sat, Oct 18, 2014 at 2:54 PM, Jens jens.nehlme...@gmail.com wrote:
Invoking Linker Cross-Site-Iframe
[ERROR] The Cross-Site-Iframe linker does not support script tags
in the gwt.xml files, but
IIRC is because scripts should be guaranteed to be loaded before the
onModuleLoad is run, and it was done with document.write before xsiframe
On Sun, Oct 19, 2014 at 12:12 AM, 'Goktug Gokdogan' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:
Is there any
On Sunday, October 19, 2014 12:13:04 AM UTC+2, Goktug Gokdogan wrote:
Is there any fundamental reason why we don't support script tags for
Cross-Site-IFrame?
IIRC that might have to do with detecting when scripts have finished
loading, because script in gwt.xml are guaranteed to be loaded
Does GWT 2.7 change the default linker behaviour? This configuration works
fine in GWT 2.6.1.
On Saturday, October 18, 2014 3:05:33 PM UTC-7, Jens wrote:
Because ASM 4+ guarantees API compatibility, when we switched to 5.0.3 (to
support Java 8) we decided to use it directly without
Seems to me that the script injector isn't perfect with the onload callback
but its one of the ways to do it after the onmodule load. I often will
inject them in the dom afterwords. Google mays has an interesting way where
it has a call back after its loaded which is nifty. Or I will poll until
2.7 uses xsiframe by default when std was the default in previous
versions.
On Sunday, October 19, 2014 12:42:27 AM UTC+2, Jim Douglas wrote:
Does GWT 2.7 change the default linker behaviour? This configuration
works fine in GWT 2.6.1.
On Saturday, October 18, 2014 3:05:33 PM UTC-7, Jens
Ok, now I see 8578
https://code.google.com/p/google-web-toolkit/issues/detail?id=8578 with
the ReleaseNote-BreakingChange tag.
On Saturday, October 18, 2014 3:53:54 PM UTC-7, Thomas Broyer wrote:
2.7 uses xsiframe by default when std was the default in previous
versions.
On Sunday,
34 matches
Mail list logo
