LogFrame: Use list for display or make use of table features

[lehnerpat]

The internal frame LogFrame used for displaying the execution log currently utilizes a table (complete with model implementations which are shared with other frames).

This is somwhat overkill, since it only displays a single column of text lines at the moment.

I suggest the frame (and with it, its layout and usage) be optimized in one of two ways:

1. use a list-style element for displaying the log. This could be simply a JTextArea set to read-only mode or a JList which also needs a Model, but a simpler one than a table.
2. make use of the table features by splitting log lines into columns (e.g. datettime - log level - origin - message)

[smetzlaff]

I really do not see necessity for changing the LogFrame: it works as expected and no performance bottleneck is visible in the current LogFrame implementation.

[lehnerpat]

Well, no, it's not necessary -- I just thought it'd be nice to have :P

[smetzlaff]

I could imagine a LogFrame in which the log output can be filtered by the user regarding e.g. the log level, the pipeline stage, or even an arbitrary matching regex pattern. I think that might be a useful extension of the logging capabilities of the simulator.