Re: writing doctype and the head section
GWT javascript code is hosted inside a html page, so you can't write the doctype and head section. What you could do though is write a servlet (or jsp etc) that generates the host page, giving you complete programatical control over the html document contents rather than using a static template. -- 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: Development mode - refresh is not enough to see my changes!
When using development mode in Eclipse, there is a reload web app button in the development mode tab of the GWT plugin. When I have made changes to the app, I often have to hit the reload web app button and then refresh in the browser. This is very quick. I don't know how Development Mode works with IDEA, but I will take a guess that you get something similar to the Hosted Mode in GWT pre 2.0. Is there not a reload/refresh option somewhere there? -- 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-tool...@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.
Correct GWT 2.0 way to replace calls to deprecated StyleInjector.injectStylesheet and StyleInjector.setContents
I have an existing GWT project that uses StyleInjector.injectStylesheet and StyleInjector.setContents from the GWT Incubator. I have upgraded to GWT 2.0 and see that StyleInjector is now an official GWT class. Unfortunately the two methods I am using (injectStylesheet and setContents) are now deprecated and I am not sure how best to replace their usage. On initial display of the page I call StyleInjector.injectStylesheet to inject some CSS styles with values specific to the data displayed. At a later point when I refresh the data I need to change the CSS style values, so I call StyleInjector.setContents which replaces the styles I originally created. I may end up replacing the CSS styles thousands of times in the course of a user session. The none deprecated methods inject, injectAtStart and injectAtEnd do not seem to do a replace. Is that correct? What am I supposed to do? -- 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-tool...@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.
Graceful shutdown of development mode with Eclipse plug in for GWT 2.0?
Some of my session objects implement HttpSessionBindingListener so that they can do stuff on valueUnbound when the session ends (such as when the servlet container is shutdown). In the old hosted mode this worked fine as closing the hosted mode window caused a graceful shutdown of jetty. With the GWT 2.0 plugin for Eclipse I can only see an option in development mode to Terminate which is not a graceful shutdown and does not cause valueUnbound to be fired. Am I missing something? -- 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-tool...@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: Graceful shutdown of development mode with Eclipse plug in for GWT 2.0?
On Dec 18, 11:20 am, Yozons Support on Gmail yoz...@gmail.com wrote: This would be nice for those who have a robust server side system in place. Right now, we're definitely testing how the app reacts to a hard crash. :) One thing I found is that using the reload web server option in the eclipse Development Mode view does properly trigger valueUnbound. Our java servlets communicate with Windows COM objects using J-Interop and Google Protocol Buffers. When the web app gets a hard crash, it takes a little while for the COM objects to realise and kill themselves. When the session is closed gracefully we get a chance to tell the COM objects to close. At the moment I am doing a reload web server followed by a Terminate so that things are cleaned up reasonably well. -- 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-tool...@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.
ScrollTable with frozen column?
Out of the box ScrollTable does not seem to support frozen column(s). Has anyone implemented that? -- 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-tool...@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: PopupPanel.center() not working in Firefox 3.5.5
Why aren't you using GWT provided Window.getClientWidth() and Window.getClientHeight()? -- 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-tool...@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: incubator's PagingScrollTable(pagination+Sorting)
On Nov 16, 3:27 pm, Davis Ford davisf...@zenoconsulting.biz wrote: Hi, here's a blog post I made that shows how I'm using the widget. It may help if you are still looking for a solution. http://zenoconsulting.wikidot.com/blog:17 http://zenoconsulting.wikidot.com/blog:17Regards, Davis Very nice article. Have you tried adding fixed columns to PagingScrollTable? -- 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-tool...@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=.
Re: Calling listbox.clear() is very slow in IE for large list boxes
That is what I ended up doing. I remove and recreate the list box rather than calling clear() and the performance is fine. The remove performance seems to remain constant regardless of the number of entries in the list. I am not sure there is anything gwt can do about this. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Calling listbox.clear() is very slow in IE for large list boxes
Calling listbox.clear() is very slow in IE for large list boxes when compared to every other browser. I have several list boxes on a page that may contain several thousand items each. I need to repopulate these on occasion. It seemed simple just to call listbox.clear() and then go through my data load logic. This works absolutely fine in Firefox, Chrome and Safari but performs very badly in IE. Is this just IE being slow as usual? Clearing a listbox seems like a trivial task and should be fast, right? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
