niloc132

.my-large-icon-tree .x-tree3-node-icon {// or .my-large-icon-tree img.x-tree3-node-icon
  height: 24px !important;
  width: 24px !important;
}

niloc132

<project-modules id="moduleCoreId" project-version="1.5.0">
    <wb-module deploy-name="mygwtproj">
        <wb-resource deploy-path="/" source-path="/target/mygwtproj-0.1-SNAPSHOT" />
        <wb-resource deploy-path="/WEB-INF/classes" source-path="/src/main/java"/>
        <wb-resource deploy-path="/WEB-INF/classes" source-path="/src/main/resources"/>
        <wb-resource deploy-path="/WEB-INF/classes" source-path="/src/test/java"/>
        <property name="context-root" value="/"/>
        <property name="java-output-path" value="/mygwtproj/target/mygwtproj-0.1-SNAPSHOT/WEB-INF/classes"/>
    </wb-module>
</project-modules>

niloc132

/*
Starting from http://my.opera.com/Vorlath/blog/2009/06/18/halting-problem-composability-and-compositionality
First, my apologies on reopening what is apparently not a recent blog post - the author might
long since have decided to no longer pursue this, but this was pointed out to me today, and
it looked like an interesting discussion to take part on. Whoops.

Consider any language able to turn a string into executable code: Javascript has an eval 
function able to take a string, and execute it. This can be used to turn a block of code into 
something which can be executed by simply calling a function.
*/

niloc132

                        <plugin>
                                <groupId>org.codehaus.mojo</groupId>
                                <artifactId>gwt-maven-plugin</artifactId>
                                <version>${gwt.plugin.version}</version>
                                <dependencies>
                                        <dependency>
                                                <groupId>com.google.gwt</groupId>
                                                <artifactId>gwt-user</artifactId>
                                                <version>${gwt.version}</version>
                                        </dependency>

niloc132

package com.sencha.example.emst.client.widget;

import java.util.HashMap;
import java.util.HashSet;
import java.util.Map;
import java.util.PriorityQueue;
import java.util.Set;

import com.google.gwt.event.dom.client.ClickEvent;
import com.google.gwt.event.dom.client.ClickHandler;

niloc132

diff --git a/GWThree-lib/pom.xml b/GWThree-lib/pom.xml
index 3493234..d97a622 100755
--- a/GWThree-lib/pom.xml
+++ b/GWThree-lib/pom.xml
@@ -15,21 +15,10 @@
     <version>${project.parent.version}</version>
 
     <artifactId>GWThree-lib</artifactId>
-    <dependencies><dependency>
-        <groupId>${project.parent.groupId}</groupId>

niloc132

  interface MyAltTextImageTemplate extends SafeHtmlTemplates {
    @Template("<img alt=\"{0}\" src=\"{1}\" />")
    SafeHtml image(String altText, SafeUri image);
  }

niloc132

public class HasCellImpl<M,V> implements HasCell<M,V>
{

   public HasCellImpl(ValueProvider<? super M, V> vp, Cell<V> cell)
   {
      this.cell = cell;
      this.vp = vp;
   }

   @Override

niloc132

package com.example.client;

import com.google.gwt.core.client.EntryPoint;
import com.google.gwt.regexp.shared.RegExp;
import com.google.gwt.user.client.Window;

public class Test implements EntryPoint {
  private static final String REGEX = "([0-9]|[0-5][0-9])"; 

  @Override

niloc132

This is a sample of how to set up your GXT 3 project to build from nightlies and support-only builds using your support credentials. We build every night if changes have been merged into trunk, and make that available for viewing at http://staging.sencha.com:8080/examples-dev/ as well as from our maven repository.