Post by chriscrawford on Sept 28, 2015 15:09:27 GMT -8
It will be cleaner if I organize this diary by weeks. I don't need to burden the reader with trivial details. My goal for this week is to get the engine components of FroggerLogger operational.
Monday: I have stripped out the Interpreter components and am now focusing on bringing back all the engine components. Just now I am wrestling with the problem that Facundo solved neatly with results that span several entries. For example, when beginning the process of determining whether an actor has a role to play, FroggerLogger adds the entry:
DirObject Camiggdo considering reacting
There follow a series of calculations in the Interpreter, which don't show up yet. If Camiggdo decides to react, then the next line is
Camiggdo executing role Victim
Facundo had come up with a nice way to merge these into a single line, reading like this:
DirObject Camiggdo considering reacting; reacts as Victim
This permits the author to see the result easily without having to open up the nodes underneath it. This kind of problem shows up in many different places in the logger. Should I try to implement it? It will require some serious programming. I haven't yet decided.
Monday: I have stripped out the Interpreter components and am now focusing on bringing back all the engine components. Just now I am wrestling with the problem that Facundo solved neatly with results that span several entries. For example, when beginning the process of determining whether an actor has a role to play, FroggerLogger adds the entry:
DirObject Camiggdo considering reacting
There follow a series of calculations in the Interpreter, which don't show up yet. If Camiggdo decides to react, then the next line is
Camiggdo executing role Victim
Facundo had come up with a nice way to merge these into a single line, reading like this:
DirObject Camiggdo considering reacting; reacts as Victim
This permits the author to see the result easily without having to open up the nodes underneath it. This kind of problem shows up in many different places in the logger. Should I try to implement it? It will require some serious programming. I haven't yet decided.