f0xdx / letras Goto Github PK

What steps will reproduce the problem?
1. Start Letras and host multiple regions
2. Remove regions in reverse order than they have been added 
3. The RPS will deadlock

I already have an idea why this happens and hopefully provide a fix shortly

*Goal*: make it easier for new users to deploy Letras for their use case
*Outcome*: design and descriptions for some deployment configurations 

*Goal*: gather documentation in the google code wiki
*Outcome*: all relevant documentation is in the google code wiki and links are 
correct

*Goal*: Move the tools to a separate location where they will not be included 
in the pre processing step (they must have their own pre processing step 
however). This will avoid the problem with the metaclasses of tools becoming 
present in the metaclasses.xml of Letras which will result in a harmless but 
ugly exception. 
*Outcome*: changed build.xml and separate directory for tools

*Goal*: Possibility to configure the outgoing zone to which region samples are 
dispatched the RegionProcessor
*Outcome*: config option in node.conf.xml

What steps will reproduce the problem?
1. Start Letras and a PenMonitor
2. Connect a pen and open the inspector window in PenMonitor
3. Not sure, but connect a second pen; shutdown letras; fool around 
4. The PenMonitor crashes. Clicking is not possible anymore and values are not 
updated

Console shows RMCException or AWT Thread Exception.

*Goal*: clearer distinction between api (convenience classes) and psi (mundo 
communication)
*Outcome*: cleaned psi package. relevant classes moved to api. duplicates 
removed.
Allowed dependencies: ps -> psi; ps -> api; api -> psi;

*Goal*: sporadic concurrent modification exceptions should not occur anymore
*Outcome*: patch that fixes the above

*improve readability of code in the ps package. take care to use same code 
conventions and paradigms