/todo/app.todo

http://zoop.googlecode.com/ · Unknown · 51 lines · 51 code · 0 blank · 0 comment · 0 complexity · 782f3e687fc15ef0e19deb9672121f03 MD5 · raw file

  1. - new stuff
  2. - have a multi-part-code
  3. - possibly IP address or host info of some kind
  4. - some hash of filename/line number/error string or something to match up multiple instances of the same error
  5. - a unique error instance code (this is probably all we need to show the user)
  6. - a custom code that we can put into errors that we trigger so we can search for them later or be alerted when they occur
  7. - Object
  8. - __callStatic
  9. - __isset
  10. - __unset
  11. - error
  12. - optionally support the show errors stuff as defined in php.ini and the use of @ symbols
  13. - allow you to override it in config.yaml
  14. - convert all errors to exceptions
  15. - create an error handler that throws an exception will all relevent info it in it
  16. - create a handler for any exception that doesn't get handled elsewhere that is the same as our current error handler
  17. - figure out what is up with the sqlite pdo exception stack traces
  18. - make it handle links to php docs work correctly
  19. - make links to zoop apis???
  20. - backtrace
  21. - format html function
  22. + basic file, line, function
  23. - add in parmamters
  24. - add in OOP info
  25. - classes
  26. - objects
  27. - full object context information
  28. - add some js magic to the parmaters to you can see what you want when and only when you want
  29. - make it capture the result and return it
  30. - convert to use the same class format as the cli version, abstract logic out into a base class
  31. - format cli function
  32. - basic display
  33. - add color, bold, etc, to make it more easily readable
  34. - use a curses interface if it is available
  35. - limit the number of errors that we display
  36. - when we hit the limit just terminate the script
  37. - make the backtrace formatter into a backtrace class, put it into the error module
  38. - allow for popping of rows in the backtrace
  39. - html formatting
  40. - cli formatting
  41. - logging
  42. - log to a file
  43. - add in full context information, including post variables
  44. - other
  45. - check for ini options that are not secure or in bad form
  46. - register globals
  47. - magic quotes
  48. - if magic quotes is on we need to warn them that their stuff will be double escaped when they try to put it into the database
  49. - debugging
  50. - the cool thing that formats things all nice
  51. - some sort of generalized echo_r substitute that formats stuff all nice according to the output device (terminal, browser, graphic, etc)