acquaman/acquaman — Issue #239: Reorganization of AMExporterAscii
Author: dretrex
Created: 2012-02-24 22:31:38+00:00
State: open
Labels: Impact  - Low, Module - Data Management, Reason - Code Cleanup, Reason - Confusing API

Now that I've started subclassing some of the exporter classes, I think a small reorganization of the classes should be undertaken (which I'm more than willing to do). I think that AMExporterGeneralAscii should be an abstract class and the current iteration of AMExporterGeneralAscii be transformed into AMExporter1DGeneralAscii (or at least something specifying 1D scans). The reason is that the general ascii exporter can't be used for my 2D map scans because the specific assumptions made(which were not wrong, just limited in scope to the current sets of scans we were using). I think this is an appropriate generalization since there is no specificity in a general ascii exporter (general text file? Can't get much more general than that), but the current implementation is limiting and non-obvious once multiple exporters become available. Having built one already and like going to build two more in the near future, I can see this being of some benefit.