New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
inspect/explore when gemtools/tode not active ... #21
Comments
dalehenrich
referenced
this issue
in dalehenrich/tode
Jun 3, 2014
- interaction invented to record headless interactions in object log - Issue #63 and glassdb/glass#21
dalehenrich
added a commit
that referenced
this issue
Jun 3, 2014
- add object log entries to default action for GsInteractions - add ObjectLogEntry class>>interaction, ObjectLogEntry class>>interaction:, and ObjectLogEntry class>>interaction:object: for easy filtering out/in of interactions - GsExploreInteraction added for #explore message... really only needed for GemTools at the moment ... tODE treats explore like inspect - GsInformInteraction added so that default response for an inform: message (that allows for debugging of Warning) can be differentiated from confirm:
dalehenrich
added a commit
that referenced
this issue
Jun 3, 2014
- add object log entries to default action for GsInteractions - add ObjectLogEntry class>>interaction, ObjectLogEntry class>>interaction:, and ObjectLogEntry class>>interaction:object: for easy filtering out/in of interactions - GsExploreInteraction added for #explore message... really only needed for GemTools at the moment ... tODE treats explore like inspect - GsInformInteraction added so that default response for an inform: message (that allows for debugging of Warning) can be differentiated from confirm:
dalehenrich
added a commit
that referenced
this issue
Jul 25, 2017
pick up latest changes needed for 3.4
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As pointed out on the glass list information should be recorded in the object log when certain interactive messages like the following:
are sent ... These messages are routed to an instance of GsInteraction and there is a defaultAction for each interaction, so it should be straightforward to do
The text was updated successfully, but these errors were encountered: