mortimer 21932aaaf0 a | 6 anni fa | |
---|---|---|
.. | ||
Classes | 6 anni fa | |
.DS_Store | 6 anni fa | |
LICENSE.txt | 6 anni fa | |
README.md | 6 anni fa |
CocoaLumberjack is a fast & simple, yet powerful & flexible logging framework for Mac and iOS.
platform :ios, '5.0'
pod 'CocoaLumberjack'
DDLog.h
imports by #import <CocoaLumberjack/CocoaLumberjack.h>
.DDLogC
macros for regular DDLog
macros.ddLogLevel
variable's type to DDLogLevel
LOG_LEVEL_*
) macros with DDLogLevel
enum valuesLOG_FLAG_*
) macros with DDLogFlag
enum valuesDDLogMessage
ivars and method calls to the new ivars and methods
logMsg
with _message
logLevel
with _level
logFlag
with _flag
logContext
with _context
lineNumber
with _line
(type changed from int
to NSUInteger
)file
with _file
(filename
contains just the file name, without the extension and the full path)timestamp
with _timestamp
methodName
with function
DDAbstractLogger
formatter
to logFormatter
YSSingleFileLogger
ivars are no longer accesible, use the methods instead[DDLog addLogger:withLogLevel:]
with [DDLog addLogger:withLevel:]
If an included library requires it, you can force CocoaLumberjack 1.x by setting the version before the conflicting library:
pod 'CocoaLumberjack', '~> 1.9'
pod 'ConflictingLibrary'
It is similar in concept to other popular logging frameworks such as log4j, yet is designed specifically for Objective-C, and takes advantage of features such as multi-threading, grand central dispatch (if available), lockless atomic operations, and the dynamic nature of the Objective-C runtime.
In most cases it is an order of magnitude faster than NSLog.
It takes as little as a single line of code to configure lumberjack when your application launches. Then simply replace your NSLog statements with DDLog statements and that's about it. (And the DDLog macros have the exact same format and syntax as NSLog, so it's super easy.)
One log statement can be sent to multiple loggers, meaning you can log to a file and the console simultaneously. Want more? Create your own loggers (it's easy) and send your log statements over the network. Or to a database or distributed file system. The sky is the limit.
Configure your logging however you want. Change log levels per file (perfect for debugging). Change log levels per logger (verbose console, but concise log file). Change log levels per xcode configuration (verbose debug, but concise release). Have your log statements compiled out of the release build. Customize the number of log levels for your application. Add your own fine-grained logging. Dynamically change log levels during runtime. Choose how & when you want your log files to be rolled. Upload your log files to a central server. Compress archived log files to save disk space...