Download xapi-core-process JAR file with all dependencies
xapi-gwt-test from group net.wetheinter (version 0.5)
Gwt testing utils
xapi-jre from group net.wetheinter (version 0.5)
This module exists solely to package all other jre 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.
It also allows dependent modules to discover new features,
as modules graduate from labs to final, they will be added here.
As you type X_, autocomplete will expose newly added services.
xapi-gwt from group net.wetheinter (version 0.5)
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.
xapi-jre-reflect from group net.wetheinter (version 0.3)
This module contains a classpath scanner, and bytecode reader.
It is useful in any java runtime environment, and allows java code to
parse bytecode into a meta structure of classes, annotations, methods and fields.
This meta structure is used throughout xapi to allow us to extend java structures
in a cross-platform compliant way (exposing services and service objects so
you can hack support for whatever runtime you need).
It is especially useful for fast runtime injection, and as an extensible
structure during codegen (which exposes mutable interfaces for our meta structure)
xapi-gwtc-impl from group net.wetheinter (version 0.5)
This module contains the business logic of running gwt compiles.
It implements and exposes all functionality of the gwt compiler,
and should only ever be included in dev-mode runtimes that need to perform gwt compiles.
In the maven plugin, the jre frontend and this backend are used together in one runtime.
In the collide plugin, the gwt frontend runs in the browser, and this backend runs in vert.x server.
xapi-dev-source from group net.wetheinter (version 0.5)
A fluent, functional codegen utility
xapi-dev-bytecode from group net.wetheinter (version 0.5)
A lightweight (readonly) fork of javassist,
used to load class structure, annotations and metadata from bytecode.
xapi-dev-file from group net.wetheinter (version 0.5)
Helper methods for dealing w/ java.io.File
xapi-gwtc-api from group net.wetheinter (version 0.5)
This module contains the core api surrounding a gwt compile.
It exposes compile events, and interfaces to act as controllers.
The default implementations will function only from a command line (or web server).
The other modules are gui frontends that merely speak to an api backend.
xapi-gwt-inject from group net.wetheinter (version 0.5)
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-dev-template from group net.wetheinter (version 0.5)
A templating system for using in creating cross-platform frameworks.
xapi-gwt-model from group net.wetheinter (version 0.5)
This module contains the generators needed to enable GWT support for our model interfaces.
xapi-dev-maven from group net.wetheinter (version 0.5)
A set of tools for scanning all sorts of maven data.
xapi-components from group net.wetheinter (version 0.5)
A web component API for manually building web components via WebComponentBuilder, or generating them from interfaces via WebComponentFactory
xapi-dev from group net.wetheinter (version 0.5)
Everything needed to run a comprehensive dev environment.
Just type X_ and pick a service from autocomplete;
new dev modules will be added as they are built.
The only dev service not included in the uber jar is xapi-dev-maven,
as it includes all runtime dependencies of maven, adding ~4 seconds to build time,
and 6 megabytes to the final output jar size (without xapi-dev-maven, it's ~1MB).
Page 1 from 2 (items total 22)
© 2015 - 2025 Weber Informatics LLC | Privacy Policy