Related posts:

1. SmartGWT portal is getting ready I’m sure by now the news of the new GWT...

Related posts:

1. a couple of GWT calendar projects – gwt-scheduler and gwtsimiletimeline I just looked over the list of gwt projects hosted...

No related posts.

I personally have no idea whether paging is better than live grids for usability – none of the rich UI desktop systems I’ve worked on used paging (10000 or even 100000 rows is not too bad for the user if responsiveness is good and sorting/drilling is organized well), however none of the web apps I’ve developed or used had more than 200 rows per “page”.  I think the key is in the UI organization around the grid and visual responsiveness of components…

Related posts:

1. Ext-GWT (GXT) releases preview of new Grid widget Darrell from ExtJs just released a preview of the new...

There is now also a little portal example that is getting integrated into SmartClient and SmartGWT – here is the forum post announcement and the demo after the break.

Related posts:

1. Ext GWT releases preview with grids, portal, webdesktop support A new preview release of Ext GWT (1.1. Alpha 2)...
2. Open Flash Charts for GWT There is now a wrapper project hosted on Google Code...
3. gwtapps – desktop and messenger examples I really like the GWT Apps book by Ryan Dewsbury...

Related posts:

1. gwtapps – desktop and messenger examples I really like the GWT Apps book by Ryan Dewsbury...
2. Ext-GWT 1.1 is out There is a new version (1.1) of Ext-GWT library available...

what does the code look like you might ask? Here you go:

GWT.runAsync(new RunAsyncCallback() {

public void onFailure(Throwable caught) {
callback.onFailure(caught);
}

public void onSuccess() {
callback.onSuccess(onInitialize());
}
});

where onInitialize() can have whatever your complex nature desires.

Haven’t tried this particular build yet, but looking forward to, in a few days.

Related posts:

1. GWT is going non-monolithic (runAsync) There have been many discussions on GWT forums about the...

It’s a very early version right now, but I think is worth following. It’s licensed under Apache 2.0.

Related posts:

1. gwt-incubator – what’s in it? gwt-incubator project is basically a gwt playpen area. It has...
2. GWT wrapper for Dojo (Tatami) v. 1.2 is out There is a new drop of Tatami project available ....

One thing I wish for is that Ext-GWT was better interoperable with native GWT widgets/layouts. But maybe it’s just wishful thinking on my part, since I also understand the complexity of getting RIA stuff work smoothly across the browsers and various hacks developers put into place to deal with cross browser issues.

Related posts:

1. gwt-incubator – what’s in it? gwt-incubator project is basically a gwt playpen area. It has...

1. First things first, I don’t use GWT’s embedded tomcat server and rely on developing/debugging GWT apps with the -noserver option. This way I can use whatever server technology (Jetty+Spring is my favorite) I like sacrificing very little of what GWT offers.
2. My maven pom.xml has a profile that I use to compile all my GWT code and setup my server environment for hosted GWT mode development. Here it is:


<profile>
<id>gwt</id>
<build>
<plugins>
<plugin>
<artifactId>maven-antrun-plugin</artifactId>
<executions>
<execution>
<phase>compile</phase>
<configuration>
<tasks>
<path id="compile.class.path">
<dirset dir="${basedir}">
<include name="src/main/java"/>
</dirset>
<path refid="maven.compile.classpath"/>
</path>
<!--property name="compile_classpath" refid="compile.class.path"/>
<echo message="compile classpath: ${compile_classpath}"/>
<parallel threadCount="2" failonany="yes" -->
<java classname="com.google.gwt.dev.GWTCompiler"
fork="true"
failonerror="true"
maxmemory="1024m">
<classpath refid="compile.class.path"/>
<arg value="-out"/>
<arg value="${project.build.directory}/www"/>
<arg value="com.company.module1.gwt.Module1"/>
</java>
<java classname="com.google.gwt.dev.GWTCompiler"
fork="true"
failonerror="true"
maxmemory="1024m">
<classpath refid="compile.class.path"/>
<arg value="-out"/>
<arg value="${project.build.directory}/www"/>
<arg value="com.company.module2.gwt.Module2"/>
</java>
<!--/parallel-->
<copy todir="${basedir}/src/main/webapp">
<fileset dir="${project.build.directory}/www">
<exclude name="*gwt-tmp/"/>
<exclude name="*-aux/"/>
<exclude name="**/*.cache.html"/>
</fileset>
</copy>
</tasks>
</configuration>
<goals>
<goal>run</goal>
</goals>
</execution>
</executions>
</plugin>

3.  If you understand what profile above does, then the command to compile all the server and client code is something like the following: mvn clean compile -P gwt  (this compilation needs to be usually done only once)

4.  Once compilation finishes, the server (in this case Jetty) can be easily brought up with: mvn jetty:run

5. The final step is to launch the GWT hosted mode via Eclipse. Below is an example of such launch configuration:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<launchConfiguration type="org.eclipse.jdt.launching.localJavaApplication">
<listAttribute key="org.eclipse.debug.core.MAPPED_RESOURCE_PATHS">
<listEntry value="/sample"/>
</listAttribute>
<listAttribute key="org.eclipse.debug.core.MAPPED_RESOURCE_TYPES">
<listEntry value="4"/>
</listAttribute>
<booleanAttribute key="org.eclipse.debug.core.appendEnvironmentVariables" value="true"/>
<listAttribute key="org.eclipse.jdt.launching.CLASSPATH">
<listEntry value="&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; standalone=&quot;no&quot;?&gt; &lt;runtimeClasspathEntry containerPath=&quot;org.eclipse.jdt.launching.JRE_CONTAINER&quot; javaProject=&quot;sample&quot; path=&quot;1&quot; type=&quot;4&quot;/&gt; "/>
<listEntry value="&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; standalone=&quot;no&quot;?&gt; &lt;runtimeClasspathEntry id=&quot;org.eclipse.jdt.launching.classpathentry.defaultClasspath&quot;&gt; &lt;memento exportedEntriesOnly=&quot;false&quot; project=&quot;sample&quot;/&gt; &lt;/runtimeClasspathEntry&gt; "/>
<listEntry value="&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; standalone=&quot;no&quot;?&gt; &lt;runtimeClasspathEntry internalArchive=&quot;/sample/src/main/java&quot; path=&quot;3&quot; type=&quot;2&quot;/&gt; "/>
</listAttribute>
<booleanAttribute key="org.eclipse.jdt.launching.DEFAULT_CLASSPATH" value="false"/>
<stringAttribute key="org.eclipse.jdt.launching.MAIN_TYPE" value="com.google.gwt.dev.GWTShell"/>
<stringAttribute key="org.eclipse.jdt.launching.PROGRAM_ARGUMENTS" value="-out src/main/webapp com.company.module1.gwt.Module1/Module1.html -noserver -port 8080"/> <!-- -port 6434"/> -->
<stringAttribute key="org.eclipse.jdt.launching.PROJECT_ATTR" value="sample"/>
<stringAttribute key="org.eclipse.jdt.launching.VM_ARGUMENTS" value="-Xmx1024M"/>
</launchConfiguration>

in the next post I’ll describe how to setup GWT Maven2 dependencies correctly. I would certainly like Google to provide a maven central to grab all the GWT stuff from (as well as fixed GWT itself to better support native libraries under maven), however at the moment that needs to be done manually.

No related posts.