Re: GWT Compilation Time Performance Improvement
Maybe you should get more RAM...4GB isn't a lot when running all the things you need for GWT development. Alternatively, run some (or even all) of the required processes on another computer. Paul On 06/09/12 05:33, Niraj Salot wrote: Hi Members, Thanks for all your suggestion/comments. We have already tried below mentioned options to improve the compilation time overall. 1. Memory Settings. -Xmx and Xms 2. localWorkers 3. DraftCompile The question could arise to members mind that why we need to compile a lot but the thing is :- while doing the development work If we use the development mode provided by GWT , sometimes happens that the end output in production mode is diff. then development mode. So we can not trust that what is shown in development mode will be same in production mode. Hence developers compile their code on their machine and test it before putting something on main server. The issue is developers machine have overall RAM of 4 GB only. And when Jboss , Eclipse and Compilation of GWT runs , It is very very slow. So for even the small changes , developers needs to compile , build the WAR and then deploy to check that his code is working ok or not. I am looking for some option which could allow me to pre-compile GWT modules. So that If some GWT module is not changed and when I compile the main module , that GWT module should not compile as it is not changed at all. I am not still not getting how to use the concept of *.gwtar files which is mentioned in our discussion. Would appreciate if someone can provide more details on the same. Thanks,Niraj. On Tuesday, 4 September 2012 11:40:19 UTC+5:30, Niraj Salot wrote: Hi Members, We are using GWT Version 2.4 in our current project. On server side, we are using Spring Custom JDBC framework. We are using Maven as our Build Tool. The application is getting deployed on JBOSS 7 Server. Currently we have everything in one single Eclipse Project. Means one Application.gwt.xml file and one ApplicationContext.xml for spring. We have around 2000 Java files out of which around 1500 are for GWT related source files. The project is still growing with more source files. We are fine with timings of Java to Javac [class file] Compilation time. But when It comes to Java to JavaScript , It is a issue. We have used all hacks mentioned in the GWT Forum. Like. 1. Compiling for only one Local 2. Compiling for only one Browser But still the compilation is taking 4-6 minutes.. OR even 7 minutes some times. With this question, I would like to know the options available to improve the same. We are thinking to Split the Project like this WAY: * Module 1 (JAR Build) * Module 2 (JAR Build) * Module Main (WAR Build). This would contain Application.gwt.xml file which would inherit Module 1 Module 2. Now Question comes: *1) Will this help us in Improving the compilation time?* *2) IF we change only Module 2 and then compile Module Main, will GWT still compile Module 1 as it is inherited by Module Main?* Please share your views on above scenario. We have even tried out GWT 2.5 option but no help in performance improvements. Thanks, Niraj Salot. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/xXHXkkCzV4oJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT future
Powerdrill a tool used internally by Google is based on GWT. http://vldb.org/pvldb/vol5/p1436_alexanderhall_vldb2012.pdf https://plus.google.com/+ResearchatGoogle/posts/UaDPdYu2q1u On Monday, July 23, 2012 9:14:49 AM UTC+2, AG wrote: I'm an Architect and we have been looking to port our legacy HTML w/ Java Script based web app (with java backend) to a next generation web application. We are a java shop so GWT is very popular with our developers and I have been so called GWT fan-boy all along. However, lately I'm strongly considering moving away from GWT. Following are my observations that are scaring me to start looking for GWT alternatives: 1. Larry Page has been killing no-so-happening (or revenue generating) projects from google. I was reading that 30+ projects have already been killed/shelved ever since Larry became CEO. -- I understand the need for this and I also understand that GWT currently enjoys a healthy developer community. 2. DART - Looks like its the next big thing within google to develop web applications. As a google outsider, at least this is what it seems like. Google IO 2012 has no sessions for GWT while DART had several and there is even a session to convert GWT apps to DART. 3. The latest update to Google Developer portal ( http://developers.google.com) has no direct links to GWT. The web development section goes to chrome. I think the GWT team can address some of my concerns but it would be great if Google's management can stand behind GWT as a platform of choice for web development - similar to how Microsoft stands behind theirs development platforms. AG -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/RU2Iys-7N1cJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Compilation Time Performance Improvement
I don't know if I am missing something, but, have you tried to upgrade to GWT 2.5 and use SuperDevMode? In my case I was needing 2 minutes each time that I made any change and now 15 seconds(or less). Maybe for your developers is worth to try it. My 2 cents, Adolfo. 2012/9/6 Paul Robinson ukcue...@gmail.com Maybe you should get more RAM...4GB isn't a lot when running all the things you need for GWT development. Alternatively, run some (or even all) of the required processes on another computer. Paul On 06/09/12 05:33, Niraj Salot wrote: Hi Members, Thanks for all your suggestion/comments. We have already tried below mentioned options to improve the compilation time overall. 1. Memory Settings. -Xmx and Xms 2. localWorkers 3. DraftCompile The question could arise to members mind that why we need to compile a lot but the thing is :- while doing the development work If we use the development mode provided by GWT , sometimes happens that the end output in production mode is diff. then development mode. So we can not trust that what is shown in development mode will be same in production mode. Hence developers compile their code on their machine and test it before putting something on main server. The issue is developers machine have overall RAM of 4 GB only. And when Jboss , Eclipse and Compilation of GWT runs , It is very very slow. So for even the small changes , developers needs to compile , build the WAR and then deploy to check that his code is working ok or not. I am looking for some option which could allow me to pre-compile GWT modules. So that If some GWT module is not changed and when I compile the main module , that GWT module should not compile as it is not changed at all. I am not still not getting how to use the concept of *.gwtar files which is mentioned in our discussion. Would appreciate if someone can provide more details on the same. Thanks,Niraj. On Tuesday, 4 September 2012 11:40:19 UTC+5:30, Niraj Salot wrote: Hi Members, We are using GWT Version 2.4 in our current project. On server side, we are using Spring Custom JDBC framework. We are using Maven as our Build Tool. The application is getting deployed on JBOSS 7 Server. Currently we have everything in one single Eclipse Project. Means one Application.gwt.xml file and one ApplicationContext.xml for spring. We have around 2000 Java files out of which around 1500 are for GWT related source files. The project is still growing with more source files. We are fine with timings of Java to Javac [class file] Compilation time. But when It comes to Java to JavaScript , It is a issue. We have used all hacks mentioned in the GWT Forum. Like. 1. Compiling for only one Local 2. Compiling for only one Browser But still the compilation is taking 4-6 minutes.. OR even 7 minutes some times. With this question, I would like to know the options available to improve the same. We are thinking to Split the Project like this WAY: - Module 1 (JAR Build) - Module 2 (JAR Build) - Module Main (WAR Build). This would contain Application.gwt.xml file which would inherit Module 1 Module 2. Now Question comes: *1) Will this help us in Improving the compilation time?* *2) IF we change only Module 2 and then compile Module Main, will GWT still compile Module 1 as it is inherited by Module Main?* Please share your views on above scenario. We have even tried out GWT 2.5 option but no help in performance improvements. Thanks, Niraj Salot. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/xXHXkkCzV4oJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- El precio es lo que pagas. El valor es lo que recibes. Warren Buffet -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Update progress message box code progresses
Hi, I have a requirement to update the progress in the message box as the code progresses. Interesting thing is, I have to make only single call to the server side, and there are couple of things done at the server side. I need to keep updating the message/progress bar as and when each task completes in the server side. I can't split the calls from client to server as network operation is really expensive in my office. Each network request slows down the system very badly. Updating the progress bar will give the user a feeling that application is not taking long time ;-). Thanks in advance... -dingolfy -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/8jyX33PL45QJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Tracking multiple steps in a RPC request on the client
Hi, Did you manage to get around this problem? I'm also facing the same issue. Thanks, -dingolfy On Friday, 9 September 2011 20:07:21 UTC+1, Nestor wrote: Could you clarify that? My understanding is that once I send a response back to the client, the connection is closed. How do I then get a response for the next step? If I make another RPC request, is there a guarantee that I'll connect to the same session that executed the previous step? Let me try to illustrate what I'm going for: Client submits RPC request for Step 1 Server receives request and executes Step 1 Once Step 1 is complete, server sends response with progress update Client receives response and displays progress update to user Client sends RPC request for Step 2 Server receives request Server takes data generated from Step 1 (preserved how?) Server executes Step 2 and sends response with progress update Client receives response and displays progress update Client sends RPC request for Step 3 ...and so on. My main concern is how to preserve the interim data from one RPC call to the next. On Sep 6, 3:55 pm, mohit ranjan shoonya.mo...@gmail.com wrote: Make an async RPC call and update UI on OnSuccess/OnFailure() Mohit On Wed, Sep 7, 2011 at 1:13 AM, Nestor nestord...@gmail.com wrote: I'm trying to find out how to implement the following functionality. Any help would be appreciated. The client sends a RPC request to the server for a set of data. The server has to query the data, then perform some additional processinf (e.g., filter, sort) before sending it back to the client. While this processing is going on, a progess bar is displayed to the user, indicating what step is being performed (Retrieving, Filtering, etc.) I've been looking at Server Push as a potential solution, but I'm not sure how to implement it for this situation. I suppose the server could send status messages indicating completion of each step in the process before sending the final result set. Am I on the right track? Thank you. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-we...@googlegroups.comjavascript:. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com javascript:. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.- Hide quoted text - - Show quoted text - -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/NjdK5FcnnzUJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: when compile, cannot found the file in jar
I answer myseslf, hope could benefit to others with similar problem. inherits name='hk.gov.ehr.service.tch. als.admin.viewer.AlsAdminViewerWebApp'/ is needed. Otherwise, cannot compile. And, if the dependent gwt app. has entry-point class defined in *.gwt.xml, it will run, that is, two entry-point class will be run, one is your own gwt application, the other is the dependency gwt application entry-point class. In my case, I comment the entry-point in the *.gwt.xml of my dependent gwt application. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/eStft53REXIJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Update progress message box code progresses
If you can't use WebSockets and you don't want to do additional requests to get the server progress you can only guess the progress while your long running server request is active. You would define a reasonable default execution time for a given task and use this for your progress bar to fake progress. You could track the real execution time of the task and when the task completes calculate an average execution time and save it somewhere on the client (local storage, cookie). When the task is started the next time you use the calculated average time instead of the default one and continue to recalculate the average time on task completion. Over time you get a good approximation about how long a task typically takes to complete and your fake progress bar will be more accurate. If the estimated execution time of a task runs out, your progress bar would be at 99% and then you simply wait until your server request completes to show 100%. The time to wait at 99% will be shorter the better the calculated average time will be. -- J. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/MfRBVsZdCecJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Update progress message box code progresses
Oh just read that your single request results in multiple tasks on the server. Progress estimation still works but you have to do it for each step, example: Default execution time: Task 1 (total: 30 sec) - Step 1: 10 sec - Step 2: 5 sec - Step 3: 15 sec You start your Task 1 by doing a single long running server request and your progress bar message will show Step 1, Step 2, Step 3 for the defined durations and stops at 99% in Step 3 and waits for the request to complete. Lets say you wait an additional 9 seconds for the task to complete. So your Task 1 has taken 39 seconds instead of 30 seconds. Next create an average of 30 and 39 = 34,5 seconds and then distribute the additional 4,5 seconds on your three steps and save the new estimated execution times. Over time your progress bar will become more accurate for each step. -- J. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/a411RGUHMW8J. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: How to obfuscate RequestFactory type name, not only the operations ( GWT 2.4 )
I'm also very interested in this; I'd looked briefly going back but didn't find anything either. On 5 September 2012 11:01, zz zhi.z...@gmail.com wrote: Hi, I've searched all over the web, but didn't quite get my question answered. How to obfuscate the type name of my request factory interface that extends RequestFactory? I can only see operations on service are obfuscated. For gwt-rpc, it's enabled by adding below to module file. inherit name='com.google.gwt.user.**RemoteServiceObfuscateTypeName**shttp://code.google.com/p/google-web-toolkit/source/browse/trunk/user/src/com/google/gwt/user/RemoteServiceObfuscateTypeNames.gwt.xml?r=9519' / Is there anything similar required to enable obfuscation for RequestFactory? Regards, zz -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/ggMXO4wGPiEJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: RequestFactory , ServiceLocator and Generic Dao class , NoSuchMethodFound
Hi Yucong, I struggle with the very same problem. Have you solved it? Pleace let me know! -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Loading different panels based on roles (user/amdin)
Probably more elegant ways, but in case it's useful here is how I do it. User authenticates, process returns me object from server with user's full name, access lists, etc. Main menu bar is defined in UI binder but menu elements are defined matching java code. Public menu items are added to menubar. Admin menu items are added after access check: if (Access.hasAccess(me, MyConst.ACCESS_ADMIN)) { configMenuItem.setVisible(true); configMenuItem.setCommand(appConfigCmd); } However, this simply hiding the menu items. The real access control is within the servlets. Any method in a servlet that requires special access checks for that access from the server side session object. IMO - Never trust the client for limiting client access, just hiding forbidden menu items from a user for better UI design. -W On Tuesday, September 4, 2012 2:40:32 AM UTC-5, j3r wrote: I have a docklayout panel as follow north: Header west: MENU center: content When logged, different roles (admin or user) will have a different MENU. Does anyone have a simple say to achieving this. THANKS IN ADVANCED! -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/XOeunULJ8FQJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: How to obfuscate RequestFactory type name, not only the operations ( GWT 2.4 )
I haven't tried it but I suppose you could implement the mapping on the server-side in a ServiceLayerDecorator's resolveRequestFactory method. The problem would be doing it on the client-side (both in the GWT generator and the VM implementation). A hackish way for GWT code could be to do a search/replace on the generated JS code. The proper way would be to add an annotation on the RequestFactory sub-interfaces that the generator and InProcessRequestFactory would use instead of the interface's binary name. Note that the ServiceLayerDecorator would still be needed on the server-side, but maybe we could provide a simple one. Would you mind filing an issue in the tracker (if no one already did it) ? (it's a rather simple patch –change the implementation of getFactoryTypeToken()– so if you really need/want it, feel free to jump ahead and contribute it!) On Thursday, September 6, 2012 2:29:33 PM UTC+2, James Horsley wrote: I'm also very interested in this; I'd looked briefly going back but didn't find anything either. On 5 September 2012 11:01, zz zhi@gmail.com javascript: wrote: Hi, I've searched all over the web, but didn't quite get my question answered. How to obfuscate the type name of my request factory interface that extends RequestFactory? I can only see operations on service are obfuscated. For gwt-rpc, it's enabled by adding below to module file. inherit name='com.google.gwt.user.**RemoteServiceObfuscateTypeName**shttp://code.google.com/p/google-web-toolkit/source/browse/trunk/user/src/com/google/gwt/user/RemoteServiceObfuscateTypeNames.gwt.xml?r=9519' / Is there anything similar required to enable obfuscation for RequestFactory? Regards, zz -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/ggMXO4wGPiEJ. To post to this group, send email to google-we...@googlegroups.comjavascript: . To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com javascript:. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/7LShJ0O9v0MJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Sorry, more spam from me. Do not click any links.
Sorry, more spam from me. Do not click any links. I will be closing this email account down. Regards Paul -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: How to obfuscate RequestFactory type name, not only the operations ( GWT 2.4 )
On Thursday, September 6, 2012 3:58:34 PM UTC+2, Thomas Broyer wrote: Would you mind filing an issue in the tracker (if no one already did it) ? I did a few years ago: http://code.google.com/p/google-web-toolkit/issues/detail?id=5729 It was closed as a duplicate of http://code.google.com/p/google-web-toolkit/issues/detail?id=5394, which is fixed and released in 2.4... but it doesn't really fix 5729. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/K7InVqQH19cJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: How to kill a GWT request which has not yet completed
Paul Stockley pstockley1@... writes: You can cancel RPC requests. Just define your async interface as returning Request. You can then use the returned Request object to cancel the call. If you do this you also need to be aware your server code would throw an IO error due to the connection being closed by the client. I have a general catch point (doUnexpectedFailure) in my derivation of RemoteServiceServlet that just ignores these errors. On Nov 19, 10:19 pm, Gaurav Vaish gaurav.va...@... wrote: RPC request cannot be cancelled. Use the method Request::cancel() with RequestBuilder. Request req = requestBuilder.send(...); req.cancel(); //when needed. -- Happy Hacking, Gaurav Vaishwww.mastergaurav.com On Nov 20, 12:47 am, Sunit Katkar sunitkat...@... wrote: Hi Paul, I have a question: how did you manage to add a catch point for IOException in your derivation of RemoteServiceServlet if the method that sends the response, processPost(), is marked as final, therefore, not possible to override? Can you please explain better or paste here an example of this? Kind regards, Silvestre -- -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: fundamental problems with predictive layout
Most modern browsers are pretty consistent with CSS2 and even CSS3. There are still some differences, but in a few instances where I ran into them, GWT could not help me. Sometimes you have to specify -moz or -webkit specific rules in your CSS file. In some situations (e.g. vertical-align in Firefox vs Chrome) the result is a few pixels off, but only a very good UI designer would even notice. I bet in most of the discussions that you read on CSS issues, people are talking about older versions of IE and Firefox 3. There are many great GWT widgets that insulate you from major browser issues, especially LayoutPanel, PopupPanel, DialogBox, DataGrid. But it's too expensive to try and figure out solutions for minor issues, so they still remain. If fact, I think that trying to be fully cross-browser hurts GWT. GWT's popup panel is a table where every rounded corner is its own cell, even though all modern browsers support border-radius rules. I would love to see GWT drop support for IE -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/iIf2mEQKb0EJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: fundamental problems with predictive layout
Sorry, I meant to say that I would love GWT to drop support for IE 7, an maybe even IE 8, if it allows to greatly simplify the library, reduce the generated code size, significantly reduce compilation time, and speed up development of new features. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/6PfX2p6QaLkJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Not able to use Celltable for a requirement where I need different widgets under one column.
Hi! You should be able to use custom table rendering of a GWT 2.5 cell table to do what you want in your point (1) (extending AbstractCellTableBuilder and implement the buildStandardRowImpl method to put the relevant cell type into the column that alters based upon your condition in your point (2). Then pass that renderer to the cell table, instead of the standard one, using its setTableBuilder method) Information about this is a little sparse, but you could check out: * http://showcase2.jlabanca-testing.appspot.com/#!CwCustomDataGrid , or * GWTinAction edition 2 http://www.manning.com/tacy - a relevant example http://code.google.com/p/gwtinaction2/wiki/DataPresentation(different cells in the Tags column) can be found in code herehttp://code.google.com/p/gwtinaction2/source/browse/trunk/gwtia-ch10-data-presentation-widgets/src/com/manning/gwtia/ch10/client/datagrid/CellDataGridExample.java. (it is still work in progress just now, so missing comments, but should be relatively self explanatory) Hope that helps in some way! //Adam On Sunday, September 2, 2012 11:43:43 AM UTC+2, Saurabh Tripathi wrote: Hi all, I am stuck here with a requirement which is mentioned as follow: 1)A table where one or more (for now just one) column need to have different widgets in editable cell. for example: Class is Plant having property: 'name' and access method: 'String getName()'; Now if(name.equals(true) || name.equals(false){ --- Render CheckBox with respective checked value }else if(name.equals(~)) { - Render ListBox with some predefined items }else { -just render the String. } 2)The cell where we render just the String should be Editable (i.e on click textbox appear for edit), other than this other cells should be non-editable i.e cells for checkbox and listbox should be non editable, You may find this requirement very unusual and I agree it is because here we dealing with raw xml/text kind of metadata. Anyway I have given a lot of effort over this, but I am in a catch 22 situation if somehow I am able to attain 1 condition than I am have editable problem, if somehow I make that up, the valueupdater doesn't seem to work properly At last I am thinking that may be 'CellTable' API was never there for such kind of requirement. So FlexTable could be the answer. Even if it is so there would be a lot of work for me then like - implementing sorting(while click on header), pagination etc, it would be great if some open source library is already there for it. Thanks in advance -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/Xy3F9oc6y0EJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: fundamental problems with predictive layout
I think you're misunderstanding how GWT works. Everything written using GWT compiles down to HTML, CSS, and other native web technologies - there is no difference between panels (LayoutPanels or otherwise) and widgets as far as mapping goes. What seems to be the issue here is that the abstraction provided by GWT can be rather leaky. If you don't understand what the generated code looks like and how it is rendered, then you will likely run into problems. For example, the HTML markup you posted previously contains an empty, (presumably) statically positioned DIV - this is rendered by the browser as an element with zero height. It's not a problem with GWT per se; if anything, the problem is that your expectations don't match those of the framework. It's also worth noting that while GWT offers fairly reliable abstractions for some things (e.g. basic layout, scripted behaviors), it does not eliminate the need to understand how CSS influences presentation. What it does do is provide mechanisms for cleanly separating browser-specific requirements, so that you or someone else can do the hard work just once and have it available for re-use in the future. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/Lmq_d16h2VQJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: compiled file ending with *.htm instead of *.html
I assume it should be possible by extending IFrameLinker, and overriding getCompilationExtension(...) to return .cache.htm. Then define and add your linker as in /com/google/gwt/core/Core.gwt.xml I haven't tried it though, so you may encounter some difficulties (?) On Wednesday, September 5, 2012 4:59:05 PM UTC+2, James wrote: Is there a possible way to pass some parameter to compiler so the compiler can generate javascript file ending with *.htm instead of *.html? So far I just manually edit the generated javascript files and change the file extension. Thanks, James -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/TYqKXJwWTHoJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: How to obfuscate RequestFactory type name, not only the operations ( GWT 2.4 )
On Thursday, September 6, 2012 4:58:31 PM UTC+2, Chris Lercher wrote: On Thursday, September 6, 2012 3:58:34 PM UTC+2, Thomas Broyer wrote: Would you mind filing an issue in the tracker (if no one already did it) ? I did a few years ago: http://code.google.com/p/google-web-toolkit/issues/detail?id=5729 It was closed as a duplicate of http://code.google.com/p/google-web-toolkit/issues/detail?id=5394, which is fixed and released in 2.4... but it doesn't really fix 5729. Well, it obfuscates all type and method names, *but* the RequestFactory name (as it's needed to load the DeobfuscatorBuilder class) -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/2yp-mCXMgfMJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Need help in using CellTable
Hi, I want to populate the celltable with the data that comes from database through RPC call. Can someone give me an example application which demonstrates this. im bit confuse -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/bLsDrViE5v4J. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Compilation Time Performance Improvement
Niraj: IMHO if you want to agile GWT development you want to develop using the GWT devel mode or the GWT2.5 SuperDevMode (haven't tried myself) instead modify java - compile with ant - see the changes. You could ignore devel mode vs production differences when hard - developing, and perform a main compilation only after you finished a day's work or a module and test only for those kind of differences only in production mode. Also, I would try to run the GWT devel mode using your external server application along with the rest of your webapp, instead builtin GWT server. can I know what differences are those you are talking about ? Regards and good look On Thursday, September 6, 2012 1:33:57 AM UTC-3, Niraj Salot wrote: Hi Members, Thanks for all your suggestion/comments. We have already tried below mentioned options to improve the compilation time overall. 1. Memory Settings. -Xmx and Xms 2. localWorkers 3. DraftCompile The question could arise to members mind that why we need to compile a lot but the thing is :- while doing the development work If we use the development mode provided by GWT , sometimes happens that the end output in production mode is diff. then development mode. So we can not trust that what is shown in development mode will be same in production mode. Hence developers compile their code on their machine and test it before putting something on main server. The issue is developers machine have overall RAM of 4 GB only. And when Jboss , Eclipse and Compilation of GWT runs , It is very very slow. So for even the small changes , developers needs to compile , build the WAR and then deploy to check that his code is working ok or not. I am looking for some option which could allow me to pre-compile GWT modules. So that If some GWT module is not changed and when I compile the main module , that GWT module should not compile as it is not changed at all. I am not still not getting how to use the concept of *.gwtar files which is mentioned in our discussion. Would appreciate if someone can provide more details on the same. Thanks,Niraj. On Tuesday, 4 September 2012 11:40:19 UTC+5:30, Niraj Salot wrote: Hi Members, We are using GWT Version 2.4 in our current project. On server side, we are using Spring Custom JDBC framework. We are using Maven as our Build Tool. The application is getting deployed on JBOSS 7 Server. Currently we have everything in one single Eclipse Project. Means one Application.gwt.xml file and one ApplicationContext.xml for spring. We have around 2000 Java files out of which around 1500 are for GWT related source files. The project is still growing with more source files. We are fine with timings of Java to Javac [class file] Compilation time. But when It comes to Java to JavaScript , It is a issue. We have used all hacks mentioned in the GWT Forum. Like. 1. Compiling for only one Local 2. Compiling for only one Browser But still the compilation is taking 4-6 minutes.. OR even 7 minutes some times. With this question, I would like to know the options available to improve the same. We are thinking to Split the Project like this WAY: - Module 1 (JAR Build) - Module 2 (JAR Build) - Module Main (WAR Build). This would contain Application.gwt.xml file which would inherit Module 1 Module 2. Now Question comes: *1) Will this help us in Improving the compilation time?* *2) IF we change only Module 2 and then compile Module Main, will GWT still compile Module 1 as it is inherited by Module Main?* Please share your views on above scenario. We have even tried out GWT 2.5 option but no help in performance improvements. Thanks, Niraj Salot. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/vN3pg8mTTlcJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Nasty overlay types restrinction : Only one JavaScriptObject type may implement the methods of an interface
Hi all. I'm writing a lot of GWT overlay types for my new project YUIGWT - http://code.google.com/p/yuigwt/. I'm creating a nice and rich java hierarchy of overlay types there. Today I discovered that it is not good to let overlay types (extends JavaScriptObject implement interfaces because it seems that for a certain interface, no more than one overlay type can implement its methods. The error in question is pasted below, but this arrises a big question for me: While I understand perfectly what the error means, I would really appreciate if somebody can explain me the reasons behind this nasty restriction ? ?? [ERROR] [org.sgx.yuigwt.YuiGwtTestOnline] - Line 9: Only one JavaScriptObject type may implement the methods of an interface that declared methods. The interface (org.sgx.yuigwt.yui.yql.api.YQLQueryResult) is implemented by both (org.sgx.yuigwt.yui.yql.api.desc.DescResult) and (org.sgx.yuigwt.yui.yql.api.wheather.forecast.WheatherForecastResult) Thanks in advance. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/bVE-agIAe-kJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Nasty overlay types restrinction : Only one JavaScriptObject type may implement the methods of an interface
It's because they don't support polymorphism with overlay types. The same reason all methods are final and cannot be overridden in sub classes of a JSO. On Thursday, September 6, 2012 2:22:16 PM UTC-4, Sebastián Gurin wrote: Hi all. I'm writing a lot of GWT overlay types for my new project YUIGWT - http://code.google.com/p/yuigwt/. I'm creating a nice and rich java hierarchy of overlay types there. Today I discovered that it is not good to let overlay types (extends JavaScriptObject implement interfaces because it seems that for a certain interface, no more than one overlay type can implement its methods. The error in question is pasted below, but this arrises a big question for me: While I understand perfectly what the error means, I would really appreciate if somebody can explain me the reasons behind this nasty restriction ? ?? [ERROR] [org.sgx.yuigwt.YuiGwtTestOnline] - Line 9: Only one JavaScriptObject type may implement the methods of an interface that declared methods. The interface (org.sgx.yuigwt.yui.yql.api.YQLQueryResult) is implemented by both (org.sgx.yuigwt.yui.yql.api.desc.DescResult) and (org.sgx.yuigwt.yui.yql.api.wheather.forecast.WheatherForecastResult) Thanks in advance. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/yRfzknalyioJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Compilation Time Performance Improvement
Instead of compiling one permutation at a time, there is an option to compile multiple permutations at the same time by mutli-process. Here is the parameter I used in the Ant build.xml file (sorry, I don't use maven), all you needed to add -localWorkers within gwtc target tag: target name=gwtc depends=javac description=GWT compile to JavaScript (production mode) java failonerror=true fork=true classname=com.google.gwt.dev.Compiler classpath pathelement location=src / path refid=project.class.path / pathelement location=C:/gwt-2.5.0.rc1/validation-api-1.0.0.GA.jar / pathelement location=C:/gwt-2.5.0.rc1/validation-api-1.0.0.GA-sources.jar / /classpath !-- add jvmarg -Xss16M or similar if you see a StackOverflowError -- !-- jvmarg value=-Xmx256M/ -- jvmarg value=-Xmx1024M / arg line=-war / arg value=war / !-- Additional arguments like -style PRETTY or -logLevel DEBUG -- arg line=${gwt.args} / !-- Number of process to compile -- arg value=-localWorkers / arg value=2 / arg value=-optimize / arg value=9 / arg value=-strict / !-- arg value=-XenableClosureCompiler / -- arg value=mta.itrac.Itrac / /java /target -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/hhytunHdDYsJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Nasty overlay types restrinction : Only one JavaScriptObject type may implement the methods of an interface
We hit the problem while creating our libraries. Extending JavaScriptObject directly is not good because it restricts what your possibilities. So we used composition instead, giving us more power. So instead of public class MyClass extends JavaScriptObject{ protected MyClass(){ } } maybe you should consider something like public class MyClass{ protected JavaScriptObject nativePeer; public MyClass(){ nativePeer = createNativeJsoObject(); } } The the public API of MyClass will delegate to the JSO. this will give you a bit more work but the API will me more flexible and your users will thank you :). Cheers, Alain 2012/9/6 Sebastián Gurin sebastigu...@gmail.com Hi all. I'm writing a lot of GWT overlay types for my new project YUIGWT - http://code.google.com/p/yuigwt/. I'm creating a nice and rich java hierarchy of overlay types there. Today I discovered that it is not good to let overlay types (extends JavaScriptObject implement interfaces because it seems that for a certain interface, no more than one overlay type can implement its methods. The error in question is pasted below, but this arrises a big question for me: While I understand perfectly what the error means, I would really appreciate if somebody can explain me the reasons behind this nasty restriction ? ?? [ERROR] [org.sgx.yuigwt.YuiGwtTestOnline] - Line 9: Only one JavaScriptObject type may implement the methods of an interface that declared methods. The interface (org.sgx.yuigwt.yui.yql.api.YQLQueryResult) is implemented by both (org.sgx.yuigwt.yui.yql.api.desc.DescResult) and (org.sgx.yuigwt.yui.yql.api.wheather.forecast.WheatherForecastResult) Thanks in advance. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/bVE-agIAe-kJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Nasty overlay types restrinction : Only one JavaScriptObject type may implement the methods of an interface
On Thursday, September 6, 2012 10:05:02 PM UTC+2, nino wrote: We hit the problem while creating our libraries. Extending JavaScriptObject directly is not good because it restricts what your possibilities. So we used composition instead, giving us more power. So instead of public class MyClass extends JavaScriptObject{ protected MyClass(){ } } maybe you should consider something like public class MyClass{ protected JavaScriptObject nativePeer; public MyClass(){ nativePeer = createNativeJsoObject(); } } The the public API of MyClass will delegate to the JSO. this will give you a bit more work but the API will me more flexible and your users will thank you :). I once worked around this limitation by providing methods that simply cast the object into another JSO type. Example: https://code.google.com/p/gwt-in-the-air/source/browse/trunk/src/net/ltgt/gwt/air/core/client/filesystem/FileStream.java The native FileStream implements the IDataInput and IDataOutput interfaces (in ActionScript, which translates to having all the same methods in JavaScript), the FileStream cannot implement IDataInput / IDataOutput interfaces (the problem we're talking about), and in Java I cannot use multiple inheritance either. Solution: FileStream has a forInput() method that simply cast()s it to a IDataInput (a JSO type), and similarly for IDataOutput with a forOutput() method. In other cases, the methods could be called asXxx() (as in see this object as an Xxx) -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/XI0F9MDMUH4J. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Compilation Time Performance Improvement
Have you considered using a SSD instead of a HD? I've cut my compile times dramatically that way. On Thu, Sep 6, 2012 at 12:08 PM, Chak Lai chaklam@gmail.com wrote: Instead of compiling one permutation at a time, there is an option to compile multiple permutations at the same time by mutli-process. Here is the parameter I used in the Ant build.xml file (sorry, I don't use maven), all you needed to add -localWorkers within gwtc target tag: target name=gwtc depends=javac description=GWT compile to JavaScript (production mode) java failonerror=true fork=true classname=com.google.gwt.dev.Compiler classpath pathelement location=src / path refid=project.class.path / pathelement location=C:/gwt-2.5.0.rc1/validation-api-1.0.0.GA.jar / pathelement location=C:/gwt-2.5.0.rc1/validation-api-1.0.0.GA-sources.jar / /classpath !-- add jvmarg -Xss16M or similar if you see a StackOverflowError -- !-- jvmarg value=-Xmx256M/ -- jvmarg value=-Xmx1024M / arg line=-war / arg value=war / !-- Additional arguments like -style PRETTY or -logLevel DEBUG -- arg line=${gwt.args} / !-- Number of process to compile -- arg value=-localWorkers / arg value=2 / arg value=-optimize / arg value=9 / arg value=-strict / !-- arg value=-XenableClosureCompiler / -- arg value=mta.itrac.Itrac / /java /target -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/hhytunHdDYsJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- -- A. Stevko === If everything seems under control, you're just not going fast enough. M. Andretti -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Compilation Time Performance Improvement
Oh, and if you have to use an external device, use esata rather than usb. while usb has higher burst speeds, esata has much higher sustained transfer speeds. On Thu, Sep 6, 2012 at 3:35 PM, Andy Stevko andy.ste...@gmail.com wrote: Have you considered using a SSD instead of a HD? I've cut my compile times dramatically that way. On Thu, Sep 6, 2012 at 12:08 PM, Chak Lai chaklam@gmail.com wrote: Instead of compiling one permutation at a time, there is an option to compile multiple permutations at the same time by mutli-process. Here is the parameter I used in the Ant build.xml file (sorry, I don't use maven), all you needed to add -localWorkers within gwtc target tag: target name=gwtc depends=javac description=GWT compile to JavaScript (production mode) java failonerror=true fork=true classname=com.google.gwt.dev.Compiler classpath pathelement location=src / path refid=project.class.path / pathelement location=C:/gwt-2.5.0.rc1/validation-api-1.0.0.GA.jar / pathelement location=C:/gwt-2.5.0.rc1/validation-api-1.0.0.GA-sources.jar / /classpath !-- add jvmarg -Xss16M or similar if you see a StackOverflowError -- !-- jvmarg value=-Xmx256M/ -- jvmarg value=-Xmx1024M / arg line=-war / arg value=war / !-- Additional arguments like -style PRETTY or -logLevel DEBUG -- arg line=${gwt.args} / !-- Number of process to compile -- arg value=-localWorkers / arg value=2 / arg value=-optimize / arg value=9 / arg value=-strict / !-- arg value=-XenableClosureCompiler / -- arg value=mta.itrac.Itrac / /java /target -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/hhytunHdDYsJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- -- A. Stevko === If everything seems under control, you're just not going fast enough. M. Andretti -- -- A. Stevko === If everything seems under control, you're just not going fast enough. M. Andretti -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Meteor DDP - or similar - with GWT?
I used it in a past project and it was simple and easy enough. Seems also to be relatively up to date. There is also atmosphere that carries a gwt client side module with also out of the box experimental support for websockets and much more: https://github.com/Atmosphere/atmosphere/tree/master/modules -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/8Pow80mOjW8J. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Best MVP framework right now?
Hi, already know about gwtp, mvp4g, guit, GWT MVP, etc. But I have been some time outside from GWT world :( so now I am returning to this beatiful framework again and I would to know which have been your experiences, wich mvp framework do you recommend to use in this days? Best regards. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/muuBMaT1-rIJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: fundamental problems with predictive layout
Hi Abraham, the only empty DIV I see is the label, and it's empty because the label does not contain text. Do you agree to the statement posted in this thread that the GWT's layout panels should be used for the overall page layout (defining the main areas of a page) and that the small layouts (widgets and so on) should be positioned with CSS? Maybe you misunderstood my posting: I also said that GWT compiles to HTML and CSS. But it produces different compilations for different browsers. In contrast, everything you put directly into the element attributes will go unchanged into the client. However, even Google states that in strict mode many panels do not work as expected, e. g. HorizontalPanel, which should be replaced by a FlowPanel where all children should float to the left (which does'nt work in some cases). The goal was predictive layout, but it seems to be more like trial and error, at least in some cases. Magnus -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/2wxQpkENIM4J. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: fundamental problems with predictive layout
Hi Andrei! There are many great GWT widgets that insulate you from major browser issues, especially LayoutPanel, PopupPanel, DialogBox, DataGrid. But it's too expensive to try and figure out solutions for minor issues, so they still remain. Yes, they do. I built my app with these panels and it works great. I also think that it's ok if you have to try and figure out solutions for minor issues. But I would like to have a general rule how to integrate these minor solutions into the overall layout, e. g. into a surrounding LayoutPanel? For example, the solution posted by Jens works perfectly in isolation, but when I put it into a LayoutPanel it didn't work at all. Magnus -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/wZLHC3bWqocJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
[gwt-contrib] fix Nullpointer in CellWidget.onBrowserEvent (issue1820805)
LGTM http://gwt-code-reviews.appspot.com/1820805/ -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] Re: Issue 7381: 2 RequestFactory with 2 differents Proxy on the same domain class (issue1712803)
https://gwt-code-reviews.appspot.com/1712803/diff/2001/user/src/com/google/web/bindery/requestfactory/vm/impl/Deobfuscator.java File user/src/com/google/web/bindery/requestfactory/vm/impl/Deobfuscator.java (right): https://gwt-code-reviews.appspot.com/1712803/diff/2001/user/src/com/google/web/bindery/requestfactory/vm/impl/Deobfuscator.java#newcode122 user/src/com/google/web/bindery/requestfactory/vm/impl/Deobfuscator.java:122: private MapString, ListString merge(MapString, ListString domainToClientType1, On 2012/09/06 19:21:57, skybrian wrote: Hmm. Thanks, but I'm still rather lost and need some context, probably because I don't understand the RequestFactory wire protocol. I'll try to shed some light (though ti has nothing to do with the wire protocol actually). To be specific, what is a domain? Domain types are the kind of objects pointed to by @ProxyFor/@ProxyForName annotations on proxies (which are here called client types) What's an example key to this map? In the MobileWebApp sample, that would be com.google.gwt.sample.mobilewebapp.server.domain.Task (a domain type's binary name). What is the value? The list of client types mapped to that domain type, ordered from the most to the least specific. That is, the proxies with a @ProxyFor or @ProxyForName pointing to that domain type, and all their super-interfaces. In the MobileWebApp sample, for the Task domain type, the values would be (in order) com.google.gwt.sample.mobilewebapp.shared.TaskProxy and com.google.web.bindery.requestfactory.shared.EntityProxy. But you can map several proxies to the same domain type, in which case you'd have more than that. Why would we have multiple values for the same key? What is this map for, anyway? The map is used when constructing the response. Let's say I have an Employee and Manager (extends Employee) domain types, and an EmployeeProxy with @ProxyFor(Employee.class). Some method (a service method, or a getter in another bean) has a return type of Employee on the server-side (mapped as EntityProxy on the client-side). The value could very-well be a Manager in practice. This is where the map comes into play: which client type should be used? RF will take the returned value's class (say, Manager) and looks for a corresponding proxy type that extends EmployeeProxy (because the client method's return type is EmployeeProxy). First case: there's no entry with Manager as key, so RF looks at the superclass. It finds an entry for Employee, with values EmployeeProxy and EntityProxy. EmployeeProxy matches, so let's use that. Second case: there's a ManagerProxy extends EmployeeProxy with @ProxyFor(Manager.class), so RF will find an entry with values ManagerProxy, EmployeeProxy and EntityProxy. ManagerProxy extends EmployeeProxy (the type we look for), so let's use that: the client will receive/reconstruct a ManagerProxy. Third case: there's a ManagerProxy with no relationship to EmployeeProxy, and with @ProxyFor(Manager.class). RF will find an entry for Manager with values ManagerProxy and EntityProxy. Nothing matches EmployeeProxy, so let's look at the superclass. There's an entry for Employee with an exact match (EmployeeProxy). There's also a fourth case: you have some heavy-weight domain object with many properties, so you map it with 2 proxies: one for all the properties, and a lightweight one with only a few properties (used for lists of such proxies, e.g. in search results or in a value picker). Let's say I have a Message domain type (with subject, date, recipient, sender and body properties), and I map it with 2 proxies: MessageProxy with all same properties and MessageProxyLite mapping only subject, date and sender (with no inheritance relationship between both proxies). The entry in the map for Message will have values MessageProxy, MessageProxyLite and EntityProxy. And of course, all those cases can be mixed and matched. https://gwt-code-reviews.appspot.com/1712803/ -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] Re: Issue 7381: 2 RequestFactory with 2 differents Proxy on the same domain class (issue1712803)
Thanks Thomas, that helps. (I think serverTypeToProxyTypes might be a better name.) I was curious about how often this code it gets run. It looks like it happens on every RPC call though this path: SimpleRequestProcessor.processInvocationMessages() - ResolverServiceLayer.updateDeobfuscator() - Deobfuscator.Builder.merge() I would expect that once it's warmed up, most of the time there is no actual change to the map (the classes are already in there), and yet for each (key,value) pair in the map of all server types, it will build a new TreeSet, merge the proxy types that are already there (using a pretty slow comparator), and make it immutable again, on every RPC call. This seems kind of inefficient. Is there something we can do to make the common case fast? - Brian On Thu, Sep 6, 2012 at 2:11 PM, t.bro...@gmail.com wrote: https://gwt-code-reviews.appspot.com/1712803/diff/2001/user/src/com/google/web/bindery/requestfactory/vm/impl/Deobfuscator.java File user/src/com/google/web/bindery/requestfactory/vm/impl/Deobfuscator.java (right): https://gwt-code-reviews.appspot.com/1712803/diff/2001/user/src/com/google/web/bindery/requestfactory/vm/impl/Deobfuscator.java#newcode122 user/src/com/google/web/bindery/requestfactory/vm/impl/Deobfuscator.java:122: private MapString, ListString merge(MapString, ListString domainToClientType1, On 2012/09/06 19:21:57, skybrian wrote: Hmm. Thanks, but I'm still rather lost and need some context, probably because I don't understand the RequestFactory wire protocol. I'll try to shed some light (though ti has nothing to do with the wire protocol actually). To be specific, what is a domain? Domain types are the kind of objects pointed to by @ProxyFor/@ProxyForName annotations on proxies (which are here called client types) What's an example key to this map? In the MobileWebApp sample, that would be com.google.gwt.sample.mobilewebapp.server.domain.Task (a domain type's binary name). What is the value? The list of client types mapped to that domain type, ordered from the most to the least specific. That is, the proxies with a @ProxyFor or @ProxyForName pointing to that domain type, and all their super-interfaces. In the MobileWebApp sample, for the Task domain type, the values would be (in order) com.google.gwt.sample.mobilewebapp.shared.TaskProxy and com.google.web.bindery.requestfactory.shared.EntityProxy. But you can map several proxies to the same domain type, in which case you'd have more than that. Why would we have multiple values for the same key? What is this map for, anyway? The map is used when constructing the response. Let's say I have an Employee and Manager (extends Employee) domain types, and an EmployeeProxy with @ProxyFor(Employee.class). Some method (a service method, or a getter in another bean) has a return type of Employee on the server-side (mapped as EntityProxy on the client-side). The value could very-well be a Manager in practice. This is where the map comes into play: which client type should be used? RF will take the returned value's class (say, Manager) and looks for a corresponding proxy type that extends EmployeeProxy (because the client method's return type is EmployeeProxy). First case: there's no entry with Manager as key, so RF looks at the superclass. It finds an entry for Employee, with values EmployeeProxy and EntityProxy. EmployeeProxy matches, so let's use that. Second case: there's a ManagerProxy extends EmployeeProxy with @ProxyFor(Manager.class), so RF will find an entry with values ManagerProxy, EmployeeProxy and EntityProxy. ManagerProxy extends EmployeeProxy (the type we look for), so let's use that: the client will receive/reconstruct a ManagerProxy. Third case: there's a ManagerProxy with no relationship to EmployeeProxy, and with @ProxyFor(Manager.class). RF will find an entry for Manager with values ManagerProxy and EntityProxy. Nothing matches EmployeeProxy, so let's look at the superclass. There's an entry for Employee with an exact match (EmployeeProxy). There's also a fourth case: you have some heavy-weight domain object with many properties, so you map it with 2 proxies: one for all the properties, and a lightweight one with only a few properties (used for lists of such proxies, e.g. in search results or in a value picker). Let's say I have a Message domain type (with subject, date, recipient, sender and body properties), and I map it with 2 proxies: MessageProxy with all same properties and MessageProxyLite mapping only subject, date and sender (with no inheritance relationship between both proxies). The entry in the map for Message will have values MessageProxy, MessageProxyLite and EntityProxy. And of course, all those cases can be mixed and matched. https://gwt-code-reviews.appspot.com/1712803/ -- http://groups.google.com/group/Google-Web-Toolkit-Contributors