Artifacts using GWT Dev (18)

Sort by:Popular▼

✓Popular✓Newest

In order to implement the core XApi dependency injection in gwt, we had to swap out the injection methods themselves with magic methods that call into generated-on-the-fly provider classes.

XApi Gwt Collections Implementation

Gwt testing utils

All Gwt jre emulation code goes in this module, as well as any gwt-compiler overrides. xapi-gwt-api.jar must come before gwt-dev.jar on your compile classpath. A plugin is being built to automatically adjust maven runtime dependencies, but users of ant or IDEs will need to ensure the super jar comes before gwt-dev. We will petition gwt to accept our mods, but, until then, if you want bleeding edge features, you gotta do bleeding edge configuration. Code that ties directly into other ...

This module contains the basic logger interface, and a few adapter implementations. Note, to use an adapter, you will be responsible for providing dependencies; this module only uses provided scope, to avoid leaking dependencies for adapters.

GWT Codeserver

This module exists solely to package all other gwt modules into a single uber jar. This makes deploying to non-mavenized targets much easier. Of course, you would be wise to inherit your dependencies individually; the uber jar is intended for projects like collide, which have complex configuration, and adding many jars would be a pain.

A client-side implementation of io for gwt, which can adapt to various io providers. The inital version will simply use GWT-RPC, but will provide a mutable factory to inject custom strategies.

A web component API for manually building web components via WebComponentBuilder, or generating them from interfaces via WebComponentFactory

A set of generator utils to create raw html from annotated data models.