Need a flexible logging system about leapgesture HOT 3 OPEN

For the 1st version of the logging system, I will integrate it with LeapGestureManagement Class, which is on top of all classes.
The logging system will desgin in 3 different levels.
0 -- no logging
1 -- error message(ERRORs that make the system stop working)
2 -- debug(all the tracing information)
format of the loggin system is
[TIME][ FILE:LINE] [CLASS NAME:FUNCTION]LOGGING CONTENT

all logging information will be wrapper into the #if MACRO should not be compiled into the release binary

from leapgesture.

Here is my idea about different levels:
0 - no logging at all. Not very necessary as long as we keep level 1 concise
1 - recording. Very critical info such as "the system is initialized". Used to quickly locate which part is finished and which is next.
2 - warning. Undesired but okay issue such as "high network delay" or "one hand is missing".
3 - error. Unexpected but known issue, such as the error reported from leap
4 - panic. Something must mess up, such as malloc fails
5 - debug. Anything you want to check, but SHOULD NOT checkin.

Therefore, ideally we do not need to differentiate debug or release. But it is okay to use macro to achieve efficiece.

from leapgesture.

Another thing is that, traditionally, if we are in level 2, we should see both recording and warding. But ideally we would want to select different level to display the content only in that level, which is not efficient in performance. If it can be done, it is great. If not, probably for level 0 - 4, we do the traditional implementation. For level 5, we always display it but use a macro to make sure it is not in the release binary.

from leapgesture.