Jeremy, I just ran into your comments on line 16 of the new DO_Common file about throwing an exception.
So I just wanted to post here that everyone should start brainstorming a one-size-fits-all ultimate error handling/logging solution for OpenIT 2.1.
I've used the PEAR::Log package in another project and absolutely *love* it, so if you don't know where to start, check it out.
Why do I say to put this off until 2.1? Because my big plan for 2.1 is to start moving code into our newborn OO model. The changelog and notifications are perfect candidates, and error handling should be thrown in as well at some level.
The hardest part will be creating a logging system which handles critical application errors like "Cannot find DB" and small user errors like "Invalid date" in appropriate ways.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Jeremy, I just ran into your comments on line 16 of the new DO_Common file about throwing an exception.
So I just wanted to post here that everyone should start brainstorming a one-size-fits-all ultimate error handling/logging solution for OpenIT 2.1.
I've used the PEAR::Log package in another project and absolutely *love* it, so if you don't know where to start, check it out.
Why do I say to put this off until 2.1? Because my big plan for 2.1 is to start moving code into our newborn OO model. The changelog and notifications are perfect candidates, and error handling should be thrown in as well at some level.
The hardest part will be creating a logging system which handles critical application errors like "Cannot find DB" and small user errors like "Invalid date" in appropriate ways.