X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=TODO;h=d88fce5102ec0817b9fc2b4c860bd30adf0b68ab;hb=19c64905295c1483ceaa41d0ba498b52bf4fab5e;hp=c8c6b5dbd0268f30a1eda489775cef370dd6b010;hpb=57bf5a34ada2c150521492f92435e5490afe67a9;p=catagits%2FCatalyst-Runtime.git diff --git a/TODO b/TODO index c8c6b5d..d88fce5 100644 --- a/TODO +++ b/TODO @@ -1,33 +1,82 @@ -Back-compat investigation: +# Known Bugs: - - Get engines tested: - - Catalyst-Engine-HTTP-Prefork + - Bug ->go or ->visit causes actions which have Args or CaptureArgs called + twice when called via ->go or ->visit. -Known issues: + Test app: http://github.com/bobtfish/catalyst-app-bug-go_chain/tree/master - - Catalyst-Log-Log4perl Deep recursion on subroutine "MockApp::setup" due - to Adopt::NEXT not remembering which setup methods were already called - and which not, like NEXT does. Log::Log4perl needs to be fixed and the - problem should be described in Upgrading.pod. (rafl) +# Compatibility warnings to add: - - CatalystX-CRUD and CatalystX-CRUD-ModelAdapter-DBIC - fail tests against 5.80 (karpet) + - $self->config should warn as config should only ever be called as a + class method (TESTS). - - Waiting on new releases: - - Catalyst::Plugin::Authentication - 0.100092 - - Catalyst::Action::RenderView - 0.08 - - Catalyst::Plugin::DebugCookie - 0.999002 +# Proposed functionality / feature additions: -Documentation: +## Log setup needs to be less lame - - Manual / Tutorial updates +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. - - extends in components with attributes must be inside a BEGIN block. +Simple example: Catalyst::Plugin::Log::Colorful should just be a +subclass of Catalyst::Log, no ::Plugin:: needed. - - How to write Moosified Catalyst components. +See also: Catalyst::Plugin::Log::Dispatch and +http://github.com/willert/catalyst-plugin-log4perl-simple/tree - - Catalyst/Upgrading.pod +# REFACTORING -Profiling: +## The horrible hack for plugin setup - replacing it: - - vs 5.70 and optimisation as needed. + * 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: + + - Moving setup_components etc into the container + + - This is so that you can just load the container and get models etc from it, + without loading Catalyst. + + - Allowing people to change component lifecycles + + - This is done by being able to use an alternate Service class.. + + 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. + + 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;