PuffinPlot issue tracker

Bug: a88/b1b

ID : b1b7eeb4-ba0f-4cd3-9a18-0fca75a6bd96
Short name : a88/b1b
Status : open
Severity : minor
Assigned :
Reporter : Pontus Lurcock <pont@talvi.net>
Creator : Pontus Lurcock <pont@talvi.net>
Created : Mon, 03 Nov 2014 11:43:37 +0000
Target : 1.4
Summary : Decouple plotting from GUI

Comment: --------- Comment ---------
ID: f3e33ca5-f9c4-41f2-9c56-2ed8112229e5
Short name: a88/b1b/f3e
From: Pontus Lurcock <pont@talvi.net>
Date: Mon, 03 Nov 2014 11:54:41 +0000

Ideally all the plotting classes should be useable headless, without
having to instantiate a PuffinApp or create any windows. A couple of
plots still make reference to PuffinApp; there are some other 
dependencies on classes in the puffinplot.window package. Plots
make use of GraphDisplay, which subclasses JPanel. It's not 
immediately obvious how much work it would take to decouple plots
fully from Swing, but it's definitely worth looking into. Especially
for publication, being able to script a plot is a strong selling
point. It might be possible now in a desktop environment with a 
redundant PuffinPlot main window, but obviously headless scripting
would be greatly preferable.