status, peer/app from a Rolonic perspective

First I want to report that I have not yet started converting PList. But I have worked out a strategy for the conversion. Second I want to report that all the code is in working order.

Now Peer/App pairs are a bit like AWT--you don't ever get one without the other. But in this case it is the factory which decides (using some tables) which class of App goes with a given type of Peer. One difference to note here is that Peer is the object which the programmer creates, while in AWT it is the reverse.

Peer/App is also a bit like COM aggrigation. The Peer holds the App object and exposes the App's interface.

But a better (i.e. more Rolonic) way to think about Peer/App is that Peer handles partness (i.e. Peer deals with the framework) while App largely handles logic and state. App then is almost a POJO, except that it is aware of its environment (via calls to Peer) and is responsible for its own serialization. As usual, there is no history/Journal--that will not be implemented until we reach JOODBMS.