UIBinder content assist incomplete?
I'm currently trying to setup a GWT 2.7 Dev-Environment. I want to be able to use content assist for UIbinder xml files, and what does work for me is when I type a and press Ctrl+Space (or wait for a second there) I get a list of classes to choose from. First problem is it starts with AbbreviatePositionalValues (com.google.gwt.thirdparty.common.css.compiler.passes) and ends with AWTPermission (java.awt). So the problems I infer from that: -) The list is incomplete (very much so). And this is probably because the list overflows, because its too long, because -) it contains completely irrelevant classes like from java.awt Second problem: I can't start to type to filter that list. as soon as I type a single character the popup vanishes. I think I remember that in the past I was able to type g: and then press ctrl+space to get a (filterable!) list of the classes inside the package com.google.gwt.user.client.ui I'm using Eclipse Luna 1a (4.4.1) and the latest eclipse gwt plugin from this update site: https://dl.google.com/eclipse/plugin/4.4 -- You received this message because you are subscribed to the Google Groups Google Web Toolkit 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Login + CRUD example
This is a web-based CRUD-Application that I've wrote for my employer over the last few years and now got permission to open-source it: https://github.com/fhcampuswien/atom It uses GWT for the front-end and Hibernate to persist the data in the back-end. The data-structure only needs to be defined in one central place (the DomainObject classes), since both GUI and back-end are written in a generic way that is not dependent on the data-structure. The user authentication code in the version I've open sourced is not complete/functional since the part that I did not open-source interacts with a single-sign-on system we use here at the FH Campus Wien and would be useless for anybody else anyway. I'd love to hear comments if anybody finds the time to take a look. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Visibility problems when using css.InterfaceGenerator
just ran into this issue with gwt 2.6.0 and the css generation controlled
by gwt-maven-plugin 2.6.0
Is there a fix yet? is there some option to set to make the interface
public?
I guess I will implement your workaround extending the protected interfaces
with a public one, but I also would prefer to not have to do that.
On Friday, April 1, 2011 10:21:57 AM UTC+2, Raphael Bauer wrote:
On Wed, Mar 30, 2011 at 12:07 PM, Thomas Broyer t.br...@gmail.com
javascript: wrote:
Every member of an interface can only be public (and is implicitly so,
without the need to explicitly use the 'public' keyword), including inner
interfaces.
http://java.sun.com/docs/books/jls/third_edition/html/interfaces.html#9.5
Thanks Thomas. That makes total sense.
But the problem are not the members of the interface, but the
visibility of the interface itself I guess
http://java.sun.com/docs/books/jls/third_edition/html/interfaces.html#9.1.1
).
In my opinion
interface MyGeneratedCssInterface extends CssResource {
is quite different to
public interface MyGeneratedCssInterface extends CssResource {
Maybe my explanation of the problem was not the best. Sorry.
Best,
Raphael
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-we...@googlegroups.com
javascript:.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com javascript:.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit 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 http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
Re: How to embed HTML from TextResource using UiBinder
Is there an easier way by now?
Am Mittwoch, 3. April 2013 01:10:52 UTC+2 schrieb Thomas Broyer:
On Wednesday, April 3, 2013 12:34:06 AM UTC+2, Pat wrote:
I found something that works, even though I think that should be possible
with less glue code...
It should be possible to create a SafeHtmlResource, that could validate
the content of the resource at build-time.
Otherwise, your solution below is the only one I could think about.
interface TextsBundle extends ClientBundle { @Source(text.txt)
TextResource myText(); }
class SafeHtmlTexts {
@Inject TextBundle texts;
public SafeHtml myText() { return
SafeHtmlUtils.fromSafeConstant(texts.myText().getText()); }
}
class ViewImpl {
private final SafeHtmlTexts texts;
@Inject public ViewImpl(..., SafeHtmlTexts texts) { this.texts = texts;
... }
...
@UiFactory SafeHtmlTexts create() { return texts; }
You could simply use a @UiField for 'texts' rather than the @UiFactory. If
you want the SafeHtmlTexts to be provided (by GIN apparently), use
@UiField(provided=true) (and you can then have your field 'final').
}
ViewImpl.ui.xml:
ui:with field='texts' type='SafeHtmlTexts'/
...
divui:safehtml from={texts.myText}//div
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit 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 http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
Re: gwt-maven-archetypes with multiple client modules
Okey! So you've helped me make a huge step forward yesterday, thanks for that Thomas! Now I've got a new problem I can't find my way around: I've tried to move the App.java App*.gwt.xml into from the package group.id into the package group.id.client package, and adapted the references within the pom.xml and gwt.xml files (and also in gwt.xml change source path= / to source path=client / ), but when I try to do a maven build it always fails: [INFO] Compiling module group.id.client.App [INFO]Finding entry point classes [INFO] [ERROR] Unable to find type 'group.id.client.App' [INFO] [ERROR] Hint: Previous compiler errors may have made this type unavailable [INFO] [ERROR] Hint: Check the inheritance chain from your module; it may not be inheriting a required module or a module may not be adding its source path entries properly The step Finding entry point classes takes quite long, around 5 seconds before the failure shows.. When I undo the move and restore the references to group.id.App it works again as expected. Do you have an idea, what could cause that? Have I missed something that needs adapting when moving the module entrypoint? Am Mittwoch, 22. Mai 2013 14:46:53 UTC+2 schrieb Thomas Broyer: On Wednesday, May 22, 2013 1:08:38 PM UTC+2, Thomas Käfer wrote: Thanks for your reply, and thanks for the info! Have a working debug-able environment now! With this Debug As… → Web Application (running on an external server) on the client project, I get the error Could not find any host-pages in project name-client My setup is generated by your maven archetype modular-webapp and nearly no changes, only played around with debug configurations and maven a little bit. This is strange 'cause I tested it as I was replying, with a freshly created modular-webapp project. I had an error about test-client/target/test-client-1.0.0-SNAPSHOT not existing, but that was because I hadn't previously mvn package (or even run mvn tomcat7:run). I deleted the launch config and started again (Debug As…) and it just worked. But based on your other info I've managed to create a Web Application debug configuration manually, and it works! That's generally what I do, as I like to have control. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit 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 http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: gwt-maven-archetypes with multiple client modules
Am Donnerstag, 23. Mai 2013 13:18:47 UTC+2 schrieb Thomas Broyer: If you use source path=client/ then the gwt.xml has to be in group.id, otherwise only group.id.client.client.* classes are in the source path. group.id.client.App is not an thus cannot be found. Oh my god, I'm so stupid.. Thanks so much! I'm really not worth the money they pay me ;) -- You received this message because you are subscribed to the Google Groups Google Web Toolkit 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 http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: gwt-maven-archetypes with multiple client modules
how to launch the DevMode from within eclipse on a setup with seperate client server project like your maven-archetype modular-webapp, without using maven? I'm trying to find this already for a few weeks, but I did not find a solution yet. Problem with the maven gwt:run launch is, that the client-side code isn't debug-able that way -- only server-side with the tomcat7-run can be debugged that way.. I've tried to create an eclipse run configuration analog to my single-project setups, but nothing worked so far... Am Freitag, 7. Dezember 2012 10:01:00 UTC+1 schrieb Thomas Broyer: On Friday, December 7, 2012 9:45:19 AM UTC+1, kim young ill wrote: Hi there, i start using this for gwt-modular webapp, quite great, Thanks but now i put a second gwt-module in the client package, how to configure the pom file so that both are avail. in -Ddev ? You'll have to replace the module with modules in the gwt-maven-plugin configuration, and add the modules as module child elements. You'd probably want to introduce another property in addition to gwt.module. Note that I made this dev profile only to make it easier to start up, but I highly recommend you to launch the DevMode from your IDE. gwt:run is far from ideal in this multi-module setup. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit 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 http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: gwt-maven-archetypes with multiple client modules
Thanks for your reply, and thanks for the info! Have a working debug-able environment now! With this Debug As… → Web Application (running on an external server) on the client project, I get the error Could not find any host-pages in project name-client My setup is generated by your maven archetype modular-webapp and nearly no changes, only played around with debug configurations and maven a little bit. But based on your other info I've managed to create a Web Application debug configuration manually, and it works! Huge thanks again! (also for creating these archetypes) Am Mittwoch, 22. Mai 2013 12:44:04 UTC+2 schrieb Thomas Broyer: On Wednesday, May 22, 2013 12:09:44 PM UTC+2, Thomas Käfer wrote: how to launch the DevMode from within eclipse on a setup with seperate client server project like your maven-archetype modular-webapp, without using maven? I'm trying to find this already for a few weeks, but I did not find a solution yet. Problem with the maven gwt:run launch is, that the client-side code isn't debug-able that way -- only server-side with the tomcat7-run can be debugged that way.. Yes it is; far from ideal, but it's possible: use gwt:debug instead of gwt:run, and then attach a debugger to the process; see http://mojo.codehaus.org/gwt-maven-plugin/debug-mojo.html I've tried to create an eclipse run configuration analog to my single-project setups, but nothing worked so far... It should be as easy as Debug As… → Web Application (running on an external server) and using http://localhost:8080/ as the External server root and unchecking Select an HTML page; assuming you run Tomcat with mvn tomcat7:run (or any other setup such that it serves both myapp-client/target/myapp-client-1.0.0-SNAPSHOT and myapp-server/target/myapp-server-1.0.0-SNAPSHOT in the webapp; otherwise just go edit the launch configuration and change the -war to point to the myapp-server/target/myapp-server-1.0.0-SNAPSHOT) -- You received this message because you are subscribed to the Google Groups Google Web Toolkit 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 http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Re: Help getting super dev mode to work
Did I understand the procedure correctly? 1.) add those properties to your Application.gwt.xml file 2.) run the super dev mode, wait until compiled and The code server is ready. Next, visit: http://localhost:9876/; is showing 3.) run the normal dev mode 4.) browse http://127.0.0.1:/Application.html?gwt.codesvr=127.0.0.1:9997 and press the bookmarklet Dev Mode On -- this procedure gives me Can't find any GWT Modules on this page. Best Regards, Thomas. Am Sonntag, 17. Juni 2012 16:57:48 UTC+2 schrieb Daniel Kurka: I can`t seem to get super dev mode to work. I am always Can't find any GWT Modules on this page., due to window.__gwt_activeModules being undefined. The super dev mode code server compiled fine. I have got the bookmarklets. I compiled my GWT app the standard way and I am able to run it in the browser, but still window.__gwt_activeModules is undefined. What am I missing? Who is supposted to set that variable? -Daniel -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
Re: GWT compiler doesn't create symbol maps files
thanks for posting this, I was just having the same problem! On 23 Okt., 16:03, Alexander azi...@gmail.com wrote: A miracle happened, I found the reason. inherits name=com.google.gwt.junit.JUnit/ I don't even know how much time I have spent. On Oct 23, 6:13 pm, Alexander azi...@gmail.com wrote: Hello. GWT compiler doesn't create directory symbolMaps deploy. Already for a long time I'm trying to solve this problem. Every time I spend on it about a day without results. Folder rpcPolicyManifest created in WEB-INF/deploy folder, but symbolMaps not. I tried to compile and through gwt-maven-plugin and directly through com.google.gwt.dev.Compiler, with custom -deploy. Many people asks how to disable generation of this files but seems that nobody has same problem. Except one guy:http://stackoverflow.com/questions/7504644/gwt-compiler-doesnt-create... But he has no answer too. GWT version 2.4.0. On 2.3.0 I have same result. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
