X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Runtime.git;a=blobdiff_plain;f=TODO;h=2dc0bfdbdd3cef5a623da46229e576ecf1f2b1f9;hp=85fff20067336854efc27d40d42af4266b4e1bcd;hb=3db3a59fefa0cd2859282f7a3e0429a7152637c5;hpb=a8ffc0d80fe65e92aaa6b5160ed24887258d9616

diff --git a/TODO b/TODO
index 85fff20..2dc0bfd 100644
--- a/TODO
+++ b/TODO
@@ -1,25 +1,39 @@
-Known Bugs:
-   - Moose bug causes issues if you use Moose in your application, but want to
-     use base classes which have not been converted to Moose yet.
+Pre 0004:
 
-     Tests in Moose for this are: http://tinyurl.com/c2k85c
+   - Certain errors in your application to do with using other code which does
+     not exist can cause an 'Unknown error' issue.
 
-     Note: This issue _does not affect_ components which have been converted to
-           Moose, or applications which do not use Moose, and causes a 
-           compile-time error if present.
+     This is now fixed, by moving back to B::Hooks::EndOfScope, but this (used
+     to) cause issues with the following modules:
 
-   - Bugs with actions with Args or CaptureArgs being caled multiple times
-     when called via ->go or ->visit.
+     - Catalyst-Authentication-Credential-HTTP
+     
+      according to comments in r8991. Retest these before shipping anything..
 
-     Test app: http://github.com/bobtfish/catalyst-app-bug-go_chain/tree/master
+     - Document method modifiers called on things before setup not working in your app class.
 
-   - Certain errors in your application to do with using other code which does
-     not exist can cause an 'Unknown error' issue.
+Known Bugs:
 
-     Test app: http://github.com/bobtfish/catalyst-app-bug-unknown-error/tree/master
+   - Bug ->go or ->visit causes actions which have Args or CaptureArgs caled
+     twice when called via ->go or ->visit.
+
+     Test app: http://github.com/bobtfish/catalyst-app-bug-go_chain/tree/master
 
 Compatibility warnings to add:
 
    - $self->config should warn as config should only ever be called as a
      class method.
 
+Proposed functionality / feature additions:
+
+    - Log setup needs to be less lame, so Catalyst::Plugin::Log::* can die
+      in a fire. Having $c->log_class would be a good start. kane volunteered
+      to do some of this.
+
+      Simple example: Catalyst::Plugin::Log::Colorful should just be a
+      subclass of Catalyst::Log, no ::Plugin:: needed.
+
+      See also: Catalyst::Plugin::Log::Dispatch and
+      http://github.com/willert/catalyst-plugin-log4perl-simple/tree
+
+