[catagits/Reaction.git] / TODO

#--------#---------#---------#---------#---------#---------#---------#---------
* General
  - Explore NYTProf to see if it can tell us anything about places where we 
    could improve speed
  - Should we set up some kind of ticketing application to keep track of issues 
    as the project becomes larger and more complex?
    - If so, move all comments beginning with #XXX to proper tickets 

* Reaction::UI::View
  - Add an environment variable that disables caching of compiled templates to 
    facilitate template tweaking on a development environment
  - Add an API call to clear caching of compiled templates. Most likely a 
    simple clearer.

* Reaction::UI::Controller::*
  - Develop a REST controller that works with the default IM Actions

* groditi
  - Improve and finish code generator.
  - Run Autodoc on any files without documentation. Stubs are better than nothing.
    - Improve how pretty code is, which is the main problem ATM.

* Reaction::UI::ViewPort::*
  - Improve Field vp to take a option for ordering (wreis: please elaborate)
    <groditi> sort => 'lexical', sort => 'numberical' sort => sub {...} 
              comes to mind
    <groditi> isa => 'Sort', required => 0; subtype Sort => as 'CodeRef'; 
              coerce Coderef => from Str ...
  - Fix HiddenArray

* Reaction::UI::ViewPort::Field
  - Why did the check for non lazy_fail lazy attrs go away? it breaks my IMs
    code is commented out, but does anyone know why?

* Reaction::Types::*
  - Eliminate the ones we can spin into external MooseX::Types stuff
  - re-export the types from MooseX::Types::Common as Reaction types
  - same thing but with the DateTime and MooseX::Types::DateTime
Commit	Line	Data
b9c9838d	1	#--------#---------#---------#---------#---------#---------#---------#---------
6447c1dd	2	* General
b9c9838d	3	- Explore NYTProf to see if it can tell us anything about places where we
	4	could improve speed
	5	- Should we set up some kind of ticketing application to keep track of issues
	6	as the project becomes larger and more complex?
6447c1dd	7	- If so, move all comments beginning with #XXX to proper tickets
	8
	9	* Reaction::UI::View
b9c9838d	10	- Add an environment variable that disables caching of compiled templates to
	11	facilitate template tweaking on a development environment
	12	- Add an API call to clear caching of compiled templates. Most likely a
	13	simple clearer.
6447c1dd	14
	15	* Reaction::UI::Controller::*
	16	- Develop a REST controller that works with the default IM Actions
	17
	18	* groditi
	19	- Improve and finish code generator.
	20	- Run Autodoc on any files without documentation. Stubs are better than nothing.
afd1c910	21	- Improve how pretty code is, which is the main problem ATM.
	22
	23	* Reaction::UI::ViewPort::*
b9c9838d	24	- Improve Field vp to take a option for ordering (wreis: please elaborate)
	25	<groditi> sort => 'lexical', sort => 'numberical' sort => sub {...}
	26	comes to mind
	27	<groditi> isa => 'Sort', required => 0; subtype Sort => as 'CodeRef';
	28	coerce Coderef => from Str ...
afd1c910	29	- Fix HiddenArray
b9c9838d	30
	31	* Reaction::UI::ViewPort::Field
	32	- Why did the check for non lazy_fail lazy attrs go away? it breaks my IMs
baee102d	33	code is commented out, but does anyone know why?
	34
	35	* Reaction::Types::*
	36	- Eliminate the ones we can spin into external MooseX::Types stuff
	37	- re-export the types from MooseX::Types::Common as Reaction types
	38	- same thing but with the DateTime and MooseX::Types::DateTime