Interpreter output to sidebar rather than minor mode

[rob]

From Jesse Aldridge on the peppy-dev list:

There's still one issue though - if the error occurs in another file, the file is opened in a new tab, but the output window doesn't appear on the new tab so you have to refer back to the original file to see what the error message was. I end up having to flip back and forth quite a few times. Maybe you could copy over the output from the original tab to the new one?

[rob]

Maybe the output window should be associated with the whole frame rather than just the tab? (A sidebar vs a minor mode, in peppy parlance.) All processes in the same frame would then use the same output log. I'm guessing that's how SciTE works?

That might be confusing if you have a long-running process in one tab that's constantly updating the output log and you're trying to look at the error log that occurred from a process in another tab. They both wrote to the same output log, but now it's constantly scrolling because of the other output.

But maybe we just live with that, because frames are cheap in peppy (unlike monolithic IDEs that limit you to one top level window). If you want to run a different process, use a new frame -- chances are it's a totally unrelated program anyway.

The more I think about a single output log per frame, the more I like it. It simplifies things, for sure.

[rob]

(In [1439]) Fixed #469: added output_log classpref to JobControlMixin? to choose where output goes: minor mode or sidebar

• changed ErrorLogSidebar? to only print output to the requested frame
• added sidebar controller to wrap the JobOutputMixin? interface and send the output to the Information sidebar