Progress on Check Register sample COODBMS application

The check register is to the point where it can process checks, which is to say it is hardly started but what is done is working if not very usable. But even a fragment of an application is very helpful in developing COODBMS.

Case in point, the transaction to process a check contains an action DEnt which contains all the necessary data (payto, amount, date, etc.) but no application logic. Actions get evaluated by the target object. So where do we put the check processing logic in the check register rolon? In a DSec of course!

Now TRolons always have a main DSec with an execute method that gets called to process the transaction. Similarly, a rolon can have an Eval DSec which evaluates actions with otherwise unrecognized opcodes. This Eval DSec has an eval method and when it is called it in turn calls the eval method on all subordinate descriptor nodes successively until the action is processed. So we can extend the capabilities of a rolon just by adding DEnts to the Eval DSec. And it is precisely this kind of composability which is what Rolonics is all about.

At this point the priority is to continue to work on the check register application and to polish the API a bit to make the application code a bit less awkward to write. Hmm. I think I need to work up a guide as well.