I am developing a scraping tool for a complex javascript website, this is complicated because it is not easy to satisfy all variable requirements; frequently, I am getting the wrong response. However, it is not easy to spot such instances. This would be much easier if there were a feature to directly watch the response that Webharvest is processing, i.e. by saving it to a temporary file - or maybe even by showing a HTML render view of the response within the WebHarvest IDE. One easy for making this accessible, would be adding links to the log that bring up a view of the downloaded response.
Also, it would probably make sense to use additional log levels (i.e. WARNING, ERROR) and provide an option to select the corresponding log level to be shown in the window. Differentiating between different types/origins of log messages would also seem to make sense. At the moment, the log is fairly verbose and actually more a backtrace than a log.
maybe another tab could be used to show all downloaded stuff in plain text?, possibly with an option to view the source code in a dedicated window
Debugging a configuration is really complicated without having a possibility to look at what WebHarvest is actually processing.