That looks very cool! I agree that logging objects is the way to go, and now that we have
all this infrastructure we should be able to better make use of object-based logs.
I was just thinking about this issue a couple of weeks ago, and beacon might just be the
solution for me. I hope to find the time in a few weeks to start using it!
On Jun 15, 2014, at 9:04 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote:
Hi,
I like very much the new energy people are putting into creating the SystemLogger engine
for Pharo. I think this is a specifically important area for which we have to have a
solution out of the box. At the same time, I also think that Pharo provides an
infrastructure that makes room for ideas that are otherwise hard to reach in other
languages or environments.
Stef asked for collaborations around this project, so here is my literally small
contribution: a rather different logging engine. It is called Beacon, it is based entirely
on Announcements, it has ~200 lines of code, it has no tags or levels, and in my opinion
it is fully functional.
You can see a detailed description here including some informal comparisons with
SystemLogger:
http://www.humane-assessment.com/blog/beacon
Please let me know what you think. I would be happy to join forces to reach a mature
solution that is both versatile and that can show how Pharo is different.
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
---> Save our in-boxes!
http://emailcharter.org <---
Johan Fabry -
http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile