gwidgets / gwt-app-archetypes Goto Github PK

View Code? Open in Web Editor NEW

10.0 4.0 1.0 112 KB

A set of maven archetypes for scaffolding your GWT application.

License: Apache License 2.0

Java 35.19% HTML 64.81%

gwt maven-archetype

gwt-app-archetypes's Introduction

Description

This project provides a set of archetypes for starting your GWT application.

Available archetypes

The available archetypes are:

gwt-simple: minimal ready to run gwt project with an empty entry point class. It makes use of the net.ltgt.gwt.maven maven plugin. To run dev mode: mvn gwt:devmode. More info on goals and configuration can be found on the plugin's documentation.
gwt-simple-mojo-plugin: same as gwt-simple except that it uses the org.codehaus.mojo plugin. To run dev mode: mvn package gwt:run. More info on goals and configuration can be found on the plugin's documentation.
spring-boot-gwt: This archetype is an integration of GWT into a spring boot application. There are two predefined profiles for running GWT dev mode and for running the application in production. To run the spring boot app with GWT in devmode you need to run the following commands: mvn spring-boot:run and in a different window mvn gwt:devmode -Pgwt-dev. If you don't need to you use GWT devmode and you need to run or package the application you can use the gwt-prod profile. For example: mvn package -Pgwt:prod. Spring Boot version: 1.5.2.RELEASE, GWT version: 2.8.0. This archetypes uses the net.ltgt.gwt.maven GWT plugin.

Usage

On Windows:

mvn archetype:generate -DarchetypeGroupId=com.gwidgets.maven                ^
  -DarchetypeArtifactId={artifactName}          ^
  -DarchetypeVersion=0.4                ^
  -DgroupId={yourGroupId}                               ^
  -DartifactId={yourArtifactID}                            ^
  -Dmodule={moduleName}                                  ^
  -Dversion={yourVersion}

On Linux/Mac Os:

mvn archetype:generate -DarchetypeGroupId=com.gwidgets.maven                \
  -DarchetypeArtifactId={artifactName}          \
  -DarchetypeVersion=0.4                \
  -DgroupId={yourGroupId}                                \
  -DartifactId={yourArtifactID}                             \
  -Dmodule={moduleName}                                   \
  -Dversion={yourVersion}

gwt-app-archetypes's People

Contributors

Stargazers

Watchers

Forkers

matned666

gwt-app-archetypes's Issues

Why use Event.sinkEvents+Event.setEventListener rather than element.addEventListener?

Even weirder that addEventListener is actually used in the nav list detail archetype for the submenus, mixed with Event.sinkEvents and Event.setEventListener for top menu items.

Web resources need cleanup

The HTML host page still includes a comment hinting at using Quirks Mode to help with layout; that was true a few years ago, but no longer holds, and particularly not when using Iron and Paper elements.

It also includes a hidden iframe that used to be needed for IE6 and IE7 for GWT history, but those browsers aren't supported anymore by GWT.

Finally, the __module__.css contains styles for CSS classes that are not used; this is a leftover from the basic webAppCreator generated code / Hello sample (that also comes as an archetype with Mojo's Maven Plugin for GWT). Maybe the file should simply be deleted, as it looks like this is replaced with the app-theme.html include.

The styles/main.css looks like it's not used at all.

dagger-compiler included in the WAR, should be optional or have scope provided

…or you could use <annotationProcessorPaths> instead of adding it as a dependency (using maven-compiler-plugin 3.5.1; see #1)

Actually, all Dagger dependencies end up in the war's WEB-INF/lib, also including dagger-gwt and dagger-2.5-sources.jar.

You don't need build-helper-maven-plugin

…if you use maven-compiler-plugin 3.5.1 (actually, this has been added in 3.2 but it required mvn clean until 3.5.1)

You can then even use <annotationProcessorPaths> (added in 3.5) instead of adding dagger-compiler to the classpath.

GWT Activities is useless in those archetypes

There's only one activity in the code, that does all the entry-point is supposed to do; so the ActivityManager and ActivityMapper add unnecessary complexity. The entry-point could use a PlaceChangeEvent.Handler to the same effect.

Using GWT Activities here would make one activity per "menu item" (and given the page layout, that'd be one activity per place –generally speaking, there are more activities than places in a project). I'm really not sure how well that'd play with the Iron elements though…

Couldn't load app from Super Dev Mode. server at http://192.168.56.1:9876. Please make sure this server is ready. Do you want to try again?

It would be great if you could help me out here. I have also read the following link, but couldn't solve the problem:

gwtproject/gwt#7535