Thanks!

The first thing I do if I open the console window is removing the text:

jAlbum 29b12 system console running Groovy (Groovy Scripting Engine)
This section captures debug prints sent to System.out and System.err
The top section evaluates expressions.
Press Ctrl+E to evaluate an expression. (Evaluates selected text if selection is active)
You have access to the basic jAlbum implicit objects such as engine and window
 
Sample expressions:
4*(3+2); // Basic calculations
engine.getSkin(); // Use of implicit object
for (AlbumObject ao : selectedObjects) System.out.println(ao); // Iterate over selected objects
window.messageBox("You can interact with any Java object");

so that is easier to see what is really important.

You could do me a favour to remove this text always and explain this in the help if I click the help button!

You don't have to select anything. If you don't, jAlbum executes everything entered in the upper panel.

Yes, it's more convenient to put small scriptlets in the upper panel and have the output go in the lower panel. The output is sometimes lengthy, and if we would force users to mix input and output on the same panel, then they'd need to scroll back and forth between the input script and the generated output. It becomes pretty much like the old BASIC nightmare from the early 80's . But now you CAN actually select and execute statements from the lower panel too, as a quick convenience, so it's up to you.

The documentation already explains the use of the two panels. It needs updating now but it described how it was working perfectly well.

Exactly. 2 panels is a good thing, but it doesn't hurt that jAlbum now allows code to be selected and executed in the lower panel too. I've added a comment to the upper panel: // Code input area. This will hopefully make its use a bit more clear