I am developing a GWT application using GWT, SmartGWT and GWTP. At the beginning I run the development mode with IE 8 and it works fine. But when I run the dev mode with FF, some Click Events are not response. I don't know if this happens because I use SmartGWT or GWTP. Could anyone tell me what's happening? Thanks.
Here is the code for one the not responding ClickEvent on the SmartGWT listgrid:
navigationListGrid.addRecordClickHandler(new RecordClickHandler() {
#Override
public void onClick(ClickEvent event) {
Record record = event.getRecord();
PlaceRequest myRequest = new PlaceRequest(record.getAttributeAsString("place"));
placeManager.revealPlace(myRequest);
}
});
Firefox releases updates rapidly, and their plugin design means that the GWT Dev Mode plugin must be modified every time a new release is made, the recompiled, and re-released. Long before an official release is made, Alan Leung on the GWT team posts a link to the next version. I've been using FF9 for some time, with the plugin provided on this post https://groups.google.com/d/msg/google-web-toolkit/jZ02n9v9-H4/87XWXmjcCoAJ. If you still have problems with that plugin and FF9, add a comment on that thread with a code sample to reproduce it so the plugin bug can be investigated before the official version is released.
Chrome is actually significantly slower than most other browsers in Dev mode (compiled javascript will probably be faster in Chrome though) and there are bugs that the team is unable to keep up with http://code.google.com/p/google-web-toolkit/issues/detail?id=5778#c65 - the recomendation from project member Thomas Broyer is to use firefox instead.
If you also have problems with Firefox with compiled javascript, that may suggest a bug with GWT, but in production mode, GWT should be fully compatible with the latest Firefox versions.
GWT is not compatible with all Firefox Versions. Currently, it can only run on Firefox prior to Firefox 6!
Related
We have developed an eclipse rcp application using 3.5 and are trying to move it to 4.2.1.
It is a simple RCP application with a view. On doing the basics and launching it I found that the setShellStyle(SWT.MIN) is not working anymore. Since it was a single view application, it didnt require re-sizing, hence we had disabled re-sizing using this API.
But with the new Eclipse (Eclipse 4.2.1), the re-size/maximize button is enabled even when this method is called. I have verified that other APIs called from here work (other than this I used setShowStatusLine(false) and setShowCoolBar(false).
Is this a known problem with Eclipse 4 or whether there is a different API to get this functionality working with this.
I appreciate any kind of help I can get here.?
Long time reader, first time asking a question.
Most of my development work has been in .NET using Visual Studio. Recently I took over maintenance of a website built on PHP and downloaded NetBeans as an IDE.
NetBeans has a very nice CSS property wizard for HTML projects that highlights the CSS rules in use for a particular element and lets you edit the rules directly. However, this doesn't appear to be available for PHP projects, even for pure HTML files within the project. Is that correct, or am I just missing some configuration? I can't seem to find any confirmation either way in the documentation or forums. (It would be unfortunate if it didn't work... it's a really useful feature.)
Thanks,
Terry
If you are referring to the visual CSS editing support that works with Google Chrome and the WebKit browser embedded in NetBeans, then this feature will be available for PHP projects in the upcoming NetBeans 7.4 release. See also this blog post: https://blogs.oracle.com/netbeanswebclient/entry/html5_development_with_java_ee
Hope this helps,
Petr
I've recently gone through the following link:
https://developers.google.com/web-toolkit/release-notes#Release_Notes_Current
There's a point under title : Breaking Changes and Other Changes of Note
GWT no longer supports ChromeFrame. The implementation caused more bugs than it solved.
Does this mean that Chrome browser won't support GWT 2.5? Or am I misunderstood? Can anyone explain this?
Thanks in advance.
EDIT Google confirms an error in the release notes: https://groups.google.com/d/msg/google-web-toolkit-contributors/wzilCaLySCU/aYMwD2zzOrsJ
This is probably related to http://code.google.com/p/google-web-toolkit/issues/detail?id=6665
Technically, there should be nothing special to support ChromeFrame (which is not the same as Chrome, so to answer your question: yes you're misunderstanding that statement from the release notes).
Actually, I believe the release notes are wrong: GWT 2.4 had issues with ChromeFrame (actually, when it was installed but disabled), and this has been fixed in 2.5 (see link to issue above).
I'll get in touch with Google to know more about it and possibly have the release notes fixed (if the above is right). Edit: done (will contact some directly by mail if needed).
ChromeFrame is a plugin for Internet Explorer that uses Chrome's rendering and JavaScript engine instead of IE's equivalents. So this statement does not refer to the standalone Chrome browser (and it would be strange indeed if it did).
ChromeFrame is a plugin for other browsers than Chrome
I wonder if there is a way to perform a step-by-step debugging of the compiled GWT code, in order to determine how some events are being fired.
The interest I have on this is that I'm using SmartGWT, and for some reason the click events on their components propagate to pop up windows that occupy the same position. However this only happens in Mobile Safari.
Even more interesting it only happens with smartGWT version of onClick and not with the plain GWT onClick.
Mostly a hack for now, but I suppose it'll work (you'll have to recompile your app though):
First, compile a recent GWT from trunk: https://developers.google.com/web-toolkit/makinggwtbetter#workingoncode
Then recompile your app with source maps enabled: http://code.google.com/p/google-web-toolkit/wiki/SourceMaps
Follow the steps in the comments of this wiki page to be able to use SourceMaps in Chrome, then re-deploy your app
Get Chrome on the Dev channel: http://www.chromium.org/getting-involved/dev-channel
Use http://www.iwebinspector.com/ to start Mobile Safari with remote debugging and then connect to it from your Chrome desktop: http://www.webkit.org/blog/1620/webkit-remote-debugging/
Finally, enable source maps in Chrome so you'll see your Java code in the Web Inspector!
See http://www.youtube.com/watch?v=-xJl22Kvgjg for a preview of the future of debugging with GWT, that will allow this kind of things in a much less hackish way in the near future.
I don't know if there is a nice way to debug compiled javascript GWT code, but why do you need it?
For described purpose it's better to use GWT development mode with debugging options. You can add the following parametres e-Xdebug -Xrunjdwp:transport=dt_socket,address={PORT},server=y,suspend=n to the development mode running command, it will give an opportunity to add breakpoints to the cliend side GWT/SmardGWT source code. Then for debugging you should connect to port specified in parametres from your java IDE.
Debugging GWT https://developers.google.com/web-toolkit/doc/latest/DevGuideCompilingAndDebugging
I am using eclipse to develop an extjs based application with apache tomcat v6, and it seems to me like that the tool is not the best because sometimes (often) I have to restart the server to view changes in the browser even so I do small changes (js file). If you can advice me which tool is more convenient for Ext-Js (4.x) or tricks for eclipse.
You need to set up a way to disable page caching. You can do this through browser development tools (IE Developer Tools, Firebug, Chrome Development Tools, etc.) or through your server configuration.
In my work, we use a Java class that takes a list of JavaScript/CSS files and appends the request time as a Unix date to prevent the browser from caching. It then inserts the script tags into the page so the output looks like this:
<script type="text/javascript" src="app.js?_cb=20120319123456"></script>
So everything you access a page, the _cb param updates and it gets the new version of the file every time.
If you're already doing something like this and it isn't working, I would recommend switching to NetBeans. That's what I use and it works great.
If you're using MVC - which is brand-new feature of Ext JS 4 - you'll never need to restart or publish changes to application server. It always gets the updated file from file system.