Mark Guzdial wrote:
>
> I'll try to answer for the things not yet addressed earlier.
>
> >And is there any easy way to debug a #process: method? A 'self halt' seems
> >not to work. It seems that the only way to debug is to emit string on the
> >Display.
>
> In general, debugging webserver code is hard. Got any good ideas?
>
You can't beat the Squeak environment for debugging web applications.
I am currently using PWS and have modified several methods to help with debugging
during development. If an error occurs and debugging is turned off, the page that is
returned with errors has a "hidden" comment showing a full stack trace. If debugging
is turned on, you get a notifier window that you can dig into and debug. You can also
use halt messages if debugging is turned on to get a notifier and open a debugger.
As you can guess, I am not running headless servers at the moment.
I am planning to try Comanche soon and will add similar changes there if necessary.
If you are interested in this code, let me know and I'll put together a suitable
change set.
-Mark Schwenk
WellThot Inc.
See you at Camp Squeak.
