Re: GWT project with maven
cannot believe you know know this yet: https://github.com/tbroyer/gwt-maven-archetypes On Thu, May 23, 2013 at 5:36 AM, Navin Surtani navssurt...@gmail.comwrote: Take a look here for source code for the basic HelloWorld example: https://github.com/steinsag/gwt-maven-example I used that as an example to follow while building my application. On Thursday, May 23, 2013 7:32:35 AM UTC+8, Srinivasa Rao wrote: Hi , I am looking for the GWT project with the maven setup. Can you please provide me the link for the sample project ? -- 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. -- 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.
asm.js
Have a quick read through this article if you don't know what asm.js is: http://arstechnica.com/information-technology/2013/05/native-level-performance-on-the-web-a-brief-examination-of-asm-js/ With firefox already supporting it, GWT should have the firefox compile target target asm.js for, at least, things like ArrayList. I didn't see anything about it in the recent I/O talk - has anybody looked at how difficult it would be to support in the GWT compiler ? Ryan -- 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: Exception reporting is broken in GWT: would you support a kickstarter project to fix it?
On Wednesday, May 22, 2013 11:53:47 PM UTC+2, Alex Epshteyn wrote: Thanks for your comment. Let me respond to your points: 1) I've seen this point discussed before, and the standard counter-argument is that the spirit of OSS is free as in freedom, not beer. Lots of developers get paid to work on OSS projects. 2) This is actually one of the reasons I'm thinking about raising funds. I am already on the verge of using my patch inside my own GWT-based app, but if I get some funding I'd be able to justify taking the extra time to make sure the patch will pass the review process. +1 to those 2 points. 3) I must point out that your third argument is not in the spirit of GWT, which aims to support as many browsers as possible. That's not entirely true. GWT only ever supported the 4 major browser engines: Trident (IE), WebKit (SquirrelFish / V8; aka Safari / Chromium), Gecko (Firefox) and Presto (Opera). Jens is right: we'll soon remove support for IE6 and 7, and then for IE8 (not long after MS drops support for WinXP). GWT never really supported Opera, and the level of support was only against the latest version. Now that Opera is moving from Presto to Chromium, that means one less platform to support in the very near future (by the next GWT release, but we'll probably keep the opera permutation along for one more release). As of today, you will not get good stack traces with GWT on any modern browser, including WebKit. By relevant information, I assume you mean sourcemaps support. Well, Chrome is the only browser that currently supports sourcemaps but GWT's existing support for generating stack traces with that information is very buggy, and this is one of the things I'm working on improving. I'm also not optimistic that sourcemaps will achieve universal support any time soon, if ever. Chromium has it for a while (hence Chrome –all platforms–, Opera for Android –though what matters is the remote debugger, not the browser– and Opera.next), and Firefox is starting to roll it out [1,2] in 23 (currently Aurora channel) and I'm told the next Safari should have it too [3]. Will IE ever have it? I believe so, particularly now that MS is pushing languages that compile to JS (TypeScript, which can generate sourcemaps). Obviously that would only be available in IE11 (or later), but it seems like it would be possible to have support in your IDE with the help of an IE plugin [4] for IE8/9/10 (would it work in Windows 8 though?) That said, source maps support in the browser is related to, but different from stack trace resymbolization. [1] https://hacks.mozilla.org/2013/05/firefox-developer-tool-features-for-firefox-23/ [2] https://hacks.mozilla.org/2013/05/compiling-to-javascript-and-debugging-with-source-maps/ [3] http://stackoverflow.com/questions/16446114/is-it-possible-to-enable-javascript-source-maps-in-safari-6 [4] http://wiki.eclipse.org/JSDT/Debug/IE -- 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: JPA issue: A parent cannot be established or changed once an object has been persisted.
Dear Juan, For this purpose I use the GWT-s Request Factory. However, in order to simplify the problem, I have created a server side persistence example using a simple servlet where one company and two users are created. Please have a look at the MyTestServlet.java within the Zip File. https://dl.dropboxusercontent.com/u/2983671/JPA_Problem/JPA_Problem.zip The funny thing is, I get now a different Eror: javax.persistence.PersistenceException: Illegal argument Caused by: java.lang.IllegalArgumentException: cross-group transaction need to be explicitly specified, see TransactionOptions.Builder.withXGfound both Element { type: Tradesman id: 361 } and Element { type: Tradesman id: 362 } When I remove the @PrePersit from User class it works just fine! The Error pops up as soon as i modify a parameter on Tradesman entity (more exactly on its parent class User). I really do not understand this behavior. ... I also must admit that I am not very advanced in JPA. Thank you for very much for your help. Best regards: Nermin Am Mittwoch, 22. Mai 2013 15:28:50 UTC+2 schrieb Juan Pablo Gardella: Show how you are persisting the entities. 2013/5/22 Nermin use...@gmx.de javascript: Dear Alfredo and Juan, obviously there is an hidden problem with my code i simply do not see. Could you please have a short look at these 3 classes (full code) and tell me what am I doing wrong here: https://dl.dropboxusercontent.com/u/2983671/JPA_Problem/JPA_Problem.zip Please note: Everything works fine as log as I do not try to make any changes to the Tradesman entity (its parameters). When is set new password or any other parameter, i get an error message of type: Detected attempt to establish Company(no-id-yet) as the parent of Tradesman(358) but the entity identified by Tradesman(358) has already been persisted without a parent. A parent cannot be established or changed once an object has been persisted. I am using: JPA with DataNucleus on Google Datastore. (Standard setting that come with GWT 2.5) Thank you in advance for your help!! Best regards: Nermin Am Dienstag, 21. Mai 2013 18:29:54 UTC+2 schrieb Alfredo Quiroga-Villamil: Or use a cascade persist, merge to force creation or merge respectively Sent from my iPhone On May 21, 2013, at 7:02 AM, Juan Pablo Gardella gardella...@gmail.com wrote: You should persist company before persist Tradesman or attach to an existent company. This relation should be explicit. Create company.addTrademan(Trademan t) method: company.addTrademan(Trademan t){ users.add(t); t.setCompany(this); } Call this in a transactional method. Juan 2013/5/21 Nermin use...@gmx.de Dear Juan, I tried *@ManyToOne(optional=false)*, unfortunately no changes. In my current setting, the @PrePersist is called only once. (I see it on system out) That means: no multiple attempts to persist Tradesman entity. However, it looks to me that whenever I change parameters on the Tradesman entity JPA creates/persists for some reason the Tradesman in the DB, independently from the Company entity. I use Standard GWT settings: GWT 2.5, DataNucleus on Appengine Datastore. The scenario I am describing here is a standard scenario you will face when using GWT with JPA. I am surprised that my code is not working. @PrePersist works fine as long as the Entity is not in a owned relation with other entities. Does anyone has an idea what could be wrong here? Thank you!! Nermin @Thomas: Thank you for the advise. I will Am Dienstag, 21. Mai 2013 12:01:43 UTC+2 schrieb Juan Pablo Gardella: Update your entity as: @Entity public class Tradesman extends User{ @ManyToOne(optional=false) private Company company; *@PrePersist* public void hashPassword(){ setPassword(BCrypt.hashpw(**entity.getPassword(), BCrypt.gensalt()); } And then check where are you persisting Tradesman without company. 2013/5/21 Thomas Broyer t.br...@gmail.com On Tuesday, May 21, 2013 11:18:42 AM UTC+2, Nermin wrote: Dear GWT developers, I have a probably simple problem with my application which I am obviously not able to solve. Two Classes: Company, Tradesman @Entity public class Company { @OneToMany(cascade = CascadeType.ALL, mappedBy = company) private ListTradesman users = new ArrayListTradesman(); } @Entity public class Tradesman extends User{ @ManyToOne private Company company; *@PrePersist* public void hashPassword(){ setPassword(BCrypt.hashpw(**entity.getPassword(), BCrypt.gensalt()); } *JSR 303 validation on GWT is activated.* Here is the *error message: *Detected attempt to establish Company(no-id-yet) as the parent of Tradesman(356) but the entity identified by Tradesman(356) has already been persisted without a parent. A parent cannot be established or changed once an object has been persisted.
Re: JPA issue: A parent cannot be established or changed once an object has been persisted.
In the loop, do user.setCompany(company). You need a transaction. Create it and do the commit. 2013/5/23 Nermin user...@gmx.de Dear Juan, For this purpose I use the GWT-s Request Factory. However, in order to simplify the problem, I have created a server side persistence example using a simple servlet where one company and two users are created. Please have a look at the MyTestServlet.java within the Zip File. https://dl.dropboxusercontent.**com/u/2983671/JPA_Problem/JPA_** Problem.ziphttps://dl.dropboxusercontent.com/u/2983671/JPA_Problem/JPA_Problem.zip The funny thing is, I get now a different Eror: javax.persistence.PersistenceException: Illegal argument Caused by: java.lang.IllegalArgumentException: cross-group transaction need to be explicitly specified, see TransactionOptions.Builder.withXGfound both Element { type: Tradesman id: 361 } and Element { type: Tradesman id: 362 } When I remove the @PrePersit from User class it works just fine! The Error pops up as soon as i modify a parameter on Tradesman entity (more exactly on its parent class User). I really do not understand this behavior. ... I also must admit that I am not very advanced in JPA. Thank you for very much for your help. Best regards: Nermin Am Mittwoch, 22. Mai 2013 15:28:50 UTC+2 schrieb Juan Pablo Gardella: Show how you are persisting the entities. 2013/5/22 Nermin use...@gmx.de Dear Alfredo and Juan, obviously there is an hidden problem with my code i simply do not see. Could you please have a short look at these 3 classes (full code) and tell me what am I doing wrong here: https://dl.dropboxusercontent.**com/u/2983671/JPA_Problem/JPA_** Problem.ziphttps://dl.dropboxusercontent.com/u/2983671/JPA_Problem/JPA_Problem.zip Please note: Everything works fine as log as I do not try to make any changes to the Tradesman entity (its parameters). When is set new password or any other parameter, i get an error message of type: Detected attempt to establish Company(no-id-yet) as the parent of Tradesman(358) but the entity identified by Tradesman(358) has already been persisted without a parent. A parent cannot be established or changed once an object has been persisted. I am using: JPA with DataNucleus on Google Datastore. (Standard setting that come with GWT 2.5) Thank you in advance for your help!! Best regards: Nermin Am Dienstag, 21. Mai 2013 18:29:54 UTC+2 schrieb Alfredo Quiroga-Villamil: Or use a cascade persist, merge to force creation or merge respectively Sent from my iPhone On May 21, 2013, at 7:02 AM, Juan Pablo Gardella gardella...@gmail.com wrote: You should persist company before persist Tradesman or attach to an existent company. This relation should be explicit. Create company.addTrademan(Trademan t) method: company.addTrademan(Trademan t){ users.add(t); t.setCompany(this); } Call this in a transactional method. Juan 2013/5/21 Nermin use...@gmx.de Dear Juan, I tried *@ManyToOne(optional=false)*, unfortunately no changes. In my current setting, the @PrePersist is called only once. (I see it on system out) That means: no multiple attempts to persist Tradesman entity. However, it looks to me that whenever I change parameters on the Tradesman entity JPA creates/persists for some reason the Tradesman in the DB, independently from the Company entity. I use Standard GWT settings: GWT 2.5, DataNucleus on Appengine Datastore. The scenario I am describing here is a standard scenario you will face when using GWT with JPA. I am surprised that my code is not working. @PrePersist works fine as long as the Entity is not in a owned relation with other entities. Does anyone has an idea what could be wrong here? Thank you!! Nermin @Thomas: Thank you for the advise. I will Am Dienstag, 21. Mai 2013 12:01:43 UTC+2 schrieb Juan Pablo Gardella: Update your entity as: @Entity public class Tradesman extends User{ @ManyToOne(optional=false) private Company company; *@PrePersist* public void hashPassword(){ setPassword(BCrypt.hashpw(**enti**ty.getPassword(), BCrypt.gensalt()); } And then check where are you persisting Tradesman without company. 2013/5/21 Thomas Broyer t.br...@gmail.com On Tuesday, May 21, 2013 11:18:42 AM UTC+2, Nermin wrote: Dear GWT developers, I have a probably simple problem with my application which I am obviously not able to solve. Two Classes: Company, Tradesman @Entity public class Company { @OneToMany(cascade = CascadeType.ALL, mappedBy = company) private ListTradesman users = new ArrayListTradesman(); } @Entity public class Tradesman extends User{ @ManyToOne private Company company; *@PrePersist* public void hashPassword(){ setPassword(BCrypt.hashpw(**enti**ty.getPassword(), BCrypt.gensalt()); } *JSR 303 validation on GWT is activated.* Here is the
Re: GWT RPC Serialization on web and app server
Awesome!! Thanks. I was having problems with a jmeter test and I saw your solution...it's really that! The jmeter captured request had the reference to the hash for another deployed environment and when trying to test against another deployed war it was throwing the serializable error. Now I know how to fix it :)... El jueves, 1 de noviembre de 2012 10:27:54 UTC+1, Jens escribió: Make sure that your app server can still find the HASH.rpc file. Thats your GWT-RPC serialization policy file that the server must know in order to serialize anything that implements Serializable. If it does not find this file it falls back to the old IsSerializable mechanism and if you do not have implemented that interface serialization will fail. Normally you should see a warning in the app server log on the first RPC request when GWT's RemoteServiceServlet tries to load the serialization policy file but can not find it. For example I often have to change the lookup of that file because my deployment does not conform to GWT's standard assumptions. -- J. -- 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
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
On Thursday, May 23, 2013 12:48:50 PM UTC+2, Thomas Käfer wrote: 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? 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. -- 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.
Retrieving and manupulating search result from gwtsearch
Please, is there anyway to manipulate the search result from the gwtsearch option. It returns a list. How can i retrieve this list and make my manipulations on the list; maybe change the order the contents appear, e.t.c. The SearchContolOptions class does not have any method like getSearchList(). As a matter of fact, the results are contained in a final List variable. Thank you. -- 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: primer for mobile development
Of course you can use ADT and spin up the environment, I use ANDROVMhttp://androvm.org because it loads a whole lot faster than ADT. On Wed, May 22, 2013 at 11:33 PM, mike b mbaker.t...@gmail.com wrote: Nino , thx for the links. I will look into those. -- 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. -- 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: JPA issue: A parent cannot be established or changed once an object has been persisted.
When I try to do that, I get a following error: java.lang.NullPointerException at com.google.appengine.datanucleus.StoreFieldManager.storeRelations(StoreFieldManager.java:848) at com.google.appengine.datanucleus.DatastorePersistenceHandler.insertObjectsInternal(DatastorePersistenceHandler.java:367) at com.google.appengine.datanucleus.DatastorePersistenceHandler.insertObject(DatastorePersistenceHandler.java:218) at org.datanucleus.state.JDOStateManager.internalMakePersistent(JDOStateManager.java:2377) at org.datanucleus.state.JDOStateManager.flush(JDOStateManager.java:3769) at org.datanucleus.state.JDOStateManager.getExternalObjectId(JDOStateManager.java:1088) at org.datanucleus.state.JDOStateManager.getObjectId(JDOStateManager.java:958) at com.emajstor.server.persistence.Company.jdoGetObjectId(Company.java) at org.datanucleus.api.jpa.JPAAdapter.getIdForObject(JPAAdapter.java:272) at com.google.appengine.datanucleus.EntityUtils.getKeyForObject(EntityUtils.java:245) at com.google.appengine.datanucleus.EntityUtils.getParentKey(EntityUtils.java:853) at com.google.appengine.datanucleus.StoreFieldManager.establishEntityGroup(StoreFieldManager.java:939) at com.google.appengine.datanucleus.DatastorePersistenceHandler.insertObjectsInternal(DatastorePersistenceHandler.java:244) at com.google.appengine.datanucleus.DatastorePersistenceHandler.insertObject(DatastorePersistenceHandler.java:218) at org.datanucleus.state.JDOStateManager.internalMakePersistent(JDOStateManager.java:2377) at org.datanucleus.state.JDOStateManager.flush(JDOStateManager.java:3769) at org.datanucleus.ObjectManagerImpl.flushInternalWithOrdering(ObjectManagerImpl.java:3884) at org.datanucleus.ObjectManagerImpl.flushInternal(ObjectManagerImpl.java:3807) at org.datanucleus.ObjectManagerImpl.flush(ObjectManagerImpl.java:3747) at org.datanucleus.ObjectManagerImpl.preCommit(ObjectManagerImpl.java:4137) at org.datanucleus.ObjectManagerImpl.transactionPreCommit(ObjectManagerImpl.java:428) at org.datanucleus.TransactionImpl.internalPreCommit(TransactionImpl.java:400) at org.datanucleus.TransactionImpl.commit(TransactionImpl.java:288) at org.datanucleus.ObjectManagerImpl.close(ObjectManagerImpl.java:1090) at org.datanucleus.api.jpa.JPAEntityManager.close(JPAEntityManager.java:193) at com.emajstor.server.persistence.Company.persist(Company.java:110) at com.emajstor.server.test.MyTestServlet.testPersistenceOne(MyTestServlet.java:74) at com.emajstor.server.test.MyTestServlet.doGet(MyTestServlet.java:39) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166) at com.google.appengine.api.socket.dev.DevSocketFilter.doFilter(DevSocketFilter.java:74) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at com.google.appengine.tools.development.ResponseRewriterFilter.doFilter(ResponseRewriterFilter.java:123) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at com.google.appengine.tools.development.HeaderVerificationFilter.doFilter(HeaderVerificationFilter.java:34) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at com.google.appengine.api.blobstore.dev.ServeBlobFilter.doFilter(ServeBlobFilter.java:61) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:43) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at com.google.appengine.tools.development.StaticFileFilter.doFilter(StaticFileFilter.java:125) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at com.google.appengine.tools.development.BackendServersFilter.doFilter(BackendServersFilter.java:97) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418) at
Re: primer for mobile development
Here is a playlist of mobile web videos form Google IO 2013: http://www.youtube.com/watch?v=EPYnGFEcis4list=PLAbrfaVBC6kWiNBI1wPYhXtTke64QkLqC -- 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: asm.js
On Thursday, May 23, 2013 9:52:00 AM UTC+2, RyanZA wrote: Have a quick read through this article if you don't know what asm.js is: http://arstechnica.com/information-technology/2013/05/native-level-performance-on-the-web-a-brief-examination-of-asm-js/ With firefox already supporting it, GWT should have the firefox compile target target asm.js for, at least, things like ArrayList. I didn't see anything about it in the recent I/O talk - has anybody looked at how difficult it would be to support in the GWT compiler ? Copied from Ray Cromwell's comment on https://plus.google.com/107037260910017774154/posts/179TxALiF5v: Well, GWT assumes garbage collection semantics, and ASM.JS assumes typed arrays for everything and malloc/free semantics. So it wouldn't hard to support asm.js, but we'd end up memory leaking like crazy unless we implemented a mark/sweep collector in JS :) -- 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: asm.js
My understanding is that asm.js is all or nothing. It is designed as a target for languages that manage their own memory (that is generally not garbage collected, but you could implement garbage collection in such a system). Firefox looks at the JavaScript and decides if it is asm.js, then switches to another JavaScript interpreter that is optimized for asm.js. If this interpreter detects anything outside of the asm.js subset, it kicks all execution back to the standard interpreter. This means you can't pick part of a gwt compile to target asm.js; it would be all on none. Ed On Thursday, May 23, 2013 12:52:00 AM UTC-7, RyanZA wrote: Have a quick read through this article if you don't know what asm.js is: http://arstechnica.com/information-technology/2013/05/native-level-performance-on-the-web-a-brief-examination-of-asm-js/ With firefox already supporting it, GWT should have the firefox compile target target asm.js for, at least, things like ArrayList. I didn't see anything about it in the recent I/O talk - has anybody looked at how difficult it would be to support in the GWT compiler ? Ryan -- 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: Offline debugging my gwt app
Yves, I would try SuperDev mode and debug using Chrome Dev Tools and the source maps produced by the super dev mode code server. You don't need any special changes to your project, you just need to create a way to launch the super dev mode code server. This is documented at gwtproject.org.herehttp://www.gwtproject.org/articles/superdevmode.html. Here http://lumpofcode.blogspot.com/2012/11/configuring-gwt-codeserver-and.html?view=mosaicis a blog post I wrote with detailed instructions. Ed On Monday, May 20, 2013 11:46:08 AM UTC-7, yves wrote: Hello All, I need to debug my gwt app. The problem is that I need to debug it OFFLINE. After a tour on the net, I didn't found an answer. Thus here is the scenario. My GWT version is 2.4.0 Debugging the code is ok. Running in production offline is ok, using a cache manifest. But I can't do both : debugging offline. To avoid any config difference, I use exactly the same tomcat server deployment to run in production or in debug mode (thus with the debug option -noserver). The cache manifest is built in runtime by a dedicated service whose response depends on the current permutation. When online, the manifest is always requested in debug and in production mode (confirmed by tracing). (a subsidiary question is : why in production the manifest is called twice and in debug it is called once ?). Then I stopped tomcat. = In production offline the gwt app is running correctly. = In debug offline, nothing is displayed : the browser has loaded the app html file from its cache (confirmed by displaying the page source code), but the browser remains empty, the gwt app is not running. It seems that when offline, the google dev plugin doesn't communicate correctly with the IDE as it even doesn't realize when the development mode is stopped in the IDE (the black overlay with the message Plugin failed to connect to Development Mode server at localhost:9997 is no displayed). May be the plugin is not started when offline ? In order to help me test my app when offline, does anybody knows why the app is not running in debug offline mode and how to make it run ? Thanks a lot ! Yves -- 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.
Does GWT will work on mobile for drag and drop
https://lh6.googleusercontent.com/-csi4PNV5B2Q/UZ5nyHSHG2I/AE8/5cChr0YvGpM/s1600/Untitled.jpg Currently i am working on a project in which i have to make UI with drag and drop feature, but problem is i would like work it on android mobile. Please suggest some resource and idea. Here is screen shot of intented UI. -- 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: Exception reporting is broken in GWT: would you support a kickstarter project to fix it?
Hi Thomas, Thanks for chiming in and providing the extra info. Good to know. I'd like to ask, however, the reasons for planning to remove support for IE6/7/8? Why would we do that? It's already there and doesn't require too much maintenance. As of today, nearly 8% of my site's visitors are on IE8 and close to 1% are still on IE7. These are pretty big numbers for a high traffic website, and would translate into lost revenue if the browsers weren't supported. I can't imagine Google pulling support for a browser with that kind of usage for one of its products. . Here's the full data: https://docs.google.com/spreadsheet/ccc?key=0AvMlWdpkpAA6dGdpa3lsZTVQWl9qcFJrWmZCZ0ZZb0E#gid=0 Also, as you guys can see from the data, stack emulation is still required for 54% of my site's traffic. While I'd like to see users upgrading to the latest browsers as much as any developer, let's be realistic: WinXP is not going away any time soon (Microsoft dropping support for it isn't going to make people like my dad go out and buy a new computer). Google Analytics is shows that 80% of my users are on Windows and 21% of those are still on Windows XP: that is a very big number! On Thu, May 23, 2013 at 5:13 AM, Thomas Broyer t.bro...@gmail.com wrote: On Wednesday, May 22, 2013 11:53:47 PM UTC+2, Alex Epshteyn wrote: Thanks for your comment. Let me respond to your points: 1) I've seen this point discussed before, and the standard counter-argument is that the spirit of OSS is free as in freedom, not beer. Lots of developers get paid to work on OSS projects. 2) This is actually one of the reasons I'm thinking about raising funds. I am already on the verge of using my patch inside my own GWT-based app, but if I get some funding I'd be able to justify taking the extra time to make sure the patch will pass the review process. +1 to those 2 points. 3) I must point out that your third argument is not in the spirit of GWT, which aims to support as many browsers as possible. That's not entirely true. GWT only ever supported the 4 major browser engines: Trident (IE), WebKit (SquirrelFish / V8; aka Safari / Chromium), Gecko (Firefox) and Presto (Opera). Jens is right: we'll soon remove support for IE6 and 7, and then for IE8 (not long after MS drops support for WinXP). GWT never really supported Opera, and the level of support was only against the latest version. Now that Opera is moving from Presto to Chromium, that means one less platform to support in the very near future (by the next GWT release, but we'll probably keep the opera permutation along for one more release). As of today, you will not get good stack traces with GWT on any modern browser, including WebKit. By relevant information, I assume you mean sourcemaps support. Well, Chrome is the only browser that currently supports sourcemaps but GWT's existing support for generating stack traces with that information is very buggy, and this is one of the things I'm working on improving. I'm also not optimistic that sourcemaps will achieve universal support any time soon, if ever. Chromium has it for a while (hence Chrome –all platforms–, Opera for Android –though what matters is the remote debugger, not the browser– and Opera.next), and Firefox is starting to roll it out [1,2] in 23 (currently Aurora channel) and I'm told the next Safari should have it too [3]. Will IE ever have it? I believe so, particularly now that MS is pushing languages that compile to JS (TypeScript, which can generate sourcemaps). Obviously that would only be available in IE11 (or later), but it seems like it would be possible to have support in your IDE with the help of an IE plugin [4] for IE8/9/10 (would it work in Windows 8 though?) That said, source maps support in the browser is related to, but different from stack trace resymbolization. [1] https://hacks.mozilla.org/2013/05/firefox-developer-tool-features-for-firefox-23/ [2] https://hacks.mozilla.org/2013/05/compiling-to-javascript-and-debugging-with-source-maps/ [3] http://stackoverflow.com/questions/16446114/is-it-possible-to-enable-javascript-source-maps-in-safari-6 [4] http://wiki.eclipse.org/JSDT/Debug/IE -- You received this message because you are subscribed to a topic in the Google Groups Google Web Toolkit group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/hP8cQ7AdDUc/unsubscribe?hl=en . 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 http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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
Re: Exception reporting is broken in GWT: would you support a kickstarter project to fix it?
I agree on do not remove IE7 and IE8. A lot of user still using them. 2013/5/23 Alex Epshteyn alexander.epsht...@gmail.com Hi Thomas, Thanks for chiming in and providing the extra info. Good to know. I'd like to ask, however, the reasons for planning to remove support for IE6/7/8? Why would we do that? It's already there and doesn't require too much maintenance. As of today, nearly 8% of my site's visitors are on IE8 and close to 1% are still on IE7. These are pretty big numbers for a high traffic website, and would translate into lost revenue if the browsers weren't supported. I can't imagine Google pulling support for a browser with that kind of usage for one of its products. . Here's the full data: https://docs.google.com/spreadsheet/ccc?key=0AvMlWdpkpAA6dGdpa3lsZTVQWl9qcFJrWmZCZ0ZZb0E#gid=0 Also, as you guys can see from the data, stack emulation is still required for 54% of my site's traffic. While I'd like to see users upgrading to the latest browsers as much as any developer, let's be realistic: WinXP is not going away any time soon (Microsoft dropping support for it isn't going to make people like my dad go out and buy a new computer). Google Analytics is shows that 80% of my users are on Windows and 21% of those are still on Windows XP: that is a very big number! On Thu, May 23, 2013 at 5:13 AM, Thomas Broyer t.bro...@gmail.com wrote: On Wednesday, May 22, 2013 11:53:47 PM UTC+2, Alex Epshteyn wrote: Thanks for your comment. Let me respond to your points: 1) I've seen this point discussed before, and the standard counter-argument is that the spirit of OSS is free as in freedom, not beer. Lots of developers get paid to work on OSS projects. 2) This is actually one of the reasons I'm thinking about raising funds. I am already on the verge of using my patch inside my own GWT-based app, but if I get some funding I'd be able to justify taking the extra time to make sure the patch will pass the review process. +1 to those 2 points. 3) I must point out that your third argument is not in the spirit of GWT, which aims to support as many browsers as possible. That's not entirely true. GWT only ever supported the 4 major browser engines: Trident (IE), WebKit (SquirrelFish / V8; aka Safari / Chromium), Gecko (Firefox) and Presto (Opera). Jens is right: we'll soon remove support for IE6 and 7, and then for IE8 (not long after MS drops support for WinXP). GWT never really supported Opera, and the level of support was only against the latest version. Now that Opera is moving from Presto to Chromium, that means one less platform to support in the very near future (by the next GWT release, but we'll probably keep the opera permutation along for one more release). As of today, you will not get good stack traces with GWT on any modern browser, including WebKit. By relevant information, I assume you mean sourcemaps support. Well, Chrome is the only browser that currently supports sourcemaps but GWT's existing support for generating stack traces with that information is very buggy, and this is one of the things I'm working on improving. I'm also not optimistic that sourcemaps will achieve universal support any time soon, if ever. Chromium has it for a while (hence Chrome –all platforms–, Opera for Android –though what matters is the remote debugger, not the browser– and Opera.next), and Firefox is starting to roll it out [1,2] in 23 (currently Aurora channel) and I'm told the next Safari should have it too [3]. Will IE ever have it? I believe so, particularly now that MS is pushing languages that compile to JS (TypeScript, which can generate sourcemaps). Obviously that would only be available in IE11 (or later), but it seems like it would be possible to have support in your IDE with the help of an IE plugin [4] for IE8/9/10 (would it work in Windows 8 though?) That said, source maps support in the browser is related to, but different from stack trace resymbolization. [1] https://hacks.mozilla.org/2013/05/firefox-developer-tool-features-for-firefox-23/ [2] https://hacks.mozilla.org/2013/05/compiling-to-javascript-and-debugging-with-source-maps/ [3] http://stackoverflow.com/questions/16446114/is-it-possible-to-enable-javascript-source-maps-in-safari-6 [4] http://wiki.eclipse.org/JSDT/Debug/IE -- You received this message because you are subscribed to a topic in the Google Groups Google Web Toolkit group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/hP8cQ7AdDUc/unsubscribe?hl=en . 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 http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because
Re: Exception reporting is broken in GWT: would you support a kickstarter project to fix it?
I'd like to ask, however, the reasons for planning to remove support for IE6/7/8? Why would we do that? To simplify the code base and moving on (HTML 5) I would say. JQuery for example already did that transition. JQuery 2.0 does not support IE6-8 anymore but they still maintain JQuery 1.9.x for people that still need IE6-8 browser support. In terms of GWT you can still use the last version that supports IE6-8 and then decide yourself when its time to move to a newer GWT version for your site. -- J. -- 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: Exception reporting is broken in GWT: would you support a kickstarter project to fix it?
Fair enough, but I'm curious to know why leaving the code that supports legacy browsers would interfere with implementing new features. For example, if you want to implement a new widget called XPanel, it think it's perfectly fine to say that this widget doesn't support IE6/7/8, and leave it up to userland to chose whether to use the new widget and how to work around it for new browsers. Do you have a specific example? I'm curious. On Thu, May 23, 2013 at 5:54 PM, Jens jens.nehlme...@gmail.com wrote: To simplify the code base and moving on (HTML 5) I would say. -- 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: Spring Security and Google App Engine
I'm having the same issue with my GWT web application. issue still happens with the default GWT GAE sample project and basic spring security setup. http auto-config=true intercept-url pattern=/** access=ROLE_USER / /http Has anyone else experienced this kind of issue? or has found a work around? On Wednesday, November 28, 2012 4:09:14 PM UTC-6, Ronnie Schaniel wrote: I'm working on Spring Security implementation for a few days now. The login form is displayed if I integrate spring security in a sample project. When I enable the Google App Engine in the eclipse project settings the redirect to the login form is not working anymore, so I can not secure the EntryPoint. If I have a single service on a specific URL which is not using RPC calls the spring security works well. On the part of the application that uses RPC the login form is not rendered correctly and an exception is thrown. So most likely the rpc service is the source of the problem. In addition my Spring Security configuration: ?xml version=1.0 encoding=UTF-8? beans:beans xmlns=http://www.springframework.org/schema/security; xmlns:beans=http://www.springframework.org/schema/beans; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd http://www.springframework.org/schema/security http://www.springframework.org/schema/security/spring-security-3.0.xsd; http auto-config=true intercept-url pattern=/login.html* access=IS_AUTHENTICATED_ANONYMOUSLY / intercept-url pattern=/*.css access=IS_AUTHENTICATED_ANONYMOUSLY / intercept-url pattern=/economapp/** access=ROLE_USER / intercept-url pattern=/gwt/** access=ROLE_USER/ intercept-url pattern=/**/*.html access=ROLE_USER/ intercept-url pattern=/*.html access=ROLE_USER / intercept-url pattern=/** access=IS_AUTHENTICATED_ANONYMOUSLY / /http !-- beans:bean id=customEntryPoint class=com.nfl.economapp.security.CustomAuthenticationEntryPoint / -- beans:bean id=customAuthenticationProvider class=com.nfl.economapp.security.CustomAuthenticationProvider / authentication-manager alias=authenticationManager authentication-provider ref=customAuthenticationProvider / /authentication-manager /beans:beans Does anyone have an idea how to solve this? Or should I try Apache Shiro as an alternative? -- 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.
Google Apps Dev With GWT
Hello guys. I know there is Google App Script, but it runs online and it is JavaScript sort of. Is it possible to develop GWT apps that can integrate with Google Apps (Gmail, Spreadsheets e.t.c). -- 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: Exception reporting is broken in GWT: would you support a kickstarter project to fix it?
Do you have a specific example? I'm curious. Existing widgets should also work great on mobile devices, its not just about writing new widgets. Its also not just about widgets in general. For example there is currently an issue in GWT-RPC where only IE9 has a memory leak because GWT-RPC uses eval() to parse the server response and IE9 keeps everything eval'd in memory. Slightly changing the server code and switching to JSON.parse() on the client would solve the problem, but IE6/7 do not support JSON.parse(). So to fix this issue for IE9 the server serialization needs to figure out which IE version is talking to the server and then generate different responses (either JS or JSON). Targeting different browsers on client side is easy (deferred binding) but this time the server must target different browser versions as well. So its more complicated than it could be. https://code.google.com/p/google-web-toolkit/issues/detail?id=5736 https://gwt-review.googlesource.com/#/c/2900/ I think thats a good example where IE6/7 support costs more development resources although you know that IE6/7 doesn't really play a big role anymore. Microsoft recommends to not use them anymore and 2014 they will stop supporting IE6-8 as Windows XP extended support ends in April 2014. So would you invest a lot of work today in supporting browsers whose support officially ends in less than a year? Probably not. Its a good time now to slowly phasing out IE6/7 and later IE 8 support. -- J. -- 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: How to mark a field as completely hidden for smartgwt ListGrid?
setCanHide(flase) didn't work for me... I had to set the height of the field as 0. field.setWidth(0); On Wednesday, January 4, 2012 5:04:23 AM UTC-5, Daniel wrote: Hi guys, How to mark a field as completely hidden for smartgwt ListGrid? I do listGridFields[i].setHidden(true) according to API,But it still could be able to show the field via a context menu. and the API said 'canPickFields' has been set false can solve this problem,but where the canPickFields ? Thank you Best Regards Daniel -- 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: How to mark a field as completely hidden for smartgwt ListGrid?
actullally, listGrid.hideField(my_field); worked too, but I had to make sure this was set AFTER the field was added and its values set. On Wednesday, January 4, 2012 5:04:23 AM UTC-5, Daniel wrote: Hi guys, How to mark a field as completely hidden for smartgwt ListGrid? I do listGridFields[i].setHidden(true) according to API,But it still could be able to show the field via a context menu. and the API said 'canPickFields' has been set false can solve this problem,but where the canPickFields ? Thank you Best Regards Daniel -- 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: How to override gwt styles in uibinder?
Hi Thomas, In your post above you mention @external .gwt-*;. You also use the same trick in thishttp://stackoverflow.com/questions/8182917/how-to-override-default-css-in-modern-gwt-applications StackOverflow question. But, I have never been able to make that work. Instead I have to have @external for every gwt type that I need to override, which is quite a hassle. (Note: in your post above you don't have the leading period. I have tried it both ways just to be sure.) When I try to use @external .gwt-*; I get errors of this flavor: [ERROR] Line 69: The annotation @CssResource.ClassName is disallowed for this location [ERROR] Line 70: Syntax error on token *, delete this token The generated lines in question look like this: @ClassName(gwt-*) String gwt*(); Am I doing something wrong? -- 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] Change in gwt[master]: Fix module unloading with multiple modules on a page
Matthew Dempsky has uploaded a new change for review. https://gwt-review.googlesource.com/2941 Change subject: Fix module unloading with multiple modules on a page .. Fix module unloading with multiple modules on a page Currently, the GWT compiler in production compiles will optimize away the instanceof checks in isMyListener() because it assumes getEventListener() is actually returning an EventListener object. However, if there are multiple modules loaded on a page, the __listener property might be for an EventListener from a different module. One way to workaround this (the approach taken by this patch) is to call isMyListener() before getEventListener() returns, so the compiler can't optimize away the instanceof checks. Change-Id: I25d9471c1e14756196a11223eadb765ed303a3b4 --- M user/src/com/google/gwt/user/client/impl/DOMImpl.java 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/user/src/com/google/gwt/user/client/impl/DOMImpl.java b/user/src/com/google/gwt/user/client/impl/DOMImpl.java index c5b8187..eafd332 100644 --- a/user/src/com/google/gwt/user/client/impl/DOMImpl.java +++ b/user/src/com/google/gwt/user/client/impl/DOMImpl.java @@ -50,12 +50,9 @@ for (int i = 0; i allElements.getLength(); i++) { com.google.gwt.dom.client.Element elem = allElements.getItem(i); Element userElem = (Element) elem; - if (dom.getEventsSunk(userElem) != 0) { -dom.sinkEvents(userElem, 0); - } EventListener listener = dom.getEventListener(userElem); - // nulls out event listener if and only if it was assigned from our module - if (GWT.isScript() listener != null isMyListener(listener)) { + if (GWT.isScript() listener != null) { +dom.sinkEvents(userElem, 0); dom.setEventListener(userElem, null); } // cleans up DOM-style addEventListener registered handlers @@ -154,7 +151,9 @@ public abstract int getChildIndex(Element parent, Element child); public native EventListener getEventListener(Element elem) /*-{ -return elem.__listener; +// Return elem.__listener if and only if it was assigned from our module +var maybeListener = elem.__listener; +return @com.google.gwt.user.client.impl.DOMImpl::isMyListener(Ljava/lang/Object;)(maybeListener) ? maybeListener : null; }-*/; public native int getEventsSunk(Element elem) /*-{ -- To view, visit https://gwt-review.googlesource.com/2941 To unsubscribe, visit https://gwt-review.googlesource.com/settings Gerrit-MessageType: newchange Gerrit-Change-Id: I25d9471c1e14756196a11223eadb765ed303a3b4 Gerrit-PatchSet: 1 Gerrit-Project: gwt Gerrit-Branch: master Gerrit-Owner: Matthew Dempsky mdemp...@google.com -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Change in gwt[master]: Use JSON.parse() instead of eval() to deserialize rpc callba...
Hello Leeroy Jenkins, Thomas Broyer, I'd like you to reexamine a change. Please visit https://gwt-review.googlesource.com/2900 to look at the new patch set (#3). Change subject: Use JSON.parse() instead of eval() to deserialize rpc callback payload .. Use JSON.parse() instead of eval() to deserialize rpc callback payload Changes deserialization of the RPC callback payload to use JSON.parse() instead of eval() to avoid memory leaks in IE9. Handles special cases (Infinity, -Infinity and NaN) by converting them into strings before they are sent to the client. ClientSerializationStreamReader. readDouble() will then use Number(x) to convert the string back to a number representation. Change-Id: I6062180397f5fabed1dd5f08140c2bd43a19fa9f --- M user/src/com/google/gwt/core/client/JsonUtils.java M user/src/com/google/gwt/user/client/rpc/impl/AbstractSerializationStreamWriter.java M user/super/com/google/gwt/user/translatable/com/google/gwt/user/client/rpc/impl/ClientSerializationStreamReader.java 3 files changed, 30 insertions(+), 5 deletions(-) -- To view, visit https://gwt-review.googlesource.com/2900 To unsubscribe, visit https://gwt-review.googlesource.com/settings Gerrit-MessageType: newpatchset Gerrit-Change-Id: I6062180397f5fabed1dd5f08140c2bd43a19fa9f Gerrit-PatchSet: 3 Gerrit-Project: gwt Gerrit-Branch: master Gerrit-Owner: John Ahlroos j...@vaadin.com Gerrit-Reviewer: Brian Slesinsky skybr...@google.com Gerrit-Reviewer: Colin Alworth niloc...@gmail.com Gerrit-Reviewer: John Ahlroos j...@vaadin.com Gerrit-Reviewer: Leeroy Jenkins jenk...@gwtproject.org Gerrit-Reviewer: Thomas Broyer t.bro...@gmail.com -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Change in gwt[master]: Fix module unloading with multiple modules on a page
Thomas Broyer has posted comments on this change. Change subject: Fix module unloading with multiple modules on a page .. Patch Set 1: Code-Review+1 To make sure it won't break anything else (you're changing the contract of getEventListener; among other things, it slightly changes what RootPanel allows in detachOnWindowClose), how about using a private getRawEventListener with Object as the return type? That being said, I do think it's a sane change; the above is just a suggestion. -- To view, visit https://gwt-review.googlesource.com/2941 To unsubscribe, visit https://gwt-review.googlesource.com/settings Gerrit-MessageType: comment Gerrit-Change-Id: I25d9471c1e14756196a11223eadb765ed303a3b4 Gerrit-PatchSet: 1 Gerrit-Project: gwt Gerrit-Branch: master Gerrit-Owner: Matthew Dempsky mdemp...@google.com Gerrit-Reviewer: Leeroy Jenkins jenk...@gwtproject.org Gerrit-Reviewer: Ray Cromwell cromwell...@google.com Gerrit-Reviewer: Thomas Broyer t.bro...@gmail.com Gerrit-HasComments: No -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Change in gwt[master]: Introduces generic Composite widgets.
Thomas Broyer has posted comments on this change. Change subject: Introduces generic Composite widgets. .. Patch Set 5: Code-Review-1 (1 comment) I tend to agree with Jens here (now that we see that in isolation, without the FocusComposite and PanelComposite) When you call initWidget(Widget,T), you already have a variable holding the delegate (because you have to put it as a child of the root widget), and changing that variable to a field to make it accessible elsewhere in the class is a no-brainer (and if you use UiBinder to construct your Composite's internals, you already have that field as a @UiField, so the concept of delegate at the Composite level only comes as a duplicate). The only use case for getDelegate is when you have someone extending your Composite, so they can gain direct access to that central widget; but a) extending a Composite is probably an anti-pattern and b) exposing your widget to subclasses is a no-brainer too. I really think what we want is to have getWidget() return some 'T extends Widget'. File user/src/com/google/gwt/user/client/ui/ResizeComposite.java Line 25: public abstract class ResizeCompositeT extends Widget RequiresResize The problem here is that actually you'll want getWidget to implement RequiresResize, not necessarily getDelegate (the goal of ResizeComposite is to be able to use a RequiresResize widget as the root widget). What we want here is more: public abstract class ResizeCompositeT extends Widget RequiresResize, D extends Widget extends CompositeD implements RequiresResize and that actually doesn't simplify the implementation of ResizeComposite (it would if Composite had 2 type parameters, for the root widget and the delegate). -- To view, visit https://gwt-review.googlesource.com/2582 To unsubscribe, visit https://gwt-review.googlesource.com/settings Gerrit-MessageType: comment Gerrit-Change-Id: I41e5c07e978d442db7d8402c57605cec1b3ea09e Gerrit-PatchSet: 5 Gerrit-Project: gwt Gerrit-Branch: master Gerrit-Owner: Goktug Gokdogan gok...@google.com Gerrit-Reviewer: Brian Slesinsky skybr...@google.com Gerrit-Reviewer: Goktug Gokdogan gok...@google.com Gerrit-Reviewer: Jens Nehlmeier jens.nehlme...@gmail.com Gerrit-Reviewer: Leeroy Jenkins jenk...@gwtproject.org Gerrit-Reviewer: Matthew Dempsky mdemp...@gwtproject.org Gerrit-Reviewer: Thomas Broyer t.bro...@gmail.com Gerrit-HasComments: Yes -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Change in gwt[master]: Fix for issue 1525
Thomas Broyer has posted comments on this change. Change subject: Fix for issue 1525 .. Patch Set 1: Code-Review+1 (1 comment) File user/src/com/google/gwt/user/client/ui/CustomButton.java Line 675: if ((to == null || !DOM.isOrHasChild(getElement(), to))) { Too many parentheses. -- To view, visit https://gwt-review.googlesource.com/2922 To unsubscribe, visit https://gwt-review.googlesource.com/settings Gerrit-MessageType: comment Gerrit-Change-Id: I2d49cae5ce0f8b8248aa15347914a5cd8da95287 Gerrit-PatchSet: 1 Gerrit-Project: gwt Gerrit-Branch: master Gerrit-Owner: Hilbrand Bouwkamp hilbr...@h72.nl Gerrit-Reviewer: Thomas Broyer t.bro...@gmail.com Gerrit-HasComments: Yes -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Change in gwt[master]: Use JSON.parse() instead of eval() to deserialize rpc callba...
Matthew Dempsky has posted comments on this change. Change subject: Use JSON.parse() instead of eval() to deserialize rpc callback payload .. Patch Set 3: (2 comments) File user/super/com/google/gwt/user/translatable/com/google/gwt/user/client/rpc/impl/ClientSerializationStreamReader.java Line 57: if(!JsonUtils.hasJsonParse() || encoded.contains(].concat([)){ GWT style is: if (condition) {. Does the .contains() check really do anything for us here? Won't that be handled by the IllegalArgumentException fallback below anyway? We need to fallback if there are unstringified NaN or Infinity values too after all, right? Line 69: try { Indented too far here. -- To view, visit https://gwt-review.googlesource.com/2900 To unsubscribe, visit https://gwt-review.googlesource.com/settings Gerrit-MessageType: comment Gerrit-Change-Id: I6062180397f5fabed1dd5f08140c2bd43a19fa9f Gerrit-PatchSet: 3 Gerrit-Project: gwt Gerrit-Branch: master Gerrit-Owner: John Ahlroos j...@vaadin.com Gerrit-Reviewer: Brian Slesinsky skybr...@google.com Gerrit-Reviewer: Colin Alworth niloc...@gmail.com Gerrit-Reviewer: John Ahlroos j...@vaadin.com Gerrit-Reviewer: Leeroy Jenkins jenk...@gwtproject.org Gerrit-Reviewer: Matthew Dempsky mdemp...@google.com Gerrit-Reviewer: Thomas Broyer t.bro...@gmail.com Gerrit-HasComments: Yes -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Change in gwt[master]: Fix for issue 1525
Thomas Broyer has posted comments on this change. Change subject: Fix for issue 1525 .. Patch Set 2: Just wondering: the root issue is that you don't get mouseout events in some conditions, and by capturing events you now get mouseout events *for other elements* (which is why you removed the test about the event's target being within the button, right?). Won't that possibly cause issues that other elements don't see mouseout events either? (e.g. the button is inside a panel that itself listens to mouseover and mouseout, when hovering quickly across that panel, you enter the button which starts capturing events, the mouseout event for the button –for whichever reason– is not dispatched, but that's not a problem form the PoV of the button as it now has the mouseout event of the panel; but then the panel won't receive its mouseout event, so we're just moving the problem, right?) Could we possibly use event previewing instead? -- To view, visit https://gwt-review.googlesource.com/2922 To unsubscribe, visit https://gwt-review.googlesource.com/settings Gerrit-MessageType: comment Gerrit-Change-Id: I2d49cae5ce0f8b8248aa15347914a5cd8da95287 Gerrit-PatchSet: 2 Gerrit-Project: gwt Gerrit-Branch: master Gerrit-Owner: Hilbrand Bouwkamp hilbr...@h72.nl Gerrit-Reviewer: Thomas Broyer t.bro...@gmail.com Gerrit-HasComments: No -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Change in gwt[master]: Use JSON.parse() instead of eval() to deserialize rpc callba...
Thomas Broyer has posted comments on this change. Change subject: Use JSON.parse() instead of eval() to deserialize rpc callback payload .. Patch Set 3: -Code-Review (1 comment) That starts to look good. As discussed previously, I think we should bump the protocol version, and conditioning the server output (whether to use the .concat hack or not) the request version should be easy (in user/src/com/google/gwt/user/server/rpc/impl/ServerSerializationStreamWriter.java, there's already something about long serialization). We could also just punt to when we remove support for IE6/7. The, we can either bump the protocol version again (version 9 would be identical to 8 except for the absence of the .concat hack) or change clients to throw an IncompatibleServiceException (but then stale clients running in IE6/7 will choke on deserialization of big arrays; not really a problem right?) File user/src/com/google/gwt/core/client/JsonUtils.java Line 129: public static native boolean hasJsonParse() /*-{ We should rather add an accessor for the static field (e.g. hasNativeJsonParse) As an alternative, maybe we could use JSNI to access this field and keep it private. This is hack, but it's only temporary until we remove support for IE6/7 (where we could unconditionally use JsonUtils.safeEval(), and that one would unconditionally use JSON.parse, and that field would disappear). Given that hasNativeJsonParse would soon unconditionally return 'true', I'd prefer that we don't introduce such an API in 2.6 that we'll deprecate as soon as 3.0. -- To view, visit https://gwt-review.googlesource.com/2900 To unsubscribe, visit https://gwt-review.googlesource.com/settings Gerrit-MessageType: comment Gerrit-Change-Id: I6062180397f5fabed1dd5f08140c2bd43a19fa9f Gerrit-PatchSet: 3 Gerrit-Project: gwt Gerrit-Branch: master Gerrit-Owner: John Ahlroos j...@vaadin.com Gerrit-Reviewer: Brian Slesinsky skybr...@google.com Gerrit-Reviewer: Colin Alworth niloc...@gmail.com Gerrit-Reviewer: John Ahlroos j...@vaadin.com Gerrit-Reviewer: Leeroy Jenkins jenk...@gwtproject.org Gerrit-Reviewer: Matthew Dempsky mdemp...@google.com Gerrit-Reviewer: Thomas Broyer t.bro...@gmail.com Gerrit-HasComments: Yes -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Change in gwt[master]: Use JSON.parse() instead of eval() to deserialize rpc callba...
Matthew Dempsky has posted comments on this change. Change subject: Use JSON.parse() instead of eval() to deserialize rpc callback payload .. Patch Set 3: (2 comments) File user/src/com/google/gwt/core/client/JsonUtils.java Line 129: public static native boolean hasJsonParse() /*-{ com.google.gwt.json.client.JSONParser already uses JSNI to bypass the private, so there's precedent for this hack. File user/super/com/google/gwt/user/translatable/com/google/gwt/user/client/rpc/impl/ClientSerializationStreamReader.java Line 57: if(!JsonUtils.hasJsonParse() || encoded.contains(].concat([)){ Hm, actually if we don't care about IE6/IE7 anymore anyway, why are we even worrying about whether JsonUtils.safeEval() is fast on IE6/IE7? Can't we just do: try { results = JsonUtils.safeEval(encoded); } catch (IllegalArgumentException iae) { // Input was invalid JSON; e.g., using ].concat([ or non-stringified NaN/Infinity. results = eval(encoded); } -- To view, visit https://gwt-review.googlesource.com/2900 To unsubscribe, visit https://gwt-review.googlesource.com/settings Gerrit-MessageType: comment Gerrit-Change-Id: I6062180397f5fabed1dd5f08140c2bd43a19fa9f Gerrit-PatchSet: 3 Gerrit-Project: gwt Gerrit-Branch: master Gerrit-Owner: John Ahlroos j...@vaadin.com Gerrit-Reviewer: Brian Slesinsky skybr...@google.com Gerrit-Reviewer: Colin Alworth niloc...@gmail.com Gerrit-Reviewer: John Ahlroos j...@vaadin.com Gerrit-Reviewer: Leeroy Jenkins jenk...@gwtproject.org Gerrit-Reviewer: Matthew Dempsky mdemp...@google.com Gerrit-Reviewer: Thomas Broyer t.bro...@gmail.com Gerrit-HasComments: Yes -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Change in gwt[master]: Use JSON.parse() instead of eval() to deserialize rpc callba...
Brian Slesinsky has posted comments on this change. Change subject: Use JSON.parse() instead of eval() to deserialize rpc callback payload .. Patch Set 3: The main reason I put up this patch is that currently IE9 is leaking memory quite badly for each RPC call you make. The root cause is that eval() on IE9 is designed to keep everything evaled in memory until the browsers session dies. See https://code.google.com/p/google-web-toolkit/issues/detail?id=57366 for more details and discussion. Thanks, this is a good reason. Please add it (or something like it) to the patch description. -- To view, visit https://gwt-review.googlesource.com/2900 To unsubscribe, visit https://gwt-review.googlesource.com/settings Gerrit-MessageType: comment Gerrit-Change-Id: I6062180397f5fabed1dd5f08140c2bd43a19fa9f Gerrit-PatchSet: 3 Gerrit-Project: gwt Gerrit-Branch: master Gerrit-Owner: John Ahlroos j...@vaadin.com Gerrit-Reviewer: Brian Slesinsky skybr...@google.com Gerrit-Reviewer: Colin Alworth niloc...@gmail.com Gerrit-Reviewer: John Ahlroos j...@vaadin.com Gerrit-Reviewer: Leeroy Jenkins jenk...@gwtproject.org Gerrit-Reviewer: Matthew Dempsky mdemp...@google.com Gerrit-Reviewer: Thomas Broyer t.bro...@gmail.com Gerrit-HasComments: No -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Change in gwt[master]: Use JSON.parse() instead of eval() to deserialize rpc callba...
Brian Slesinsky has posted comments on this change. Change subject: Use JSON.parse() instead of eval() to deserialize rpc callback payload .. Patch Set 3: (3 comments) File user/src/com/google/gwt/core/client/JsonUtils.java Line 129: public static native boolean hasJsonParse() /*-{ I'm neutral on this, but I'll point out that there's very little downside to keeping this method around forever. File user/src/com/google/gwt/user/client/rpc/impl/AbstractSerializationStreamWriter.java Line 92: if (Double.isNaN(fieldValue) || Double.isInfinite(fieldValue)) { Call getVersion() here and do this only for the new version. File user/super/com/google/gwt/user/translatable/com/google/gwt/user/client/rpc/impl/ClientSerializationStreamReader.java Line 57: if(!JsonUtils.hasJsonParse() || encoded.contains(].concat([)){ Please no content sniffing. We should check the version number. -- To view, visit https://gwt-review.googlesource.com/2900 To unsubscribe, visit https://gwt-review.googlesource.com/settings Gerrit-MessageType: comment Gerrit-Change-Id: I6062180397f5fabed1dd5f08140c2bd43a19fa9f Gerrit-PatchSet: 3 Gerrit-Project: gwt Gerrit-Branch: master Gerrit-Owner: John Ahlroos j...@vaadin.com Gerrit-Reviewer: Brian Slesinsky skybr...@google.com Gerrit-Reviewer: Colin Alworth niloc...@gmail.com Gerrit-Reviewer: John Ahlroos j...@vaadin.com Gerrit-Reviewer: Leeroy Jenkins jenk...@gwtproject.org Gerrit-Reviewer: Matthew Dempsky mdemp...@google.com Gerrit-Reviewer: Thomas Broyer t.bro...@gmail.com Gerrit-HasComments: Yes -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Change in gwt[master]: Introduces generic Composite widgets.
Goktug Gokdogan has posted comments on this change. Change subject: Introduces generic Composite widgets. .. Patch Set 5: When you call initWidget(Widget,T), you already have a variable holding the delegate (because you have to put it as a child of the root widget), and changing that variable to a field to make it accessible elsewhere in the class is a no-brainer (and if you use UiBinder to construct your Composite's internals, you already have that field as a @UiField, so the concept of delegate at the Composite level only comes as a duplicate). For simple composites, they will use the single initWidget and they might use the getDelegate for access to base widget but this is not really the use case to go with getDelegate and this is NOT why I introduced it. The only use case for getDelegate is when you have someone extending your Composite, so they can gain direct access to that central widget; but a) extending a Composite is probably an anti-pattern and b) exposing your widget to subclasses is a no-brainer too. I think you totally missed the point. This is the reason why I'm saying we are going in circles. The conversation became too long and the original intention for the change started to get lost. I started working on this is, because it is not to possible safely extend Composite to introduce more reusable classes (inside or outside of SDK) that does more delegations (ResizeComposite, FocusComposite, PanelComposite, IndexPanelComposite etc). In our internal code there are already multiple of them, duplicated in different projects and written poorly. In the GWT SDK, we don't have those reusable classes so we are also duplicating the code in a poor way. ValueListBox received the second patch since I joined the team. -- To view, visit https://gwt-review.googlesource.com/2582 To unsubscribe, visit https://gwt-review.googlesource.com/settings Gerrit-MessageType: comment Gerrit-Change-Id: I41e5c07e978d442db7d8402c57605cec1b3ea09e Gerrit-PatchSet: 5 Gerrit-Project: gwt Gerrit-Branch: master Gerrit-Owner: Goktug Gokdogan gok...@google.com Gerrit-Reviewer: Brian Slesinsky skybr...@google.com Gerrit-Reviewer: Goktug Gokdogan gok...@google.com Gerrit-Reviewer: Jens Nehlmeier jens.nehlme...@gmail.com Gerrit-Reviewer: Leeroy Jenkins jenk...@gwtproject.org Gerrit-Reviewer: Matthew Dempsky mdemp...@gwtproject.org Gerrit-Reviewer: Thomas Broyer t.bro...@gmail.com Gerrit-HasComments: No -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Change in gwt[master]: Introduces generic Composite widgets.
Brian Slesinsky has posted comments on this change. Change subject: Introduces generic Composite widgets. .. Patch Set 5: -Code-Review re: In the GWT SDK, we don't have those reusable classes so we are also duplicating the code in a poor way. ValueListBox received the second patch since I joined the team. I found one patch: http://gwt-code-reviews.appspot.com/1884803/ It seems pretty straightforward. What's the other patch? -- To view, visit https://gwt-review.googlesource.com/2582 To unsubscribe, visit https://gwt-review.googlesource.com/settings Gerrit-MessageType: comment Gerrit-Change-Id: I41e5c07e978d442db7d8402c57605cec1b3ea09e Gerrit-PatchSet: 5 Gerrit-Project: gwt Gerrit-Branch: master Gerrit-Owner: Goktug Gokdogan gok...@google.com Gerrit-Reviewer: Brian Slesinsky skybr...@google.com Gerrit-Reviewer: Goktug Gokdogan gok...@google.com Gerrit-Reviewer: Jens Nehlmeier jens.nehlme...@gmail.com Gerrit-Reviewer: Leeroy Jenkins jenk...@gwtproject.org Gerrit-Reviewer: Matthew Dempsky mdemp...@gwtproject.org Gerrit-Reviewer: Thomas Broyer t.bro...@gmail.com Gerrit-HasComments: No -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Change in gwt[master]: Fixes most issues with the SoyC reports.
Hello Ray Cromwell, Leeroy Jenkins, Brian Slesinsky, I'd like you to reexamine a change. Please visit https://gwt-review.googlesource.com/1610 to look at the new patch set (#4). Change subject: Fixes most issues with the SoyC reports. .. Fixes most issues with the SoyC reports. Applied an unsubmitted patch (http://gwt-code-reviews.appspot.com/1726803/) by Alan and added a few fixes. Will show incorrect inforamtion on atoms pulled to leftover by the latest safety check. A full refactor is needed and will be done when the new Fragment Merging strategy is implemented. Change-Id: I950ebd7b367671446e3d919a00be24d4cbf3fa88 Review-Link: https://gwt-review.googlesource.com/#/c/1610/ --- M dev/core/src/com/google/gwt/dev/jjs/impl/CodeSplitter2.java M dev/core/test/com/google/gwt/dev/jjs/impl/CodeSplitter2Test.java 2 files changed, 82 insertions(+), 30 deletions(-) -- To view, visit https://gwt-review.googlesource.com/1610 To unsubscribe, visit https://gwt-review.googlesource.com/settings Gerrit-MessageType: newpatchset Gerrit-Change-Id: I950ebd7b367671446e3d919a00be24d4cbf3fa88 Gerrit-PatchSet: 4 Gerrit-Project: gwt Gerrit-Branch: master Gerrit-Owner: Roberto Lublinerman rlu...@google.com Gerrit-Reviewer: Brian Slesinsky skybr...@google.com Gerrit-Reviewer: Leeroy Jenkins jenk...@gwtproject.org Gerrit-Reviewer: Ray Cromwell cromwell...@google.com Gerrit-Reviewer: Roberto Lublinerman rlu...@google.com Gerrit-Reviewer: Thomas Broyer t.bro...@gmail.com -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Change in gwt[master]: Fixes most issues with the SoyC reports.
Roberto Lublinerman has posted comments on this change. Change subject: Fixes most issues with the SoyC reports. .. Patch Set 4: Code-Review+2 Patch 3 was +2 by skybrian and this is a manual rebase due to conflicts. -- To view, visit https://gwt-review.googlesource.com/1610 To unsubscribe, visit https://gwt-review.googlesource.com/settings Gerrit-MessageType: comment Gerrit-Change-Id: I950ebd7b367671446e3d919a00be24d4cbf3fa88 Gerrit-PatchSet: 4 Gerrit-Project: gwt Gerrit-Branch: master Gerrit-Owner: Roberto Lublinerman rlu...@google.com Gerrit-Reviewer: Brian Slesinsky skybr...@google.com Gerrit-Reviewer: Leeroy Jenkins jenk...@gwtproject.org Gerrit-Reviewer: Ray Cromwell cromwell...@google.com Gerrit-Reviewer: Roberto Lublinerman rlu...@google.com Gerrit-Reviewer: Thomas Broyer t.bro...@gmail.com Gerrit-HasComments: No -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Change in gwt[master]: Introduces generic Composite widgets.
Goktug Gokdogan has posted comments on this change. Change subject: Introduces generic Composite widgets. .. Patch Set 5: Yes, as Brian tried to explain, I ended up with this design after playing with plenty of alternatives and uses cases; at the end this is the one that I am most comfortable with. I'm open to other suggestions that would help us to write good reusable XYZComposite classes (inside or outside SDK) and still reasonable to use with UIBinder. Please play with them in your IDE and try to see how it will look like in practice for different use cases. -- To view, visit https://gwt-review.googlesource.com/2582 To unsubscribe, visit https://gwt-review.googlesource.com/settings Gerrit-MessageType: comment Gerrit-Change-Id: I41e5c07e978d442db7d8402c57605cec1b3ea09e Gerrit-PatchSet: 5 Gerrit-Project: gwt Gerrit-Branch: master Gerrit-Owner: Goktug Gokdogan gok...@google.com Gerrit-Reviewer: Brian Slesinsky skybr...@google.com Gerrit-Reviewer: Goktug Gokdogan gok...@google.com Gerrit-Reviewer: Jens Nehlmeier jens.nehlme...@gmail.com Gerrit-Reviewer: Leeroy Jenkins jenk...@gwtproject.org Gerrit-Reviewer: Matthew Dempsky mdemp...@gwtproject.org Gerrit-Reviewer: Thomas Broyer t.bro...@gmail.com Gerrit-HasComments: No -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Change in gwt[master]: Fixes most issues with the SoyC reports.
Roberto Lublinerman has submitted this change and it was merged. Change subject: Fixes most issues with the SoyC reports. .. Fixes most issues with the SoyC reports. Applied an unsubmitted patch (http://gwt-code-reviews.appspot.com/1726803/) by Alan and added a few fixes. Will show incorrect inforamtion on atoms pulled to leftover by the latest safety check. A full refactor is needed and will be done when the new Fragment Merging strategy is implemented. Change-Id: I950ebd7b367671446e3d919a00be24d4cbf3fa88 Review-Link: https://gwt-review.googlesource.com/#/c/1610/ --- M dev/core/src/com/google/gwt/dev/jjs/impl/CodeSplitter2.java M dev/core/test/com/google/gwt/dev/jjs/impl/CodeSplitter2Test.java 2 files changed, 82 insertions(+), 30 deletions(-) Approvals: Roberto Lublinerman: Looks good to me, approved Leeroy Jenkins: Verified diff --git a/dev/core/src/com/google/gwt/dev/jjs/impl/CodeSplitter2.java b/dev/core/src/com/google/gwt/dev/jjs/impl/CodeSplitter2.java index 897464d..4b6543a 100644 --- a/dev/core/src/com/google/gwt/dev/jjs/impl/CodeSplitter2.java +++ b/dev/core/src/com/google/gwt/dev/jjs/impl/CodeSplitter2.java @@ -90,7 +90,6 @@ * TODO(acleung): Figure out how to integrate with SOYC and dependency tracker. * TODO(acleung): Insert SpeedTracer calls at performance sensitive places. * TODO(acleung): Insert logger calls to generate meaningful logs. - * TODO(acleung): May be add back the old heuristics if needed. */ public class CodeSplitter2 { @@ -109,9 +108,6 @@ private FragmentPartitioningResult(int[] splitPointToFragmentMap, int numFragments) { this.splitPointToFragmentMap = splitPointToFragmentMap; fragmentToSplitPoint = new int[numFragments]; - for (int i = 0, len = splitPointToFragmentMap.length - 1; i len; i++) { -System.out.println(splitPointToFragmentMap[ + i + ] = + splitPointToFragmentMap[i]); - } for (int i = 1, len = splitPointToFragmentMap.length - 1; i len; i++) { if (fragmentToSplitPoint[splitPointToFragmentMap[i]] == 0) { fragmentToSplitPoint[splitPointToFragmentMap[i]] = i; @@ -310,6 +306,7 @@ return; } Event codeSplitterEvent = SpeedTracerLogger.start(CompilerEventType.CODE_SPLITTER); +dependencyRecorder.open(); new CodeSplitter2( logger, jprogram, jsprogram, map, fragmentsToMerge, dependencyRecorder, leftOverMergeLimit).execImpl(); @@ -608,8 +605,8 @@ * @param liveFromSplitPoint everything live from the split point, including leftovers * @param T the type of node (field, method, etc) in the map */ - private static T void updateReverseMap(int splitPoint, MapT, Integer map, Set? liveWithoutEntry, - IterableT all, Set? liveFromSplitPoint) { + private static T void updateReverseMap(int splitPoint, MapT, Integer map, + Set? liveWithoutEntry, IterableT all, Set? liveFromSplitPoint) { for (T each : all) { if (!liveWithoutEntry.contains(each)) { /* @@ -629,7 +626,9 @@ } ExclusivityMap fragmentMap = new ExclusivityMap(); - + + private MultipleDependencyGraphRecorder dependencyRecorder; + private final MapJField, JClassLiteral fieldToLiteralOfClass; private FragmentExtractor fragmentExtractor; @@ -683,6 +682,7 @@ this.jsprogram = jsprogram; this.splitPointsMerge = splitPointsMerge; this.leftOverMergeLimit = leftOverMergeLimit; +this.dependencyRecorder = dependencyRecorder; this.fragmentExtractor = new FragmentExtractor(jprogram, jsprogram, map); this.initialLoadSequence = new LinkedHashSetInteger(jprogram.getSplitPointInitialSequence()); @@ -819,10 +819,12 @@ private static class MergeLimitExceededException extends RuntimeException { } - private ControlFlowAnalyzer computeAllButNCfas( - ControlFlowAnalyzer liveAfterInitialSequence, ListInteger sp) { + private ControlFlowAnalyzer computeAllButNCfas(ControlFlowAnalyzer liveAfterInitialSequence, + ListInteger sp, ControlFlowAnalyzer.DependencyRecorder dependencyRecorder) { ListControlFlowAnalyzer allButOnes = new ArrayListControlFlowAnalyzer(); ControlFlowAnalyzer cfa = new ControlFlowAnalyzer(liveAfterInitialSequence); +cfa.setDependencyRecorder(dependencyRecorder); + for (JRunAsync otherRunAsync : jprogram.getRunAsyncs()) { if (isInitial(otherRunAsync.getSplitPoint())) { continue; @@ -832,6 +834,7 @@ } cfa.traverseFromRunAsync(otherRunAsync); } + return cfa; } @@ -843,25 +846,29 @@ */ private ControlFlowAnalyzer computeAllLiveFromSplitPoints( ControlFlowAnalyzer liveAfterInitialSequence, ListInteger splitPoints) { - ControlFlowAnalyzer cfa = new ControlFlowAnalyzer(liveAfterInitialSequence); - for (JRunAsync otherRunAsync : jprogram.getRunAsyncs()) { -
Re: [gwt-contrib] Re: Generator, get method body
Hi Roberto, sorry by the delay. What I'm doing is a generator for presentations. Given a java class with my example methods, create a set of html slides. The generator reads the javadoc and the body of the method, and put them in a hash table into the generated class. Then in client side I can use this info to insert the code and wording in my slides using gwtquery. You can see my generator in github [1], focus on parseJava() in line #73. Right now I'm using japa.parser.JavaParser [2], but I'm wondering if there is a way to use gwt parsers so as I dont have to import a 3party library. [1] https://github.com/manolo/gwt-slides/blob/master/src/main/java/org/gquery/slides/bind/SlidesGenerator.java#L73 [2] https://code.google.com/p/javaparser/ Thanks - Manolo On Wed, May 15, 2013 at 2:39 PM, Roberto Lublinerman rlu...@google.comwrote: Can you share what you are attempting to do? Generators only get to see structure (class hierarchy and method definitions) as far as I know. On Sunday, May 12, 2013 3:57:35 AM UTC-7, Manuel Carrasco Moñino wrote: Hi all Is there a way to get the body of a method in a generator? I've seen JMethodBody is used in compile time, but I dont figure out how to get it in generators. Thanks -- -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups Google Web Toolkit Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] Re: Generator, get method body
On Thu, May 23, 2013 at 5:28 PM, Manuel Carrasco Moñino man...@apache.orgwrote: What I'm doing is a generator for presentations. Given a java class with my example methods, create a set of html slides. The generator reads the javadoc and the body of the method, and put them in a hash table into the generated class. Then in client side I can use this info to insert the code and wording in my slides using gwtquery. That sounds a lot like what Showcase does -- maybe this will help: https://code.google.com/p/google-web-toolkit/source/browse/trunk/samples/showcase/src/com/google/gwt/sample/showcase/generator/ShowcaseGenerator.java -- John A. Tamplin -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Change in gwt[master]: Add History.getUrl(String token) which returns the correspon...
Johannes Barop has uploaded a new change for review. https://gwt-review.googlesource.com/2960 Change subject: Add History.getUrl(String token) which returns the corresponding URL for a history token. .. Add History.getUrl(String token) which returns the corresponding URL for a history token. This enables custom History implementations (for example a implementation with pushstate) to modify the display of URLs in widgets (for example Hyperlink). Change-Id: I9f9b261547b539489d9cee8a72f660264d64e9f2 --- M user/src/com/google/gwt/user/client/History.java M user/src/com/google/gwt/user/client/impl/HistoryImpl.java M user/src/com/google/gwt/user/client/ui/Hyperlink.java 3 files changed, 20 insertions(+), 2 deletions(-) diff --git a/user/src/com/google/gwt/user/client/History.java b/user/src/com/google/gwt/user/client/History.java index 285ffee..03a29e8 100644 --- a/user/src/com/google/gwt/user/client/History.java +++ b/user/src/com/google/gwt/user/client/History.java @@ -18,6 +18,7 @@ import com.google.gwt.core.client.GWT; import com.google.gwt.core.client.impl.Disposable; import com.google.gwt.core.client.impl.Impl; +import com.google.gwt.dom.client.AnchorElement; import com.google.gwt.event.logical.shared.ValueChangeEvent; import com.google.gwt.event.logical.shared.ValueChangeHandler; import com.google.gwt.event.shared.HandlerManager; @@ -240,4 +241,14 @@ WrapHistory.remove(impl.getHandlers(), listener); } } + + /** + * Gets the corresponding URL for the given history token. + * + * @param historyToken History token to generate the URL for. + */ + public static String getUrl(String historyToken) { +return impl.getUrl(historyToken); + } + } diff --git a/user/src/com/google/gwt/user/client/impl/HistoryImpl.java b/user/src/com/google/gwt/user/client/impl/HistoryImpl.java index af675cd..d960111 100644 --- a/user/src/com/google/gwt/user/client/impl/HistoryImpl.java +++ b/user/src/com/google/gwt/user/client/impl/HistoryImpl.java @@ -16,12 +16,16 @@ package com.google.gwt.user.client.impl; import com.google.gwt.core.client.JavaScriptObject; +import com.google.gwt.dom.client.AnchorElement; import com.google.gwt.event.logical.shared.HasValueChangeHandlers; import com.google.gwt.event.logical.shared.ValueChangeEvent; import com.google.gwt.event.logical.shared.ValueChangeHandler; import com.google.gwt.event.shared.GwtEvent; import com.google.gwt.event.shared.HandlerManager; import com.google.gwt.event.shared.HandlerRegistration; +import com.google.gwt.user.client.DOM; +import com.google.gwt.user.client.Element; +import com.google.gwt.user.client.History; /** * Native implementation associated with @@ -149,6 +153,10 @@ } } + public String getUrl(String historyToken) { +return # + History.encodeHistoryToken(historyToken); + } + protected native String decodeFragment(String encodedFragment) /*-{ // decodeURI() does *not* decode the '#' character. return decodeURI(encodedFragment.replace(%23, #)); diff --git a/user/src/com/google/gwt/user/client/ui/Hyperlink.java b/user/src/com/google/gwt/user/client/ui/Hyperlink.java index 61b9821..3366aa4 100644 --- a/user/src/com/google/gwt/user/client/ui/Hyperlink.java +++ b/user/src/com/google/gwt/user/client/ui/Hyperlink.java @@ -342,8 +342,7 @@ assert targetHistoryToken != null : targetHistoryToken must not be null, consider using Anchor instead; this.targetHistoryToken = targetHistoryToken; -String hash = History.encodeHistoryToken(targetHistoryToken); -DOM.setElementProperty(anchorElem, href, # + hash); +DOM.setElementProperty(anchorElem, href, History.getUrl(targetHistoryToken)); } public void setText(String text) { -- To view, visit https://gwt-review.googlesource.com/2960 To unsubscribe, visit https://gwt-review.googlesource.com/settings Gerrit-MessageType: newchange Gerrit-Change-Id: I9f9b261547b539489d9cee8a72f660264d64e9f2 Gerrit-PatchSet: 1 Gerrit-Project: gwt Gerrit-Branch: master Gerrit-Owner: Johannes Barop j...@barop.de -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Change in gwt[master]: Add History.getUrl(String token) which returns the correspon...
Johannes Barop has posted comments on this change. Change subject: Add History.getUrl(String token) which returns the corresponding URL for a history token. .. Patch Set 1: Please note the missing test for History.getUrl as I unsure how to write a good test case for it. I'm open for suggestions -- To view, visit https://gwt-review.googlesource.com/2960 To unsubscribe, visit https://gwt-review.googlesource.com/settings Gerrit-MessageType: comment Gerrit-Change-Id: I9f9b261547b539489d9cee8a72f660264d64e9f2 Gerrit-PatchSet: 1 Gerrit-Project: gwt Gerrit-Branch: master Gerrit-Owner: Johannes Barop j...@barop.de Gerrit-Reviewer: Johannes Barop j...@barop.de Gerrit-HasComments: No -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] Re: Generator, get method body
Thank John for the link. The ShowcaseGenerator, is actually reading the content of the source files and generating .html files, but I want to extract method bodies and their javadoc so what I need an AST. So my question is more about how to use the gwt ast from a generator. On Thu, May 23, 2013 at 11:32 PM, John A. Tamplin j...@jaet.org wrote: On Thu, May 23, 2013 at 5:28 PM, Manuel Carrasco Moñino man...@apache.org wrote: What I'm doing is a generator for presentations. Given a java class with my example methods, create a set of html slides. The generator reads the javadoc and the body of the method, and put them in a hash table into the generated class. Then in client side I can use this info to insert the code and wording in my slides using gwtquery. That sounds a lot like what Showcase does -- maybe this will help: https://code.google.com/p/google-web-toolkit/source/browse/trunk/samples/showcase/src/com/google/gwt/sample/showcase/generator/ShowcaseGenerator.java -- John A. Tamplin -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] Re: Generator, get method body
On Thu, May 23, 2013 at 7:56 PM, Manuel Carrasco Moñino man...@apache.orgwrote: The ShowcaseGenerator, is actually reading the content of the source files and generating .html files, but I want to extract method bodies and their javadoc so what I need an AST. So my question is more about how to use the gwt ast from a generator. The GWT AST is not available to generators, so you will have to build your own -- you can use JDT as that is included with GWT. -- John A. Tamplin -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] Re: Generator, get method body
Even if it were accessible to the generators the GWT AST does not contain javadocs nor comments. Roberto Lublinerman | Software Engineer | rlu...@google.com | 408-500-9148 On Thu, May 23, 2013 at 5:35 PM, John A. Tamplin j...@jaet.org wrote: On Thu, May 23, 2013 at 7:56 PM, Manuel Carrasco Moñino man...@apache.org wrote: The ShowcaseGenerator, is actually reading the content of the source files and generating .html files, but I want to extract method bodies and their javadoc so what I need an AST. So my question is more about how to use the gwt ast from a generator. The GWT AST is not available to generators, so you will have to build your own -- you can use JDT as that is included with GWT. -- John A. Tamplin -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Change in gwt[master]: Chooses a default GWT source level to match the current java...
Roberto Lublinerman has posted comments on this change. Change subject: Chooses a default GWT source level to match the current java runtime. .. Patch Set 4: @Matthew, I ended up fixing ApiCompatibilityChecker to accept also the java source level in the configuration file so there is no need now to change the old file. -- To view, visit https://gwt-review.googlesource.com/2910 To unsubscribe, visit https://gwt-review.googlesource.com/settings Gerrit-MessageType: comment Gerrit-Change-Id: I69dc0e9b1ac0ecf9a40ee2a08d8d555319d0af6f Gerrit-PatchSet: 4 Gerrit-Project: gwt Gerrit-Branch: master Gerrit-Owner: Roberto Lublinerman rlu...@google.com Gerrit-Reviewer: Leeroy Jenkins jenk...@gwtproject.org Gerrit-Reviewer: Matthew Dempsky mdemp...@google.com Gerrit-Reviewer: Roberto Lublinerman rlu...@google.com Gerrit-Reviewer: Thomas Broyer t.bro...@gmail.com Gerrit-HasComments: No -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.