X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=TODO;h=d88fce5102ec0817b9fc2b4c860bd30adf0b68ab;hb=19c64905295c1483ceaa41d0ba498b52bf4fab5e;hp=cc83150ee6ea4558ff771c62fb3f93eb7071943f;hpb=1d9dd18007b36d6c0cd19fa2b7be72840dd0cda1;p=catagits%2FCatalyst-Runtime.git

diff --git a/TODO b/TODO
index cc83150..d88fce5 100644
--- a/TODO
+++ b/TODO
@@ -1,42 +1,82 @@
-Pre 0004:
+# Known Bugs:
 
-   - Certain errors in your application to do with using other code which does
-     not exist can cause an 'Unknown error' issue.
+   - Bug ->go or ->visit causes actions which have Args or CaptureArgs called
+     twice when called via ->go or ->visit.
 
-     This is now fixed, by moving back to B::Hooks::EndOfScope, but this (used
-     to) cause issues with the following modules:
+     Test app: http://github.com/bobtfish/catalyst-app-bug-go_chain/tree/master
 
-     - Catalyst-Plugin-Session-PerUser
-     - Catalyst-Plugin-Session-Store-File
-     - Catalyst-Authentication-Credential-HTTP
-     - Catalyst-Plugin-SmartURI
+# Compatibility warnings to add:
 
-     according to comments in r8991. Retest these before shipping anything..
+  - $self->config should warn as config should only ever be called as a
+    class method (TESTS).
 
-     - Document method modifiers called on things before setup not working in your app class.
+# Proposed functionality / feature additions:
 
-Known Bugs:
+## Log setup needs to be less lame
 
-   - Bug ->go or ->visit causes actions which have Args or CaptureArgs caled
-     twice when called via ->go or ->visit.
+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.
 
-     Test app: http://github.com/bobtfish/catalyst-app-bug-go_chain/tree/master
+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
+         catalyst_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)
+
+## GSOC
+
+### Next large steps:
 
-Compatibility warnings to add:
+  - Moving setup_components etc into the container
 
-   - $self->config should warn as config should only ever be called as a
-     class method.
+    - This is so that you can just load the container and get models etc from it,
+      without loading Catalyst.
 
-Proposed functionality / feature additions:
+  - Allowing people to change component lifecycles
 
-    - 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.
+    - This is done by being able to use an alternate Service class..
 
-      Simple example: Catalyst::Plugin::Log::Colorful should just be a
-      subclass of Catalyst::Log, no ::Plugin:: needed.
+      I.E. We currently force everything to do Catalyst/IOC/Service/WithAcceptContext.pm, but
+      things without an ACCEPT_CONTEXT could just not bother, and it would be nice to have
+      one that cached the object in request scope (i.e. Catalyst::Component::InstancePerContext)
+      etc.
 
-      See also: Catalyst::Plugin::Log::Dispatch and
-      http://github.com/willert/catalyst-plugin-log4perl-simple/tree
+      However we need to work out an interface for people to setup / configure this.
 
+### To polish off
 
+  - Document current methods
+  - +    $class->container->get_sub_container('model')->make_single_default;
++    $class->container->get_sub_container('view')->make_single_default;