X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Runtime.git;a=blobdiff_plain;f=TODO;h=d8af8654286e7b4cea92c838ed0e20ba1a79274e;hp=bec19e9db61616f2efeb5906a9331c5c2ce3a829;hb=d23aa3fb3ba885c5f6ab589b3d708e7286f8dc25;hpb=35ea2ce8f440c1a94408a6e8f4ec169e907b940b diff --git a/TODO b/TODO index bec19e9..d8af865 100644 --- a/TODO +++ b/TODO @@ -1,25 +1,76 @@ -Known issues: +# Known Bugs: -Documentation: + - Bug ->go or ->visit causes actions which have Args or CaptureArgs called + twice when called via ->go or ->visit. - - Catalyst/Upgrading.pod needs brushing up + Test app: http://github.com/bobtfish/catalyst-app-bug-go_chain/tree/master - - Warning when you pass $c->model("MyApp::Model::Foo") is the generic - warning for regex fall back. Should be more specific about what you - screwed up, and the docs for $c->model should be more explicit about - what is expected. This probably also applies to view/controller. +# Compatibility warnings to add: - - Run more smokes + - $self->config should warn as config should only ever be called as a + class method (TESTS). - - Test/document ->Class::MOP::Object::meta call in ::ClassData +# Proposed functionality / feature additions: - - Change dispatcher and upgrade docs appropriately (no new method needed) +## Log setup needs to be less lame - - Using anything ::[CMV]:: should warn (once, on boot). +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. - - TestApp should not use NEXT. There should be a TestAppNEXTCompat - which does but is standalone.. +Simple example: Catalyst::Plugin::Log::Colorful should just be a +subclass of Catalyst::Log, no ::Plugin:: needed. -Profiling: +See also: Catalyst::Plugin::Log::Dispatch and +http://github.com/willert/catalyst-plugin-log4perl-simple/tree - - vs 5.70 and optimisation as needed on perl 5.8 (5.10 is already faster!). +# REFACTORING + +## PSGI + +### Blockers + + * Fix nginx middlewares so that they are generic, or can somehow + be used by people with their own .psgi files + * Fix a sane / nicer way to do custom engines. + +#### Script survey + +### Nice to have + + * Capture arguments that the plack engine component was run with somewhere, + to more easily support custom args from scripts (e.g. Gitalist's + --git_dir) + * throw away the restarter and allow using the restarters Plack provides + * remove per-request state from the engine instance + * be smarter about how we use PSGI - not every response needs to be delayed + and streaming + +## 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)