gwidgets / gwt-app-archetypes Goto Github PK

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.

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…

…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.

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.

The instructions will only work if you clone the repo and mvn install the archetypes locally; but they're available in Sonatype OSSRH snapshots repo.

See https://github.com/tbroyer/gwt-maven-archetypes#generate-a-project for an example.

There's no reason to set the project.build.outputDirectory to WEB-INF/classes when there's no server-side code.

Hi, first I thank you for the archetype that combines GWT and Spring Boot.
However, I have problem when I enable SSL on Spring Boot. I get the following error:

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

…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.