Florian Friedrich d2cbd0aa19 Update Demos 3 lat temu
..
Base.lproj d2cbd0aa19 Update Demos 3 lat temu
FineGrainedLogging.xcodeproj d2cbd0aa19 Update Demos 3 lat temu
en.lproj d2cbd0aa19 Update Demos 3 lat temu
FineGrainedLogging-Info.plist f670be745b Update Demos 8 lat temu
FineGrainedLoggingAppDelegate.h 04421a3411 Spelling. 7 lat temu
FineGrainedLoggingAppDelegate.m d2cbd0aa19 Update Demos 3 lat temu
FineGrainedLogging_Prefix.pch 04421a3411 Spelling. 7 lat temu
MYLog.h 04421a3411 Spelling. 7 lat temu
ReadMe.txt e5f15c24b1 Renamed `Xcode` folder to `Demos` - contains remaining demo projects 11 lat temu
TimerOne.h 04421a3411 Spelling. 7 lat temu
TimerOne.m 04421a3411 Spelling. 7 lat temu
TimerTwo.h 04421a3411 Spelling. 7 lat temu
TimerTwo.m 04421a3411 Spelling. 7 lat temu
main.m 04421a3411 Spelling. 7 lat temu

ReadMe.txt

This Xcode project demonstrates fine grained logging. The Lumberjack framework supports much more than simple log levels. For example, you might want to categorize your log statements according to functionality. This would allow you to toggle log statements according to the modules you are currently developing. For example:

DDLogEngine(@"Low oil");
DDLogRadio(@"Switching to FM2");

It could even be more advanced than this. You might have log levels within the separate log statements. For example:

DDLogEngineWarn(@"Low oil");
DDLogRadioVerbose(@"Switching to FM2");

Then you could change log levels per module.

As you can see, the framework is very flexible. Each project may have different logging requirements, and you can customize the framework to match your needs.

This particular project demonstrates adding two new log statements based on functionality. They represent hypothetical timers which are critical to the application. The implementation of these timers also spans across multiple files, so there is a need to have central control over the log statements.

For more information, see the Wiki article:
https://github.com/CocoaLumberjack/CocoaLumberjack/wiki/FineGrainedLogging