Also, I think being able to specify rotations for images (or elements in general?) would be terribly useful. Or, similarly, the ability to render something from a BufferedImage instead of being tied only to the filesystem.

can’t wait to finish my work to post vid of my game with all the power
of nifty!!

It would be great for 1.4 to see a more java-friendly API.
- The java builders are great, but I often found myself building the whole tree then parsing it to get some Element/Controller pointers.
Something like
Screen screen = new Screen(“main”);
Layer layer = new Layer(“layer”);
layer.childLayoutVertical();
screen.addLayer(layer);
ScreenController ctrl = screen.getController();

Or even better,
screen.addLayer(new Layer() {
initParam() {
childLayoutVertical();
}
});
- Concerning the findControl methods, why do we have to pass the class? Can’t we just get the interface and cast it ourselves if necessary?
- In the control builder, one can pass a Controller instance ( controller(myControllerInstance); ). This is total useless as only the class name is taken into account. It would be nice to be able to pass a real controller instance that will be bound when the elemtn will be built.
- When a new element is built, is it cached in any way? I use a windowed interface, and i notice a delay upon each window creation. It would be nice if i could create one once, then clone it if i need more instance. Somethinglike
private static MyWindow instance = new MyWindow();
//
MyWindow newWindow = instance.cloneElement();
newWindow.setController(new MyWindowController(Object someparam));
myDroppableArea.add(newWindow);

I mainly use java to build ui, and I often find some possible improvement. I should write them down as its quickly forgotten.

Anyway, many thanks for this piece of code! You are doing a great job!