Re: GWT UI Library: which one?
Hello to all, I'd like to share my experience and that of my development team. For nearly eight years we develop GWT applications. GWT we believe is really an awesome tool. We too have had the experience with Polymer and I must say it was not bad. But java is always java, control over the code I think is the first thing. With javascript that, at least for our skil, is more complicated. Our latest project was built using GWT-Material not bad but the lack of data binding is a bit boring. We tested also GWTPolymer but perhaps still young GWT Bootstrap 3 we never tested in real project. Il giorno ven 25 nov 2016 alle ore 08:34 Frank ha scritto: We started our project in Angular with bootstrap. But after about 4 months we dropped in and re-started in GWT with Bootstrap 3. The UI looks identical, but we are much better in programming in Java (this may be a personnal preference). But don't use that GWT bootstrap link you posted. That is for bootstrap 2. There is also a bootstrap 3 wrapper --> https://github.com/gwtbootstrap3/gwtbootstrap3 (and a demo http://gwtbootstrap3.github.io/gwtbootstrap3-demo/snapshot/) Also the bootstrap 2 wrapper isn't as good, used it in a project a few years back and it had quite a lot of problems. Bootstrap 3 wrapper is much better. Op vrijdag 25 november 2016 08:26:31 UTC+1 schreef coderwurst: A screen shot showing how the modern UI looks like is my task, but the examples that have been talked about so far look as if they are based on Bootstrap - my idea is to mock something using GWT-Bootstrap ( http://gwtbootstrap.github.io/) and compare this to a version with Angular2 and Bootstrap-UI (https://angular-ui.github.io/bootstrap/) -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GwtMaterialDesign vs gwt-polymer-elements
Thanks for all the feedback. Didn't know that GWT Material was wraps materializecss. I think polymer is the future. However the more seamless integration of GWT Material with GWT Widgets as well as a more gradual migration might give it a bit of an edge for my use case. Also probably easier bringing the team up to scratch with it as they know GWT. Tough one. Thomas On 30 November 2016 at 11:45, Slava Pankov wrote: > I just don't get this trend with "burying" widgets and UiBinder. Even with > Errai I don't see any meaningful replacement for composite UI, i.e. design > simple blocks as ... and then reuse them with > > Though with Polymer it looks like it's possible by defining web component > for each logical block. > > > On Wednesday, November 23, 2016 at 2:40:45 PM UTC-8, Amit Munwes wrote: >> >> I decided to go with Polymer: >> 1. Very active framework and not specific to GWT developers - so you can >> find answers/examples etc. easily as well as a growing set of web >> components that can be used within your app >> 2. High-end material design components, in browsers as well as mobile >> devices >> 3. Great documentation >> 4. Future-proofing regarding GWT 3.0, using only JS-Interop with no >> widgets >> 5. I use Vaadin's generator directly (not the packaged JAR) so we can >> upgrade Polymer version any time a new version is available >> >> On Friday, November 18, 2016 at 1:45:26 AM UTC+2, tbb wrote: >>> >>> Hi all, >>> >>> I've got a 3 year old enterprise GWT app which also has a mobile app >>> based on GWT. Our current design style is based on Bootstrap. As things >>> change, I'd like to freshen the UX by using Material Design. I've seen 2 >>> libraries: GwtMaterialDesign and gwt-polymer-elements. >>> >>> From what I can see: >>> - Both showcases look great, esp both seem to have an "enterprise" class >>> table/grid control. >>> - GwtMaterialDesign: Read quite positive things in terms of community. >>> - gwt-polymer-elements: By Vaadin which are quite active in the GWT >>> world now, based on "real" Polymer elements and the new GWT 2.8 elemental >>> (?) >>> >>> Would be great if anyone could comment on using either of them as I >>> think once we've decided for one of the libraries, it will be hard to >>> switch. >>> >>> Any feedback would be great! >>> >>> Thanks, >>> Thomas >>> >>> >>> >>> -- > You received this message because you are subscribed to a topic in the > Google Groups "GWT Users" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/google-web-toolkit/5HF8RKs_w3Y/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > google-web-toolkit+unsubscr...@googlegroups.com. > To post to this group, send email to google-web-toolkit@googlegroups.com. > Visit this group at https://groups.google.com/group/google-web-toolkit. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
[no subject]
Hi Group, Tried to update to GWT 2.8 Got some errors, so I reverted to GWT 2.7 and getting the following errors: How can I determine if it is my code or a library issue? I am beginning to believe it is a failing hard drive but dont know how to tell, hard drive checks do not show any issues. ERROR > Compiling module com.CyberObjects.wrrw.WRRWWebMaterial >[ERROR] An internal compiler exception occurred > com.google.gwt.dev.jjs.InternalCompilerException: Unexpected error during > visit. > at > com.google.gwt.dev.jjs.ast.JVisitor.translateException(JVisitor.java:121) > at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:296) > at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:285) > at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:128) > at > com.google.gwt.dev.jjs.ast.JCastOperation.traverse(JCastOperation.java:67) > at > com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:381) > at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:293) > at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:285) > at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:128) > at > com.google.gwt.dev.jjs.ast.JDeclarationStatement.traverse(JDeclarationStatement.java:49) > at > com.google.gwt.dev.jjs.ast.JModVisitor$ListContext.traverse(JModVisitor.java:95) > at > com.google.gwt.dev.jjs.ast.JModVisitor.acceptWithInsertRemove(JModVisitor.java:351) > at com.google.gwt.dev.jjs.ast.JBlock.traverse(JBlock.java:92) > at > com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:381) > at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:293) > at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:149) > at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:145) > at com.google.gwt.dev.jjs.ast.JMethodBody.traverse(JMethodBody.java:83) > at > com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:381) > at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:293) > at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:285) > at com.google.gwt.dev.jjs.ast.JMethod.visitChildren(JMethod.java:600) > at com.google.gwt.dev.jjs.ast.JMethod.traverse(JMethod.java:569) > at > com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:381) > at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:293) > at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:285) > at com.google.gwt.dev.jjs.impl.UnifyAst.mainLoop(UnifyAst.java:1505) > at com.google.gwt.dev.jjs.impl.UnifyAst.exec(UnifyAst.java:870) > at > com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$Precompiler.unifyJavaAst(JavaToJavaScriptCompiler.java:1305) > at > com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$Precompiler.constructJavaAst(JavaToJavaScriptCompiler.java:1038) > at > com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$Precompiler.precompile(JavaToJavaScriptCompiler.java:954) > at > com.google.gwt.dev.jjs.MonolithicJavaToJavaScriptCompiler.precompile(MonolithicJavaToJavaScriptCompiler.java:303) > at > com.google.gwt.dev.jjs.JavaScriptCompiler.precompile(JavaScriptCompiler.java:38) > at com.google.gwt.dev.Precompile.precompile(Precompile.java:286) > at com.google.gwt.dev.Precompile.precompile(Precompile.java:229) > at com.google.gwt.dev.Precompile.precompile(Precompile.java:145) > at com.google.gwt.dev.Compiler.run(Compiler.java:206) > at com.google.gwt.dev.Compiler.run(Compiler.java:158) > at com.google.gwt.dev.Compiler$1.run(Compiler.java:120) > at > com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java:55) > at > com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRunner.java:50) > at com.google.gwt.dev.Compiler.main(Compiler.java:127) > Caused by: java.lang.AbstractMethodError: > org.apache.xerces.dom.ElementNSImpl.setUserData(Ljava/lang/String;Ljava/lang/Object;Lorg/w3c/dom/UserDataHandler;)Ljava/lang/Object; > at > com.google.gwt.uibinder.rebind.W3cDocumentBuilder.startElement(W3cDocumentBuilder.java:127) > at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown > Source) > at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown > Source) > at > org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown > Source) > at > org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown > Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown > Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown > Source) > at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) > at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) > at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
Re:
Try by removing Xerces library. Check http://stackoverflow.com/questions/14014989/java-lang-abstractmethoderror-org-apache-xerces-dom-elementimpl-gettextcontent On Wed, 30 Nov 2016 at 15:48 Ed wrote: > Hi Group, > > Tried to update to GWT 2.8 Got some errors, so I reverted to GWT 2.7 and > getting the following errors: > > How can I determine if it is my code or a library issue? > > I am beginning to believe it is a failing hard drive but dont know how to > tell, hard drive checks do not show any issues. > > ERROR > > Compiling module com.CyberObjects.wrrw.WRRWWebMaterial >[ERROR] An internal compiler exception occurred > com.google.gwt.dev.jjs.InternalCompilerException: Unexpected error during > visit. > at > com.google.gwt.dev.jjs.ast.JVisitor.translateException(JVisitor.java:121) > at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:296) > at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:285) > at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:128) > at > com.google.gwt.dev.jjs.ast.JCastOperation.traverse(JCastOperation.java:67) > at > com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:381) > at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:293) > at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:285) > at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:128) > at > com.google.gwt.dev.jjs.ast.JDeclarationStatement.traverse(JDeclarationStatement.java:49) > at > com.google.gwt.dev.jjs.ast.JModVisitor$ListContext.traverse(JModVisitor.java:95) > at > com.google.gwt.dev.jjs.ast.JModVisitor.acceptWithInsertRemove(JModVisitor.java:351) > at com.google.gwt.dev.jjs.ast.JBlock.traverse(JBlock.java:92) > at > com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:381) > at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:293) > at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:149) > at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:145) > at com.google.gwt.dev.jjs.ast.JMethodBody.traverse(JMethodBody.java:83) > at > com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:381) > at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:293) > at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:285) > at com.google.gwt.dev.jjs.ast.JMethod.visitChildren(JMethod.java:600) > at com.google.gwt.dev.jjs.ast.JMethod.traverse(JMethod.java:569) > at > com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:381) > at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:293) > at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:285) > at com.google.gwt.dev.jjs.impl.UnifyAst.mainLoop(UnifyAst.java:1505) > at com.google.gwt.dev.jjs.impl.UnifyAst.exec(UnifyAst.java:870) > at > com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$Precompiler.unifyJavaAst(JavaToJavaScriptCompiler.java:1305) > at > com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$Precompiler.constructJavaAst(JavaToJavaScriptCompiler.java:1038) > at > com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$Precompiler.precompile(JavaToJavaScriptCompiler.java:954) > at > com.google.gwt.dev.jjs.MonolithicJavaToJavaScriptCompiler.precompile(MonolithicJavaToJavaScriptCompiler.java:303) > at > com.google.gwt.dev.jjs.JavaScriptCompiler.precompile(JavaScriptCompiler.java:38) > at com.google.gwt.dev.Precompile.precompile(Precompile.java:286) > at com.google.gwt.dev.Precompile.precompile(Precompile.java:229) > at com.google.gwt.dev.Precompile.precompile(Precompile.java:145) > at com.google.gwt.dev.Compiler.run(Compiler.java:206) > at com.google.gwt.dev.Compiler.run(Compiler.java:158) > at com.google.gwt.dev.Compiler$1.run(Compiler.java:120) > at > com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java:55) > at > com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRunner.java:50) > at com.google.gwt.dev.Compiler.main(Compiler.java:127) > Caused by: java.lang.AbstractMethodError: > org.apache.xerces.dom.ElementNSImpl.setUserData(Ljava/lang/String;Ljava/lang/Object;Lorg/w3c/dom/UserDataHandler;)Ljava/lang/Object; > at > com.google.gwt.uibinder.rebind.W3cDocumentBuilder.startElement(W3cDocumentBuilder.java:127) > at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown > Source) > at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown > Source) > at > org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown > Source) > at > org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown > Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown > Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown > S
Re:
@Juan - That was it, thank you very much. Ed On Wed, Nov 30, 2016 at 1:51 PM, Juan Pablo Gardella < gardellajuanpa...@gmail.com> wrote: > Try by removing Xerces library. Check http://stackoverflow. > com/questions/14014989/java-lang-abstractmethoderror-org- > apache-xerces-dom-elementimpl-gettextcontent > > On Wed, 30 Nov 2016 at 15:48 Ed wrote: > >> Hi Group, >> >> Tried to update to GWT 2.8 Got some errors, so I reverted to GWT 2.7 and >> getting the following errors: >> >> How can I determine if it is my code or a library issue? >> >> I am beginning to believe it is a failing hard drive but dont know how to >> tell, hard drive checks do not show any issues. >> >> ERROR >> >> Compiling module com.CyberObjects.wrrw.WRRWWebMaterial >>[ERROR] An internal compiler exception occurred >> com.google.gwt.dev.jjs.InternalCompilerException: Unexpected error >> during visit. >> at com.google.gwt.dev.jjs.ast.JVisitor.translateException( >> JVisitor.java:121) >> at com.google.gwt.dev.jjs.ast.JModVisitor.accept( >> JModVisitor.java:296) >> at com.google.gwt.dev.jjs.ast.JModVisitor.accept( >> JModVisitor.java:285) >> at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:128) >> at com.google.gwt.dev.jjs.ast.JCastOperation.traverse( >> JCastOperation.java:67) >> at com.google.gwt.dev.jjs.ast.JModVisitor.traverse( >> JModVisitor.java:381) >> at com.google.gwt.dev.jjs.ast.JModVisitor.accept( >> JModVisitor.java:293) >> at com.google.gwt.dev.jjs.ast.JModVisitor.accept( >> JModVisitor.java:285) >> at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:128) >> at com.google.gwt.dev.jjs.ast.JDeclarationStatement.traverse( >> JDeclarationStatement.java:49) >> at com.google.gwt.dev.jjs.ast.JModVisitor$ListContext. >> traverse(JModVisitor.java:95) >> at com.google.gwt.dev.jjs.ast.JModVisitor.acceptWithInsertRemove( >> JModVisitor.java:351) >> at com.google.gwt.dev.jjs.ast.JBlock.traverse(JBlock.java:92) >> at com.google.gwt.dev.jjs.ast.JModVisitor.traverse( >> JModVisitor.java:381) >> at com.google.gwt.dev.jjs.ast.JModVisitor.accept( >> JModVisitor.java:293) >> at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:149) >> at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:145) >> at com.google.gwt.dev.jjs.ast.JMethodBody.traverse( >> JMethodBody.java:83) >> at com.google.gwt.dev.jjs.ast.JModVisitor.traverse( >> JModVisitor.java:381) >> at com.google.gwt.dev.jjs.ast.JModVisitor.accept( >> JModVisitor.java:293) >> at com.google.gwt.dev.jjs.ast.JModVisitor.accept( >> JModVisitor.java:285) >> at com.google.gwt.dev.jjs.ast.JMethod.visitChildren(JMethod.java:600) >> at com.google.gwt.dev.jjs.ast.JMethod.traverse(JMethod.java:569) >> at com.google.gwt.dev.jjs.ast.JModVisitor.traverse( >> JModVisitor.java:381) >> at com.google.gwt.dev.jjs.ast.JModVisitor.accept( >> JModVisitor.java:293) >> at com.google.gwt.dev.jjs.ast.JModVisitor.accept( >> JModVisitor.java:285) >> at com.google.gwt.dev.jjs.impl.UnifyAst.mainLoop(UnifyAst.java:1505) >> at com.google.gwt.dev.jjs.impl.UnifyAst.exec(UnifyAst.java:870) >> at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$ >> Precompiler.unifyJavaAst(JavaToJavaScriptCompiler.java:1305) >> at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$ >> Precompiler.constructJavaAst(JavaToJavaScriptCompiler.java:1038) >> at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$ >> Precompiler.precompile(JavaToJavaScriptCompiler.java:954) >> at com.google.gwt.dev.jjs.MonolithicJavaToJavaScriptComp >> iler.precompile(MonolithicJavaToJavaScriptCompiler.java:303) >> at com.google.gwt.dev.jjs.JavaScriptCompiler.precompile( >> JavaScriptCompiler.java:38) >> at com.google.gwt.dev.Precompile.precompile(Precompile.java:286) >> at com.google.gwt.dev.Precompile.precompile(Precompile.java:229) >> at com.google.gwt.dev.Precompile.precompile(Precompile.java:145) >> at com.google.gwt.dev.Compiler.run(Compiler.java:206) >> at com.google.gwt.dev.Compiler.run(Compiler.java:158) >> at com.google.gwt.dev.Compiler$1.run(Compiler.java:120) >> at com.google.gwt.dev.CompileTaskRunner.doRun( >> CompileTaskRunner.java:55) >> at com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger( >> CompileTaskRunner.java:50) >> at com.google.gwt.dev.Compiler.main(Compiler.java:127) >> Caused by: java.lang.AbstractMethodError: org.apache.xerces.dom. >> ElementNSImpl.setUserData(Ljava/lang/String;Ljava/lang/ >> Object;Lorg/w3c/dom/UserDataHandler;)Ljava/lang/Object; >> at com.google.gwt.uibinder.rebind.W3cDocumentBuilder.startElement( >> W3cDocumentBuilder.java:127) >> at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown >> Source) >> at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown >> Source) >> at >> org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown >> Source) >> at org.apache.xerce
Re: GWT 2.8 compile fails; 2.7 works
Oops! I do get the error. I was wrong when I said it worked for me. When I
attempted to change the GWT version from 2.7.0 to 2.8.0 in eclipse, eclipse
switched it back to 2.7.0 for reasons I cannot figure out. Given below are
the offending UiBinder code, the corresponding Java code, and the stack
trace when switching a running application from GWT 2.7 to 2.8. Any help
would be greatly appreciated.
http://dl.google.com/gwt/DTD/xhtml.ent";>
PeruseLab -
Loading your drawings...
public class Loader extends Composite {
interface LoaderUiBinder extends UiBinder {
}
private static LoaderUiBinder uiBinder = GWT.create(LoaderUiBinder.class
);
@UiField
PopupPanel launchPad;
@UiField
MaterialColumn container;
public Loader() {
initWidget(uiBinder.createAndBindUi(this));
}
public void hide() {
clear();
launchPad.hide(true);
}
public void show() {
launchPad.show();
}
private void clear() {
while (container.getWidgetCount() > 0) {
container.remove(0);
}
}
}
Caused by: java.lang.NoSuchMethodError: com.google.gwt.uibinder.rebind.
UiBinderWriter.(Lcom/google/gwt/core/ext/typeinfo/JClassType;Ljava/
lang/String;Ljava/lang/String;Lcom/google/gwt/core/ext/typeinfo/TypeOracle;
Lcom/google/gwt/uibinder/rebind/MortalLogger;Lcom/google/gwt/uibinder/rebind
/FieldManager;Lcom/google/gwt/uibinder/rebind/messages/MessagesWriter;Lcom/
google/gwt/uibinder/rebind/DesignTimeUtils;Lcom/google/gwt/uibinder/rebind/
UiBinderContext;ZZLjava/lang/String;Lcom/google/gwt/dev/resource/
ResourceOracle;Lcom/google/gwt/resources/rg/GssResourceGenerator$GssOptions
;)V
at com.google.gwt.uibinder.rebind.UiBinderGenerator.generateOnce(
UiBinderGenerator.java:174)
at com.google.gwt.uibinder.rebind.UiBinderGenerator.generate(
UiBinderGenerator.java:128)
at com.google.gwt.core.ext.IncrementalGenerator.generateNonIncrementally(
IncrementalGenerator.java:40)
at com.google.gwt.dev.javac.StandardGeneratorContext.
runGeneratorIncrementally(StandardGeneratorContext.java:745)
at com.google.gwt.dev.cfg.RuleGenerateWith.realize(RuleGenerateWith.java:
103)
at com.google.gwt.dev.shell.StandardRebindOracle$Rebinder.rebind(
StandardRebindOracle.java:78)
at com.google.gwt.dev.shell.StandardRebindOracle.rebind(
StandardRebindOracle.java:262)
at com.google.gwt.dev.shell.StandardRebindOracle.rebind(
StandardRebindOracle.java:251)
at com.google.gwt.dev.PrecompilationContextCreator$1.
getAllPossibleRebindAnswers(PrecompilationContextCreator.java:86)
at com.google.gwt.dev.jjs.impl.UnifyAst$UnifyVisitor.
createStaticRebindExpression(UnifyAst.java:519)
at com.google.gwt.dev.jjs.impl.UnifyAst$UnifyVisitor.createRebindExpression
(UnifyAst.java:487)
at com.google.gwt.dev.jjs.impl.UnifyAst$UnifyVisitor.
maybeHandleMagicMethodCall(UnifyAst.java:415)
at com.google.gwt.dev.jjs.impl.UnifyAst$UnifyVisitor.visit(UnifyAst.java:
402)
at com.google.gwt.dev.jjs.ast.JMethodCall.traverse(JMethodCall.java:265)
at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361)
at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273)
... 46 more
[ERROR] at Loader.java(29): GWT.create(Loader$LoaderUiBinder.
class)
com.google.gwt.dev.jjs.ast.JMethodCall
[ERROR] at Loader.java(29): (Loader$LoaderUiBinder) GWT.create(
Loader$LoaderUiBinder.class)
com.google.gwt.dev.jjs.ast.JCastOperation
[ERROR] at Loader.java(29): static Loader$LoaderUiBinder
uiBinder = (Loader$LoaderUiBinder) GWT.create(Loader$LoaderUiBinder.class)
com.google.gwt.dev.jjs.ast.JDeclarationStatement
[ERROR] at Loader.java(24): {
Composite.$clinit();
static Loader$LoaderUiBinder uiBinder = (Loader$LoaderUiBinder) GWT.create
(Loader$LoaderUiBinder.class);
}
com.google.gwt.dev.jjs.ast.JBlock
[ERROR] at Loader.java(24): {
Composite.$clinit();
static Loader$LoaderUiBinder uiBinder = (Loader$LoaderUiBinder) GWT.create
(Loader$LoaderUiBinder.class);
}
com.google.gwt.dev.jjs.ast.JMethodBody
[ERROR] at Loader.java(24): com.snkv.peruse.client.Loader.
$clinit()V
com.google.gwt.dev.jjs.ast.JMethod
[ERROR] Compiler returned false
[WARN] recompile failed
On Monday, November 21, 2016 at 4:07:42 PM UTC-5, jgindin wrote:
>
> In our app, we have a UiBinder widget (SomeViewImpl) which has, as its
> root element, a widget which itself is a UiBinder widget
> (CollectionManagementLayout).
>
> My UiBinder declaration in SomeViewImpl looks like this:
> interface CollectionManagementPanelUiBinder extends
> UiBinder {}
>
>
> The UiBinder XML for the SomeViewImpl class starts off like this:
>
> . . .
>
>
>
>
> This code c
Re: GWT 2.8 compile fails; 2.7 works
Here's the remainder of the stack trace
at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273)
... 46 more
[ERROR] at Loader.java(29): GWT.create(Loader$LoaderUiBinder.
class)
com.google.gwt.dev.jjs.ast.JMethodCall
[ERROR] at Loader.java(29): (Loader$LoaderUiBinder) GWT.create(
Loader$LoaderUiBinder.class)
com.google.gwt.dev.jjs.ast.JCastOperation
[ERROR] at Loader.java(29): static Loader$LoaderUiBinder
uiBinder = (Loader$LoaderUiBinder) GWT.create(Loader$LoaderUiBinder.class)
com.google.gwt.dev.jjs.ast.JDeclarationStatement
[ERROR] at Loader.java(24): {
Composite.$clinit();
static Loader$LoaderUiBinder uiBinder = (Loader$LoaderUiBinder) GWT.create
(Loader$LoaderUiBinder.class);
}
com.google.gwt.dev.jjs.ast.JBlock
[ERROR] at Loader.java(24): {
Composite.$clinit();
static Loader$LoaderUiBinder uiBinder = (Loader$LoaderUiBinder) GWT.create
(Loader$LoaderUiBinder.class);
}
com.google.gwt.dev.jjs.ast.JMethodBody
[ERROR] at Loader.java(24): com.snkv.peruse.client.Loader.
$clinit()V
com.google.gwt.dev.jjs.ast.JMethod
[ERROR] Compiler returned false
On Wednesday, November 30, 2016 at 2:45:35 PM UTC-5, Velusamy Velu wrote:
>
> Oops! I do get the error. I was wrong when I said it worked for me. When I
> attempted to change the GWT version from 2.7.0 to 2.8.0 in eclipse, eclipse
> switched it back to 2.7.0 for reasons I cannot figure out. Given below are
> the offending UiBinder code, the corresponding Java code, and the stack
> trace when switching a running application from GWT 2.7 to 2.8. Any help
> would be greatly appreciated.
>
> http://dl.google.com/gwt/DTD/xhtml.ent";>
>xmlns:g="urn:import:com.google.gwt.user.client.ui"
> xmlns:m="urn:import:gwt.material.design.client.ui">
>
>
>
>
>
> PeruseLab -
> Loading your drawings...
> "false" ui:field="progressBar" />
>
>
>
>
>
>
>
> public class Loader extends Composite {
>
> interface LoaderUiBinder extends UiBinder {
> }
>
> private static LoaderUiBinder uiBinder = GWT.create(LoaderUiBinder.
> class);
>
> @UiField
> PopupPanel launchPad;
>
> @UiField
> MaterialColumn container;
>
> public Loader() {
> initWidget(uiBinder.createAndBindUi(this));
> }
>
> public void hide() {
> clear();
> launchPad.hide(true);
> }
>
> public void show() {
> launchPad.show();
> }
>
> private void clear() {
> while (container.getWidgetCount() > 0) {
> container.remove(0);
> }
> }
> }
>
>
> Caused by: java.lang.NoSuchMethodError: com.google.gwt.uibinder.rebind.
> UiBinderWriter.(Lcom/google/gwt/core/ext/typeinfo/JClassType;Ljava/
> lang/String;Ljava/lang/String;Lcom/google/gwt/core/ext/typeinfo/TypeOracle
> ;Lcom/google/gwt/uibinder/rebind/MortalLogger;Lcom/google/gwt/uibinder/
> rebind/FieldManager;Lcom/google/gwt/uibinder/rebind/messages/
> MessagesWriter;Lcom/google/gwt/uibinder/rebind/DesignTimeUtils;Lcom/google
> /gwt/uibinder/rebind/UiBinderContext;ZZLjava/lang/String;Lcom/google/gwt/
> dev/resource/ResourceOracle;Lcom/google/gwt/resources/rg/
> GssResourceGenerator$GssOptions;)V
> at com.google.gwt.uibinder.rebind.UiBinderGenerator.generateOnce(
> UiBinderGenerator.java:174)
> at com.google.gwt.uibinder.rebind.UiBinderGenerator.generate(
> UiBinderGenerator.java:128)
> at com.google.gwt.core.ext.IncrementalGenerator.generateNonIncrementally(
> IncrementalGenerator.java:40)
> at com.google.gwt.dev.javac.StandardGeneratorContext.
> runGeneratorIncrementally(StandardGeneratorContext.java:745)
> at com.google.https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
Re: GWT 2.8 compile fails; 2.7 works
> Oops! I do get the error. > Your error is a different one. Your error means you either have GWT 2.7 and 2.8 on classpath or some of your 3rd party libraries have bundled some older copies of UiBinder generator files. -- J. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT 2.8 compile fails; 2.7 works
> *My question is*: Should this have failed in GWT 2.7? Or is there a bug > in GWT 2.8? > Given that the error message The interface UiBinder cannot be implemented more than once with different arguments: UiBinder and UiBinder< CollectionManagementLayout,SomeViewImpl> already sounds dumb (arguments are both the same and not different), I would guess its a bug. If you can create a small, self contained example project that demonstrates the issue you should file a bug on github. -- J. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT 2.8 generates code 14% bigger than GWT 2.7
SSO is not working for my project, I cannot successfully compile with it. Put the following to my gwt.xml, but no luck: On Tuesday, November 29, 2016 at 6:44:37 AM UTC-8, Kirill Prazdnikov wrote: > > Do you use SSO ? SSO script is smaller then no SSO. Did you run CC on it ? > > 29 нояб. 2016 г. 17:29 пользователь "Etienne Basso" > написал: > >> Hi Ignacio, >> >> This is not only about loading time over the network, but also about >> script parsing by the web browser. >> In 98% of the case this is not an issue, but I have a very specific use >> case were the code is directly embedded on a special device which doesn't >> even have a real CPU but an ASIC emulating one. This device is really >> really not powerful and GWT is the only framework providing decent speed. >> I noticed significant differences in the script parsing delay as js sources >> are getting bigger. >> >> In my case 100KB are a huge deal. >> >> Le samedi 26 novembre 2016 09:56:27 UTC+1, Ignacio Baca Moreno-Torres a >> écrit : >>> >>> But IMO if you really care user experience you have other places to >>> improve your page. I thinks updating to the last version is always a good >>> idea, if any security or compatibility blocker problem is detected in your >>> version you will need to update, and having a old version won't help. Also >>> this helps move forward the community and the lib (GWT), because everyone >>> focused in the last version, also focus the issues and improvements in that >>> version. >>> >>> The small step back eliminating the closure compiler just increase a bit >>> the code size of your app. But 100k?! did you see the trends and the >>> average code size of webs? >>> http://httparchive.org/trends.php?s=All&minlabel=Nov+15+2014&maxlabel=Nov+1+2016, >>> >>> you should note that even google.com uses 500k in 13request to load, >>> and it's ""just"" a text inbox in the center of your window ( >>> http://httparchive.org/viewsite.php?pageid=70036564). >>> >>> I might be wrong, but probably trying to embed the app.nocache.js in >>> your index.html will gain some milliseconds, probably just that dummy >>> change will get more ms than the cache-ables 100k you have lose without the >>> closure pass. If your app is quite big, various MBs, you should take care >>> than the first split point load a minimum as possible to show something to >>> the user. But, in your case, less than a 1M, I think that using split point >>> is not a good idea. Your code will get cached, and most of static apps >>> already has more than 500k of JS, so your single page app having a 500k-1M >>> of JS is pretty reasonable. >>> >>> You can go forward and apply the progressive web concepts ( >>> https://developers.google.com/web/progressive-web-apps/checklist). >>> Pretty sure you get there without the closure compiler ;). Service workers >>> will allow maximum control to preload other split point or resources, and >>> to absolutely control how your app caches, so you can use previous version, >>> load the next one and in the next page reload the new app version will be >>> used. This is not easy at all, but... some time we focus on the >>> optimization we have no control of (like the closure pass) and we don't >>> apply other we have control of, but that requires our effort. >>> >>> So, 😀 update to GWT 2.8! it's awesome!, try other solutions to improve >>> page loads and share how you do it! >>> >>> On Friday, November 25, 2016 at 10:39:44 PM UTC+1, Slava Pankov wrote: @Jens I've tried WITHOUT any success to use closure compiler externally with GWT 2.8 See my question here: https://groups.google.com/forum/#!searchin/google-web-toolkit/closure$20compiler%7Csort:date/google-web-toolkit/k_kjIv9Klsg/LZAZiUf9BAAJ Still want to find out exact steps to get it working :-( On Friday, November 25, 2016 at 2:43:11 AM UTC-8, Kirill Prazdnikov wrote: > > Hi Jens, > > What if we have SSO linker ? > Then no hacks is needed, right ? > Then just run the Google Closure Compiler on the output. > -- >> >> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT 2.8 generates code 14% bigger than GWT 2.7
Please try single permutation On Thu, Dec 1, 2016 at 1:50 AM, Slava Pankov wrote: > SSO is not working for my project, I cannot successfully compile with it. > Put the following to my gwt.xml, but no luck: > > > > > > > On Tuesday, November 29, 2016 at 6:44:37 AM UTC-8, Kirill Prazdnikov wrote: >> >> Do you use SSO ? SSO script is smaller then no SSO. Did you run CC on it ? >> >> 29 нояб. 2016 г. 17:29 пользователь "Etienne Basso" >> написал: >> >> Hi Ignacio, >>> >>> This is not only about loading time over the network, but also about >>> script parsing by the web browser. >>> In 98% of the case this is not an issue, but I have a very specific use >>> case were the code is directly embedded on a special device which doesn't >>> even have a real CPU but an ASIC emulating one. This device is really >>> really not powerful and GWT is the only framework providing decent speed. >>> I noticed significant differences in the script parsing delay as js sources >>> are getting bigger. >>> >>> In my case 100KB are a huge deal. >>> >>> Le samedi 26 novembre 2016 09:56:27 UTC+1, Ignacio Baca Moreno-Torres a >>> écrit : But IMO if you really care user experience you have other places to improve your page. I thinks updating to the last version is always a good idea, if any security or compatibility blocker problem is detected in your version you will need to update, and having a old version won't help. Also this helps move forward the community and the lib (GWT), because everyone focused in the last version, also focus the issues and improvements in that version. The small step back eliminating the closure compiler just increase a bit the code size of your app. But 100k?! did you see the trends and the average code size of webs? http://httparchive.org/t rends.php?s=All&minlabel=Nov+15+2014&maxlabel=Nov+1+2016, you should note that even google.com uses 500k in 13request to load, and it's ""just"" a text inbox in the center of your window ( http://httparchive.org/viewsite.php?pageid=70036564). I might be wrong, but probably trying to embed the app.nocache.js in your index.html will gain some milliseconds, probably just that dummy change will get more ms than the cache-ables 100k you have lose without the closure pass. If your app is quite big, various MBs, you should take care than the first split point load a minimum as possible to show something to the user. But, in your case, less than a 1M, I think that using split point is not a good idea. Your code will get cached, and most of static apps already has more than 500k of JS, so your single page app having a 500k-1M of JS is pretty reasonable. You can go forward and apply the progressive web concepts ( https://developers.google.com/web/progressive-web-apps/checklist). Pretty sure you get there without the closure compiler ;). Service workers will allow maximum control to preload other split point or resources, and to absolutely control how your app caches, so you can use previous version, load the next one and in the next page reload the new app version will be used. This is not easy at all, but... some time we focus on the optimization we have no control of (like the closure pass) and we don't apply other we have control of, but that requires our effort. So, 😀 update to GWT 2.8! it's awesome!, try other solutions to improve page loads and share how you do it! On Friday, November 25, 2016 at 10:39:44 PM UTC+1, Slava Pankov wrote: > > @Jens > > I've tried WITHOUT any success to use closure compiler externally with > GWT 2.8 > See my question here: https://groups.google.co > m/forum/#!searchin/google-web-toolkit/closure$20compiler% > 7Csort:date/google-web-toolkit/k_kjIv9Klsg/LZAZiUf9BAAJ > Still want to find out exact steps to get it working :-( > > > On Friday, November 25, 2016 at 2:43:11 AM UTC-8, Kirill Prazdnikov > wrote: >> >> Hi Jens, >> >> What if we have SSO linker ? >> Then no hacks is needed, right ? >> Then just run the Google Closure Compiler on the output. >> > -- >>> >>> -- > You received this message because you are subscribed to a topic in the > Google Groups "GWT Users" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/google-web-toolkit/IIQk4xH0-g8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > google-web-toolkit+unsubscr...@googlegroups.com. > To post to this group, send email to google-web-toolkit@googlegroups.com. > Visit this group at https://groups.google.com/group/google-web-toolkit. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and sto
