Permalink
Browse files

Fixed CocoaLumberjack files location by moving them to a separate fol…

…der.
  • Loading branch information...
tomaz committed Jun 3, 2010
1 parent acbcda1 commit 17c0ec9ab1c942ec268c7fa09b25b2f874b12afc
Showing with 36 additions and 6 deletions.
  1. 0 ...pplication/Core Data Application with Unit Testing/Common/ThirdParty/{ → DDLog}/DDConsoleLogger.h
  2. 0 ...pplication/Core Data Application with Unit Testing/Common/ThirdParty/{ → DDLog}/DDConsoleLogger.m
  3. 0 ...a Application/Core Data Application with Unit Testing/Common/ThirdParty/{ → DDLog}/DDFileLogger.h
  4. 0 ...a Application/Core Data Application with Unit Testing/Common/ThirdParty/{ → DDLog}/DDFileLogger.m
  5. 0 ...on/Cocoa Application/Core Data Application with Unit Testing/Common/ThirdParty/{ → DDLog}/DDLog.h
  6. 0 ...on/Cocoa Application/Core Data Application with Unit Testing/Common/ThirdParty/{ → DDLog}/DDLog.m
  7. +1 −1 ...a Application/Core Data Application with Unit Testing/___PROJECTNAME___.xcodeproj/project.pbxproj
  8. 0 ...pplication/Cocoa Application/Core Data Application/Common/ThirdParty/{ → DDLog}/DDConsoleLogger.h
  9. 0 ...pplication/Cocoa Application/Core Data Application/Common/ThirdParty/{ → DDLog}/DDConsoleLogger.m
  10. 0 ...s/Application/Cocoa Application/Core Data Application/Common/ThirdParty/{ → DDLog}/DDFileLogger.h
  11. 0 ...s/Application/Cocoa Application/Core Data Application/Common/ThirdParty/{ → DDLog}/DDFileLogger.m
  12. 0 ...emplates/Application/Cocoa Application/Core Data Application/Common/ThirdParty/{ → DDLog}/DDLog.h
  13. 0 ...emplates/Application/Cocoa Application/Core Data Application/Common/ThirdParty/{ → DDLog}/DDLog.m
  14. +1 −1 ...s/Application/Cocoa Application/Core Data Application/___PROJECTNAME___.xcodeproj/project.pbxproj
  15. +34 −4 Readme.markdown
@@ -463,7 +463,7 @@
73B7167F11B8310E00BD7D8E /* DDLog.h */,
73B7168011B8310E00BD7D8E /* DDLog.m */,
);
- name = DDLog;
+ path = DDLog;
sourceTree = "<group>";
};
73D87EBE1174902F0015C80E /* Testing */ = {
@@ -340,7 +340,7 @@
73B715EA11B8227800BD7D8E /* DDLog.h */,
73B715EB11B8227800BD7D8E /* DDLog.m */,
);
- name = DDLog;
+ path = DDLog;
sourceTree = "<group>";
};
7756732906782D8800D1FEB8 /* Models */ = {
View
@@ -8,8 +8,8 @@ http://www.gentlebytes.com/2010/04/xcode-project-using-coredata/
You are free to use/modify the templates for your own needs!
-Installation
-============
+Installation and Usage
+======================
To install, copy Application folder to ~/Library/Application Support/Developer/Shared/Xcode.
Note that this will overwrite your existing `File Templates` and `Project Templates`
@@ -18,8 +18,8 @@ folders; if you use other templates in there, copy each folder contents individu
After copying, the templates are ready to use (no Xcode restart is required!).
-Usage
-=====
+Usage of Project Templates
+--------------------------
To use project templates, start a new project, then in Xcode New Project window, select
Application option in the User Templates section on the left side of the window. This
@@ -46,6 +46,36 @@ on github wiki pages for details on how to do that.
This should be basically everything you need to get a working skeleton.
+Usage of File Templates
+-----------------------
+
+To use file templates, create a new file, then select Cocoa Class from User Templates
+section of Xcode New File window. On the right you'll see the option of selecting
+either Objective-C class or Objective-C test case class. In the bottom part of the
+window you can then select various options or subclasses to use. Note that most are
+suited for use with above custom project templates, but you may find them useful
+othewise too.
+
+
+Special Considerations
+----------------------
+
+If you'll use CocoaLumberjack logging framework, you might experience problems with your
+custom classes logging levels not being detected by DDLog class (especially if using
+`updateLoggingLevelsOfAllClassesWithValue:` or `updateLoggingLevelsForClasses:levelValue:`
+methods from `DDLog(GBLogExtensions)` category. The problem is due to custom subclasses
+are not detected as being registered by `DDLog`s private `isRegisteredClass:` method.
+The reason is in testing for conformance to `NSObject` protocol which rejects most
+classes, even though they are derived from `NSObject` class... I admit, I didn't go
+into details about this, so I've adopted a quick (and dirty) solution at the moment -
+for each of my classes, I make them conform to an empty `GBDynamicLogger` protocol
+and this solves the problem. Note that this MUST be done for each subclass as well!
+
+
+Thanks
+======
+
+
LICENCE
=======

0 comments on commit 17c0ec9

Please sign in to comment.