X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=TODO;h=2dd12f7840c0634778d5a503b6477fbe0c33f2d7;hb=d2598ac82e8508f4d6da90ec60a1ed60840c2016;hp=fa1db507d6ef75330163f259ef932607b07a24d0;hpb=443f472fe17ccd394e4db3df07cae42ba29de5ff;p=catagits%2FCatalyst-Runtime.git

diff --git a/TODO b/TODO
index fa1db50..2dd12f7 100644
--- a/TODO
+++ b/TODO
@@ -1,28 +1,63 @@
-  - Add Class::Accessor compats
-    * Catalyst::Request
-    * Catalyst::Response
-    * Catalyst::Dispatcher
-    * Catalyst::Request::Upload
-    * Catalyst::Action
-    * Catalyst::ActionChain
-    * Catalyst::ActionContainer
-
-  - Make classes immutable at setup() time
-
-
-  - GRODITI's list:
-    * Update Test suite to not assume MyApp ISA Controller
-      - After that I'll set up attr handlers that will output helpful
-        error messages when you do it as well as how to fix it.
-    * comments marked /Moose TODO/i in the code
-    * Fix the CDI compat hack so we can start moving to immutable
-    * Profile before and after immutable.
-    * Now would be a good time to lay ground for the App / Ctx split
-    * Howto mantain branch in sync with the latest checkins ?
-    * Eliminate all instances of $instance->{$key}
-    * MooseX::Emulate::CAF seems to be working like a charm :)
-    * General code cleanups can't hurt
-    * How do we move from NEXT to C3 ? I have never used either of them
-      - What does the lineraized mro look like when we are using moose 
-        method modifiers?
-        - Does they all get clumped together or what? Is it a non-issue?
+# Known Bugs:
+
+   - Bug ->go or ->visit causes actions which have Args or CaptureArgs called
+     twice when called via ->go or ->visit.
+
+     Test app: http://github.com/bobtfish/catalyst-app-bug-go_chain/tree/master
+
+   - Bricas' Exception blog post
+
+     http://bricas.vox.com/library/post/catalyst-exceptionclass.html
+
+     Broken by recent exception refactoring
+
+# 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
+
+# REFACTORING
+
+##  The horrible hack for plugin setup - replacing it:
+
+ * Have a look at the Devel::REPL BEFORE_PLUGIN stuff
+   I wonder if what we need is that combined with plugins-as-roles
+
+## App / ctx split:
+
+  NOTE - these are notes that t0m thought up after doing back compat for
+         _component_class, may be inaccurate, wrong or missing things
+         bug mst (at least) to correct before trying more than the first 2
+         steps. Please knock yourself out on the first two however :)
+
+  - Eliminate actions in MyApp from the main test suite
+  - Uncomment warning in C::C::register_action_methods, add tests it works
+    by mocking out the logging..
+  - Remove MyApp @ISA controller (ask metaclass if it has attributes, and if
+                                  so you need back compat :/)
+  - Make Catalyst::Context, move the per request stuff in there, handles from
+    main app class to delegate
+  - Make an instance of the app class which is a global variable
+  - Make new instance of the context class, not the app class per-request
+  - Remove the components as class data, move to instance data on the app
+    class (you probably have to do this for _all_ the class data, good luck!)
+  - Make it possible for users to spin up different instances of the app class
+    (with different config etc each)
+  - Profit! (Things like changing the complete app config per vhost, i.e.
+    writing a config loader / app class role which dispatches per vhost to
+    differently configured apps is piss easy)
+