improved pager; improved Maypole::View::TT documentation

[maypole.git] / wishlist.txt

diff --git a/wishlist.txt b/wishlist.txt
index 21cdea978b4c0ffb7063165f41e3fa194b2a3a70..7ee5bfbb76034566236441a483c9573736a0d972 100644 (file)
--- a/wishlist.txt
+++ b/wishlist.txt
@@ -10,21 +10,43 @@ send_output() should return a status code
 Move template test out of process() and into handler_guts() - maybe\r
 Fix bug 14570 - returning error codes breaks CGI::Maypole\r
 Write Maypole::Manual::Exceptions\r
+Test and refactor external_redirect()\r
+\r
+Fix Mp::P::USC\r
 \r
 2.12\r
 ====\r
 Maypole::instance()\r
 Better plugin architecture, for models and bits of models. \r
 Investigate problems reported with adopt() - rt 15598\r
+Re-implement Maypole::Cache as Maypole::Plugin::Cache, probably using \r
+    start_request_hook, and not overriding handler_guts()\r
+Handle repeat form submissions.\r
+Implement internal_redirect().\r
+Build a more sophisticated app for testing. \r
+Move class_of() to the controller - need to do this to support multiple models. \r
+Multiple model support.\r
 \r
 3.0\r
 ====\r
-encapsulate all request data in HTTP::Request object, and all response data \r
+Encapsulate all request data in HTTP::Request object, and all response data \r
 in HTTP::Response object\r
 \r
-add email handling - like Rails - via model plugins\r
+Look at HTTP::Body\r
+\r
+Easier file uploads - look at incorporating Mp::P::Upload\r
+\r
+Add email handling - like Rails - via model plugins. \r
+\r
+An e-commerce model plugin would be nice - or proof of concept.  \r
+\r
+Add validation layer(s), or just an API\r
+\r
+killer apps: SVN model; mitiki; Pet Shop; \r
+\r
+Multiple views - HTML, text-only, PDF, SOAP, XML  - use request data to switch\r
+to an alternate view_object - switch via a factory method.\r
 \r
-add validation layer, or just an API\r
+Maybe rename the model to PModel (Presentation Model)?\r
 \r
-killer apps: SVN model; mitiki; Pet Shop;\r
 \r