Does anyone mind if I do minor refactoring in some scripts to improve the error display?
Currently, a lot of scripts do a bunch of work at the global outside the _html wunderbar section. That means that errors are just reported in ruby, not wunderbar, and it's very friendly to users. If most of the code that does stuff (mostly grabbing source data, which is usually the only thing that would fail) is instead inside the _body? section, then wunderbar traps errors and displays them in the context of the page output. That gives a much better user experience. In some scripts, it would also mean refactoring some code into a doStuff() method, so that the various data manipulation steps many scripts take can be organized as a chunk, and the user output can be cleaner. Comments? -- - Shane https://www.apache.org/foundation/marks/resources
