I found some time and at least compiling the core api was no problem. The dead code elimination kicked in and complete erased every trace of Qi4J from the compiled javascript so the measurement is completely meaningless. I'm working now to use at least some features to get a more interesting figure.
I think I should also elaborate a bit more on what I actually want to achieve. Obviously there is no point in running all of Qi4J on the browser. Low level layers like persistency would be possible by proxying but that could involve lots of roundtrips which is exactly what you want to avoid to get a smooth GUI. What I want to do is to just move GUI code plus one or more entities to the browser. This way simple businesslogic (that doesn't need backends like DB's) can be executed right there. The user can then work in that GUI and manipulate the entities. The underlying Property objects keep track of get()s and set()s to record a UoW which is sent back to the server when something is committed. When the logic is more complex or needs more data (entities) and a call to the server is needed I hope to be able to hide that fact by proxying. I don't want any GWT specific knowledge in the domain logic! So essentially only the api, the domain code and a GWT specific runtime needs to be compiled. cheers, Guus
_______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
