The main idea of Zeroi is to be able to use any logging system (like SOS, XRay, Luminic Box, XTrace…) in your MTASC project, without having to change the code of your app. In fact your code doesn't even need to know about Zeroi. Inside your app you only use trace statements. The traces are forwarded to the logging system of your choice.
That's what the name Zeroi is standing for: Zero Impact.
Zeroi supports loglevels and an optional LoggerConfig XML file to set special loglevels for classes and packages.
You can download the latest release version here.
There is no installation. You only have to add the zeroi classpath and the a few classes to your MTASC compile arguments.
The usage of Zeroi is very simple which is implicised by the name Zeroi which means “zero impact”.
If you are alreay familiar with MTASC simply check out the subversion repository read the README.txt and study the example including the corresponding ANT build.xml. More detailed instructions follow if there is an audiance for it.
In short words add this to your MTASC commandline:
If you want to use a logconfig XML-File do it like in the example MainClass using LoggerConfig.init([PATH_TO_CONFIG.xml], callback);
To understand it also see the example logConfig.xml.
To get an idea of how the log output looks like:
Of every log you see:
Using Zeroi with LuminicBox.Log (FlashInspector): http://www.websector.de/blog/2007/03/04/debugging-with-mtasc-ant-and-zeroi/
Using Zeroi with XTrace: http://www.websector.de/blog/2007/03/12/extension-for-zeroi-xtracepublisher/
There is a community of users and developers for this project who share their experiences on the mailing list. Please search through the archives to see if your question has been answered before submitting it to the mailing list.
Zeroi Mailing List: Subscribe and manage your subscription
This project has a Subversion (SVN) repository at: Zeroi Subversion Repository
Sometimes the history replays twice and you got the first logs doubled when using SOS.
Also define special methods of a class with a LogLevel so LogLevel definition goes down to methods.
Any feature you are missing? Please tell us and also write it into the mailinglist!
Discussion