On 9/13/05, John Krystynak <[EMAIL PROTECTED]> wrote: > What are the other Six Great Imponderables of Maypole? I want to know > now, so I don't waste ponderage cycles...
1. Why use moniker for template directories, and table name for paths? 2. Why is template_root the first item returned from paths() (and why is it returned at all)? 3. Why does Maypole have a related_class method, which it doesn't use? 4. What does it mean that Maypole::Constants::ERROR = -1, and so does Maypole::Constants::DECLINED? 5. What is the Best Way to handle exceptions in Maypole? 6. Why does Maypole::Application make your application inherit from Maypole::Application, which provides no methods? (OK, that one's fixed in svn, but...why?) 7. What is the Secret 7th Great Imponderable? 8. Why does send_output() not return a status code (apart from the obvious - handler_guts doesn't check for one). 9. Why are there nine '7 Great Imponderables'? d. ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Maypole-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/maypole-users
