Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Integrate MiniBeacon #4537
Beacon brings much more than logging to the transcript.
Mostly I use in-memory loggers, e.g. CircularMemoryLogger, which means I typically log something like:
Now I can inspect the log, see where this happened in relation to other objects and inspect anObject.
I really suggest you read: http://www.humane-assessment.com/blog/debugging-duplicated-behavior-with-gtinspector/ (I know this is biased because I'm working with Doru now, but I started using this long before I joined).
I've used a file logger a couple of times in the last few years: once when the problem only occurred in headless mode, and once when the problem caused the image to become 100% cpu bound and the UI unresponsive. So the file logger definitely has a place, but it's fairly infrequent.
I've merged your changes back in to https://github.com/feenkcom/pharo-beacon if you'd like to merge directly from there.
I have some more enhancements planned, e.g. when inspecting a memory log it would be nice to be able to display relative times instead of absolute times so that performance issues are easier to spot.
Thanks for your refactoring!