Currently, Objects Groups show a snapshot of the objects present in a given top-level cell at some point during the system's evolution, but there is nothing to display what state the system (or top-level cell, if they have separate states) is in. It would be good to add something into the cpobjects environment, or a new cpstate command to go inside a cpobjects environment, that is then typeset nicely to show the state of the system. How this should look is entirely unclear, however.
Thinking about it further, it might be a good idea to add in some more elements, explaining e.g.
The current state of the system
The previous state of the system
The numbers of the rules applied to make the transition
Perhaps even the actual specific rules applied themselves. Preferably, I could get rule cross-referencing working, and then that way only the labels for the rules need to be included in a given Objects Group's declaration, and the rest could be worked out automatically.
The previous Objects Group that the current one has been derived from, at least when there has only been a single step between them
None of this is strictly necessary, but it would probably go a long way to helping casual readers orient themselves as they follow along with an example.
Currently, Objects Groups show a snapshot of the objects present in a given top-level cell at some point during the system's evolution, but there is nothing to display what state the system (or top-level cell, if they have separate states) is in. It would be good to add something into the
cpobjectsenvironment, or a newcpstatecommand to go inside acpobjectsenvironment, that is then typeset nicely to show the state of the system. How this should look is entirely unclear, however.Thinking about it further, it might be a good idea to add in some more elements, explaining e.g.
None of this is strictly necessary, but it would probably go a long way to helping casual readers orient themselves as they follow along with an example.