That's a finished production site ... how did you debug during its development? 'Cause Formaldehyde is for development, not for production ... I guess you have implented your own error manager/debugger, right? Well, with Formaldehyde you do not need to implement anything. Moreover, ASAIK, Formaldehyde is the only one able to catch even Fatal Error ... in few words, it catches everything. I would like to know other opinions, I mean people that actually spent few minutes to understand what is Formaldehyde before they reply ... Regards > Date: Fri, 11 Sep 2009 08:38:47 -0400 > To: an_red@xxxxxxxxxxx; php-general@xxxxxxxxxxxxx > From: tedd.sperling@xxxxxxxxx > Subject: RE: [Formaldehyde] The Most Basic Ajax - PHP Error Debugger > > At 11:35 PM +0200 9/10/09, Andrea Giammarchi wrote: > >Being something nobody thought before I was expecting some comment > >... zero Ajax developers here? > > Andrea: > > No, I develop in ajax. Here's one of my demos: > > http://webbytedd.com/a/ajax-site/ > > Please note that the above site can be expanded/edited/altered > without ever touching the ajax code that makes it work. As such, I > don't need an ajax debugger because the above is an example of an > ajax site that never needs any ajax debugging. > > Please note. the above is dead in the water with javascript disabled. > But I have ways around that. > > Cheers, > > tedd > > -- > ------- > http://sperling.com http://ancientstones.com http://earthstones.com > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > _________________________________________________________________ Share your memories online with anyone you want. http://www.microsoft.com/middleeast/windows/windowslive/products/photos-share.aspx?tab=1
